BSOD on Win7
I regret to inform you that RealTemp 3.36
may be causing BSOD's on my system now, after doing an in-place upgrade from Vista x64 to Win7 x64.
Here's a summary of my issue:
- RealTemp is run on logon through Task Scheduler. As per the instructions posted either here or on Xtremesystems, a Task is set up in Task Scheduler to run the app with "highest privileges".
- After one logs in to Win7 (using an administrative account, etc.), does his usual stuff, blahblahblah, he suspends the computer through the Start Menu. The suspension goes through just fine.
- Whether it's 30 seconds later or 30 minutes later the computer is Resumed - either by moving mouse, pressing spacebar or hitting the power button, and the computer resumes normally.
- At the Win7 "enter your password" screen, either WAIT 20 seconds, or quickly log in and wait 20 seconds.
- STOP 0x000000f4 (0x0000000000000003, 0xfffffa8008b0ab30, 0xfffffa8008b0ae10, 0xfffff80002fd3240)!
- I spent some time debugging the minidump file in WinDbg but could not get it to point to the actual driver causing the issue.
- If I stop/close/kill RealTemp before the suspend/resume - the suspend/resume will work fine.
If I leave RealTemp running at time of suspend (actually Sleep) then I will always get a BSOD about 15-20 seconds after Resuming.
Any ideas?
NOTE: Before determining it was RealTemp causing the issue, I had looked at other devices on my system and tried disabling/removing them before going into Sleep. Like my USB WLAN NIC, etc. They had no effect.
Please don't say it's because I did an in-place upgrade.
This is the only thing that's not working.
EDIT: Problem Solved. BSOD was due to Microsoft's crappy default AHCI driver which apparently doesn't play nice with Intel ICH10R south bridge in AHCI mode. After installing Intel Matrix Storage Manager drivers, the problem went away. RealTemp was not the cause, although it's interesting that the problem only showed itself while RealTemp was running.