Recent content by Puluke

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 >...

Yes, you said to uninstall Turbo Boos, but you'll note that you pointed to TurboB.sys every previous time, not Impcd.sys. I DID un-install TurboB.sys when you asked me to do so, and I did make every possible change in BIOS to turn off Turbo Boost functionality. I have now un-installed Impcd.sys...

With all due respect, you didn't ask me a million times to uninstall impcd.sys; you asked me to uninstall TurboB.sys, which I did. I will uninstall SpeedFan, although the CPU stress test (Prime95) which you recommended, highly recommended installing SpeedFan to monitor temps during stress test...

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...

Despite updates to current levels of all drivers, BSODs continue ... :( One recent behavioral change in my laptop is that the system hasn't come out of Standby mode the last few times I've tried, requiring forced power-off. I believe that the crash dumps include some of these abnormal Windows...

OK, I have un-installed TurboB.sys, and installed and confirmed latest versions of Intel and Lenovo drivers; latest copy of DriverView output attached. We'll see ...

OK, I have removed the last traces of ESET (eamonm.sys). This really seems like a high-odds candidate for BSOD root cause, since it may very likely have been interfering with the latest updates to MSE anti-virus processing in some unpredictable way. Thanks for noticing it! I did a bit more...

That's very strange, since I uninstalled ESET last September and installed MSE, at the suggestion of one of the great folks on this forum. Apparently the ESET uninstall didn't successfully remove everything. It would be nice to think that this may be the "smoking gun" which will resolve my...

As previously noted, I changed BIOS and Power Management settings to limit Max CPU performance Turbo Boost which may have been causing thermal issues when Core i5 540 was using its standard operation turbo boost functionality. Two days of relatively stable operation, followed by another BSOD...

OK, I updated the BIOS Power --> Adaptive Thermal Management --> Scheme for AC setting from "Maximize Performance" (which "Reduces CPU throttling") to "Balanced", and also updated the ThinkPad Power Manager --> System Settings --> AC: Maximum CPU Speed from "Highest" to "Low". "Adaptive" may be...

I've done nothing (explicitly) to "over-clock" my processor. Maybe there's some power management or related setting that should be adjusted downwards??

All drivers updated to latest versions, memory and HDD tests run for many hours with no errors. However, 4 more BSODs since last report, three of them just this afternoon. Wondering whether starting over with new HDD with new Windows 7 install would help, or whether root cause may be...

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. Uploading SF Diagnostics info again... Thanks.Link Removed due to 404 Error

OK, I ran CHKSDK /F and HDDScan for a couple of hours, with no errors, and all parameters well within valid ranges. I have noticed that the dirty bit does get set frequently (FSUTIL Dirty query c:) for some unknown reason, requiring CHKDSK /F or /R operations, but rarely shows any corrupted...

I let the Memtest86 test run all night. After 16h18m "wall time" it completed 20 passes with 0 errors. I think I was hoping for at least some intermittent memory errors after this extensive memory testing, so at least we'd know that a hardware component was the root cause. We'll see how long...