DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD then failing to reboot.

Treloarm · 13 Sep 2014

Hi Guys,

So for the last day I have been having fairly regular BSODs. The screen will fuzz for a split second then BSOD. Afterwards the computer will reboot itself a couple of times before actually getting through to BIOS and then booting. They tend to occur whilst gaming but also have happened just while browsing the web.

I would be really grateful for any advice you guys could give me, I am really reluctant to get a new PC! The Debug zip is attached.

Many thanks in advance,

Mike

Golden · 14 Sep 2014

The most recent BSOD is from July and identifies the Broadcom Adapter driver as significantly outdated.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {6, fffffa800acf5a20, 43787254, 0}

*** WARNING: Unable to verify timestamp for bcmwlhigh664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwlhigh664.sys
Probably caused by : bcmwlhigh664.sys ( bcmwlhigh664+a154 )

Followup: MachineOwner
---------
start             end                 module name
fffff880`03a17000 fffff880`03b4e000   bcmwlhigh664 T (no symbols)           
    Loaded symbol image file: bcmwlhigh664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwlhigh664.sys
    Image name: bcmwlhigh664.sys
    Timestamp:        Tue Apr 19 16:43:08 2011 (4DAD3604)
    CheckSum:         00137E7A
    ImageSize:        00137000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it by following this link:
NETGEAR Support | Welcome

Treloarm · 15 Sep 2014

Hi Golden,

Thanks very much for your time and helping me solve this.

Is there any reason why a BSOD would not be recorded in such a manner that the DM log collector could not detect it? The BSOD screen tells me a physical memory dump is completed.

I had about 5 BSODs on Saturday, and each time the pc would fail to boot once afterwards.