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: Several BSoD related to "ntoskrnl.exe"

01 Dec 2013   #11
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

If you are sure that the memory is free from errors, enable driver verifier for one more time. This crash dump is not providing about on which it is crashed.

BTW, it appears that Daemon Tools are still there.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3452, 402000, fffff70001084b70, 8dd00001a9c83424}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35163 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003452, The subtype of the bugcheck.
Arg2: 0000000000402000
Arg3: fffff70001084b70
Arg4: 8dd00001a9c83424

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


BUGCHECK_STR:  0x1a_3452

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  rundll32.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030ffe33 to fffff8000308ebc0

STACK_TEXT:  
fffff880`07928ee8 fffff800`030ffe33 : 00000000`0000001a 00000000`00003452 00000000`00402000 fffff700`01084b70 : nt!KeBugCheckEx
fffff880`07928ef0 fffff800`0305f892 : fffffa80`0a951b30 fffffa80`00000000 fffff8a0`000001fc fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x35163
fffff880`079297a0 fffff800`0336315a : fffff8a0`0210c060 fffff880`07929ae0 00000000`00000000 fffffa80`0a8991d0 : nt!MmCleanProcessAddressSpace+0x96
fffff880`079297f0 fffff800`033492ed : 00000000`000000ff 00000000`00000001 000007ff`fffd6000 fffffa80`0a905550 : nt!PspExitThread+0x56a
fffff880`079298f0 fffff800`030816fa : 00000000`00000001 fffff880`07929a68 00000000`0095f800 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`07929920 fffff800`03081a40 : 00000000`77cf45e8 fffff880`079299a0 fffff800`03349260 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`079299a0 fffff800`0308def7 : fffffa80`0a8991d0 00000000`77cf45c0 00000000`000000c0 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff880`07929ae0 00000000`77c42bba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0095f618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c42bba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35163
fffff800`030ffe33 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35163

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+35163

BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+35163

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



My System SpecsSystem Spec
.
01 Dec 2013   #12
Erox

Winsows 7 Ultimate x64
 
 

Allright, I double, tripplechecked to see if Daemon tools was properly uninstalled, i repeated the earlier steps of how to uninstall the SPTDs, and followed the instructions of how to manually uninstall Daemon Tools ( on this link )

I enabled verifier once again, bluescreened 3-5 seconds after start-up (after my dekstop appeared on-screen),

good news(?); dump recorded
My System SpecsSystem Spec
02 Dec 2013   #13
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Daemon Tools is still starting up with windows.
Code:
DAEMON Tools Lite    "c:\program files (x86)\daemon tools lite\dtlite.exe" -autorun    Even-PC\UpdatusUser    HKU\S-1-5-21-3575535164-2222396146-1872462359-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
The BSOD is occured on Nova Shield
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {e3, fffff880047913ef, 13f0f0360, 0}

*** WARNING: Unable to verify timestamp for NSKernel.sys
*** ERROR: Module load completed but symbols could not be loaded for NSKernel.sys
Probably caused by : NSKernel.sys ( NSKernel+113ef )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000e3, Kernel Zw API called with user-mode address as parameter.
Arg2: fffff880047913ef, Address inside the driver making the incorrect API call.
Arg3: 000000013f0f0360, User-mode address used as API parameter.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_e3

FAULTING_IP: 
NSKernel+113ef
fffff880`047913ef 85c0            test    eax,eax

FOLLOWUP_IP: 
NSKernel+113ef
fffff880`047913ef 85c0            test    eax,eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  GoogleCrashHan

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800035554ec to fffff800030c8bc0

STACK_TEXT:  
fffff880`071f9718 fffff800`035554ec : 00000000`000000c4 00000000`000000e3 fffff880`047913ef 00000001`3f0f0360 : nt!KeBugCheckEx
fffff880`071f9720 fffff800`03555fd5 : fffffa80`07def8d0 fffff800`0355732e ffffffff`80001948 ffffffff`80001948 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`071f9760 fffff800`035574ae : 00000000`002ffa01 fffff8a0`026dc6e0 00000000`00000000 fffff800`0356701d : nt!ViZwCheckAddress+0x35
fffff880`071f97a0 fffff800`03559d62 : fffff880`047913ef fffff880`071f9a20 ffffffff`80001948 fffff880`04790b0a : nt!ViZwCheckUnicodeString+0x2e
fffff880`071f97e0 fffff880`047913ef : fffff980`23272fe0 ffffffff`80001948 fffff880`071f9a20 fffff880`071f9b00 : nt!VfZwQueryValueKey+0x42
fffff880`071f9830 fffff980`23272fe0 : ffffffff`80001948 fffff880`071f9a20 fffff880`071f9b00 00000000`00001000 : NSKernel+0x113ef
fffff880`071f9838 ffffffff`80001948 : fffff880`071f9a20 fffff880`071f9b00 00000000`00001000 fffff880`071f9870 : 0xfffff980`23272fe0
fffff880`071f9840 fffff880`071f9a20 : fffff880`071f9b00 00000000`00001000 fffff880`071f9870 00000000`00000002 : 0xffffffff`80001948
fffff880`071f9848 fffff880`071f9b00 : 00000000`00001000 fffff880`071f9870 00000000`00000002 fffff880`047909ec : 0xfffff880`071f9a20
fffff880`071f9850 00000000`00001000 : fffff880`071f9870 00000000`00000002 fffff880`047909ec 00000000`00000000 : 0xfffff880`071f9b00
fffff880`071f9858 fffff880`071f9870 : 00000000`00000002 fffff880`047909ec 00000000`00000000 fffff880`071f9a60 : 0x1000
fffff880`071f9860 00000000`00000002 : fffff880`047909ec 00000000`00000000 fffff880`071f9a60 fffff880`071f9b60 : 0xfffff880`071f9870
fffff880`071f9868 fffff880`047909ec : 00000000`00000000 fffff880`071f9a60 fffff880`071f9b60 00000000`00000c40 : 0x2
fffff880`071f9870 00000000`00000000 : fffff880`071f9a60 fffff880`071f9b60 00000000`00000c40 00000000`00000000 : NSKernel+0x109ec


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  NSKernel+113ef

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NSKernel

