So, I was having multiple problems with my system, including BSODs. I reinstalled Windows.
One day later I got a BSOD.
Caused by ntoskrnl.exe - critical object termination.
I am really starting to suspect it is my RAM at this point - can anyone verify this?
All files included. Thank You.
catz95, I will try ti help with this error. You only have one dump file, Please do not run any disk cleanup tools as they sometimes will clean all dump and error reporting files which we will need. From your one dump file, I see nothing that indicates it is ram. However, that does not mean it isn't ram.
Can you tell me any more information about the crashes. Does it happen while using a specific program or during any specific activity? Is there anything you usually do that results in a crash? Any information you can provide will help out a lot. This is what I got from your one dump file.
What is outlined in red is the only thing that is of any help at this point. Once we gets several, we may be better able to see a pattern.Code: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: fffffa8009194710, Terminating object Arg3: fffffa80091949f0, Process image file name Arg4: fffff80002fc6270, Explanatory message (ascii) Debugging Details: ------------------ ----- ETW minidump data unavailable----- PROCESS_OBJECT: fffffa8009194710 IMAGE_NAME: wininit.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: wininit FAULTING_MODULE: 0000000000000000 PROCESS_NAME: wininit.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x. BUGCHECK_STR: 0xF4_IOERR CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre STACK_TEXT: fffff880`068b89c8 fffff800`0304eab2 : 00000000`000000f4 00000000`00000003 fffffa80`09194710 fffffa80`091949f0 : nt!KeBugCheckEx fffff880`068b89d0 fffff800`02ff9abb : ffffffff`ffffffff fffffa80`09b35880 fffffa80`09194710 fffffa80`09194710 : nt!PspCatchCriticalBreak+0x92 fffff880`068b8a10 fffff800`02f78f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`09194710 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486 fffff880`068b8a60 fffff800`02cbfe53 : fffffa80`09194710 00000000`c0000006 fffffa80`09b35880 00000000`7794c541 : nt!NtTerminateProcess+0xf4 fffff880`068b8ae0 00000000`7797157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`009df7b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7797157a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner IMAGE_VERSION: FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe ANALYSIS_SOURCE: KM
Would you look at your system specs and see if there is any additional info that would help, like the Manufacturer and model of your PSU as well as what CPU Cooling you use. We sometimes have to look up a component and need the Manufacturer and model of any component to do that.
I would like to know your CPU and GPU temps at all times. If you need software that will do that, I will suggest some.
The part above in red is the Stop Code 0XF4 and a reason of an I/O error which suggests the file system or a hard drive, to me.
Please run the short and long test with Seatools for Dos on your hard drive. Please read the instructions carefully SeaTools for DOS and Windows - How to Use
Also run Check Disk Disk Check
Please let us know the results as well as any reason you would think it could be memory. Also, if you have any more BSODs please upload the Blue Screen of Death (BSOD) Posting Instructions again in a new post.
Hello,
Thank you for the detailed response. I will try to answer as thoroughly as I can.
The crashes generally do not happen while using a specific program - but I have
noticed a pattern. They happen (mostly) during these scenarios:
1: I leave my computer on for an hour+, while I go do something else. Right after I log
back on, the system lags out and a BSOD occurs.
2: I have 2 USB 3.0 ports on the front of my case. Sometimes, when I plug something into them (even hardware I've used for a long time), 2-3 seconds later, I get a BSOD.
The BSOD I uploaded here was a critical object termination- but sometimes it will be a kernel data inpage error
(still caused by ntoskrnl.exe)
My PSU is a Corsair CX600 600W.
For my CPU, I use the Intel Stock Cooling fan.
I have uploaded my CPU and GPU temps - (just wondering- what did you mean by "at all times"?)
I have run CHKDSK and the Western Digital Lifeguard Software tests on my hard drive-
both came back with no issues.
Hope this helps - if I missed anything please let me know.
Thanks
You will usually get more accurate results if you run Seatools or Western Digital Lifeguard for DOS, because it runs from ram while the hard drive is not in use.
What I meant by at all times means that you should know at any time what your CPU temp is. I use Core Temp (Core Temp) and have it set so that the hottest core shows in the system tray. I can also pull it up and it will show each core, the current, minimum and maximum temp has been for each core.
EVGA's Precision X is an excellent program and will allow you to set a custom fan profile as well as put your GPU temps on screen during gaming and several other things.
I ran Western Digital Lifeguard for DOS, no errors came up.
I am really stumped as for what the cause is.
(Should I download Precision X / Core Temp?)
If it is the temperature causing the BSOD, how would I stop it?
Also, how likely is it that this is the cause? Could it be anything else?
(If I get more BSODs I will upload the dmp files as needed.)
Until we know what is causing it, everything is suspect, and yes temps can be the cause. One of the features of modern CPUs and GPUs is when the temps reach a certain point, the Operating System will shut down in order to protect itself from damage. There are many ways to help bring temps down, but first lets see what is causing your problems. It may not be temps.
Ok, thank you. In the meantime should I wait until another BSOD occurs, so we can better
guess what is causing it?
Quote