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: STOP 0xF4 CRITICAL_OBJECT_TERMINATION

15 Jun 2011   #1

Windows 7 Professional x64
 
 
STOP 0xF4 CRITICAL_OBJECT_TERMINATION

Hey Folks!

I hope YOU can help me ! ; )

First of all, my english is not very well, because i am Austrian, so im sorry for all kinds of lingual interferrations ;P



I have owned the hardware listed on the bottom and installed Windows 7 x64 one Week before.

Yesterday my PC got a BSOD after running several Minuites in idle.

First of all, my Specs:

Windows 7 Prof. x64 bit full retail vers.

Gigabyte 870-UD3 Rev. 2.1 with the latest BIOS

AMD Phenom II X6 1090T 3.2 GHz 125W

Corsair XMS3 — 8GB Dual Channel DDR3 Memory Kit (CMX8GX3M4A1333C9)

Asus ENGTX 480

System HD: OCZ Vertex 3 120GB Firmware 2.06

Second HD: Western Digital Caviar Blue 1 TB

Soundcard extern: Creative X-FI Gamer


All Drivers are installed from Windows, except the USB 3.0 Driver, Windows couldnt find one, so i installed the one coming with the CD. The Networkcard Driver got an Update from Windows Update, i installed them too.

For the ext. Soundcard, i installed the one from Creative's Website, it worked well without Errors.

So i googled this Error, some forums say this may cause by an HDD Error ( my OCZ Vertex3 is brandnew - 1 week) so i did a CheckDisk, without Errors.

I also tested my RAM with MemTest 86+ for a few Hours (Over Night) completing with 0 Errors.

Here's what the Dump said:


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


