Solved BSOD caused by ntoskrnl.exe

[Hykon]

I'm not seeing the optimized defaults, I haven't really tampered with anything, so would they already be set to that?

 

[essenbe]

I don't know if it will help you, but here is the XMP in my BIOS. Also look at the bottom right of the bios page and the different shortcuts to optimized defaults and other stuff is there. They should be on yours too. Almost every board I have seen has them. Optimized defaults is normally F5.

View attachment 279969

View attachment 279970

 

[Hykon]

All right, I will go back in and check again. I just finished moving the video card to the slot closer to the CPU. When I restarted, my resolution was at 800x600 rather than 1920x1080. I set it to 1920x1080 with the right click > Screen Resolution at the desktop. Do I need to re download drivers or anything for the card since it moved slots? A little screen came up saying drivers installed for the card, but I just want to be sure.

EDIT: okay, i hit F7 to set my optimized defaults, then I enabled XMP and set the timings and frequency to what you specified, and the video card is moved and now displaying as 3.0 X16 like you said, anything else?

 

[essenbe]

OK, usually when you set XMP it sets it for you. When you do it manually, you set them yourself. Was there much difference in what they set and what you set? You should be in better shape now. There will be things along and along as you learn the bios better. Learn it and don't be afraid of it. It is what basically controls everything on your computer. The better you know it, the more comfortable you will feel. As long as the memory tab on CPUZ reads the same within a couple on the frequency as the XMP value on the SPD tab, you should be good to go. The setting XMP and setting timings manually are ususally an either or. Read the manual and look aound bios. You'll get a better idea of how it works.

 

[Hykon]

Yeah, the defaults weren't much different then what you said.

The frequency was already 1600 I believe. And now CPUz shows that the timings are much more in sync.

Also, why is it that the slot makes such a difference for the video card? Could that have been the cause of all these BSODs?

As I type, I've been in the clear since switching the slots and changing the BIOS.

Am I clear to attempt using other software?

 

[essenbe]

Your manual will tell you the different slots. I could explain it to you, but it would be a little complicated. I really wouldn't thing your GPU running at X4 would cause the BSODs, but I guess t is possible. I would more think that the ram may have been an issue. The timings under the SPD tab, XMP values really need to match the memory tab. The frequency can, and often is a few numbers off, but the timings are critical. I would like you to run memtest86+ http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Run it for 8-10 passes which will take several hours. If you can, take a picture of the screen with your camera or cell phone.

Haswell is brand new technology and many of the programs are not up to speed with it. You will just have to deal with it until the software catches up. That's the price we pay for keeping up with new technology. Software is always playing catch up. You said you downloaded and installed the chipset drivers. What about the other drivers. You wll need them and also download all the important windows updates, I just don't install updates for hardware. I find them myself. Go to device manager and see if anything there has exclamation points or yellow triangles on it. If it does, you have a problem with that item. Usually you need a driver for it.

 

[Hykon]

Alright, starting memtest, will report back with a cellphone photo of the results after it runs overnight. Still BSOD free ^_^

About the drivers, the other ones were Audio and the SATA things you mentioned I didn't need before. I attempted to install the newer BIOS but when I ran the .exe it said it wasn't compatible with 64 bit Windows.

 

[Hykon]

Here is the photo of MemTest

 

[essenbe]

That's why I asked for a photo. I really don't know if it was tested properly. Look at the picture, it shows your ram as DDR- 0 and timings 19-15-15-31, Tripple Chanel and a base clock of 0. Let me see if I can find out anything. Remember what I said last night about software having to catch up to the latest technology.

Also, were you running memtest86 or memtest86+? they are different programs by different people.

 

[Hykon]

Yeah I noticed that as well. I thought it was weird. It's also saying I have an i7 32 nano-meter architecture, when it's an i5 Haswell.

Still I'm BSOD free for going on 8 or so hours.

 

[essenbe]

Well, That's great news. I say if it ain't broke, don't fix it. See how it does for a few days. I don't know if you saw the edit to my post above, but were you running memtest86 or memtest86+. Yes, they are different programs by different companies. Memtest86+ is a much better one in my opinion, and most othere here.

 

[Hykon]

I believe it was MemTest86+

EDIT: was definitely the + version

 

[Hykon]

