When resuming from Sleep mode, BSOD and restart occurs

Hey there,

I recently upgraded my notebook hard drive from a Western Digital WD2500BEVT 250GB to a SAMSUNG Spinpoint M7E HM641JI 640GB hard drive (and "cloned" from the old to the new). The only problem since the switch is when I resume from sleep mode. My laptop goes into sleep mode fine, but upon resuming, it correctly shows the log-in screen (there is a password on my account) for a few seconds, then proceeds to flash a BSOD for a split-second before restarting and showing the error recovery, unexpected shutdown screen. I have looked in my minidump file folder, but no recent dumps show up, so I am not attaching the file. The event logger shows many errors, including Kernal-Power event ID 41.

I have tried playing with the sleep settings (hybrid sleep, etc.) in the Advanced Power Settings with no luck. Drivers are all up-to-date. I assume it is a problem with the new Samsung hard drive. With my old drive, the moment I woke the computer from sleep, I would be able to log-in and resume where I left off almost instantly.

I attached the Event Viewer log in a .zip file.

Windows 7 Ultimate x64 Retail
Hardware approx. 2 years old (Samsung HDD is new)
Last OS installation approx. 6-8 months ago (Old HDD was "cloned" to the new 640GB HDD)
System Health Report passed with no errors

Gateway T-6836 Laptop
Intel GM965 chipset
Intel Core 2 Duo T5750 @ 2.00 GHz
4GB Memory
Intel Graphics Media Accelerator X3100

Thanks,
Shane

Thanks for the reply, ttran,

I did what you said there, but still no new dump files were created after I made my computer BSOD. However, I was able to read the BSOD now:

***STOP 0x000000F4 (0x0000000000000003, 0xFFFFFA80074E6B30, 0xFFFFFA80074E6E10, 0xFFFFF80002F8E540)

From what I've read, Error #3 has to do with the hard drive. I'm guessing that something isn't quite "right" because I cloned my old hard drive to a different brand and size of hard drive, so there may be some compatibility issue.

Tuan,

I installed that hotfix (unzipped to C:\ is that correct?) because it sounded like that might fix the problem, but it did not fix the problem. The same error # showed on the BSOD (F4), but with different error codes in the parenthesis (are these different each time?).

Shane