Solved BSOD when resuming from Sleep WIN 7 Home ASUS P5n73AM MB

[seanh46]

I have formatted and re-installed windows, updated my BIOS, checked all of my drivers, disabled Hibernation
Opened up the case, checked the cables, cleaned out the machine. all to no avail

I have included a dump file,
(let me know if I didn't do it right)

I am willing to do anything at this point
just don't know what to do

 

[YoYo155]

Welcome to SF Sean .

A single dump file is usually not enough and I would like to have more to get a better "feel" of the system.
I see you have CCleaner installed, please STOP using it along the troubleshooting procedure
as it deletes the dumps files which we need.

BugCheck F4, {3, 86948b68, 86948cd4, 82c29eb0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

Please start by testing the HDD.

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check- Scroll down to OPTION TWO of the tutorial and use the /R switch in the CHKDSK command | chkdsk C: /R.
2. Then Post the Disk Check results following | This Tutorial.
3. Once back in Windows, download Crystal Disk Info and post a screenshot (multiple shots if you have more than one drive).
4. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
5. If SeaTools for DOS is unable to recognize your HDD:
6. Visit HDDdiag and follow the instructions | Or follow the instructions below.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fx key.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

Re-seat the sata and power.

Let us know the results.

 

[seanh46]

thanks

Thanks for checking that out for me, I will generate a few more dumps, and get a file uploaded in the next few days, just FYI, I have ran Sea Tools on my HD and it has passed a long FIX all, but I am willing to do it again and, I will not run CCLEaner until we get this resolved!

 

[YoYo155]

Acknowledged, keep us posted.

 

[seanh46]

A few more dump files

I ran the SF Diagnostic tool again and got a few more dump files,
I can't thank you guys enough for taking the time to look at it.
Any suggestions you have will be greatly appreciated

 

[YoYo155]

So... where are the new files ?

 

[seanh46]

Oops!

Here it is

 

[YoYo155]

Thanks .
Unfortunately the new bug check are again indicating of an HDD hardware issue,
what have you manged to complete from the list above?
Did you try a different set of SATA (Data & Power) cables?
Did you try a different SATA Port on the motherboard?

I would also check for malicious software.

Please scan for possible infection and file corruption.

• Download TDSS-Killer and scan for rootkits.
• Download Kaspersky Rescue CD and scan for other types of infections. (a how-to tutorial)
• Download Malwarebytes and DON'T activate the trail (uncheck the box at the end of the installation)
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

(*Kaspersky Rescue CD from a USB thumbdrive)

 

[seanh46]

You're a Genius!
Changing the SATA Port on the Motherboard fixed it !!!!!
I booted up after changing it, and Windows posted a message saying to reboot for changes to take effect
and PRESTO it worked
THANK YOU SOOOOO MUCH

 

[YoYo155]

Haha I appreciate the feedback .
Just make sure you remember that the SATA port in question is possibly corrupt .

Keep the thread open for a couple of days and if all goes smoothly mark the thread as solved .