Windows 7 - The bugcheck was: 0x000000f4

babubabi · 02-09-2012

Hi Guys,

I just bought a new box few days ago.
every day (at night) when I was not on the machine it crush and reboots with this error.

I have noticed you already got this error on this forum but I was not able to find information that could help me solve this issue.

This is my System:
OS: Windows 7 Ultimate 74bit
CPU: i7 2600k
MEM: 4x4 DDr3 1600
SSD: Patriot Wildefire 120gb

The OS is brand new, most of the applications are located on another network machine, So only MSE and Office 2007 are installed.

I am not familiar with the Windows Debugger Tool, So I was not able to make much of it.
In case any of you can find some time to check my dump files, here are some links for all my dump files:
020812-4648-01.dmp
020812-4945-01.dmp
020912-4664-01.dmp
020912-7831-01.dmp
020712-4664-01.dmp
020712-5007-01.dmp

Any help would be so very much appreciated!

Thank You

writhziden · 02-09-2012

Code:

Loading Dump File [F:\BSODDmpFiles\babubabi\020912-7831-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e47670
Debug session time: Thu Feb  9 00:34:07.223 2012 (GMT-7)
System Uptime: 0 days 12:47:44.020
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800f1df060, fffffa800f1df340, fffff80002f828b0}

Probably caused by : _

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800f1df060, Terminating object
Arg3: fffffa800f1df340, Process image file name
Arg4: fffff80002f828b0, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa800f1df060

IMAGE_NAME:  _

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: _

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  ’æÌ

BUGCHECK_STR:  0xF4_’æÌ

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030095e2 to fffff80002c7ec40

STACK_TEXT:  
fffff880`07be99c8 fffff800`030095e2 : 00000000`000000f4 00000000`00000003 fffffa80`0f1df060 fffffa80`0f1df340 : nt!KeBugCheckEx
fffff880`07be99d0 fffff800`02fb699b : ffffffff`ffffffff fffffa80`0f336160 fffffa80`0f1df060 fffffa80`0f1df060 : nt!PspCatchCriticalBreak+0x92
fffff880`07be9a10 fffff800`02f36448 : ffffffff`ffffffff 00000000`00000001 fffffa80`0f1df060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`07be9a60 fffff800`02c7ded3 : fffffa80`0f1df060 fffff880`c0000006 fffffa80`0f336160 fffffa80`0f058300 : nt!NtTerminateProcess+0xf4
fffff880`07be9ae0 00000000`77c115da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03e8df58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c115da


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4______IMAGE__

BUCKET_ID:  X64_0xF4______IMAGE__

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

A windows system process was terminated unexpectedly. Possible causes are hard disk errors... System file corruption... Viruses... Lack of Windows updates... Drivers...
Thanks to Dave76 for help understanding possible causes.

Do the following steps and test after each to see if stability increases. Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Scan for viruses with a full scan using the free version (do not start the trial) of Malwarebytes : Free anti-malware, anti-virus and spyware removal download and see the Good and Free system security combination. for better security steps and scanning tools.
Install all Windows Updates.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

babubabi · 02-10-2012

Hi, Thanks for the reply!

No overclocking was made at any time.. I'll wait for the system to stable for a while first.
And at this point I have only 1 SSD installed. No other Disks or even a CD/DVD.

Step 1 - Check Disk

I ran the Windows Check Disk (it had to be scheduled). Here is a Copy of the results from the Event-Log:
Text file 2.10.12_checkdsk.txt

In fact, here is my entire System & Application logs from the last 3 days:
System System(Last3Days).evtx
Application Application(Last3Days).evtx

Basically it happens once or twice a day, so it might take a little while before the next crush.
Would you recommend me stressing the systems? if so using which application?

Since, it seems to me the Check Disk went well (no errors) I continued to the next step.

Step 2 - SFC

"no integrity violations". screen shot:
sfc.png

Since no "no integrity violations" found, I continued to the next step.
I will now close everything & Start the Mal-ware check. Will report back when done.

Thanks!!

babubabi · 02-10-2012

I'm back..

Step 3 - Mal-ware

The Mal-ware results went fine with No malicious items. Screen Shot:
malware.png

My system is brand new, any suspicious activities are made on my old machine.
I am a network admin, I run this machine secure and isolated with very few software & hardware installed.
So at this point I think I can skip the System Security Combinations, since most are already installed and configured.

Step 4 - Windows Updates

Right now I am still waiting for my new Product Key. So the system is not yet activated.
But all Security & Critical Updates are already installed.
Hardware Drivers are installed from CD, So I will now continue to the next step to check the drivers compatibility or maybe newer drivers version.

*by the way, before I wrote this post I found an article that talks about a known failure of the SendForce Controllers (sf-2281) . The article is in Hebrew.. but here it is:
HWzone -
So this gave me the idea to update my SSD FW, following the manufacture instructions:
Patriot Memory
Unfortunately this was done few days ago and did not solved the problem.

Step 5 - Driver Verifier

Driver Verifier was configured as instructed.
Waiting for new dump files...

writhziden · 02-10-2012

Everything appears to check out. It may interest you to read the quote by usasma in post #2 of BSOD playing Battlefield 3, just got a new SSD is that the problem ? since you have an ssd, and your crashes may very well be related to your drive.

Disable driver verifier before doing any steps to increase stability with the ssd.

babubabi · 02-10-2012

Ok Bro,

I will disconnect the SSH and install a normal disk.
After installing OS and all I will post the results.

Thanks for all the help!

writhziden · 03-01-2012

How is the system running after the install on the normal disk?

babubabi · 03-02-2012

Hey, I'm sorry I forgot to reply on time. It was a very long treatment.

Yes, the machine was working well with IDE installed.
Meanwhile I sent back the SSD for diagnostic, after few days they said they didn't find anything.

I gave them the whole machine, they reinstalled a new OS on the SSD and started testing.
Now listen to what they told me:
After few more days they called and said they didn't find any problem and that they were about to call me to take it back. But then.. during a restart attempt the machine did not start at all.. no POST and M.B is dead.
So, I replaced the M.B with a better one (Z68XP-UD4) and since than the machine is working very well with the same SSD.

So I can only assume there was a conflict with the SSD and some component on the old M.B.

Finally after it was working for few days I totally forgot to update this post.

Many Thanks!

writhziden · 03-02-2012

You're welcome.

Sounds like quite the ride, but I'm glad it was all sorted in the end. Enjoy!

Windows 7 - The bugcheck was: 0x000000f4

The bugcheck was: 0x000000f4 problems?