Ntoskrnl.exe BSOD error

BringTheRuck

Reputable
Jan 1, 2015
5
0
4,510
Hello everyone I have been encountering a BSOD that seems to be associated with the ntoskrnl.exe file. Also, I never have this issue unless my computer is asleep for a long period of time. I come back and it needs to recover from an "unexpected shutdown."

Here is the dump file located on my business server: http://www.pinnatec.com/dump/

Thanks for the help in advance!
 
Solution
looks like the system told the device bcmwl664.sys Thu Aug 22 01:20:36 2013 to power down to save power,
the device had pending requests and did not handle them correctly.

I would look to find a update for this device driver or locate the device in windows device manager and tell windows not to put it to sleep.
------------

also note: the device driver data could have been corrupted by any number of the various 3rd party drivers you have on your system.
(I would be looking at razer overlay software as a potential corruption point)

i would also remove AsInsHelp64.sys Thu Jan 03 21:36:10 2008
Asus Ai Booster software from 2008 is just not a good idea

note: if you change your memory dump type from minidump to full or kernel memory...
looks like the system told the device bcmwl664.sys Thu Aug 22 01:20:36 2013 to power down to save power,
the device had pending requests and did not handle them correctly.

I would look to find a update for this device driver or locate the device in windows device manager and tell windows not to put it to sleep.
------------

also note: the device driver data could have been corrupted by any number of the various 3rd party drivers you have on your system.
(I would be looking at razer overlay software as a potential corruption point)

i would also remove AsInsHelp64.sys Thu Jan 03 21:36:10 2008
Asus Ai Booster software from 2008 is just not a good idea

note: if you change your memory dump type from minidump to full or kernel memory dump. The memory dump will save the internal logs that will show certain errors made by the razer drivers.

note:
internal error was:
A Client Driver is holding the Power IRP(\Driver\BCM43XX)






 
Solution