BSOD - ntoskrnl.exe - BAD_POOL_CALLER

[Takedown]

I've been getting increasing BSODs on my Y560. It happens randomly, but when I backup the system image is always BSODs at 45%. I used BlueScreenView and received the following:

==================================================
Dump File : 050113-37362-01.dmp
Crash Time : 5/1/2013 4:06:47 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`040d000d
Parameter 4 : fffffa80`082210e0
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+318c8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\050113-37362-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 279,312
==================================================

==================================================
Dump File : 050113-25958-01.dmp
Crash Time : 5/1/2013 2:35:07 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : fffff880`079c9ff8
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`0360b123
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75c00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\050113-25958-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 280,144
==================================================

I'm thinking it might be a bad sector on my HD or something. I'm less educated on this topic than most others.

I can only show my two most recent BSODs because I accidently ran CCleaner and forgot to uncheck the dump file check-box.

The dump files are in my dropbox: https://dl.dropboxusercontent.com/u/54762176/Dump/Dump.zip

 

[Dsprague]

It appears that your wireless driver is causing the problem:

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

Use !analyze -v to get detailed debugging information.

BugCheck C5, {fffff880079c9ff8, 2, 0, fffff8000360b123}

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

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

Driver Reference Table - NETw5s64.sys

Please update the driver from here: https://downloadcenter.intel.com/Default.aspx

 

[Takedown]

Ok. Thank you. But why would that cause a BSOD when I am backing up the system? I'm going to try backing up again and will get back to you after if finishes.

 

[Takedown]

Ok, I updated the driver and wireless software. After that, I proceeded with the full image backup and did not get a bluescreen! Thank you, you've saved me a whole lot of time.

 

[Dsprague]

Glad to hear that everything worked out.

 

[Takedown]

It's been 10 days now, and I just got another bluescreen. It seems like the same origin as the last ones I have been having. Any time I try to check the dump file myself I get a bunch of errors regarding the "Symbol search path" or something. Anyway, the latest dump file I put in my dropbox:

https://dl.dropboxusercontent.com/u/54762176/Dump/051313-30201-01.zip

I hope the problem can get resolved, as I did update my wireless driver and it I wan't expecting to get a bluescreen again.

Thank you again,

Adam

 

[Dsprague]

It looks like this BSOD was caused by a number of factors, first start by updating the following drivers:

fffff800`00b9c650  fffff880`012700ecUnable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys

Driver Reference Table - iaStor.sys

Please update the driver from here: https://downloadcenter.intel.com/Default.aspx

fffff800`00b9c660  fffff880`05848ca0Unable to load image \SystemRoot\system32\DRIVERS\k57nd60a.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for k57nd60a.sys
*** ERROR: Module load completed but symbols could not be loaded for k57nd60a.sys
 k57nd60a+0x48ca0

Driver Reference Table - k57nd60a.sys

Please update the driver from here: Ethernet NIC Driver Downloads | Broadcom

fffff800`00b9c680  fffff880`0201d0d8Unable to load image \SystemRoot\system32\drivers\btwavdt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for btwavdt.sys
*** ERROR: Module load completed but symbols could not be loaded for btwavdt.sys
 btwavdt+0xd0d8

Driver Reference Table - btwavdt.sys

PLease update the driver from here: Bluetooth Software Download | Broadcom

fffff800`00b9c698  fffff880`02094e9cUnable to load image \SystemRoot\system32\drivers\btwaudio.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for btwaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for btwaudio.sys
 btwaudio+0x9e9c

Driver Reference Table - btwaudio.sys

The download link is the same as the one above, they come bundled as a package of drivers.

once those drivers are up to date see this tutorial to deal with the problems being caused by USB ports, from the looks of things:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800b7f8060, fffff80000b9c518, fffffa800ecb7010}

[COLOR="Red"]Probably caused by : usbhub.sys[/COLOR]

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

http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html

 

[Takedown]

Ok, thank you for your help. I'll tell you if anything goes wrong again. Why can't I see what you see in the minidump? I just get a bunch of garbled errors (I'm using WinDbg).

 

[Dsprague]

Unlike programs like Who crashed and Bluescreen viewer WinDbg needs to be configured, and to find the information you need to help troubleshoot you actually need to know what your doing, its not just going to flat out tell you what is wrong (although sometimes it does). Here are some helpful links to get you started:

http://www.sevenforums.com/crash-lockup-debug-how/26584-configuring-debugging-tools.html

http://www.sevenforums.com/crash-lockup-debug-how/277355-debugging-bsod-my-way.html

http://www.sevenforums.com/crash-lockup-debug-how/206858-bsod-tutorials-information-links.html

http://www.sevenforums.com/tutorials/260163-bsod-commands-windbg.html