Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: 0xF4 BSOD before and after reimage

28 Apr 2016   #1
freddiej32

Win7 64 bit
 
 
0xF4 BSOD before and after reimage

Computer bluescreen's often. It did it before and after we reimaged it. Any ideas? Below are a couple of the mini dumps. Any help is appreciated.

Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\021816-9921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\cache*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.19135.amd64fre.win7sp1_gdr.160121-1718
Machine Name:
Kernel base = 0xfffff800`03859000 PsLoadedModuleList = 0xfffff800`03aa0730
Debug session time: Thu Feb 18 17:15:16.909 2016 (GMT-4)
System Uptime: 0 days 7:36:52.060
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800b1b8b10, fffffa800b1b8df0, fffff80003bd4e80}

Probably caused by : wininit.exe

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

0: 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: fffffa800b1b8b10, Terminating object
Arg3: fffffa800b1b8df0, Process image file name
Arg4: fffff80003bd4e80, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa800b1b8b10

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: WmiPrvSE.exe

BUGCHECK_STR: 0xF4_WmiPrvSE.exe

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80003c636f2 to fffff800038cd3c0

STACK_TEXT:
fffff880`098e49c8 fffff800`03c636f2 : 00000000`000000f4 00000000`00000003 fffffa80`0b1b8b10 fffffa80`0b1b8df0 : nt!KeBugCheckEx
fffff880`098e49d0 fffff800`03b8814b : ffffffff`ffffffff fffffa80`0c469b50 fffffa80`0b1b8b10 fffffa80`0993d500 : nt!PspCatchCriticalBreak+0x92
fffff880`098e4a10 fffff800`03b84cd8 : ffffffff`ffffffff 00000000`00000001 fffffa80`0b1b8b10 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29746
fffff880`098e4a60 fffff800`038cc653 : fffffa80`0b1b8b10 fffff880`00000001 fffffa80`0c469b50 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`098e4ae0 00000000`755a9e43 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0178de28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x755a9e43


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: wininit.exe

FAILURE_BUCKET_ID: X64_0xF4_WmiPrvSE.exe_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_WmiPrvSE.exe_IMAGE_wininit.exe

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

Loading Dump File [C:\Windows\Minidump\040816-10093-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\cache*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.19160.amd64fre.win7sp1_gdr.160211-0600
Machine Name:
Kernel base = 0xfffff800`03812000 PsLoadedModuleList = 0xfffff800`03a59730
Debug session time: Fri Apr 8 09:14:59.877 2016 (GMT-4)
System Uptime: 0 days 1:13:52.938
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800b1d7060, fffffa800b1d7340, fffff80003b8e780}

Probably caused by : wininit.exe

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: fffffa800b1d7060, Terminating object
Arg3: fffffa800b1d7340, Process image file name
Arg4: fffff80003b8e780, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa800b1d7060

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: WmiPrvSE.exe

BUGCHECK_STR: 0xF4_WmiPrvSE.exe

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80003c1c7e2 to fffff80003886080

STACK_TEXT:
fffff880`0d8ea9c8 fffff800`03c1c7e2 : 00000000`000000f4 00000000`00000003 fffffa80`0b1d7060 fffffa80`0b1d7340 : nt!KeBugCheckEx
fffff880`0d8ea9d0 fffff800`03b42e4b : ffffffff`ffffffff fffffa80`0700b060 fffffa80`0b1d7060 fffffa80`0bdab770 : nt!PspCatchCriticalBreak+0x92
fffff880`0d8eaa10 fffff800`03b3f9d8 : ffffffff`ffffffff 00000000`00000001 fffffa80`0b1d7060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x28c16
fffff880`0d8eaa60 fffff800`03885313 : fffffa80`0b1d7060 fffff880`00000001 fffffa80`0700b060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`0d8eaae0 00000000`747d9e43 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0185d9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x747d9e43


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: wininit.exe

FAILURE_BUCKET_ID: X64_0xF4_WmiPrvSE.exe_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_WmiPrvSE.exe_IMAGE_wininit.exe

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


