Random BSOD (2 months+ old self-built Desktop) - Windows 7 x64

[hieigodsend]

Hi everyone!

First of all, it's my first time here so please kind to me if I make any mistakes. I have read all the rules and steps I could find (hopefully I didn't break or missed any of them).
To cut it short, my Desktop PC have been experiencing random BSODs. I couldn't locate the specific cause and have tried to do some long googling to try and fix it myself, but still the problem occurs. So after all the readings and test I have done, I now have a headache and frustrations, hence I come here to you guys, asking for your kind help. I will try to accommodate anything you guys need or want me to do, but of course I would rather have the easiest/quickest things to try first, and have the hardest parts (like buying new hardware or fully re-installing OS) as a last resort. I have attached the folders/files required by the BSOD posting instructions. Also some (maybe useful) things you might want to know:

1.) Usual usage of my PC is browsing (chrome), watching videos from YouTube, and playing games.
2.) Tried to use DDU (Display driver uninstaller) and then made a clean installation of my GPU's updated Driver.
3.) Installed an updated Keyboard driver, mouse firmware, and Realtek HD Audio Driver/Codecs.
4.) Made sure there aren't any new updates to install from Windows Updates or Anti-Virus.
5.) Checked PC Temperature (using HWMonitor), and didn't found anything unusual. It's also very cold here in our place.
6.) All Fans seems to be working fine. No odd noises.
7.) No overclocking or anything similar.
8.) Using updated Chrome, updated Windows Defender, and legit updated ESET NOD32 Antivirus 7.
9.) Idle CPU Usage: 1-10%, Physical Memory: 15-25%

· OS - Windows 7 x64
· None, fresh clean system pre-windows 7 installation.
· Purchased it and installed myself.
· I built my PC about 2 months ago. Only old part is the Keyboard (3-4 yrs old).
· Same time I built my system. Never re-installed it yet.

· CPU - Intel Haswell Core i5 4570 3.20GHz 6MB LGA1150
· Video Card - Gigabyte GV-N770OC-2GD GeForce GTX770 Overclocked 2GB GDDR5 PCI-E3.0
· MotherBoard - Gigabyte G1.Sniper B5 Intel B85 ATX Haswell LGA1150
· Power Supply - Corsair RM Series RM650 650W Fully Modular PSU 80Plus Gold
· Memory - Corsair CMZ8GX3M2A1600C9 Vengeance 2x4GB DDR3-1600 CL9
· CPU Cooler - Noctua NH-U12S CPU Cooler with NF-F12 PWM
· Main Drive - Samsung 840 EVO Series 250GB 2.5" SATA3 SSD (MZ-7TE250BW)
· Secondary Drive - Western Digital Caviar Blue WD10EZEX 1TB 64MB Cache SATA3
· CD Drive - ASUS DRW-24D3ST Green DVD Writer SATA
· Monitor - ASUS VS239H-J 23" 5ms LED IPS Monitor
· Mouse - Corsair Vengeance M65 FPS Laser Gaming Mouse - White
· Keyboard - Logitech G110 Gaming Keyboard

 

[blueelvis]

Hi hieigodsend & welcome to the forums ^_^,

I have analyzed your dump files and all of them reported the same error which is the VIDEO_TDR_FAILURE (116) which means that the display driver was not able to recover within the time frame provided i.e. generally 2 seconds. Below is provided the analysis of your latest dump file just for the informative purposes:-

Read More:

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


VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006a5c130, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f9cfd1c, 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`0f9cfd1c 48ff25ddb9edff jmp qword ptr [nvlddmkm+0x867700 (fffff880`0f8ab700)]


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`0278ca48 fffff880`0fd05140 : 00000000`00000116 fffffa80`06a5c130 fffff880`0f9cfd1c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0278ca50 fffff880`0fcd8867 : fffff880`0f9cfd1c fffffa80`084c2000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0278ca90 fffff880`0fd04f4f : 00000000`ffffd84d 00000000`00000080 fffffa80`06a5c130 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0278cb40 fffff880`0fdd403d : fffffa80`08fce310 00000000`00000080 00000000`00000000 fffffa80`0841a410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0278cbc0 fffff800`02f7373a : 00000000`010ae192 fffffa80`081fdb50 fffffa80`069a6040 fffffa80`081fdb50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0278cc00 fffff800`02cc88e6 : fffff800`02e52e80 fffffa80`081fdb50 fffff800`02e60cc0 fffffa80`07a8bad0 : nt!PspSystemThreadStartup+0x5a
fffff880`0278cc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16




STACK_COMMAND: .bugcheck ; kb


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


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}

The problem is related to the Video Card which is pretty obvious on seeing the output of the Dump File .
I googled for your problem a bit and I found this a viable solution of changing and increasing the TDR timeout delay. Please follow the below instructions to increase the TDR delay timeout and see if the problem is resolved or not. :-

1. In the start menu type "regedit" hit enter.
2. Navigate through regedit like this: HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet \Control\ GraphicsDrivers
3.Then create a a REG_DWORD file called TdrDelay and set the value to 60 (right click, new, DWORD)
ex. "TdrDelay"=dword:00000060 (60 seconds)
4.Then navigate to
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ GraphicsDrivers\DCI]
and Create a Value called:

"Timeout"=dword:00000060
**THEN RESTART YOUR SYSTEM TO APPLY CHANGES**

Source :- M17x-R4, BSOD, NVKFLT 116 - Alienware Forum - Alienware Club - Dell Community

Please report back whether this works or not and if it doesn't, I would be glad to help you out further ^_^.

Also to anyone senior who is reading this thread, I had a similar problem where the driver apparently kept on crashing and recovering and this was the same error I guess. Could this also solve the problem of mine?

@Seniors :- I tried my best to analyze this, still if you think that there are any problems, please feel free to correct me ^_^.

 

[hieigodsend]

Hi!

I had a black screen error a day ago which says something about GPU PCIe power port needs to be replug or something. It made me think that the cause might be that one so I opened the case and was shocked that the power port to the GPU is so loose. Don't know exactly what cause it (i really hate plugs like that, they're so hard to plug/unplug sometimes). After replugging it tightly as i could, I've been observing if I still get BSOD. This is the 3rd day that I haven't gotten it, will continue to observe. I will reopen this thread again if ever that happens.

That being said, I'm really grateful for your help. I've saved the solution you have given me and will try it asap if I get the similar problem once again!. Lots of thanks!.

 

[blueelvis]

Hi!

I had a black screen error a day ago which says something about GPU PCIe power port needs to be replug or something. It made me think that the cause might be that one so I opened the case and was shocked that the power port to the GPU is so loose. Don't know exactly what cause it (i really hate plugs like that, they're so hard to plug/unplug sometimes). After replugging it tightly as i could, I've been observing if I still get BSOD. This is the 3rd day that I haven't gotten it, will continue to observe. I will reopen this thread again if ever that happens.

That being said, I'm really grateful for your help. I've saved the solution you have given me and will try it asap if I get the similar problem once again!. Lots of thanks!.

Loose connections are always a problem. Not only they make the system unstable but there is also chance of frying up the mobo in extreme cases so I would recommend you get that port fixed ASAP ^_^.

In case of further problem, please do not hesitate to post back here ^_^