Plagued by BSOD - Win7x64

M

muymalestado

Member
Joined
Dec 1, 2013
Posts
7
BSOD seems more frequent after MS Win7 update

Any help to get rid of BSOD appreciated

Phil




· OS - Windows 7
· x64
· Win7x64 Home Premium· OEM version (came pre-installed on system)
· Age of system: about 2 years
· Age of OS installation: about 2 years - original installation - regular automatic updates

· CPU: Intel Core 4x i3 CPU M 370 @ 2.40GHz
· Video Card: NVIDIA GeForce GT 425 M
· MotherBoard: ACPI x64 - based PC
· Power Supply: (laptop, skip this one)

· System Manufacturer: Acer
· Exact model number: Aspire 5745DG
 

Attachments

Hi,

We have various bug checks from the attached DMP's:

BAD_POOL_CALLER (c2)

This indicates that the current thread is making a bad pool request.

If we take a look at the call stack:

Code: 
STACK_TEXT:  
fffff880`08953768 fffff800`03401be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`042db124 : nt!KeBugCheckEx
fffff880`08953770 fffff880`01b6aebd : 00000000`00000490 fffffa80`07f5e8f0 fffffa80`0518f118 00000000`00000490 : nt!ExDeferredFreePool+0x1201
fffff880`08953820 fffff880`01b6a7df : fffffa80`0518f118 00000000`00000000 fffffa80`051ef76c 00000000`00000000 : [COLOR=#ff0000][I][B]rdyboost[/B][/I][/COLOR]!ST_STORE<SMD_TRAITS>::StReleaseRegion+0x59
fffff880`08953880 fffff880`01b694ce : fffffa80`0518f0b0 00000000`00000001 fffffa80`0518f0b0 00000000`00000001 : [COLOR=#ff0000][I][B]rdyboost[/B][/I][/COLOR]!ST_STORE<SMD_TRAITS>::StDmCleanup+0x183
fffff880`089538c0 fffff880`01b68a27 : fffffa80`0518f0b0 00000000`00000001 fffffa80`0518f0b0 fffff880`08953ca0 : [COLOR=#ff0000][I][B]rdyboost[/B][/I][/COLOR]!SMKM_STORE<SMD_TRAITS>::SmStCleanup+0x7a
fffff880`08953900 fffff880`01b6898a : fffff880`01b8b8f0 00000000`00000008 fffffa80`0518f0b0 fffff880`01b8b870 : [COLOR=#ff0000][I][B]rdyboost[/B][/I][/COLOR]!SMKM_STORE_MGR<SMD_TRAITS>::SmStoreMgrCallback+0x4b
fffff880`08953940 fffff880`01b8f4b8 : fffff880`01b8b870 fffff880`08953ca0 00000000`00000000 fffffa80`050abc58 : [COLOR=#ff0000][I][B]rdyboost[/B][/I][/COLOR]!SMKM_STORE_MGR<SMD_TRAITS>::SmCleanup+0x9a
fffff880`08953970 fffff880`01b70b26 : fffffa80`08fc6210 fffffa80`08fc6210 00000000`00000000 00000000`00000000 : [I][COLOR=#ff0000][B]rdyboost[/B][/COLOR][/I]!SmdRBContextShutdown+0x94
fffff880`089539b0 fffff800`035eb3a7 : 00000000`00000000 fffffa80`097a9e50 fffffa80`097a9f68 fffffa80`08fc6210 : [COLOR=#ff0000][I][B]rdyboost[/B][/I][/COLOR]!SmdDispatchDeviceControl+0x3ce
fffff880`08953a10 fffff800`035ebc06 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`08953b40 fffff800`032cde53 : fffffa80`00000000 0000007f`ffffffff 00000000`00000000 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`08953bb0 00000000`77ae132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00e1eca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ae132a

FAILURE_BUCKET_ID: X64_0xc2_7_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+59

^^ It appears rdyboost.sys was the cause of the crash.

Code: 
3: kd> !poolval fffffa8007f5e8f0
Pool page fffffa8007f5e8f0 region is Unknown

Validating Pool headers for pool page: fffffa8007f5e8f0

Pool page [ fffffa8007f5e000 ] is __inVALID.

Analyzing linked list...
[ fffffa8007f5e840 --> fffffa8007f5ea20 (size = 0x1e0 bytes)]: Corrupt region

^^ Possible hardware issues causing pool corruption.

DRIVER_CORRUPTED_EXPOOL (c5)

This indicates that the system attempted to access invalid memory at a process IRQL that was too high.

If we take a look at the call stack:

