BSOD F4- Debuging help.

I get this F4 BSOD a few times a week. Kernel dump file is too large to post on here (even zipped) but i was able to put this file on here instead:

Here is some more data i managed to attain:

PROCESS_OBJECT: fffffa80099e98c0

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0xF4_C0000005

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`086a50e8 fffff800`034195e2 : 00000000`000000f4 00000000`00000003 fffffa80`099e98c0 fffffa80`099e9ba0 : nt!KeBugCheckEx
fffff880`086a50f0 fffff800`033c699b : ffffffff`ffffffff fffffa80`098b2380 fffffa80`099e98c0 fffffa80`099e98c0 : nt!PspCatchCriticalBreak+0x92
fffff880`086a5130 fffff800`03346448 : ffffffff`ffffffff 00000000`00000001 fffffa80`099e98c0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`086a5180 fffff800`0308ded3 : fffffa80`099e98c0 fffff800`c0000005 fffffa80`098b2380 00000000`041406a0 : nt!NtTerminateProcess+0xf4
fffff880`086a5200 fffff800`0308a470 : fffff800`030da67f fffff880`086a5b78 fffff880`086a58d0 fffff880`086a5c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`086a5398 fffff800`030da67f : fffff880`086a5b78 fffff880`086a58d0 fffff880`086a5c20 00000000`04141ee0 : nt!KiServiceLinkage
fffff880`086a53a0 fffff800`0308e2c2 : fffff880`086a5b78 00000000`000713b8 fffff880`086a5c20 00000000`041419b8 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`086a5a40 fffff800`0308ce3a : 00000000`00000001 00000000`04140c58 00000000`04147301 00000000`000713b8 : nt!KiExceptionDispatch+0xc2
fffff880`086a5c20 00000000`77be8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`04140c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77be8e3d


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe

Followup: MachineOwner

I suffered the dreaded F4 stop error and discovered it was all due to POWER MANAGEMENT.

In the latest install, I have disabled BIOS support for power management on my MSI-7522 mobo (X58 chipset, Core i7-920, 24GB RAM) and selected Performance power profile with NO MODIFICATIONS.

System was crashing during the night, always at idle, and research told me a critical thread was being terminated and the system restarted to avoid other unpleasant conditions.

No BIOS PM support, no Windows changes to the performance profile, and the box remained stable for FIFTEEN DAYS. Looks like I found my problem, hope this helps you, too.

MARK STRELECKI
Atlanta, GA. USA

My previous comment about power management being at the center of my BSOD F4 instability with Win7x64 has now been shown to be plain WRONG.

I upgraded this X58 Core i7-920 system to the max 24GB RAM and thought that was initially the culprit. Then I did a buncha reading on the interwebs and decided it was caused by power management settings - C1E, EIST, HPET, BFD, OMG and too many other acronyms to mention.

Well, I was wrong, and this is how I know:

The latest BSOD left the hard drive light on the box lit solidly. It just stayed ON. And instead of turning off the PC as I had always done, I pressed and released the RESET button.

Lo and behold, when the system restarted, THERE WAS NO BOOT DEVICE (SSD).

I turned it off, waited 30 seconds, then powered back on, AND EVERYTHING WAS FINE. Booted from SSD just like it always did.

OK, I started thinking about the MicroCenter 60GB SSD I had installed and wondered if there might be a newer firmware out there. My studies say that this is a rebranded ADATA S599 drive with Sandforce 1222 controller and YES! There IS a newer firmware. I was at 3.1.0. and the one at the ADATA website was 3.4.6.

I had made up my mind to return the drive and replace it with one of the super Samsung models, so I took the chance at upgrading the firmware to see if it made any difference.

Turned off antivirus, but forgot about WinPatrol which was running when I did the upgrade. The flash utility hung, and my heart dropped, thinking WinPatrol had prevented something from being written properly (Scotty was saying he was checking my "new startup program" - oh boy!).

I turned the box off, then repowered it and was greeted by several cycles of on for three seconds, then off, then on again for three seconds, then off. This repeated a dozen times and I thought "It's a goner. Shut her down and let's give this one up."

So I pressed and held the power button, and instead of turning OFF like it normally would, the system came on AND STAYED ON and booted to a full desktop where a balloon told me that a new device had been configured (the SSD) and I needed to restart.

Holy Moses, Batman. Was this gonna work, or what?

Long story short, it worked, the system has been stable for over 48 hours, and my faith in experimental techniques has been renewed.

Thank you, interwebs, Google and these forums. So far, so good!


MARK STRELECKI
Atlanta, GA