Windows 7 BSOD Remusing From S3 Sleep, No Dumbp Created

[pro-logic]

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.

 

[ChatGPT]

It seems like you are facing a frustrating Blue Screen of Death (BSOD) issue when waking your system from S3 sleep mode. The error you mentioned, "The requested data was not placed into memory because of an I/O status of 0xc000000e" along with the F4 BSOD error code, could indicate issues related to your hard drives not restarting properly after coming out of sleep mode. Here are some steps you can take to troubleshoot and potentially resolve this issue: 1. Check RAID Configuration - Ensure that your RAID configuration is set up correctly and that both of your 500GB Seagate drives are functioning normally. 2. Update RAID Controller Drivers - Make sure that you have the latest drivers for your Intel ICH10R RAID controller. Visit the manufacturer's website to download and install the most up-to-date drivers. 3. Check Power Options - Verify that all power-saving settings, especially those related to the hard drives, are properly configured. You mentioned setting HDD sleep to never, which is correct. 4. Verify Disk Health - Check the health of your Seagate hard drives using tools like CrystalDiskInfo or Seagate SeaTools to ensure they are functioning correctly. 5. Test with a Single Drive - As you mentioned, cloning your RAID to a single disk connected directly can help isolate whether the RAID setup is causing the issue. Monitor the system's behavior with the single disk. 6. Check Event Viewer - Examine the Windows Event Viewer for any disk-related errors or warnings that might provide more insight into the cause of the BSOD. 7. Disable Hibernation - Try disabling hibernation temporarily to see if the issue persists. You can do this by running the command powercfg -h off in an elevated Command Prompt. 8. Update BIOS - Ensure that your motherboard's BIOS is up to date. Check the Gigabyte website for any available BIOS updates and follow their instructions for updating. 9. Monitor System Health - Keep an eye on system temperatures and other hardware parameters using monitoring tools to rule out any overheating or hardware-related issues. By following these steps, you should be able to troubleshoot the BSOD issue you are experiencing when waking your system from S3 sleep mode. If the problem persists, further diagnostics may be required to pinpoint the exact cause of the issue.