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

17 Jan 2015   #21

Windows 7 Home Premium 64-Bit

If it is still the same I/O NTFS error, what should I do?

Also, could the GPU error become an issue?

My System SpecsSystem Spec
17 Jan 2015   #22

Windows 10 Pro/ Windows 10 Pro Insider

Like I said before, until we find out the cause, everything could be an issue. The graphics driver could be a cause or it could be a victim. Lets try 2 things. Please go to the Motherboard's web site and install any updated drivers, espevcially chipset and sata drivers. Next run check disk Disk Check.
My System SpecsSystem Spec
17 Jan 2015   #23

Windows 7 Home Premium 64-Bit

I checked all my drivers- they were up to date.

I had already ran chkdsk about a week or two ago and it said it had no problems

I also ran windbg and checked one of the dmp files

Here is what came up

A process or thread crucial to system operation has unexpectedly exited or been
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.
Arg1: 0000000000000003, Process
Arg2: fffffa8008cf3b30, Terminating object
Arg3: fffffa8008cf3e10, Process image file name
Arg4: fffff80002f98270, Explanatory message (ascii)

Debugging Details:

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

PROCESS_OBJECT: fffffa8008cf3b30

IMAGE_NAME: wininit.exe


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




ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

fffff880`09092e38 fffff800`03020ab2 : 00000000`000000f4 00000000`00000003 fffffa80`08cf3b30 fffffa80`08cf3e10 : nt!KeBugCheckEx
fffff880`09092e40 fffff800`02fcbabb : ffffffff`ffffffff fffffa80`084b6640 fffffa80`08cf3b30 fffffa80`08cf3b30 : nt!PspCatchCriticalBreak+0x92
fffff880`09092e80 fffff800`02f4af04 : ffffffff`ffffffff 00000000`00000001 fffffa80`08cf3b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`09092ed0 fffff800`02c91e53 : fffffa80`08cf3b30 fffff800`c0000005 fffffa80`084b6640 00000000`02f00340 : nt!NtTerminateProcess+0xf4
fffff880`09092f50 fffff800`02c8e410 : fffff800`02cdd82f fffff880`09093a38 fffff880`09093790 fffff880`09093ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`090930e8 fffff800`02cdd82f : fffff880`09093a38 fffff880`09093790 fffff880`09093ae0 00000000`ff3cb938 : nt!KiServiceLinkage
fffff880`090930f0 fffff800`02c92242 : fffff880`09093a38 00000000`02f80000 fffff880`09093ae0 00000000`ff3cf894 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`09093900 fffff800`02c90dba : 00000000`00000001 00000000`02f00a58 00000000`00000001 00000000`02f80000 : nt!KiExceptionDispatch+0xc2
fffff880`09093ae0 00000000`775a8e5d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02f00a60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775a8e5d




FAILURE_BUCKET_ID: X64_0xF4_c0000005_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_c0000005_IMAGE_wininit.exe


FAILURE_ID_HASH_STRING: km:x64_0xf4_c0000005_image_wininit.exe

FAILURE_ID_HASH: {a2dbcacb-935a-5ba8-e51d-9f8a30f04f43}

Followup: MachineOwner

I made a tally of sorts of which errors come up under BUGCHECK_STR to see if I could find a
pattern - these are from the 6 dmp files I have so far


2 Times


3 Times

0x116 (GPU Driver)

1 Time
My System SpecsSystem Spec

17 Jan 2015   #24

Windows 10 Pro/ Windows 10 Pro Insider

It's a Windows core process and will not cause a BSOD, unless it has been altered, corrupted or in some way changed. Unless I am mistaken it is the process that starts many of the Windows background processes that run in the background with Windows, among other things.
Stop code F4 in my experience is usually a hard drive, although there are several other things that can cause it, like Anti Virus, bad drivers and some software, even ram. Yours has been fairly consistent a code F4.
Microsoft Security essentials has never been know to cause a BSOD that I have ever seen.

If you would like to try and see if there is an obvious driver that is causing it. Create a manual restore point before doing anything else. It may be your only way back. The link of how to do it is below. Make sure you have the installation disk, just in case. When setting it up, sort the drivers by provider, and enable all drivers not provided by Microsoft. Don't enable any drivers from Microsoft.
warning   Warning
Be sure to create a System Restore point before proceeding further System Restore Point - Create

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
information   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.
warning   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

Tip   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
18 Jan 2015   #25

Windows 7 Home Premium 64-Bit

I started running driver verifier at around 9:30 last night.

So, if it is a driver causing the issue, a crash should happen in the next 24 hours?

Should I turn if off if it has been 24 hours without a crash?

Fingers crossed.
My System SpecsSystem Spec
18 Jan 2015   #26

Windows 10 Pro/ Windows 10 Pro Insider

You can, but I prefer you leaving it on for 24 hours of actual use, not just idling.
My System SpecsSystem Spec
18 Jan 2015   #27

Windows 7 Home Premium 64-Bit

So I did end up getting a BSOD - I didn't see it crash, I just came back to my PC after leaving it for
~15 Min and it said Windows did not shut down correctly.

The dmp file is attached, as well as a picture.

It said it was caused by ISCTD64.sys.


Also, am I good to turn driver verifier off?
My System SpecsSystem Spec
18 Jan 2015   #28

Windows 10 Pro/ Windows 10 Pro Insider

I'll check, but that is Intel Smart Connect Technology Driver
My System SpecsSystem Spec
18 Jan 2015   #29

Windows 10 Pro/ Windows 10 Pro Insider

I've asked for more help.
My System SpecsSystem Spec
18 Jan 2015   #30

Windows 7 Home Premium 64-Bit

What do you mean?

Are you asking me for info, or did you ask someone else about the issue

I can provide some more info if needed
My System SpecsSystem Spec

 Ntoskrnl.exe BSOD after new Windows 7 install

Thread Tools

Similar help and support threads
Thread Forum
Random BSoD's. Clean Windows Install. 0x124. BSV says ntoskrnl.exe
Hello everyone, I hope you are doing better than me. This might turn into somewhat of a lengthy post, but I'll try to keep it as short as possible. I've been having a problem with this build for a couple weeks now. System specs are as follows: MoBo: ASUS Rampage IV Black Edition BIOS...
BSOD Help and Support
BSOD caused by ntoskrnl.exe after clean install/windows update.
Hi, After performing a fresh install along with the basic drivers to get me going everything went fine. however after windows connected to the internet and downloaded and installed the so called important updates the system restarted just before windows logon screen it was applying the usual...
BSOD Help and Support
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

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 01:40.
Twitter Facebook Google+