Code: 
STACK_TEXT:  
fffff880`033cac18 fffff800`032c2169 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`033cac20 fffff800`032c0de0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000011 : nt!KiBugCheckDispatch+0x69
fffff880`033cad60 fffff800`033f7b05 : fffffa80`07affb00 00000000`00000801 00000000`00000000 fffff800`033f6d0e : nt!KiPageFault+0x260
fffff880`033caef0 fffff800`033f64f1 : fffffa80`07a0ba00 fffffa80`07e52300 00000000`00000000 5254535f`000007ff : nt!ExDeferredFreePool+0x249
fffff880`033caf80 fffff880`00e1db6f : fffffa80`07e58ea0 fffffa80`07e5232e 00000000`5254535f 00000000`000000af : nt!ExFreePoolWithTag+0x411
fffff880`033cb030 fffff880`00e22f4f : fffffa80`04abf9c0 00000000`00000000 00000000`00000000 fffff880`00e2c730 : ACPI!GetObjectPath+0x167
fffff880`033cb060 fffff880`00e22e2b : fffffa80`04abf9c0 fffffa80`07e58ea0 00000000`00000000 00000000`00000000 : ACPI!AsyncEvalObject+0x77
fffff880`033cb0c0 fffff880`00e1b795 : 00000000`00000000 fffffa80`04abf9c0 00000000`00000000 00000000`00000000 : ACPI!SyncEvalObject+0x143
fffff880`033cb170 fffff880`00e0de26 : fffffa80`04abf9c0 fffff880`00e0f6e8 fffffa80`07e58e58 00000000`00000000 : ACPI!AMLIEvalNameSpaceObject+0xbd
fffff880`033cb1c0 fffff880`00e3a09d : fffff880`033cb810 00000000`5244415f fffffa80`00000000 fffffa80`04abf940 : ACPI!ACPIGet+0x2be
fffff880`033cb260 fffff880`00e38ca1 : fffffa80`07e525b0 fffff880`033cb400 fffffa80`07e2a930 00000000`000004ef : ACPI!ACPIBusAndFilterIrpQueryCapabilities+0x2d1
fffff880`033cb370 fffff880`00e01ae8 : fffffa80`05102ee3 00000000`00000009 fffffa80`07e2a930 fffffa80`05102c60 : ACPI!ACPIIrpCompletionRoutineWorker+0x69
fffff880`033cb3a0 fffff800`032c65d1 : fffff8a0`00024010 00000000`00000000 00000000`00000000 00000000`00000000 : ACPI!ACPIIrpGenericFilterCompletionHandler+0x44
fffff880`033cb3d0 fffff880`04b46d0b : fffff880`009ea180 00000000`00000000 fffff800`034526f0 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`033cb4c0 fffff880`04b37a1f : fffffa80`05102ee0 fffffa80`04eb6010 fffffa80`07e2b440 fffffa80`05102c60 : [COLOR=#ff0000][I][B]usbhub[/B][/I][/COLOR]!UsbhPdoPnp_QueryCapabilities+0x13f
fffff880`033cb4f0 fffff880`04b13fb7 : fffffa80`05102ee0 fffffa80`07e525b0 00000000`00000001 00000000`000007ff : [COLOR=#ff0000][I][B]usbhub[/B][/I][/COLOR]!UsbhPdoPnp+0x9b
fffff880`033cb520 fffff880`00e38c12 : fffffa80`00000000 fffffa80`07e2a930 fffff8a0`00003a10 00000000`000007ff : [COLOR=#ff0000][I][B]usbhub[/B][/I][/COLOR]!UsbhGenDispatch+0x57
fffff880`033cb550 fffff880`00e3c2c6 : fffff880`00e3c2a0 fffffa80`07e2a930 fffffa80`04eb6010 fffffa80`05102c60 : ACPI!ACPIIrpSetPagableCompletionRoutineAndForward+0xfe
fffff880`033cb580 fffff880`00e0ba8f : fffff880`033cb810 00000000`00000001 fffffa80`05102c60 fffffa80`05102f28 : ACPI!ACPIFilterIrpQueryCapabilities+0x26
fffff880`033cb5d0 fffff880`02caa190 : fffffa80`0416b660 fffff880`033cb6d0 fffffa80`05102f28 fffffa80`05102c60 : ACPI!ACPIDispatchIrp+0x17b
fffff880`033cb650 fffffa80`0416b660 : fffff880`033cb6d0 fffffa80`05102f28 fffffa80`05102c60 00000000`00000000 : [COLOR=#ff0000][I][B]nvstusb[/B][/I][/COLOR]+0x3190
fffff880`033cb658 fffff880`033cb6d0 : fffffa80`05102f28 fffffa80`05102c60 00000000`00000000 fffff880`02cac397 : 0xfffffa80`0416b660
fffff880`033cb660 fffffa80`05102f28 : fffffa80`05102c60 00000000`00000000 fffff880`02cac397 00000000`05060000 : 0xfffff880`033cb6d0
fffff880`033cb668 fffffa80`05102c60 : 00000000`00000000 fffff880`02cac397 00000000`05060000 fffff880`033cb688 : 0xfffffa80`05102f28
fffff880`033cb670 00000000`00000000 : fffff880`02cac397 00000000`05060000 fffff880`033cb688 fffff880`033cb688 : 0xfffffa80`05102c60

We have a nvstusb.sys call (Stereoscopic 3D USB controller driver from nVidia), and then three usbhub.sys calls.

BAD_POOL_HEADER (19)

This indicates that a pool header is corrupt.

If we take a look at the call stack:
Code: 
STACK_TEXT:  
fffff880`033bd9c8 fffff800`0340dcae : 00000000`00000019 00000000`00000020 fffffa80`08092600 fffffa80`080926a0 : nt!KeBugCheckEx
fffff880`033bd9d0 fffff880`059ae465 : fffff8a0`0cf4d7d0 fffffa80`08092610 fffff880`4d52564e fffff880`033bdc80 : nt!ExDeferredFreePool+0x12da
fffff880`033bda80 fffff8a0`0cf4d7d0 : fffffa80`08092610 fffff880`4d52564e fffff880`033bdc80 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0x198465
fffff880`033bda88 fffffa80`08092610 : fffff880`4d52564e fffff880`033bdc80 00000000`00000000 fffff880`0599d1a6 : 0xfffff8a0`0cf4d7d0
fffff880`033bda90 fffff880`4d52564e : fffff880`033bdc80 00000000`00000000 fffff880`0599d1a6 fffff800`037a8770 : 0xfffffa80`08092610
fffff880`033bda98 fffff880`033bdc80 : 00000000`00000000 fffff880`0599d1a6 fffff800`037a8770 00000000`00000000 : 0xfffff880`4d52564e
fffff880`033bdaa0 00000000`00000000 : fffff880`0599d1a6 fffff800`037a8770 00000000`00000000 fffff880`033bdbd0 : 0xfffff880`033bdc80

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+198465 )

^^ nVidia video driver.

Code: 
2: kd> !poolval fffffa8008092600
Pool page fffffa8008092600 region is Unknown

Validating Pool headers for pool page: fffffa8008092600

Pool page [ fffffa8008092000 ] is __inVALID.

Analyzing linked list...
[ fffffa8008092600 --> fffffa8008092720 (size = 0x120 bytes)]: Corrupt region

^^ Possible hardware issues causing pool corruption.

----------------------------------------------------------

1. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

3. What USB related devices do you have connected on a regular basis?

4. Let's disable ReadyBoost via services.msc ~ Warning, if after disabling and restarting you have very long boot times, re-enable it.

Start > Search bar > services.msc > scroll down until you see ReadyBoost > right click > Properties > Startup type drop-down box > Disabled > Apply > OK > Restart computer.

Regards,

Patrick
 
Thank you so much Patrick for this analysis. It is instructive to see your logic/analysis written out. I am in danger of learning something.

So: rdyboost is not a service. Finding the .sys file I re-named it appending the filename DISABLE-ME we'll see how that goes. Where it came from I could not say. rdyboost.sys appears in several Registry keyvalues, and as keynames. Can all references to rdyboost be deleted from the Registry? It would be a short job. I suspect an incomplete un-install of something.

Further: the permanent USB item is the Logitech wireless mouse dongle - the driver signed by Microsoft - driver date 20/05/2013.

Avast: Do you mean ditch Avast? Swap it for MS Essentials? Or is this just move Avast aside while doing this process?

NVIDIA: Clearing up exactly how to carry out this and preserve the laptop.

I'll be sure to respond when all processes are done.

Phil
 
So: rdyboost is not a service. Finding the .sys file I re-named it appending the filename DISABLE-ME we'll see how that goes. Where it came from I could not say. rdyboost.sys appears in several Registry keyvalues, and as keynames. Can all references to rdyboost be deleted from the Registry? It would be a short job. I suspect an incomplete un-install of something.
Click to expand...

Hm, it's risky... I'd leave it alone for now and we'll come back to it if it appears to be the ultimate culprit.