Loading Dump File [C:\Documents and Settings\atw124g7\Desktop\061411-8954-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Code:
 
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309f650
Debug session time: Tue Jun 14 18:28:55.178 2011 (UTC + 2:00)
System Uptime: 0 days 0:31:33.364
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck F4, {3, fffffa80097689e0, fffffa8009768cc0, fffff800031dcf40}
 
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
 
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : csrss.exe
 
Followup: MachineOwner
---------
 
1: 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: fffffa80097689e0, Terminating object
Arg3: fffffa8009768cc0, Process image file name
Arg4: fffff800031dcf40, Explanatory message (ascii)
 
Debugging Details:
------------------
 
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
 
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
 
ADDITIONAL_DEBUG_TEXT: 
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
 
MODULE_NAME: csrss
 
FAULTING_MODULE: 0000000000000000 
 
DEBUG_FLR_IMAGE_TIMESTAMP: 0
 
PROCESS_OBJECT: fffffa80097689e0
 
IMAGE_NAME: csrss.exe
 
CUSTOMER_CRASH_COUNT: 1
 
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
 
BUGCHECK_STR: 0xF4
 
CURRENT_IRQL: 0
 
STACK_TEXT: 
fffff880`0759b0e8 fffff800`032617d2 : 00000000`000000f4 00000000`00000003 fffffa80`097689e0 fffffa80`09768cc0 : nt+0x7fd00
fffff880`0759b0f0 00000000`000000f4 : 00000000`00000003 fffffa80`097689e0 fffffa80`09768cc0 fffff800`031dcf40 : nt+0x4077d2
fffff880`0759b0f8 00000000`00000003 : fffffa80`097689e0 fffffa80`09768cc0 fffff800`031dcf40 00000000`035a1e00 : 0xf4
fffff880`0759b100 fffffa80`097689e0 : fffffa80`09768cc0 fffff800`031dcf40 00000000`035a1e00 fffffa80`097689e0 : 0x3
fffff880`0759b108 fffffa80`09768cc0 : fffff800`031dcf40 00000000`035a1e00 fffffa80`097689e0 fffff800`0320fbdb : 0xfffffa80`097689e0
fffff880`0759b110 fffff800`031dcf40 : 00000000`035a1e00 fffffa80`097689e0 fffff800`0320fbdb ffffffff`ffffffff : 0xfffffa80`09768cc0
fffff880`0759b118 00000000`035a1e00 : fffffa80`097689e0 fffff800`0320fbdb ffffffff`ffffffff fffffa80`0a141b60 : nt+0x382f40
fffff880`0759b120 fffffa80`097689e0 : fffff800`0320fbdb ffffffff`ffffffff fffffa80`0a141b60 fffffa80`097689e0 : 0x35a1e00
fffff880`0759b128 fffff800`0320fbdb : ffffffff`ffffffff fffffa80`0a141b60 fffffa80`097689e0 fffffa80`097689e0 : 0xfffffa80`097689e0
fffff880`0759b130 ffffffff`ffffffff : fffffa80`0a141b60 fffffa80`097689e0 fffffa80`097689e0 ffffffff`ffffffff : nt+0x3b5bdb
fffff880`0759b138 fffffa80`0a141b60 : fffffa80`097689e0 fffffa80`097689e0 ffffffff`ffffffff 00000000`00000008 : 0xffffffff`ffffffff
fffff880`0759b140 fffffa80`097689e0 : fffffa80`097689e0 ffffffff`ffffffff 00000000`00000008 fffffa80`097689e0 : 0xfffffa80`0a141b60
fffff880`0759b148 fffffa80`097689e0 : ffffffff`ffffffff 00000000`00000008 fffffa80`097689e0 00000000`c0000005 : 0xfffffa80`097689e0
fffff880`0759b150 ffffffff`ffffffff : 00000000`00000008 fffffa80`097689e0 00000000`c0000005 fffffa80`0a141b60 : 0xfffffa80`097689e0
fffff880`0759b158 00000000`00000008 : fffffa80`097689e0 00000000`c0000005 fffffa80`0a141b60 fffff800`03192838 : 0xffffffff`ffffffff
fffff880`0759b160 fffffa80`097689e0 : 00000000`c0000005 fffffa80`0a141b60 fffff800`03192838 ffffffff`ffffffff : 0x8
fffff880`0759b168 00000000`c0000005 : fffffa80`0a141b60 fffff800`03192838 ffffffff`ffffffff 00000000`00000001 : 0xfffffa80`097689e0
fffff880`0759b170 fffffa80`0a141b60 : fffff800`03192838 ffffffff`ffffffff 00000000`00000001 fffffa80`097689e0 : 0xc0000005
fffff880`0759b178 fffff800`03192838 : ffffffff`ffffffff 00000000`00000001 fffffa80`097689e0 00000000`00000008 : 0xfffffa80`0a141b60
fffff880`0759b180 ffffffff`ffffffff : 00000000`00000001 fffffa80`097689e0 00000000`00000008 00000000`746c6644 : nt+0x338838
fffff880`0759b188 00000000`00000001 : fffffa80`097689e0 00000000`00000008 00000000`746c6644 fffff880`0759b200 : 0xffffffff`ffffffff
fffff880`0759b190 fffffa80`097689e0 : 00000000`00000008 00000000`746c6644 fffff880`0759b200 00000000`00000000 : 0x1
fffff880`0759b198 00000000`00000008 : 00000000`746c6644 fffff880`0759b200 00000000`00000000 00000000`00000000 : 0xfffffa80`097689e0
fffff880`0759b1a0 00000000`746c6644 : fffff880`0759b200 00000000`00000000 00000000`00000000 00000000`035a0c40 : 0x8
fffff880`0759b1a8 fffff880`0759b200 : 00000000`00000000 00000000`00000000 00000000`035a0c40 00000000`035a0680 : 0x746c6644
fffff880`0759b1b0 00000000`00000000 : 00000000`00000000 00000000`035a0c40 00000000`035a0680 00000000`0010001f : 0xfffff880`0759b200
 
 
STACK_COMMAND: kb
 
FOLLOWUP_NAME: MachineOwner
 
BUCKET_ID: WRONG_SYMBOLS
 
Followup: MachineOwner
---------
 
1: kd> !process fffffa80097689e0 3
GetPointerFromAddress: unable to read from fffff80003109000
NT symbols are incorrect, please fix symbols
I hope you Guys can help me, it frustrates me so much : ( : ( : (


THANKS A LOT!

I hope you've got every Information you need!

Andi

My System SpecsSystem Spec
.

Reply

 STOP 0xF4 CRITICAL_OBJECT_TERMINATION




Thread Tools



Similar help and support threads for2: STOP 0xF4 CRITICAL_OBJECT_TERMINATION
Thread Forum
Solved BSOD Error 0xF4 CRITICAL_OBJECT_TERMINATION 1 hour after cold boot BSOD Help and Support
Many Random BSOD, STOP 0xF4 BSOD Help and Support
0xf4 BSOD Critical_Object_Termination BSOD Help and Support
BSOD playing games (Diablo 3), error 0xF4 Critical_Object_Termination BSOD Help and Support
CRITICAL_OBJECT_TERMINATION 0xf4 in new pc build ntoskrnl+7cc80 BSOD Help and Support
BSOD-Stop 0xF4 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 08:32 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33