Hi,
I have a rather infuriating BSOD on wake from S3.
I have a GA-EX58-UD5 motherboard with my system drive 2x500GB Seagests in RAID 0 connected via the ICH10R raid controller.
I'm running Windows 7 SP1 64bit.
I suspect that the HDDs are not restarting when coming out of S3. When I resume from S3 my computer will get to the login screen, I can actually log in, and then my computer decides to die. I'll sometimes get an error that says something along the lines of "The requested data was not placed into memory because of an I/O status of 0xc000000e"
Then I get a BSOD with a F4 error and no minidum is created.
I suspect the HDDs not starting up are the culprit because when if I have resource manager running after return from S3 the IO is 0MB/s, and the minidump fails to write to disk.
In my power options I have HDD sleep set to never.
For "fun" I'm now cloning my RAID to a single disk connected directly (not via the ICH10R) to see if the problem persists.
Does anybody have any suggestions? Thanks in advance.
I have a rather infuriating BSOD on wake from S3.
I have a GA-EX58-UD5 motherboard with my system drive 2x500GB Seagests in RAID 0 connected via the ICH10R raid controller.
I'm running Windows 7 SP1 64bit.
I suspect that the HDDs are not restarting when coming out of S3. When I resume from S3 my computer will get to the login screen, I can actually log in, and then my computer decides to die. I'll sometimes get an error that says something along the lines of "The requested data was not placed into memory because of an I/O status of 0xc000000e"
Then I get a BSOD with a F4 error and no minidum is created.
I suspect the HDDs not starting up are the culprit because when if I have resource manager running after return from S3 the IO is 0MB/s, and the minidump fails to write to disk.
In my power options I have HDD sleep set to never.
For "fun" I'm now cloning my RAID to a single disk connected directly (not via the ICH10R) to see if the problem persists.
Does anybody have any suggestions? Thanks in advance.