Further: the permanent USB item is the Logitech wireless mouse dongle - the driver signed by Microsoft - driver date 20/05/2013.
Click to expand...

Is that the only USB device you use on a day-to-day basis? Nothing else?

Avast: Do you mean ditch Avast? Swap it for MS Essentials? Or is this just move Avast aside while doing this process?
Click to expand...

For now, remove it and replace it as I instructed. It's a potential problem and getting it out of the way for now will help a lot and possibly stop the crashes if it's the issue.

NVIDIA: Clearing up exactly how to carry out this and preserve the laptop.
Click to expand...

Apologies, I meant to tell you to ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

Regards,

Patrick
 
Further: the permanent USB item is the Logitech wireless mouse dongle - the driver signed by Microsoft - driver date 20/05/2013.
Click to expand...

Is that the only USB device you use on a day-to-day basis? Nothing else?


NVIDIA: Clearing up exactly how to carry out this and preserve the laptop.
Click to expand...

Apologies, I meant to tell you to ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.
Click to expand...

No apologies required, of course, I have the updated new NVIDIA driver (2 years newer). I have instructions to replace it by uninstalling the old one piece by piece (five files / five uninstalls in total), then reboot and use VGA to see to install the new one. But, one old driver file is THE ONE which displays the screen and should be the last to be uninstalled, and of course my old driver file set does not indicate which file that is so I am trying to find out. I suppose if I uninstall in the wrong order I shall just have to drop into VGA to complete any last uninstall prior to doing the install on the new driver.

As to the USB device - yes, the Logitech USB wireless mouse is in use all the time. Other uses of the USB are rare, eg., transferring photos and are not knowingly related to BSOD BAD_POOL_CALLER.

Phil
 
Understood Phil, thanks for the update. Let me know when the nVidia installation in regards to the driver is all taken care of, or if you have any issues.

Regards,

Patrick
 
OK. Help required please.

It seems NVIDIA driver files are the cause of the BAD_POOL_CALLER crashing.

The new NVIDIA driver file set has been downloaded to the Desktop & unzipped ready for their own setup.exe to do its stuff.

Uninstalling two of the five existing NVIDIA driver file set was OK. They are gone.

Upon uninstallation of each of the three remaining driver files caused a BAD_POOL_CALLER error crash and they cannot be uninstalled.

After the crashes the method of restoring the laptop to working is to boot into safe mode, then reboot into normal mode. Leaving three NVIDIA driver files unable to be uninstalled.

Can I just find all the NVIDIA files on the HDD and delete them? Then reboot to get a VGA screen. Then use the new driver setup.exe to install a clean install of new NVIDIA files?

That would leave the old Registry entries sitting there. Would the new driver install wipe out the old Registry entries?

I do not see any other way to proceed.

Thanks.

Phil
 
I tried driver sweeper. I selected NVIDIA. It ran. What it did I am not sure. After running several of the listed files were not ticked - meaning, what?

I cannot get Perfmon.html to be attached. Is there another way to pass that file to you?

Thanks.

Phil
 

Attachments

I don't fully understand the analysis and logging software so it is only luck when a well formed log file emerges.

However; uninstalling has caused endless BAD_POOL_CALLER errors and fails to remove most of the driver file set, so using Driver Sweeper was the answer to that. All that is left of the NVIDIA drivers are a few small entries in The Registry.

My problem now, I believe, is to identify the correct graphics card driver and the correct procedure to install that. Acer refers to the NVIDIA list of drivers - NVIDIA refers to the Acer list of drivers. I am waiting for one of these two to blink and tell me which to install, and how to do that correctly.

Thanks for help to date.

Phil
 
I would personally, use the Acer drivers first, since some OEMs make the driver specify to your model. Does it run fine in Safe Mode?
 
Thanks all for the responses to my query. I feel I have arrived at the end of it, but time will tell if the BSOD returns. Here is what I did.

After Driver Sweeper I hand deleted several remaining NVIDIA files. Then I trawled the Registry and deleted virtually all keys and values referring to NVIDIA - a few values would not be changed/deleted.

In Safe Mode I found a recent - not the latest - NVIDIA driver on the NVIDIA site and installed that. Prior to the Registry clean-out it would not install. This driver seemed OK in Safe Mode. It seems OK in Normal Mode. NVIDIA offers updates to a newer version which I refuse until a month or so passes to ensure what is there is OK. As I do not do games I suspect updates would not offer anything to me.

The laptop now works like new, or, like it should have all along.

Thank you for guidance in working this out.
 
Welcome, hopefully your system remains stable for the next couple of weeks. Please update us when you can.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top