Total Members Voted: 1
0 Members and 1 Guest are viewing this topic.
You can add me to the listAnd the last update said "full windows 8 compatibility"Log files, a crash report and my system information are in my dropbox athttps://www.dropbox.com/sh/v3z6p88rsfpjk8x/001NpL7mgw/AVASTThanks
Not sure if it has to do with Avast but from yesterday, the web browsing is not as smooth as before. I turned off Avast and its smoother.
Quote from: clickman on November 04, 2012, 10:59:45 PMPatch installed and tested.... Crashed!Lukor, I have sent you the additional logging file as well as uploaded a new dump on the incoming.Hope this will help.Hi clickman, from the dump it seems you haven't updated to the patched driver correctly. It still shows the old one, build 29 Oct.Lukas.
Patch installed and tested.... Crashed!Lukor, I have sent you the additional logging file as well as uploaded a new dump on the incoming.Hope this will help.
Quote from: Chris Thomas on November 05, 2012, 05:00:58 PMNot sure if it has to do with Avast but from yesterday, the web browsing is not as smooth as before. I turned off Avast and its smoother.Win8 + avast Free ?
how is it looking? I had removed avast for now. I have an SSD cache setup and needless to say blue screens are scary.
Crash dump directory: D:\Windows\MinidumpCrash dumps are enabled on your computer.On Tue 11/6/2012 12:14:57 AM GMT your computer crashedcrash dump file: D:\Windows\Minidump\110512-47720-01.dmpThis was probably caused by the following module: aswnet.sys (0xFFFFF880069BB3AA) Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFF880069BB3AA)Error: DRIVER_IRQL_NOT_LESS_OR_EQUALfile path: D:\Windows\system32\drivers\aswnet.sysproduct: Avast Firewallcompany: AVAST Softwaredescription: AVAST Firewall Core DriverBug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswnet.sys (AVAST Firewall Core Driver, AVAST Software). Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL
windows version: Windows 8 , 6.2, build: 9200windows dir: D:\WindowsCPU: AuthenticAMD AMD FX(tm)-8150 Eight-Core Processor AMD586, level: 218 logical processors, active mask: 255RAM: 17114173440 total
Crashed again QuoteCrash dump directory: D:\Windows\MinidumpCrash dumps are enabled on your computer.On Tue 11/6/2012 12:14:57 AM GMT your computer crashedcrash dump file: D:\Windows\Minidump\110512-47720-01.dmpThis was probably caused by the following module: aswnet.sys (0xFFFFF880069BB3AA) Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFF880069BB3AA)Error: DRIVER_IRQL_NOT_LESS_OR_EQUALfile path: D:\Windows\system32\drivers\aswnet.sysproduct: Avast Firewallcompany: AVAST Softwaredescription: AVAST Firewall Core DriverBug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswnet.sys (AVAST Firewall Core Driver, AVAST Software). Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUALComputer informationQuotewindows version: Windows 8 , 6.2, build: 9200windows dir: D:\WindowsCPU: AuthenticAMD AMD FX(tm)-8150 Eight-Core Processor AMD586, level: 218 logical processors, active mask: 255RAM: 17114173440 totalFull memory.dump is being uploaded to ftp:\\ftp.avast.com\incoming
Quote from: koman90 on November 05, 2012, 02:48:56 PMYou can add me to the listAnd the last update said "full windows 8 compatibility"Log files, a crash report and my system information are in my dropbox athttps://www.dropbox.com/sh/v3z6p88rsfpjk8x/001NpL7mgw/AVASTThanksCould have swore i added it already, oh well. I'll have an answer within 24-hours. It usually happens coming out of sleep or when i have my Hyper-V VMs up. Hyper-V wouldn't be causing any issues would it?Hi, you are right, the same as clickman - you are running the original version of the driver 29 Oct 2012, where the crash hasn't been fixed. Could you please try the updated driver if it helps? Thanks. Lukas.