Loading Dump File [C:\Windows\Minidump\040816-10093-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\cache*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.19160.amd64fre.win7sp1_gdr.160211-0600
Machine Name:
Kernel base = 0xfffff800`03812000 PsLoadedModuleList = 0xfffff800`03a59730
Debug session time: Fri Apr 8 09:14:59.877 2016 (GMT-4)
System Uptime: 0 days 1:13:52.938
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800b1d7060, fffffa800b1d7340, fffff80003b8e780}

Probably caused by : wininit.exe

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: fffffa800b1d7060, Terminating object
Arg3: fffffa800b1d7340, Process image file name
Arg4: fffff80003b8e780, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa800b1d7060

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: WmiPrvSE.exe

BUGCHECK_STR: 0xF4_WmiPrvSE.exe

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80003c1c7e2 to fffff80003886080

STACK_TEXT:
fffff880`0d8ea9c8 fffff800`03c1c7e2 : 00000000`000000f4 00000000`00000003 fffffa80`0b1d7060 fffffa80`0b1d7340 : nt!KeBugCheckEx
fffff880`0d8ea9d0 fffff800`03b42e4b : ffffffff`ffffffff fffffa80`0700b060 fffffa80`0b1d7060 fffffa80`0bdab770 : nt!PspCatchCriticalBreak+0x92
fffff880`0d8eaa10 fffff800`03b3f9d8 : ffffffff`ffffffff 00000000`00000001 fffffa80`0b1d7060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x28c16
fffff880`0d8eaa60 fffff800`03885313 : fffffa80`0b1d7060 fffff880`00000001 fffffa80`0700b060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`0d8eaae0 00000000`747d9e43 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0185d9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x747d9e43


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: wininit.exe

FAILURE_BUCKET_ID: X64_0xF4_WmiPrvSE.exe_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_WmiPrvSE.exe_IMAGE_wininit.exe

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


My System SpecsSystem Spec
.
29 Apr 2016   #2
axe0

Windows 10 Pro
 
 

My System SpecsSystem Spec
Reply

 0xF4 BSOD before and after reimage




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD after reimage and updates
BSOD's at the Windows flying flag logo just before the logon screen. When it does not blue screen it hangs at the log screen for several minutes.
BSOD Help and Support
BSOD on startup 0xF4, 0x3
Stop code: 0xF4 with the first argument 0x3 The next two arguments change when it blue screens, but the ones I wrote down are: 0xFFFFFA801E1E1E10 0xFFFFF80003585270 So, for the longest time I never shut down (or put to sleep, or hibernated) my computer. Starting a few weeks, maybe a...
BSOD Help and Support
Random BSOD's after Reimage during games DOTA
Specs Windows 7 Ultimate x64 Retail The machine is mostly custom so I date the age of it at about 2-3 Years. Story is this this kid asked me to fix a machine for him he had a few hundred root kits and viruses no anti virus etc... So you can imagine the machine was in bad shape. I decide to...
BSOD Help and Support
New SSD, New OS = 0xF4 BSOD
Hi There, As you can see, I have upgraded my PC recently to a SSD drive. Installed new Win 7 x64 and if I leave my PC on overnight, I often find it crashed with 0xF4 BSOD error. I've never seen the 0xF4 error before, only now with SSD and new OS. Windows 7 x64 retail, hardware pretty much...
BSOD Help and Support
BSOD 0xf4 on Win 7 x64
Hi, I'm using Windows 7 Ultimate 64bit on a Corsair F60 SSD since 3 months and for 2 months it worked fine. Now Windows gives me BSOD randomly (daily) because it loses the ssd drive, it doesn't finds it anymore. The BSOD error is 0xF4. BSOD comes when I'm in doing something: watching a movie,...
BSOD Help and Support
BSOD-Stop 0xF4
Hey guys. I'm back with another BSOD. This time, what happened was when I first switched on the com, there was a message saying (from memory because I forgot to write it down) "The file C:\windows\winsxs\manifest\amd_64...soemthing something is corrupt and unreadable. Run CHKDSK utility. " So I...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 23:18.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App