IMAGE_NAME:  NSKernel.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  529490fd

FAILURE_BUCKET_ID:  X64_0xc4_e3_NSKernel+113ef

BUCKET_ID:  X64_0xc4_e3_NSKernel+113ef

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

3: kd> lmvm NSKernel
start             end                 module name
fffff880`04780000 fffff880`047de000   NSKernel T (no symbols)           
    Loaded symbol image file: NSKernel.sys
    Image path: NSKernel.sys
    Image name: NSKernel.sys
    Timestamp:        Tue Nov 26 17:45:57 2013 (529490FD)
    CheckSum:         0005131A
    ImageSize:        0005E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
So either dont use it, or ask the game developer about the further steps about it.
My System SpecsSystem Spec
.

13 Dec 2013   #14
Erox

Winsows 7 Ultimate x64
 
 
another bluescreen

I found some DAEMON tools lite files that I had forgotten, and found the the source of the mysterious "Nova Shield" came from my antivirus- called "Bulldog", so i just uninstalled it.

new bluescreen:
My System SpecsSystem Spec
13 Dec 2013   #15
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

If you are 100% sure that there is no error with memory, enable Driver Verifier once again.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 2cb20, 2, 7592f}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------
My System SpecsSystem Spec
13 Dec 2013   #16
Erox

Winsows 7 Ultimate x64
 
 

Thank you for a quick reply

the driver verifier gave me this blue screen:
My System SpecsSystem Spec
14 Dec 2013   #17
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

It catches the display driver this time.
Code:
BugCheck C4, {f6, 218, fffffa8008bad060, fffff8800f92a879}

*** 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+9a879 )

Followup: MachineOwner
---------
Install the NVIDIA DRIVERS 314.22WHQL only.
  • Uninstall All nvidia items in Control Panel > Programs and features
    • 3D Vision Control Driver
    • 3D Vision Driver
    • Graphics Driver
    • HD Audio Driver
    • PhysX
    • nvidia Update
    (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • Now follow Drivers - Clean Left over Files after Uninstalling
  • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Then, better you continue with DV on, to see if it catches anything else.
My System SpecsSystem Spec
14 Dec 2013   #18
Erox

Winsows 7 Ultimate x64
 
 
uh-oh

Theres been a slight problem, i dont know if im allowed to share screenshots, but this is what just showed up when i tried to boot my PC to follow your steps 5 minutes ago
My System SpecsSystem Spec
14 Dec 2013   #19
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

I have suggested this exact steps to at least 1000 of peoples. Other members also copied this instruction by quoting me and by that way it got suggested to at least 1000 more times. It never caused such a situation.

So it is not caused by following those steps.

For details, have a look here: BSOD Index
  • STOP 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
  • Usual causes: Device driver, System DLL corruption, Faulty hardware in I/O path (a disk error, faulty RAM, or a corrupted page file), BIOS
Boot into System Recovery options and try a System Restore.
My System SpecsSystem Spec
Reply

 Several BSoD related to "ntoskrnl.exe"




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD every few hours: mostly "STOP: 0x00000F4", "c00021a" & "c0000135"
Hi everyone! Yesterday my HP laptop (Windows 7) started getting BSOD with various types of errors (mostly "STOP: 0x00000F4", "STOP: 0x0000007A", "c00021a" and one "missing %hs, c0000135"). Most of the time it restarts without any issues and works fine right after the BSOD and then an hour or two...
BSOD Help and Support
BSOD - "ntkrnlmp.exe" and "ntoskrnl.exe" are the cause
Hello all, a friend was helping me to find out what this BSOD all of a sudden was from but he is out of the country now away on business. We got the point of him looking at the crash files and us using WhoCrashed, and we found that the last handful of crashes I have are all caused by...
BSOD Help and Support
"ntkrnlmp.exe" related BSOD
I bought recently this PC and it had this problem from the beginning. I tested the hardware (except power supply) and everything is working, yet i'm still getting BSOD from time to time. If you have any idea what's happening please tell me! sorry for my english
BSOD Help and Support
BSOD "Driver power state failure" caused by: ntoskrnl.exe
Hi Folks, I really hope you can help me, I followed the instructions to create the attachement. What I know so far is that this machine has BSOD'd several times...The last 2 times a ultilty called BlueScreenViewer.exe says it's due to "Driver power state failure" caused by: ntoskrnl.exe ...
BSOD Help and Support
random BSODs with new build - error related to "ntoskrnl.exe+7cc40"?
Hi A few days ago I did a new hardware build and installed W7 64 ultimate. I included a Corsair SSD as my boot drive for the speed advantage. I have done some investigation and tried to track down the cause of the BSOD but to no avail. Currently they are happening once\ twice or more...
BSOD Help and Support
"Random" BSODS after installing new GFX related to ntoskrnl.exe
Hello, Earlier this week i installed a new graphics card (ASUS GTX 560 Ti) and 4GB new memory. Every day since that i have been getting what appears to me to be random BSODS. They all seem to somehow related to ntoskrnl.exe though, but the crash messages are new everytime. I've ran memtest...
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 17:27.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App