Solved Ntoskrnl.exe BSOD after new Windows 7 install

[carz95]

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

Also, could the GPU error become an issue?

 

[essenbe]

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 http://www.sevenforums.com/tutorials/433-disk-check.html.

 

[carz95]

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

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

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

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

STACK_TEXT:
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


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0xF4_c0000005_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_c0000005_IMAGE_wininit.exe

ANALYSIS_SOURCE: KM

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

0xF4_IOERR

2 Times

0xF4_c0000005

3 Times

0x116 (GPU Driver)

1 Time

 

[essenbe]

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

Be sure to create a System Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

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

   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

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

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[carz95]

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.

 

[essenbe]

You can, but I prefer you leaving it on for 24 hours of actual use, not just idling.

 

[carz95]

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.

Bugcheck string: DRIVER_VERIFIER_IOMANAGER_VIOLATION

Also, am I good to turn driver verifier off?

 

[essenbe]

I'll check, but that is Intel Smart Connect Technology Driver

 

[essenbe]

I've asked for more help.

 

[carz95]

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

 

[essenbe]

I asked some others for help fixing this. If you have more info, I'd love to hear it.

 

[Arc]

Hi ... can you disable/uninstall Intel Smart Connect Technology?

Disable Driver Verifier. Uninstall Intel Smart Connect Technology. Let us know how the computer is running.

More troubleshooting may be required depending on the situation.
_______________________________________

BugCheck C9, {6, 103, fffff980195dadc0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ISCTD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ISCTD64.sys
*** ERROR: Module load completed but symbols could not be loaded for ISCTD64.sys
Probably caused by : ntkrnlmp.exe ( nt!IovCompleteRequest+c2 )

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

 

[carz95]

Weird...it's not showing up in programs under control panel.

I assume it would be somewhere around here...

Note: It was installed on my PC, but then I did a clean install of Windows. I do not recall
installing it at that time.

I made sure not to install it on my new windows install.

 

[essenbe]

You may have to disable it in bios, then take care of the driver in C:/Windows\system32\DRIVERS\ISCTD64.sys you can rename it from .SYS to .BAK in which case it will be there, but Windows won't load it. or delete it.

 

[carz95]

I went into bios and disabled it. Then I renamed the file with the .bak file extension
like you mentioned. I might just end up deleting it.

Thank You very much, I hope this works out. Does it look that way?

I will update as needed.

 

[essenbe]

We hope so, just keep us updated and we'll just have to see. I hope that's what the problem was.

 

[carz95]

Well, today I got another Bsod ...something with my graphics driver.

Any suggestions?

Looks like the intel one is fixed at least...

 

[essenbe]

Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800b5f44e0, fffff88004fe223c, ffffffffc000009a, 4}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7a223c )
Followup: MachineOwner

nvlddmkm
start             end                 module name
fffff880`04840000 fffff880`05260000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 13 00:53:17 2014 (548BE25D)
    CheckSum:         009E7B4F
    ImageSize:        00A20000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[carz95]

Ah, Its my nvidia driver


I found this - should I give it a shot?

Also, all my drivers are up to date

Fix: Nvlddmkm.sys Blue Screen BSOD Error in Windows 7/8/8.1

 

[essenbe]

Reinstall a different driver using this method and see if it helps http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html