Solved BSOD Random, Error: CRITICAL_OBJECT_TERMINATION

[AnnaB]

Random BSODs, have tried to update all drivers as possible, even replaced my SATA cables for my Hardrives and SSD. Posted the zip file needed for evaluation.
Usually the computer freezez up, closes all my programs, and then I loose peripherals.
Can't really say when it happens. Its almost once a day or more. Having troubles pinpointing the problem. Please help!
Ive been Having this problem for months, and the longer I've let it go, the more it's been happening lately. Especially after startup or when left idle also.



Who Crashed Log
On Sat 6/18/2016 1:38:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061716-6520-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800FC9CB10, 0xFFFFFA800FC9CDF0, 0xFFFFF80003176E40)
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.

Also have an evaluation of my DMP file.
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR ? Windows System Software ? Unique Expertise, Guaranteed Results)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23418.amd64fre.win7sp1_ldr.160408-2045
Machine Name:
Kernel base = 0xfffff800`02e00000 PsLoadedModuleList = 0xfffff800`03042730
Debug session time: Fri Jun 17 21:38:54.341 2016 (UTC - 4:00)
System Uptime: 0 days 0:03:07.153
*******************************************************************************
* *
* 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: fffffa800fc9cb10, Terminating object
Arg3: fffffa800fc9cdf0, Process image file name
Arg4: fffff80003176e40, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

PROCESS_OBJECT: fffffa800fc9cb10

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: wininit.exe

EXCEPTION_CODE: (Win32) 0xfc92980 (264841600) -

BUGCHECK_STR: 0xF4_fffffa800fc92980

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`0592ee48 fffff800`032041c2 : 00000000`000000f4 00000000`00000003 fffffa80`0fc9cb10 fffffa80`0fc9cdf0 : nt!KeBugCheckEx
fffff880`0592ee50 fffff800`031c083b : 00000000`00000001 fffffa80`0fc92980 fffffa80`0fc9cb10 00000000`00dc0f00 : nt!PspCatchCriticalBreak+0x92
fffff880`0592ee90 fffff800`03127484 : 00000000`00000001 ffffffff`ffffffff fffffa80`0fc9cb10 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x28576
fffff880`0592eee0 fffff800`02e6e693 : ffffffff`ffffffff fffffa80`0fc92980 fffffa80`0fc9cb10 00000000`00dc0f80 : nt!NtTerminateProcess+0x284
fffff880`0592ef50 fffff800`02e6ac50 : fffff800`02ef0729 fffff880`0592fa38 fffff880`0592f790 fffff880`0592fae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0592f0e8 fffff800`02ef0729 : fffff880`0592fa38 fffff880`0592f790 fffff880`0592fae0 00000000`00dc1c90 : nt!KiServiceLinkage
fffff880`0592f0f0 fffff800`02e6ea82 : fffff880`0592fa38 00000000`000134b4 fffff880`0592fae0 00000000`00dc1768 : nt! ?? ::FNODOBFM::`string'+0x40f64
fffff880`0592f900 fffff800`02e6d5fa : 00000000`00000000 00000000`ff20f630 00000000`00000001 00000000`000134b4 : nt!KiExceptionDispatch+0xc2
fffff880`0592fae0 00000000`77b17da2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00dc16b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b17da2


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_fffffa800fc92980_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_fffffa800fc92980_IMAGE_wininit.exe

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


This free analysis is provided by OSR Open Systems Resources, Inc.

 

[AnnaB]

Lately the BSOD after I've posted this has happened after startup. Not sure if that helps with information to solve the problem. I have to shutdown and restart and usually the BSOD doesn't happen for a few hours. Also been BSOD when its been idle, screen will go black.

 

[AnnaB]

Ive had around 3 bluescreens and I decided to give you guys another file for a more updated option.

 

[AnnaB]

Any updates? Just bluescreened today. Problem still persists.

 

[derekimo]

F4 is most likely storage related, check your cables, chkdsk /r, firmware on your SSD.

This is your bigger problem, especially regarding help here,

Product ID:                00371-OEM-8992671-00407
Original Install Date:     3/15/2016, 12:11:29 PM
System Boot Time:          6/20/2016, 4:24:15 PM
System Manufacturer:       MSI
System Model:              MS-7922
System Type:               x64-based PC

You have an ASUS OEM product ID on an MSI board, which makes your installation counterfeit.

Our rules state,

4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).

Counterfeit installations such as yours contained heavily modified code that causes the installation to behave it unexpected ways. Analysing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimise the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them.

 

[AnnaB]

I do apologize. I actually got this from my Boss who is a computer tech and assumed it was a legit key. I do apologize and appreciate your time for the post. I had absolutely no idea because he Helped me build this rig and had no idea that he just used a fake copy of windows. Quite upsetting. I will definitely be getting a hold of him

 

[axe0]

Many do so to not spend anything to the OS because they don't have the money or do not find it worth it to pay, but they mostly do not realise what happens to their system. We also do not know what happens when they do this, which is another reason why we do not provide support, it is unknown modification that can cause who knows what kind of trouble.