BSOD ntoskrnl.exe+27740

jasonelmore · Mar 30, 2012

I've been having BSOD all week and it's frustrating me to no end.

First it started off with my graphics card BSOD'ing during games. This kind of BSOD would turn off all my monitors and hang the system for aprox 25-30 sec then restart. So checked Bluescreenviewer to see what was going on, and it was pointing to dxgkrnl.sys

That usually means something's wrong with

Video Card Hardware
Video Card Drivers
Power Supply directly causing the Video card to mess up

So i RMA'd the gtx 480 graphics card. While i'm waiting for it to come back i bought a cheap 9800gt off of amazon for $50. Installed it today and it ran great for several hours. Then all of the sudden playing DoTA 2 i got a BSOD. I restarted, got back in my game, 5 min later, another BSOD. This time, the BSOD was the old school kind. My screen actually went blue, and my monitor didnt turn off.

So just now, i check bluescreen viewer and it's showing ntoskrnl.exe error. "ntoskrnl.exe+27740" Bug Check String "DRIVER_IRQL_NOT_LESS_OR_EQUAL"

I have attached my minidump file. Any help would be appreciated. For now i'm going to stress test each component 1 by 1 until i can find the culprit.

My windows install is about 1 and 1/2 year, so i format is a option

What do you guys think?

jasonelmore · Mar 30, 2012

Here is my dump from the other day (the BSOD i got before i RMA'd my graphics card and replaced it). Maybe it will help

writhziden · Mar 31, 2012

Possible out of date driver:

Code:

[B][COLOR="Red"]ASACPI	fffff880`03de2000	fffff880`03dea000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys
[/COLOR][/B]

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/Win7 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.)

Thanks to JMH and zigzag3143 for the above information.

Code:

[list=1][*]Loading Dump File [D:\Kingston\BSODDmpFiles\jasonelmore\033012-22760-01\033012-22760-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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0324e000 PsLoadedModuleList = 0xfffff800`03492650
Debug session time: Fri Mar 30 18:46:51.480 2012 (UTC - 6:00)
System Uptime: 0 days 0:12:26.292
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {cec, d, 8, cec}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000cec, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000cec, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fc100
 0000000000000cec 

CURRENT_IRQL:  d

FAULTING_IP: 
+3430653566336564
00000000`00000cec ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  fffff88002f1b9d0 -- (.trap 0xfffff88002f1b9d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=bdd8ef1a3b4d3100 rbx=0000000000000000 rcx=0000000000000011
rdx=000000000001f877 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000cec rsp=fffff88002f1bb60 rbp=0000000000000000
 r8=000000000002586a  r9=0000000000000000 r10=0000000000000cec
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000cec ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032ca2e9 to fffff800032cad40

FAILED_INSTRUCTION_ADDRESS: 
+3430653566336564
00000000`00000cec ??              ???

STACK_TEXT:  
fffff880`02f1b888 fffff800`032ca2e9 : 00000000`0000000a 00000000`00000cec 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx
fffff880`02f1b890 fffff800`032c8f60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`a7f36d1f : nt!KiBugCheckDispatch+0x69
fffff880`02f1b9d0 00000000`00000cec : 00000000`00000002 fffffa80`0968c660 00000000`00000004 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02f1bb60 00000000`00000002 : fffffa80`0968c660 00000000`00000004 00000000`00000000 00000000`00000000 : 0xcec
fffff880`02f1bb68 fffffa80`0968c660 : 00000000`00000004 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
fffff880`02f1bb70 00000000`00000004 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0968c660
fffff880`02f1bb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`032c8f60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\jasonelmore\032912-28033-01\032912-28033-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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03262000 PsLoadedModuleList = 0xfffff800`034a6650
Debug session time: Thu Mar 29 18:09:26.695 2012 (UTC - 6:00)
System Uptime: 0 days 1:07:02.648
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800aa5e220, fffff8800fcbdaa4, 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+ca1aa4 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800aa5e220, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fcbdaa4, 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+ca1aa4
fffff880`0fcbdaa4 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`0516cb88 fffff880`04ea5000 : 00000000`00000116 fffffa80`0aa5e220 fffff880`0fcbdaa4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0516cb90 fffff880`04e78867 : fffff880`0fcbdaa4 fffffa80`08257000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0516cbd0 fffff880`04ea4e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0aa5e220 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0516cc80 fffff880`04f73ec1 : fffffa80`08dd3460 00000000`00000080 00000000`00000000 fffffa80`08253010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0516cd00 fffff800`03578f7a : 00000000`04156429 fffffa80`082748c0 fffffa80`05510040 fffffa80`082748c0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0516cd40 fffff800`032cf9c6 : fffff800`03453e80 fffffa80`082748c0 fffff800`03461cc0 fffff880`01261384 : nt!PspSystemThreadStartup+0x5a
fffff880`0516cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+ca1aa4
fffff880`0fcbdaa4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+ca1aa4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f4e68c4

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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


[/list]

Usually caused by drivers...
A TDR 0X116 crash. See below...

H2SO4 said:

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.

Click to expand...

The above quote was taken from http://www.sevenforums.com/crashes-debugging/25912-bsod.html#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html and proceed through each step. Let us know if you need further help.

jasonelmore · Mar 31, 2012

Thanks for your reply. I had a 2005 version of asacpi.inf

I will try it out and report in a day or two and let you know if the problem stops.

thanks again

writhziden · Mar 31, 2012

You're welcome. Let us know how the system responds. If you still have problems, read through the link I provided for the TDR stop error.

BSOD ntoskrnl.exe+27740

jasonelmore

New member

My Computer

jasonelmore

New member

My Computer

writhziden

Closed by request.

My Computer

jasonelmore

New member

My Computer

writhziden

Closed by request.

My Computer