Thank you so much to everyone that contributed. This was really scary to go through on a first time build. Thank you all for your persistent support! I'll definitely be back if there are any further issues, you all helped me a ton! Thanks again!

 

[Britton30]

I just got a Haswell i5-4670K too and I used memtest 86+ Version 5.0 RC1. See this to get it. NEW !! Memtest86+ 5.00 RC1 available ! Need betatesters !
Thanks to Anak for finding it.

 

[Hykon]

48 hours with no problems, much longer than ever, then I got the same 0xF4 BSOD. Here are the dumps. Hopefully, they aren't as regular as they were before.

 

[koolkat77]

same old..

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80087aab30, fffffa80087aae10, fffff80002d83350}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa80087aab30, Terminating object
Arg3: fffffa80087aae10, Process image file name
Arg4: fffff80002d83350, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa80087aab30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`08390e38 fffff800`02e0ad22 : 00000000`000000f4 00000000`00000003 fffffa80`087aab30 fffffa80`087aae10 : nt!KeBugCheckEx
fffff880`08390e40 fffff800`02db708b : ffffffff`ffffffff fffffa80`06d9f420 fffffa80`087aab30 fffffa80`087aab30 : nt!PspCatchCriticalBreak+0x92
fffff880`08390e80 fffff800`02d37144 : ffffffff`ffffffff 00000000`00000001 fffffa80`087aab30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`08390ed0 fffff800`02a7be93 : fffffa80`087aab30 fffff800`c0000005 fffffa80`06d9f420 00000000`029a0600 : nt!NtTerminateProcess+0xf4
fffff880`08390f50 fffff800`02a78450 : fffff800`02ac781f fffff880`08391a38 fffff880`08391790 fffff880`08391ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`083910e8 fffff800`02ac781f : fffff880`08391a38 fffff880`08391790 fffff880`08391ae0 00000000`029a2110 : nt!KiServiceLinkage
fffff880`083910f0 fffff800`02a7c282 : fffff880`08391a38 00000000`0000e7ec fffff880`08391ae0 00000000`029a1be8 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`08391900 fffff800`02a7adfa : 00000000`00000001 00000000`029a0d18 00000000`00000001 00000000`0000e7ec : nt!KiExceptionDispatch+0xc2
fffff880`08391ae0 00000000`77478e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`029a0d20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77478e3d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe

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

 

[Hykon]

Changing the memory timings seemed to erase the problem. I have no clue why it came back. I was 2 days of use with no BSOD when previously I was getting them every hour at least, if not sooner. Any ideas?

 

[koolkat77]

I would install windows on an HDD and see if it is stable.

 

[Hykon]

I tried that before and got the same 0xF4 error.

 

[Vir Gnarus]

I've been called in to assist. They should be giving me the rundown on what's happened so far in a bit, but in the meantime I looked at your last crashdumps and noticed the same issue I see with a lot of these 0xF4 bugchecks, and that's a device issue has occurred. In every case, the problem was that the storage device spontaneously disappeared (c000000e - Device does not exist). This very commonly means one of a number of things:

• A hard drive is bad (usually the one holding Windows).
• Motherboard or drive controller card is bad.
• Cabling to the hard drive (power and data) is bad or loose/dirty.
• Power supply is bad.

Best approach for this would be to first reconnect or even replace the data cables connecting your hard drives to your mobo. Also reconnect power cables. If that all doesn't work, install Windows on another drive, removing the previous drive, and test that drive out. It looks like you already have, so I reckon unless this is a cabling issue, then it's a problem with the motherboard or power supply. Unfortunately the only way to tell which is bad is by process of elimination: replacing them with trusted replacements until you find the culprit. I personally point finger at the motherboard, or drive controller card if you happen to be using that, so I'd say start with that first before working on the power supply. There's no diagnostic testing procedure besides this for those two parts that can be done outside purchasing expensive diagnostic kits. There's no software analysis tools for them, nor could I ever see there being such a thing. It's just a matter of taking the plunge and see what happens.

Analysts:

Error code c000000e shows up in stack of faulting thread every time, which the other error codes (c0000005 and c0000006) are referring too.

