BSOD playing games/graphics under load

Zilberg · 22 May 2015

Hi,

Recently upgraded my computer - Below specs:

Windows 7 Ultimate x64
Intel 4790k not OC
2133 Corsair Vengeance Pro 8gb x2
2x MSI GTX680 Twin Frozr (Original was in previous build - Bought second one used)
1000w EVGA Platinum P2 PSU

BSOD only appears when running anything graphics intensive (playing assetto corso/project cars)

More recently, I attempted to OC the cards to:
+100 Core Clock
+0 Memory

After running Kombustor for approximately 2mins, cards reached 79degrees Celsius and BSOD..

Any help is appreciated.

DMP files attached

Thanks,
Luke

Arc · 23 May 2015

Try to roll back the display driver to an earlier version? It looks like the latest display driver is causing issues for you.

Report us for any further BSOD after doing it.
_________________________________________

Code:

BugCheck 50, {fffffb240ff322d0, 0, fffff880058f8a3c, 7}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+eca3c )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffb240ff322d0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880058f8a3c, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310b100
GetUlongFromAddress: unable to read from fffff8000310b1c0
 fffffb240ff322d0 Nonpaged pool

FAULTING_IP: 
nvlddmkm+eca3c
fffff880`058f8a3c 428b840174230000 mov     eax,dword ptr [rcx+r8+2374h]

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff880065992f0 -- (.trap 0xfffff880065992f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=000000a3ffffff5c
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff880058f8a3c rsp=fffff88006599480 rbp=fffff880065994f0
 r8=fffffa800ff30000  r9=fffff88005f34b78 r10=fffff88006599190
r11=0000000000000005 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nvlddmkm+0xeca3c:
fffff880`058f8a3c 428b840174230000 mov     eax,dword ptr [rcx+r8+2374h] ds:fffffb24`0ff322d0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f49552 to fffff80002ecea40

STACK_TEXT:  
fffff880`06599188 fffff800`02f49552 : 00000000`00000050 fffffb24`0ff322d0 00000000`00000000 fffff880`065992f0 : nt!KeBugCheckEx
fffff880`06599190 fffff800`02eccb6e : 00000000`00000000 fffffb24`0ff322d0 00000000`000a2c00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40221
fffff880`065992f0 fffff880`058f8a3c : 00000000`000151a0 fffffa80`0ff1f000 fffffa80`10d09000 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`06599480 00000000`000151a0 : fffffa80`0ff1f000 fffffa80`10d09000 00000000`00000002 00000000`000151a0 : nvlddmkm+0xeca3c
fffff880`06599488 fffffa80`0ff1f000 : fffffa80`10d09000 00000000`00000002 00000000`000151a0 fffffa80`0ff1f000 : 0x151a0
fffff880`06599490 fffffa80`10d09000 : 00000000`00000002 00000000`000151a0 fffffa80`0ff1f000 00000000`00000002 : 0xfffffa80`0ff1f000
fffff880`06599498 00000000`00000002 : 00000000`000151a0 fffffa80`0ff1f000 00000000`00000002 fffff880`058f8eb8 : 0xfffffa80`10d09000
fffff880`065994a0 00000000`000151a0 : fffffa80`0ff1f000 00000000`00000002 fffff880`058f8eb8 00000000`00000000 : 0x2
fffff880`065994a8 fffffa80`0ff1f000 : 00000000`00000002 fffff880`058f8eb8 00000000`00000000 fffff8a0`0ce8451d : 0x151a0
fffff880`065994b0 00000000`00000002 : fffff880`058f8eb8 00000000`00000000 fffff8a0`0ce8451d 00000000`00000000 : 0xfffffa80`0ff1f000
fffff880`065994b8 fffff880`058f8eb8 : 00000000`00000000 fffff8a0`0ce8451d 00000000`00000000 00000000`0007fdf5 : 0x2
fffff880`065994c0 00000000`00000000 : fffff8a0`0ce8451d 00000000`00000000 00000000`0007fdf5 fffffa80`00000001 : nvlddmkm+0xeceb8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+eca3c
fffff880`058f8a3c 428b840174230000 mov     eax,dword ptr [rcx+r8+2374h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+eca3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55515e64

FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+eca3c

BUCKET_ID:  X64_0x50_nvlddmkm+eca3c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_nvlddmkm+eca3c

FAILURE_ID_HASH:  {d6c4b7a9-3a33-b260-f7a4-4f4550ed207b}

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

6: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0580c000 fffff880`062c7000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 12 07:29:00 2015 (55515E64)
    CheckSum:         00A86612
    ImageSize:        00ABB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4