WD10EARS : I keep getting win7 error messages that they cannot access the HDD after sleep events


I have tried both 32 and 64bit versions of win7 professional: in both fresh installations  after some sleep/wake cycles I get a blue screen + reboot and afterwards I am informed that windows cannot access the drive. My mobo is an ASUS P5Q and win7 installations/drivers are all latest versions. The machine was working fine with the previous seagate 7200.11 drive I had in it.

Is there something to check? this is getting annoying…

I would recommend checking related system logs first.

Run eventvwr.exe > Windows Logs > System

OK, there are some errors there:

1st a critical one:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


  BugcheckCode 122 
  BugcheckParameter1 0xfffff6fb80008000 
  BugcheckParameter2 0xffffffffc000000e 
  BugcheckParameter3 0x2ebaf880 
  BugcheckParameter4 0xfffff70001000000 
  SleepInProgress true 
  PowerButtonTimestamp 0

then there are a couple of errors:

 The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007a (0xfffff6fb80008000, 0xffffffffc000000e, 0x000000002ebaf880, 0xfffff70001000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082210-16380-01. 


  param1 0x0000007a (0xfffff6fb80008000, 0xffffffffc000000e, 0x000000002ebaf880, 0xfffff70001000000) 
  param2 C:\Windows\MEMORY.DMP 
  param3 082210-16380-01

and the final error:

The previous system shutdown at 1:47:59 πμ on ‎22/‎8/‎2010 was unexpected. 


   1:47:59 πμ 


Binary data:

In Words

0000: 000807DA 00160000 002F0001 0215003B 
0008: 000807DA 00150006 002F0016 0215003B 
0010: 00000960 0000003C 00000001 00000960 
0018: 00000000 000004B0 00000001 00001BC1 

In Bytes

0000: DA 07 08 00 00 00 16 00 Ú.......
0008: 01 00 2F 00 3B 00 15 02 ../.;...
0010: DA 07 08 00 06 00 15 00 Ú.......
0018: 16 00 2F 00 3B 00 15 02 ../.;...
0020: 60 09 00 00 3C 00 00 00 `...<...
0028: 01 00 00 00 60 09 00 00 ....`...
0030: 00 00 00 00 B0 04 00 00 ....°...
0038: 01 00 00 00 C1 1B 00 00 ....Á...

after the crashes  I get the resolution center with a message that the HDD could not be accessed and to  check the cables etc… (cables are fine btw as the problem is waking up the HDD…)

crash AGAIN!!!

this time I turned on my pc and went away for ~40mins… it was sleeping (fresh win7pro x64 install, default power saving settings) when I returned SURPRISE!!! the hdd could not be accesses AGAIN after resume , blue screen , reboot  same old story… also BIOS takes it’s sweet time to recognise the HDD after it fails to wake (forgot to mention that before…)

I re-checked the cables and this time replaced it just tor fun because Seagate 7200 drives were OK with it…

I’ve escalated this thread to see if engineering is aware of this issue.

I too now have this problem occuring

Excatly as topic starter.

it started on the 22 of august

Is there a work aound ?

I am using AHCI, if that matters…

AHCI here too, and 5 mins ago after a sleep session of ~6 hrs I got a bsod on resume, with a “KERNEL_DATA_IN_PAGE_SESSION” description… this is beginning to be extremely annoying!

here are the memory.dmp and minidump: http://www.megaupload.com/?d=23XYN7JR  


are there any updates on the matter or are we just screwed here?

I haven’t heard anything yet.

Would it be worth trying the setting in Bios for HDD Delay, normally set to 0, might be worth trying some other figures. I personally use 3 cause I am using raid, and if all 6 drives are sleeping it can take a while to wake them one at a time.

yet another BSOD after wake event… bah

I am gonna try the BIOS delay thingie, but frankly this does not feel right.

I am giving the matter another week, then reverting to some otther HDD and use this one to offline store backups.

edit: there is no hdd delay option in ASUS P5Q motherboard…  so I cannot really try that

anyone plagued by this problem, try the ms hotfix that was recommended to me in this thread:  http://amibay.com/showthread.php?t=9065

after 3 days and sleep/wake cycles my pc seems to working fine , give the hotfix a shot! :wink: