BSOD Critical Object Termination, Error 0XF4

[hojoko]

I hope someone can help me with this issue. I have an Asus G74S which I have sent back twice due to BSOD issues. The first time Asus replaced a memory stick and the system board. The second time they replaced the CPU. I'm still getting BSOD errors. oh, and fun fact: This laptop is a replacement of a G73 that I had to send back 6 times due to a non-functional touchpad - I finally convinced them after about 18 months to give me another computer and here I am...

I'm really hoping that someone can help me figure this out as I have zero faith in Asus. Any help is greatly appreciated.

Anyways... I've attached the SF Diagnostic Tool zip to this post.

Here is the Windows Debugger Tool results from the last dump:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0301e000 PsLoadedModuleList = 0xfffff800`03262670
Debug session time: Sun Dec 30 07:32:33.016 2012 (UTC - 5:00)
System Uptime: 0 days 6:01:41.016
*********************************************************************
* 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, fffffa800bd496d0, fffffa800bd499b0, fffff8000339c460}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

----- ETW minidump data unavailable-----
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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
---------


And here is the WhoCrashed Results:
System Information (local)
--------------------------------------------------------------------------------

computer name: WORKDAMMIT
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 12860952576 total
VM: 2147352576, free: 1975709696




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 12/30/2012 12:32:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123012-9016-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800BD496D0, 0xFFFFFA800BD499B0, 0xFFFFF8000339C460)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 12/30/2012 12:32:33 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800BD496D0, 0xFFFFFA800BD499B0, 0xFFFFF8000339C460)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 12/30/2012 5:36:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123012-8158-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800BD70060, 0xFFFFFA800BD70340, 0xFFFFF800033D6460)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[mmkarimi]

for sympathy i have ASUS and I have changed its MOBO twice, and ones its hard with the microphone and its monitor cable....
after all, would you explain it much summarized. just mess up, what happened to cause BSOD?

 

[hojoko]

I've had 3 crashes since I last received the laptop (two days ago) and each time, it's been when I've been away from the laptop. I can't think of a common factor and in at least one crash, I know that nothing was running on the laptop. It was just on.

 

[mmkarimi]

did you ever check your system temperature?
is your cpu fan doing well?

did you check disk your hard?

and update your graphic card driver too

 

[mmkarimi]

after all asus had one thing good and that is its guaranty, they changed the devices and it was 2 years of global guaranty service

 

[hojoko]

Yes, System Temp has never gone above the low 30's in Celcius so far. I haven't done anything intensive on the laptop yet.

The CPU seems to run in the low 40's. I assume that this means that the fan is doing well.

The hard disks are fine. I've done diskcheck and I run Hard Disk Sentinel.

My graphics card driver was updated yesterday.

As for the Asus warranty... I had 2 years... apparently that starts when the reseller gets the laptop from Asus, so if I buy it four months after Asus sold it to the reseller (I purchased it from XoticPC.com) then I only have 20 months of warranty technically. In either case, I spent 18 months of it with the G73 lemon that I never actually got to use and finally after 6 RMA's I argued enough to get them to give me a refurb G74. Nevermind that I purchased the G73 when it was top of the line, and they gave me a G74 when the G75 was out already. Then they wanted to give it to me with no warranty. I had to argue to get 3 months. And it's been over a month already with the two RMA's I've done. I hate Asus so much right now that I can't put it into words.

 

[mmkarimi]

check your screen saver, as you said they happen when you are not around.. it may refer to the power management properties , maybe it tries to go sleep and it cant so bsod happens or its the screen saver

 

[hojoko]

You're @#&$ brilliant!!

I don't have a screen saver on but I've tested the sleep function and it crashes each time!

Any suggestions on how to debug this? I'll start looking online.

Thanks again!

 

[mmkarimi]

Truly yours
i think it refer to the graphic card or the ram,
because going to sleep or hibernate needs some sort of graphic support,
also when your computer wants to get sleep it tries to copy some sort information into the ram, the problem is highly possible to be on this side.
check them, check the following link to find some way to check your rams:
http://pcsupport.about.com/od/toolsofthetrade/tp/memorytest.htm

 

[mmkarimi]

Hello hojoko, and happy new year,
What was going on since our last dialog, could you find anything helpful to share?

 

[mmkarimi]

hi, did you got your answer here?
can you share what have you experienced next here for us
regards
MMKARIMI

 

[hojoko]

Hi mmkarimi,

I was spending a lot of time trying to figure it out and finally just decided to RMA it back to Asus to have them figure it out. In about 3 weeks it'll be 2 years since I purchased an Asus laptop and I have yet to actually get to use it. I may be jaded against them now but I figure I'll let them spend the resources to figure it out instead of spending days doing it myself. I did however help them out and sent them a note on what causes the crash (thanks to you). I'll post an update to let you know what happens when I get the laptop back.

-hojoko

 

[mmkarimi]

hope that they change some hardware for you with a new ones, as i told before, i had such experience before, but the good point is they just change the devices with a new one,
for me it took about more than two weeks to get it ready, hope it take much less for you

Regards
MMKarimi

 

[hojoko]

Well, I just got the laptop back. They marked it as repaired and checked off "replaced system board," "replaced hard disk drive," and "replaced power cable." I don't know what this last one is since I didn't send them my power chord... maybe they're talking about some cable in the laptop. Frankly, I call BS on this because almost every single one of my RMAs (10 to date) has had the system board replaced. Right...

Anyways, they also removed my OCZ Vertex2 SSD drive (OS drive) left it out of the laptop. Instead, they installed Windows 7 on what I was using as my storage drive (750 GB SATA). Generally the G74S comes with two 750 GB SATA drives, but I had one of mine upgraded to the SSD drive from XoticPC, which is where I originally purchased it.

They put a ton of bloatware on their installations so it runs extremely slow, however, there is no crash upon the return from Sleep Mode.

Since they removed the OCZ drive, I just put it back, made it the primary boot disk, updated the firmware on it, did whatever updates I could and tried the sleep mode again. It crashed. Looks like the OCZ drive is not compatible with the laptop. That's strange... I didn't realize an HD could be incompatible with a computer.

 

[Dsprague]

Unfortunately Hojoko the problem with OCZ is that they are incredibly fast but highly unstable from what I have seen here on the forums. Nine times out of ten if a personhas an OCZ drive and they are getting BSODs that involve some sort of hard drive error it is being cause by the OCZ SSD. Like I said great speed but the trade off is terrible stability.