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: Ntoskrnl.exe BSOD after new Windows 7 install

27 Dec 2014   #1
carz95

Windows 7 Home Premium 64-Bit
 
 
Ntoskrnl.exe BSOD after new Windows 7 install

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.


My System SpecsSystem Spec
.
28 Dec 2014   #2
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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.

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
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.

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.
My System SpecsSystem Spec
28 Dec 2014   #3
carz95

Windows 7 Home Premium 64-Bit
 
 

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
My System SpecsSystem Spec
.

28 Dec 2014   #4
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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.
My System SpecsSystem Spec
28 Dec 2014   #5
carz95

Windows 7 Home Premium 64-Bit
 
 

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?)
My System SpecsSystem Spec
28 Dec 2014   #6
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

I would. Temps can make it BSOD too. Plus I always run them on my machine.
My System SpecsSystem Spec
29 Dec 2014   #7
carz95

Windows 7 Home Premium 64-Bit
 
 

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.)
My System SpecsSystem Spec
29 Dec 2014   #8
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

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.
My System SpecsSystem Spec
30 Dec 2014   #9
carz95

Windows 7 Home Premium 64-Bit
 
 

Ok, thank you. In the meantime should I wait until another BSOD occurs, so we can better
guess what is causing it?
My System SpecsSystem Spec
30 Dec 2014   #10
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

That seems to be what we have to do. There was just not enough info for me to tell.
My System SpecsSystem Spec
Reply

 Ntoskrnl.exe BSOD after new Windows 7 install




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD, Windows 7 New Install - WinDbg says ntoskrnl.exe
Hi, I have had a BSOD twice now over the last 2 days. Both times analysis of minidump file says that probable cause is ntoskrnl.exe. I have run your diagnostic tool and have attached the output. Any help here would be much appreciated. I am sure the attached files give you the...
BSOD Help and Support
UNEXPECTED_KERNAL_MODE_TRAP BSOD (ntoskrnl.exe) (New Install)
So yeah, I was getting BSOD's with Windows 8 (Which only started in the last 2 months) so It thought it might just be a compatibility error but apparently not. I freshly installed windows 7, 2 days ago and it's still going for it. I can't even boot normally anymore it just instantly BSODS when I...
BSOD Help and Support
BSOD ntoskrnl.exe fresh windows 7 install
Hey guys, I have been having a problem with blue screens on this computer for a few weeks now. I finally got frustrated with it yesterday and reinstalled windows 7. The issues would happen any time I ran windows update. To fix it, I would have to restore to the oldest possible point, run the...
BSOD Help and Support
BSOD: ntoskrnl.exe; clean install corruption?
So I received a solid state drive for Christmas last year and haven't had any luck with installing it. I'm doing everything I can to rule out that it was DOA considering that at this point it's probably past warranty and I don't really wanna drop the money on a new one. Following a clean install...
BSOD Help and Support
BSOD after fresh install, ntoskrnl.exe
I really need help here guys, im out of ideas. About a week ago my computer started getting BSOD randomly while gaming or browsing the web. I thought it was a failing HDD so I re installed windows onto a new one after running stress tests on it to make sure it was good. I have run stress tests...
BSOD Help and Support
BSOD - NTOSKRNL.EXE (KMODE_EXCEPION_NOT_HANDLED) on Fresh OS Install
I got BSOD while I was watching a movie on Netflix and playing World of Warcraft. I was setting up my settings for Media Monkey and got this blue screen of death. I recently did a fresh install on my computer no more than a week ago. I am running Windows 7 Enterprise 64 Bit with Service Pack 1. I...
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 12:10.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App