BSOD Windows 7 64-bit - 3 BSODs after six months stable operation

#41
TurboB.sys and Impcd.sys are both related to Intel Turbo Boost. You were supposed to uninstall it the usual way via Control Panel > Programs and features (Add/Remove).


Ok, time to round up,

My Windows 7 Lenovo ThinkPad X201 X-64 system experienced 3 BSOD crashes today, after 6 months with no issues. All three bugcheck codes seem to be for different errors.

I have attached SF Diag output, CPU-Z screenshots, and RAMMon screenshots.

Thanks in advance for any help.

Bruce

View attachment 12040 View attachment 12041 View attachment 12042 View attachment 12043 View attachment 12044 View attachment 12045


Errors:

Code:
[b]0xA_nt!MiAgeWorking_Set_[COLOR="#8b0000"]memory_corruption[/COLOR]
0x24_Ntfs!NtfsOpenAttribute
0xc2_7_MPsc_fileinfo!FIStreamLogForNL 

031511-30856-01.dmp
BugCheck 19, {3, fffff8a004564660, fffff8a004564620, fffff8a004564660}
PROCESS_NAME: AcDeskBandHlpr <-- Access Connections Deskband Helper Module 
Stack: nt
Probably caused by : [COLOR="#8b0000"]Pool_Corruption[/COLOR] ( nt!ExDeferredFreePool+c7b )

032911-22900-01.dmp
BugCheck 24, {1904fb, fffff8800b865a88, fffff8800b8652e0, fffff880016e1c73}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFcbTableCompare+3 )

032911-23478-01.dmp
BugCheck 1A, {411, fffff6fcc008ae00, 558000001ea7a900, fffff8a0042f8011}
[COLOR="#8b0000"]MEMORY_MANAGEMENT (1a)[/COLOR]
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )

032911-24788-01.dmp
BugCheck 1A, {3452, 6a818000, fffff700010833f0, ded0000069df9000}
[COLOR="#8b0000"]MEMORY_MANAGEMENT (1a)[/COLOR]
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36103 )

033011-21231-01.dmp
BugCheck 7F, {8, 80050031, 6f8, fffff80002ed6610}
UNEXPECTED_KERNEL_MODE_TRAP (7f)
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )[/b]

OK, I ran CHKSDK /F and HDDScan for a couple of hours, with no errors, and all parameters well within valid ranges.

I ran HDDScan for several hours on Saturday; it showed no errors or out of range conditions. 3 or 4 stable days before another BSOD this afternoon; Bad Pool Header.

OVERCLOCKING ---> Core i5 M540 @2,53, and yours is 2,93Ghz at the moment.


SET ALL CLOCKS, VOLTAGES, TIMINGS, MULTIPLIERS EXACTLY AS RECOMMENDED BY THE MANUFACTURER.





Check your CPU-Z CPU tab to see how you're doing. The frequency is definitely supposed to go down at idle. For now, it must not exceed the stock value of 2,53.




Ran DriverUpdate, and applied all latest Intel and Lenovo drivers around 2pm yesterday (3/29). Stable until about 30 minutes ago, when another BSOD happened, with laptop basically "idling" with almost nothing going on and no user interaction at all.

Still putting off the "new HDD and start over again" route, but hoping for an "aha" moment and breakthrough soon.:(


BSOD's are caused by either HARDWARE or SOFTWARE. Finally you have updated all the drivers and uninstalled Intel Turbo Boost utilities, as you report. You also report that the hardware tests have detected no errors. Up to you to figure out what causes your blue screens. I would much recommend to set your hardware at its stock values as recommended by the manufacturer. Unplug all peripheral devices except mouse and keyboard. Uninstall INTELL TURBO BOOST utilities. If you haven't, run 10 passes of memtest.


Good luck.
 


#42
I certainly appreciate your help, and didn't intend to sound annoyed. I just wanted to clarify that while I have now uninstalled all remnants of Intel Turbo Boost Technology (TurboB.sys and Impcd.sys), it was not possible to uninstall the Impcd.sys Driver via the "usual way via Control Panel > Programs and features (Add/Remove)" as it wasn't included in the list of programs/features. I had to uninstall it via Device Manager.

All hardware is set at stock values, and I have no peripherals attached. I did run 16 passes of Memtest86 a week or two ago, and will do so again this weekend.

Thanks again for your help.


View attachment 2011-03-31 1318 Seven Forums.zip View attachment 2011-03-31 1320 DriverView output.pdf
 


#43
You may want to upgrade your bios to the latest version. Then if still no luck, put your RAM stick to another slot. Try another memory stick too.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top