BSOD Playing Wow, GW2, and LoL. CRITICAL_OBJECT_TERMINATION

Hello,

So firstly thanks for taking a look at this for me. I'll try and post as much information as possible.

I bought the PC from Ibuypower.com and since I started playing games I've been getting BSOD. I've tried everything short of reloading the OS. And I've heard theories from "It's your USB Headset" to "Reload all your Drivers"

I've used the tools listed on how to create a BSOD thread, and I've attached those files. I've also used WhoCrashed I'll post logs from that below:


computer name: ALEX-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17130991616 total
VM: 2147352576, free: 1947164672



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 5/3/2012 6:08:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050312-14367-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8010607060, 0xFFFFFA8010607340, 0xFFFFF800037D9660)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/3/2012 6:08:17 AM 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, 0xFFFFFA8010607060, 0xFFFFFA8010607340, 0xFFFFF800037D9660)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 5/3/2012 4:54:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050312-13930-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80105F6620, 0xFFFFFA80105F6900, 0xFFFFF800037DF660)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 5/2/2012 10:57:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050212-16536-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800F2BE630, 0xFFFFFA800F2BE910, 0xFFFFF800037D4660)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

-----

And I've also used OCCT for stress tests with no errors in test spans of 5-10 mins.

Here are system specs:
Processor (Intel® Core™ i7 3820 Processor (4x 3.60GHz/10MB L3 Cache) - Intel Core i7 3820))
Motherboard ([3-Way SLI] ASRock Extreme4 -- 5x SATA 6Gb/s))
Memory (16 GB [4 GB X4] DDR3-1600 Memory Module - Corsair
NVIDIA GeForce GTX 560 Ti - 2GB - Single Card
Microsoft Windows 7 Home Premium

-----

Hope this is enough information, I've tried reinstalling BIOS, Video, Audio, all the games, like I said just about everything except reloading the OS.

On a side note, when the game crashes, the first thing to go will be the sound, in other words I'll be playing the sound will go I'll continue to play 3-6 secs, and then boom BSOD, I know it's coming because the sound is always first to go.

I use to run dual monitors, I've disabled the second one, I use to run the games in windowed mode, I now run in full screen seeing if anything I can do will make the BSOD stop, but to no success.

One thing I have not tried, and I will do so now, is a different USB port for my Headset, and or a totally different headset all together. I use a Plantronics 655 DSP.

Any help would be greatly appreciated.

Thanks,
Alex

Update:

Had BSOD's last night with, and without the USB Headset plugged in. It sounds silly but I tested it, as I've read some people had their USB headsets/speakers cause BSOD!

Off to work, if no other suggestions, I'll likely be re installing the OS tonight and then the games, and see where that takes me.

Again thanks for the help in advance.

Security Software: ??? I recommend either of these two setups:

• Microsoft Security Essentials - Free Antivirus for Windows
  
  
• Good and Free system security combination.

Download and install the security setup of your choice, update the software, and then run a full scan of your system for viruses and malware. If you only install MSE, I would also suggest installing and updating Malwarebytes : Free anti-malware, anti-virus and spyware removal download, but do not start the free trial/full version of Malwarebytes. Run a full scan with Malwarebytes after updating it. Post back the results.


The crashes you had are usually due to hard disk corruption, hard disk errors, hard disk controller driver corruption, or a bad hard disk connection. Check for corruption and errors first.

• 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.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests with SeaTools for Windows. If you cannot get the Windows version to run, use SeaTools for DOS. SeaTools will check whether the hard disk is functioning properly.
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.

A clean install may resolve the issue if it was a corrupted Windows installation. Let us know if you did the clean install already and how the system is responding.

Thanks for your help, I ran all these test and had no issues, no fixes, everything seemed fine.

I then went to Radio Shack and bought a new SATA cable, and replaced that, and also resat all the components in the PC, along with a OS re install

This weekend played tons of Wow, and Lol with not a single BSOD so what fixed it? Not sure, but it's fixed, and I now know a bunch of ways to trouble shoot BSOD's

So thanks for all the help, you can consider this post Closed/resolved successfully.

You're welcome.

FYI: Any of those steps may have fixed it. Could have been a bad SATA cable, hardware not seated properly, or a corrupted install of Windows.

You may mark the thread solved when you feel comfortable doing so. :)

i have the same exact problem but i did a full reboot and everything and today i had atleast 5 BSOD's while playing LoL!! i did the reboot specifically cuz of the BSOD's but idk why its still happening ... =[

oquendo: Have you done the same steps done in this thread? If so, I would recommend you start your own thread and follow the https://www.sevenforums.com/crashes-d...tructions.html because your problem would be different from that in this thread.

i just started my own threat idk if i got the reports of the mini dump files right though check it out