BSOD occuring daily "DRIVER_IRQL_NOT_LESS_OR_EQUAL"

wehtam1062 · 25 Jun 2015

Hello
So about a week ago I started receiving the BSOD fairly frequently, about once or twice a day on average. I'm fairly concerned at this point because I do not have any system restore points that date back before the BSOD began occuring. The error I receive when my system crashes consistently says DRIVER_IRQL_NOT_LESS_OR_EQUAL. Additionally, I recently downloaded BlueScreenView to view the minidump files and it appears that ntoskrnl.exe and tcpip.sys are always involved in the problem. Any help is much appreciated! Also as a side note, in the attachment, I believe the three most recent BSODs are the most relevant. Those three are a good sample of the types of BSOD I've been receiving consistently.

Additionally, I'm not sure if this is relevant, but my laptop has been running very hot recently. When I noticed this I downloaded SpeedFan and realized that my CPU temps have been running at upwards of 90C (only when gaming), which I know is a serious problem. The computer that I'm using is a HP Pavilion, which is notorious for overheating issues, and I've never actually taken the time to clean the fans (aside from blowing compressed air into the vents, which I've heard may actually be bad for the computer). I'm hoping that the BSOD is not related to a hardware failure, especially since the error leads me to believe that it is more related to driver issues???

Arc · 26 Jun 2015

It is avast that is causing the BSODs.

Code:

BugCheck D1, {0, 2, 0, fffff8800509456b}

*** WARNING: Unable to verify timestamp for aswStm.sys
*** ERROR: Module load completed but symbols could not be loaded for aswStm.sys
Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferList+86 )

Followup: MachineOwner
---------

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Report us for any further BSOD after doing it.

wehtam1062 · 26 Jun 2015

So far so good!

This seems to have fixed the problem. Thanks a bunch!

Arc · 26 Jun 2015

Welcome. :) Let us know for any further BSOD.