1: kd> [COLOR=Blue]!niemiro.rawstack[/COLOR]
dps fffff88008390000 fffff88008391c68
fffff880`08390000  fffff800`02bc9144 nt!_imp_NtOpenSymbolicLinkObject+0x5c0c
fffff880`08390008  fffff800`02ffd2ec hal!HalpTscStallExecutionProcessor+0xe8
fffff880`08390010  fffff880`08390eb8
fffff880`08390018  fffff800`02a07000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`08390020  fffff880`012391f0 Ntfs!_GSHandlerCheck_SEH
fffff880`08390028  00000000`00000004
fffff880`08390030  fffff880`0126ad70 Ntfs!rcon+0x650
fffff880`08390038  fffff880`01285600 Ntfs!__PchSym_ <PERF> (Ntfs+0x65600)
fffff880`08390040  00000000`00000000
fffff880`08390048  fffff800`02abc696 nt!iswctype_l+0x76
fffff880`08390050  ffff0088`de940c1b
fffff880`08390058  fffff880`083905b0

...

fffff880`083913a0  00000000`00000000
fffff880`083913a8  00000000`00000000
fffff880`083913b0  00000000`00000000
fffff880`083913b8  00000000`00000000
fffff880`083913c0  00000000`00000001
fffff880`083913c8  00000000`[COLOR=Red]c000000e[/COLOR]
fffff880`083913d0  00000000`00000000
fffff880`083913d8  fffff8a0`06fa5140
fffff880`083913e0  fffffa80`09996768
fffff880`083913e8  00000000`00000000
fffff880`083913f0  fffffa80`099964a0
fffff880`083913f8  fffff880`0122f85c Ntfs!NtfsExtendedCompleteRequestInternal+0x11c
fffff880`08391400  fffff880`00000001
fffff880`08391408  00000000`00000001
fffff880`08391410  fffff880`08391550
fffff880`08391418  00000000`00000000
fffff880`08391420  fffffa80`099964a0
fffff880`08391428  00000000`[COLOR=Red]c000000e[/COLOR]
fffff880`08391430  fffff880`083916b0
fffff880`08391438  fffff880`01238f89 Ntfs!NtfsProcessException+0x829
fffff880`08391440  00000000`00000000
fffff880`08391448  00000000`00000000
fffff880`08391450  fffff880`08391550
fffff880`08391458  00000000`[COLOR=Red]c000000e[/COLOR]
fffff880`08391460  fffff8a0`00000000
fffff880`08391468  fffff880`08391558
fffff880`08391470  00000000`00000002
fffff880`08391478  fffffa80`087a09f0
fffff880`08391480  00000000`00000000
fffff880`08391488  fffffa80`07589180
fffff880`08391490  fffff8a0`06fa5010
fffff880`08391498  00000000`00000000
fffff880`083914a0  00000000`00000000
fffff880`083914a8  fffff880`083915d8
fffff880`083914b0  fffff880`083916c8
fffff880`083914b8  00000000`00000002
fffff880`083914c0  00000000`00060000
fffff880`083914c8  fffff880`083914c8
fffff880`083914d0  fffff880`083914c8
fffff880`083914d8  00000000`00000000
fffff880`083914e0  00000000`00000000
fffff880`083914e8  fffffa80`099964a0
fffff880`083914f0  fffff8a0`06fa5140
fffff880`083914f8  00000000`00000000
fffff880`08391500  fffff880`08391550
fffff880`08391508  00000000`00000000
fffff880`08391510  fffff880`083916c8
fffff880`08391518  fffff880`0122c594 Ntfs!NtfsFsdRead+0x2d4
fffff880`08391520  fffff880`08391550
fffff880`08391528  fffffa80`099964a0
fffff880`08391530  fffff880`[COLOR=Red]c000000e[/COLOR]
fffff880`08391538  fffffa80`09dadd00
fffff880`08391540  fffffa80`087aab30
fffff880`08391548  fffffa80`087a3cf0
fffff880`08391550  00000000`0158070a
fffff880`08391558  00000000`00000001
fffff880`08391560  00000000`[COLOR=Red]c000000e[/COLOR]
fffff880`08391568  00000000`00000003
fffff880`08391570  00000000`00000000
fffff880`08391578  00000000`00000000
fffff880`08391580  fffffa80`07589180
fffff880`08391588  fffffa80`099964a0
fffff880`08391590  fffff880`08391550

...

1: kd> [COLOR=Blue]!error [/COLOR][COLOR=Red]c000000e[/COLOR]
Error code: (NTSTATUS) 0xc000000e (3221225486) - A device which does not exist was specified.