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: BSOD caused by ntoskrnl.exe

06 Aug 2013   #91
essenbe
Microsoft MVP

Windows 7 Enterprise X64/Windows 10 X64
 
 

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.


My System SpecsSystem Spec
.

06 Aug 2013   #92
Hykon

Windows 7 Home Premium 64bit
 
 

I believe it was MemTest86+

EDIT: was definitely the + version
My System SpecsSystem Spec
06 Aug 2013   #93
Hykon

Windows 7 Home Premium 64bit
 
 

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


06 Aug 2013   #94
Britton30
Microsoft MVP

Windows 7 Ultimate X64 SP1
 
 

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.
My System SpecsSystem Spec
08 Aug 2013   #95
Hykon

Windows 7 Home Premium 64bit
 
 

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.
My System SpecsSystem Spec
08 Aug 2013   #96
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

same old..
Code:
*******************************************************************************
*                                                                             *
*                        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
---------
My System SpecsSystem Spec
08 Aug 2013   #97
Hykon

Windows 7 Home Premium 64bit
 
 

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?
My System SpecsSystem Spec
08 Aug 2013   #98
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

I would install windows on an HDD and see if it is stable.
My System SpecsSystem Spec
08 Aug 2013   #99
Hykon

Windows 7 Home Premium 64bit
 
 

I tried that before and got the same 0xF4 error.
My System SpecsSystem Spec
08 Aug 2013   #100
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

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.

Code:
1: kd> !niemiro.rawstack
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`c000000e
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`c000000e
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`c000000e
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`c000000e
fffff880`08391538  fffffa80`09dadd00
fffff880`08391540  fffffa80`087aab30
fffff880`08391548  fffffa80`087a3cf0
fffff880`08391550  00000000`0158070a
fffff880`08391558  00000000`00000001
fffff880`08391560  00000000`c000000e
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> !error c000000e
Error code: (NTSTATUS) 0xc000000e (3221225486) - A device which does not exist was specified.
My System SpecsSystem Spec
Reply

 BSOD caused by ntoskrnl.exe




Thread Tools





Similar help and support threads
Thread Forum
ntoskrnl.exe has caused BSOD
I have had 4 BSOD. Today, I was streaming using to Twitch with QuickSync on a Intel i3 2120. Boom a BSOD. I was also downloading something on steam also. I have noticed something very interesting in the "BlueScreenView" Application. 3 of the .dmp files have been caused by the "ntoskrnl.exe" My...
BSOD Help and Support
BSOD at least once a day caused by ntoskrnl.exe
Hello, Lately I have been getting the BSOD a fair bit. At first it was about once a couple of weeks, then it started increasing. I did a full format of the HDD in an effort to stop it, it didn't work. It just started occurring more often. I've tried updating all of the drivers, didn't work. I've...
BSOD Help and Support
BSOD caused by ntoskrnl.exe
HI I bough this Acer V3-571G-9435 laptop on Aug 20, 2012 and replaced the original HDD with OCZ vertex 3 240GB SSD before I star it up. I installed Win7 Home Premium 64 bit version. Here is the hardware information of the laptop: CPU: intel i7-3610QM Memory: Kingston DDR3-1333 2GB & A-Data...
BSOD Help and Support
BSOD caused by ntoskrnl.exe
Windows crashed while I was playing Dragon Age Origins. Can someone help me find out which driver or whatever caused this crash? System info: Windows 7 Ultimate x64 (retail) Bought this computer a few weeks ago Let me know if you guys need any more info. Thanks a lot!
BSOD Help and Support
Help please, BSOD caused by ntoskrnl.exe
Hello, i really need your help hier. My PC is crashed and frozen randomly ( while watching movies, youtube. surf net ) and I cant do anything but hard reset. Here ist the dump file, hope that you guys can read and tell me how to fix it. My specs: AMD Phenom II 1055T 6x2,8ghz ASUS M4N68T-M LE...
BSOD Help and Support
BSOD being caused by ntoskrnl.exe
Hey guys; I searched these forums for other posts; and generally people just suggested repairing windows. When i try an repair my windows 7 (Ultimate 64bit) it tells me it cannot upgrade my system to 32bit, and yes i have been clicking x64 when i choose my system type. Ill dump the...
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 04:33.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App