Really need some help with BSOD

[iceman2291]

Hey guys, think this is my first post to this forum not much of a forum person but I thought this would be my best bet.

So a little background on my problem, I cleaned out my rig the other week (very long overdue) some of the dust had become solid on the rad! Stripped it down and cleaned up the cables, left the CPU where it was but moved everything else. PC wouldn't boot, RAM LED was lit red and no display.
Tried everything to fix it, cleared CMOS, factory bios and back to updated, tried every stick of ram individually.

PC specs at the time:
Intel i5 3570k
Sabertooth Z77 Motherboard
Corsair H100i
Antec HCG 900w
Samsung Green 16GB RAM
Seagate 240GB SSD
Nvidia GTX 780 Windforce OC

Ended up buying some Corsair Vengeance Pro 16GB and a Corsair HX750 (purely because mine wasn't modular)

The first boot was fine, booted straight away and I had a blast on the Battlefront beta, next day I boot up and get this message that my pc had suffered from a BSOD locale 2057, tried searching this and get many different answer all pointing to different things, I have crash logs etc but not sure how to read them.

Weirdest thing is, if I update my graphics driver to the current version, the display will turn off after 2-10 minutes, PC will carry on running but no display, I deleted the driver in safe mode, loaded back up and windows installed an older driver, then it goes back to having the BSOD problem between 20-40 minutes usage.

Please help I'm completely baffled with this one and really don't want to waste all this money..

 

[iceman2291]

Anyone?

 

[TimAhKin]

If you can upload the dmp files somewhere, I can take a look.

 

[Ash0787]

seems to be a difficult problem, its possible that the original reason the computer wouldn't boot is unrelated to the blue screens, its unusual to get blue screen if software hasnt been changed I would say, if I had to guess I would say the problem is due to changing things in the BIOS

Might be good to analyse the windows crash information like the previous post mentioned

 

[iceman2291]

https://drive.google.com/file/d/0B8EXNxXU7O5DeHVtYnNZZTQwRGs/view?usp=sharing

^ That's the link to the DMP file

https://drive.google.com/file/d/0B8EXNxXU7O5DTnR1RVJXRE9GNjg/view?usp=sharing

^That's the link to the sysdata file

 

[varkanoid]

Here is the dmp analysis - could just be a red herring as you usually get this when a game is running. Could be indication your GPU is going. I would do a latest driver install and make sure you tick clean installation when you do it.

Spoiler

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c70c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005293128, 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+833128
fffff880`05293128 48ff2511ddebff jmp qword ptr [nvlddmkm+0x6f0e40 (fffff880`05150e40)]

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.17298 (debuggers(dbg).141024-1500) x86fre

STACK_TEXT:
fffff880`02536a48 fffff880`040dd134 : 00000000`00000116 fffffa80`0c70c4e0 fffff880`05293128 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02536a50 fffff880`040b0867 : fffff880`05293128 fffffa80`0e97e000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02536a90 fffff880`040dcf43 : 00000000`ffffd846 ffffffff`fffe7960 fffffa80`0c70c4e0 fffff880`041acf3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02536b40 fffff880`041ad03d : fffffa80`0ea44480 00000000`00000080 00000000`00000000 fffffa80`0e97d410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02536bc0 fffff800`03716b26 : 00000000`013573c4 fffffa80`0e9ad060 fffffa80`0c749040 fffffa80`0e9ad060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02536c00 fffff800`0346df66 : fffff800`035fce80 fffffa80`0e9ad060 fffff800`0360acc0 fffffa80`0da38d01 : nt!PspSystemThreadStartup+0x5a
fffff880`02536c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+833128
fffff880`05293128 48ff2511ddebff jmp qword ptr [nvlddmkm+0x6f0e40 (fffff880`05150e40)]

SYMBOL_NAME: nvlddmkm+833128

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5581075a

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

 

[iceman2291]

Thanks for that, I'd hate for it to be going already, had it about a year.

When I try to install the latest driver, the display turns off after about 30 seconds of using the pc, the old driver stays on longer