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: Keep getting a BSOD for "ntoskrnl.exe"

01 Mar 2012   #1

Windows 7 Professional x64
 
 
Keep getting a BSOD for "ntoskrnl.exe"

I don't know what happened to my post I put here yesterday. It looks like it didn't take, so here it is again.

I am inserting my "Who Crashed" report here as well. But as far as the nvdldmkm.sys BSOD, I think it's fixed as I haven't had that one in a while. All I did was disable the High Def audio in my Display driver. But as far as this one is concerned, I don't know what is going on. I just installed 2 x 120 GB Corsair SSD drives in a RAID 0.

Any ideas?

Thanks in advance!

System Information (local)
</B>
computer name: AL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 12875550720 total
VM: 2147352576, free: 1925648384



Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 2/29/2012 4:55:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022912-17518-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800A3B4050, 0xFFFFF80004576518, 0xFFFFFA800F0E6010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 2/29/2012 4:55:08 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800A3B4050, 0xFFFFF80004576518, 0xFFFFFA800F0E6010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 2/22/2012 5:38:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022212-32448-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x801F10)
Bugcheck code: 0x116 (0xFFFFFA800CDB9010, 0xFFFFF8800FA0DF10, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 295.73
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 295.73
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 295.73 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR





Conclusion
</B>
3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 295.73 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.



My System SpecsSystem Spec
.

01 Mar 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Problem devices:
Code:
High Definition Audio Controller	PCI\VEN_10DE&DEV_0BE5&SUBSYS_14703842&REV_A1\4&2EB3824&0&0118	This device is disabled.


Possible outdated drivers... Those in red are known to cause issues with Windows 7 and should be removed; the red dates mean the driver needs to be updated ASAP:
Code:
ASACPI	fffff880`0f211000	fffff880`0f219000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys
RTCore64	fffff880`0b33a000	fffff880`0b340000	Wed May 25 00:39:12 2005 (42941d90)	00004158		RTCore64.sys
PxHlpa64	fffff880`01095000	fffff880`010a0700	Wed Oct 17 12:25:02 2007 (4716537e)	00015810		PxHlpa64.sys
wdcsam64	fffff880`0402d000	fffff880`04030880	Wed Apr 16 02:39:08 2008 (4805bb2c)	0000d887		wdcsam64.sys
ALSysIO64	fffff880`08018000	fffff880`08020000	Sun Apr 19 13:41:04 2009 (49eb7e50)	0000bbad		ALSysIO64.sys
ASACPI: See below...
RTCore64: RivaTuner/EVGA Precision/MSI Afterburner (known issues w/Windows 7)... Remove from the system.
PxHlpa64.sys
wdcsam64.sys
ALSysIO64.sys



Code:
  1. Loading Dump File [D:\Kingston\BSODDmpFiles\Homeuser66\Windows_NT6_BSOD_jcgriff2\022912-17518-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`04576500? Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03090670 Debug session time: Wed Feb 29 09:55:08.101 2012 (UTC - 7:00) System Uptime: 0 days 2:30:52.036 Loading Kernel Symbols ............................................................... ................................................................ ......................................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa800a3b4050, fffff80004576518, fffffa800f0e6010} *** WARNING: Unable to verify timestamp for iaStorV.sys *** ERROR: Module load completed but symbols could not be loaded for iaStorV.sys Probably caused by : iaStorV.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa800a3b4050, Physical Device Object of the stack Arg3: fffff80004576518, Functional Device Object of the stack Arg4: fffffa800f0e6010, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: iaStorV.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c11875b MODULE_NAME: iaStorV FAULTING_MODULE: fffff880010b9000 iaStorV CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: fffff800`045764c8 fffff800`02f35cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0a3b4050 fffff800`04576518 : nt!KeBugCheckEx fffff800`045764d0 fffff800`02ed35fc : fffff800`04576600 fffff800`04576600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90 fffff800`04576570 fffff800`02ed3496 : fffffa80`0d7afc68 fffffa80`0d7afc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`045765e0 fffff800`02ed337e : 00000015`136f1f87 fffff800`04576c58 00000000`0008da9f fffff800`03041668 : nt!KiProcessExpiredTimerList+0xc6 fffff800`04576c30 fffff800`02ed3167 : 00000005`7ee647c5 00000005`0008da9f 00000005`7ee647fd 00000000`0000009f : nt!KiTimerExpiration+0x1be fffff800`04576cd0 fffff800`02ebf96a : fffff800`0303de80 fffff800`0304bcc0 00000000`00000000 fffff880`0ffa4db0 : nt!KiRetireDpcList+0x277 fffff800`04576d80 00000000`00000000 : fffff800`04577000 fffff800`04571000 fffff800`04576d40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_3_disk_IMAGE_iaStorV.sys BUCKET_ID: X64_0x9F_3_disk_IMAGE_iaStorV.sys Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\Homeuser66\Windows_NT6_BSOD_jcgriff2\022212-32448-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e05000 PsLoadedModuleList = 0xfffff800`0304a670 Debug session time: Wed Feb 22 10:38:28.861 2012 (UTC - 7:00) System Uptime: 0 days 0:00:48.923 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800cdb9010, fffff8800fa0df10, ffffffffc000009a, 4} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** 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+801f10 ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa800cdb9010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8800fa0df10, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000004, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+801f10 fffff880`0fa0df10 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`05306b88 fffff880`0ff1c000 : 00000000`00000116 fffffa80`0cdb9010 fffff880`0fa0df10 ffffffff`c000009a : nt!KeBugCheckEx fffff880`05306b90 fffff880`0feef867 : fffff880`0fa0df10 fffffa80`0c3d0000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`05306bd0 fffff880`0ff1be0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`0cdb9010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3 fffff880`05306c80 fffff880`0ffeaec1 : fffffa80`0bf84580 00000000`00000080 00000000`00000000 fffffa80`0c3b5410 : dxgkrnl!TdrResetFromTimeout+0x23 fffff880`05306d00 fffff800`0311cfee : 00000000`01f2dbc9 fffffa80`0bf36b60 fffffa80`09d40040 fffffa80`0bf36b60 : dxgmms1!VidSchiWorkerThread+0x101 fffff880`05306d40 fffff800`02e735e6 : fffff800`02ff7e80 fffffa80`0bf36b60 fffff800`03005cc0 fffff880`0126b384 : nt!PspSystemThreadStartup+0x5a fffff880`05306d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+801f10 fffff880`0fa0df10 4883ec28 sub rsp,28h SYMBOL_NAME: nvlddmkm+801f10 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68 FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
  1. This crash is due to the system sending a device driver the signal to turn itself off or turn itself on during a power cycle such as during sleep, hibernate, shut down, or startup. The device or device driver failed to respond to the signal and so the system crashed to force the power state. Could be caused by either the devices themselves or their drivers.
  2. This is a 0x116 TDR crash... see below.

For the first crash:
  • Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:
    1. Going to the Asus motherboard support site
      When you reach the website:
    2. Scroll down the page and click Utilities
    3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
    4. Search for "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (without quotes)
    5. Download and install the driver.
    6. After installation is complete, verify that it installed correctly.
      • Click Start Menu
      • Click My Computer
      • Go to C:\WIndows\System32\drivers\
      • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

    Thanks to JMH and zigzag3143 for the above information.


  • Update all Intel drivers using the Intel® Driver Update Utility



For the second crash:
Quote   Quote: Originally Posted by H2SO4 View Post
These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.
The above quote was taken from http://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.
My System SpecsSystem Spec
02 Mar 2012   #3

Windows 7 Professional x64
 
 

Thanks Writhziden! Especially for taking the time to help me out with all this info.

Quote:
ASACPI: See below...
RTCore64: RivaTuner/EVGA Precision/MSI Afterburner (known issues w/Windows 7)... Remove from the system.
PxHlpa64.sys
wdcsam64.sys
ALSysIO64.sys
I use the MSI Afterburner to help monitor my system Temp and such. Do you have any suggestions to something better? I used the ASUS one in the past, but it kept on giving me FALSE Alerts.

Pxhlpa64-not sure what to do with this one?
wdcsam64-I have already updated the Firmware and Drivers from their website a week ago, I just got this drive last week, so not sure what to do here either.
ALSysIO64-Updated to 1.0 ver. now.


Quote:
For the first crash:
Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:
Going to the Asus motherboard support site
When you reach the website:
Scroll down the page and click Utilities
Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
Search for "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (without quotes)
Download and install the driver.
After installation is complete, verify that it installed correctly.
Click Start Menu
Click My Computer
Go to C:\WIndows\System32\drivers\
Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)
Also, Thanks to JMH and zigzag3143 for the above information as well.

