Wild guess.. videocard, during Crysis

[WolfSoul]

Auto-reboot, no blue screen just plain black

 

[WolfSoul]

Any ideas

 

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\WolfSoul\Windows_NT6_BSOD_jcgriff2\012112-16520-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*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`03652000 PsLoadedModuleList = 0xfffff800`03897670
Debug session time: Fri Jan 20 21:00:07.826 2012 (UTC - 7:00)
System Uptime: 0 days 2:09:43.732
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8013680010, fffff88010561330, 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+cff330 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8013680010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010561330, 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+cff330
fffff880`10561330 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`08fbab88 fffff880`03496000 : 00000000`00000116 fffffa80`13680010 fffff880`10561330 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`08fbab90 fffff880`03469867 : fffff880`10561330 fffffa80`10db6000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`08fbabd0 fffff880`03495e0f : fffffa80`ffffd84d fffff800`00b96080 fffffa80`13680010 fffff880`03564dc0 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`08fbac80 fffff880`03564ec1 : fffffa80`0dd9a010 00000000`00000080 00000000`00000000 fffffa80`10db2010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`08fbad00 fffff800`03969fee : 00000000`027c0f27 fffffa80`10de5060 fffffa80`09d61040 fffffa80`10de5060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`08fbad40 fffff800`036c05e6 : fffff800`03844e80 fffffa80`10de5060 fffff800`03852cc0 fffff880`01a2d384 : nt!PspSystemThreadStartup+0x5a
fffff880`08fbad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+cff330
fffff880`10561330 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+cff330

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4eece814

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Follow the steps to do http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html since your error was a STOP 0x116 error. The first three posts of that thread by usasma should be followed closely.

Missed something pretty major in my post...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/Win7 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.

ASACPI	fffff880`03430000	fffff880`03438000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys

 

[WolfSoul]

Thanks man, just had another one so Im going to update that ATK Weird that they don't have one up on the Rampage page

 

[WolfSoul]

Confirmed it works.. just switched to driver not repsonding.. but that's an nvidia driver issue

 

[writhziden]

Confirmed it works.. just switched to driver not repsonding.. but that's an nvidia driver issue

Alright, let us know if you want any further help with the nVidia driver. Good luck!

 

[WolfSoul]

It's not bsod anymore.. :lol: I don't know, just seem to run into troubles of various kinds when I play Crysis

 

[writhziden]

You're welcome to upload the crash reports again and we can take a look.

 

[WolfSoul]

Might be an application isssue this time, usually crysis crashes, earlier also right after crysis did it msn followed

 

[writhziden]

Try the steps to http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html and determine which application/service is causing the conflict.

 

[WolfSoul]

Could this be because I changed my pagefile?

 

[writhziden]

Could this be because I changed my pagefile?

It may be. How did you change it?

 

[WolfSoul]

Since Im running 12 Gb RAM I figured the automatic setting for PF chips out a big chunk of my HD, had 1/2 GB earlier now going to try 4 GB

 

[writhziden]

Since Im running 12 Gb RAM I figured the automatic setting for PF chips out a big chunk of my HD, had 1/2 GB earlier now going to try 4 GB

Your pagefile size is supposed to be the size of your physical memory plus 1 MB, so it should be 12 GB + 1 MB.

 

[WolfSoul]

Well the 4 Gb seemed to make the crash happen faster..

 

[writhziden]

What happens if you set back to defaults?

 

[WolfSoul]

Ok so at least my ATK thing is fixed but Im giving up on the crysis thing
Default, if that's let Windows manage the Pf I tried that too.. no success

 

[writhziden]

I also just went through your application error logs. You should use the fixit tool provided for Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2 to resolve that error.

 

[WolfSoul]

Well I got technet and burn my isos from there.. so that ID 10 thingy will probably be on my pc all the time

 

[WolfSoul]

Also Ive checked the crysis/pagefile/memory/crash thing on google.. apparently once you change your pagefile and get crashes/erros changing your pagefile won't do a thing..