Random BSOD throughout the day (irql_not_less_or_equal)

Rebitaay · 03 Sep 2016

Hello,

I recently started getting the same BSOD very frequently.

DRIVER_IRQL_NOT_LESS_OR_EQUAL
What failed: bwcW10x64.sys

It started happening about once a day after my computer had been running for a while, and now it's happening up to 4 times a day. Just today I bluescreened three times in a row just trying to log into Windows.

At first, I suspected it was my new ram I got some weeks ago causing the issue based on what I had seen posted in other threads. I ran 8 passes of MemTest86 overnight and the only issue was "Ram may be vulnerable to high frequency row memory bit flip". So I swapped out for my old RAM, but it's still happening.

I'm at a complete loss here and I need some help. I've updated my graphics drivers, and my motherboard's drivers. I've attached everything that should be needed for analysis. Please note that any dump files from September 3rd and onward are with different RAM.

Any help would be appreciated.

Ztruker · 04 Sep 2016

Problem caused by bwcW10x64.sys.

Code:

BugCheck D1, {ffffde872ada4006, 2, 0, fffff8032ef7ffde}
*** WARNING: Unable to verify timestamp for bwcW10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for bwcW10x64.sys
Probably caused by : bwcW10x64.sys ( bwcW10x64+ffde )

bwcW10x64.sys belongs to Killer Bandwidth Control Filter Driver.

Dump also indicates a problem with e22w10x64.sys:

Code:

ffffb900`9383c608  fffff803`304690b3Unable to load image \SystemRoot\System32\drivers\e22w10x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e22w10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w10x64.sys
 e22w10x64+0x90b3

which belongs to Killer e2200 PCI-E Gigabit Ethernet Controller.

The driver for your Killer card is dated 1/22/2016. There is a newer one dated 15 August 2016 on the Killer web site:
Killer Networking - Driver Downloads

Give that a try, see if it helps.

Rebitaay · 05 Sep 2016

Thanks, I'll report back in a few days if all is well, or if it keeps happening.

Edit: It seems to have worked. Thanks!

Ztruker · 06 Sep 2016

That's good to hear.