MSI GT70 random BSOD

Nortbert · 28 May 2014

I'm experience weird BSOD, the rate is pretty random, but most of the time it happens when im playing games. I've ran the test suggested by your forums. I've also updated both graphics card drivers, and ran windows update couple time. Is there anything else that could help in case of another BSOD, I have no log of the BSOD but I know the location of the files were C:\Users\Greg\AppData\Local\Temp\WER-XXXXXXXXX.sys and C:\Windows\Minidump\XXXXXXXX.dmp (this is just a template)

Nortbert · 29 May 2014

BSOD is a 0x00000116, and is still somewhat frequent

Nortbert · 08 Jul 2014

bump

Arc · 08 Jul 2014

Hi Nortbert.

The zip you uploaded does not contain any crash dump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup program before you upload another zip.

Nortbert · 15 Jul 2014

waiting on the BSOD thanks for the reply

I also have a SFdebugFiles folder if its of any use

Arc · 15 Jul 2014

All the BSODs are caused by the nvidia display driver 337.88 WHQL.

Uninstall it, and install any version that worked good for you earlier.

Follow NVIDIA Drivers - Avoid Problems

When done, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.
_________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80077bb010, fffff8800fe33d1c, ffffffffc000009a, 4}

Unable to load image 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+98bd1c )

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: fffffa80077bb010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fe33d1c, 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+98bd1c
fffff880`0fe33d1c 48ff25ddb9edff  jmp     qword ptr [nvlddmkm+0x867700 (fffff880`0fd0f700)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`02b33a48 fffff880`0508f140 : 00000000`00000116 fffffa80`077bb010 fffff880`0fe33d1c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02b33a50 fffff880`05062867 : fffff880`0fe33d1c fffffa80`0c089000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02b33a90 fffff880`0508ef4f : fffffa80`ffffd84d 00000000`00000000 fffffa80`077bb010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02b33b40 fffff880`0515e03d : fffffa80`06b85d50 00000000`00000080 00000000`00000000 fffffa80`0c082010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02b33bc0 fffff800`0336c73a : 00000000`0259f6b5 fffffa80`0c0a38b0 fffffa80`06984890 fffffa80`0c0a38b0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02b33c00 fffff800`030c18e6 : fffff880`034a5180 fffffa80`0c0a38b0 fffff880`034b00c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02b33c40 00000000`00000000 : fffff880`02b34000 fffff880`02b2e000 fffff880`02b33460 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+98bd1c
fffff880`0fe33d1c 48ff25ddb9edff  jmp     qword ptr [nvlddmkm+0x867700 (fffff880`0fd0f700)]

SYMBOL_NAME:  nvlddmkm+98bd1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  537a8efc

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f4a8000 fffff880`1010c000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 20 04:38:44 2014 (537A8EFC)
    CheckSum:         00C1EA41
    ImageSize:        00C64000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4