Help with BSOD

focal · 08 Aug 2010

Hi, this is my first post on this forum and I've been having BSOD for a week or so and
I can't find out what is causing it.

My system is 2 and half year old custom build.

CPU: Intel Q6600
MB: Gigabyte x48-DS4 (The moterboard was changed about 2 years ago)
Ram: 4x1GB Sticks Corsair XMS-6400C4
Sound: X-Fi XtremeGamer Fatal1ty Pro Series
HDD: 3x500GB and 2x1TB
PSU: Zalman ZM-600HP

About 4 days ago it came with the BSOD and when I restarted then 3 of the HDD were
not detected in BIOS so I changed power cables and SATA cables but no luck.

Thanks
Focal

ttran · 08 Aug 2010

Check out this article in the mean time, which I suspect is your case:

STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION

KB 977178 You receive various Stop error messages in Windows 7 or in Windows Server 2008 R2 when you resume a computer that has a large SATA hard disk

BUGCHECK SUMMARY:

Code:

BugCheck A, {e, 2, 1, fffff80002eed31b}

Probably caused by : CI.dll ( CI!A_SHAUpdate+60 )
PROCESS_NAME:  System
BugCheck F4, {3, fffffa8003d57b30, fffffa8003d57e10, fffff8000317c540}

Probably caused by : csrss.exe

focal · 08 Aug 2010

Thanks, I will try this and report back.

focal · 09 Aug 2010

Hi again and thanks, this hotfix fixed the F4 BSOD but came with another.

ttran · 09 Aug 2010

There is no new DMP in the one you just uploaded. Double check the minidump folder for any newer DMP file. In the one you just upload, there are still 3 DMP as the previous one

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

Next time just simply do that instead

focal · 09 Aug 2010

I'm sorry about that. All my dump files from the minidump directory are in the new zip file.
But just 5 minutes ago the same BSOD came up with f4 error again.

But according to the date and time of the files my system didn't write dump file last night
when the new BSOD came up, I think it was the ending was a7 of the BSOD.

ttran · 09 Aug 2010

Yeah, again this is F4 error, check out this KB as well, how many OS you are having, more than 1?
Connecting a hard disk drive in slave only mode leads to system halt during resume from standby

BUGCHECK SUMMARY:

Code:

BugCheck F4, {3, fffffa8008d51b30, fffffa8008d51e10, fffff800031d2540}

Probably caused by : csrss.exe

Followup: MachineOwner
---------

focal · 09 Aug 2010

I'll try this, still not sure what hard drive is causing this.

No, I only have Windows 7 setup.

focal · 09 Aug 2010

Very strange thing happen, I disconnected all my hard drives accept the hard drive Windows 7
is installed on and my dvd drive and then I fired my machine up and every thing working fine
but then I restarted my computer and then it went into some startup recovery because it had
problem to start windows but it could not fix it so restarted again and it booted in to windows
like it was no problem before.

My question is, could this be something related to the BSOD errors?

ttran · 09 Aug 2010

When you resume a computer from sleep or from hibernation, the SATA hard disk drivers require the SATA hard disks to be ready within 10 seconds. However, a large SATA hard disk may take longer than 10 seconds to be ready. In this situation, the resume operation times out.

That is one explanation I got from a KB article. I don't know if that can be considered an answer to your situation, but as you can see, the problem is right under the name of the stop code F4 with large SATA hard disk and as I can see you have a super large hard drive right?