I have downloaded and installed this update, I thought I did this when I installed my 2xSSD's. I might have on my first install, but forgot to when I started all over again.

Verified: 5/14/2009

Intel is still "Installing" the "Automatically identify and find drivers" for this entire post I am typing up. I'll get back to you on this one....lol....using Google Chrome, will try a different browser next.

Update: IE9 worked better, it only found my RAID Drivers needed to be updated, also, which I thought I did when I installed 2 weeks ago..Everything else was "This device is unknown or unsupported. Please contact the manufacturer for possible updates."

Quote:
For the second crash:
Quote: Originally Posted by H2SO4
These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.
The above quote was taken from BSOD, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.
I have a Thermaltake Spedo Case with 8 fans inside. One blowing directly on my Video card, which the Temp is 50 Cel, 120 Far, when not gaming. In game it's a little warmer, but the BSOD Crash was when I was afk and not in game. I will still look into this one...
My System SpecsSystem Spec
.


02 Mar 2012   #4

Windows 7 Home Premium 64 Bit
 
 

I wouldn't worry too much about the other three outdated drivers as they are not as important. The Western Digital driver could be an erroneous reading of the date; that happens sometimes during uploading/crash report generation/debugging (not sure which of these three is to blame, but sometimes the dates are not accurate).

Definitely recommend removing MSI Afterburner and replacing with one/all of the following (if you do all, you can choose which seems most accurate for your system and remove the rest):
My System SpecsSystem Spec
02 Mar 2012   #5

Windows 7 Professional x64
 
 

Thanks again! I will look at these three....
My System SpecsSystem Spec
Reply

 Keep getting a BSOD for "ntoskrnl.exe"




Thread Tools



Similar help and support threads for2: Keep getting a BSOD for "ntoskrnl.exe"
Thread Forum
Solved [SOLVED] random BSOD around "ntoskrnl.exe+7cc40" BSOD Help and Support
BSOD - "ntkrnlmp.exe" and "ntoskrnl.exe" are the cause BSOD Help and Support
BSOD randomly strikes when gaming, "ntoskrnl.exe"? BSOD Help and Support
BSOD "Driver power state failure" caused by: ntoskrnl.exe BSOD Help and Support
BSOD at "random": 0x1a, 0x50, 0x3b ntoskrnl.exe+7cc80 BSOD Help and Support
Solved BSOD 0X0000009F, "ntoskrnl.exe" at random times BSOD Help and Support
Solved No BSOD. Endless startup repair loop. "ntoskrnl.exe corrupted" 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 05:29 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33