Black Screen/Crash on boot up

eggbert74 · 15 Dec 2017

Hi All,

I took advantage of all the Black Friday deals and built a new 8700k Coffee Lake PC. However, today I noticed after cold booting - right before getting to the Win10 login screen, my monitor went black. Almost like it lost signal - Screen went black, my monitor went into standby, then windows eventually rebooted.

I fired up WhoCrashed and it's saying the crash was caused by a VIDEO_TDR_ERROR, which is apparently some sort of gfx card timeout. Here's an excerpt of what it says...

On Fri 12/15/2017 8:18:47 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80EB84B6028)
Bugcheck code: 0x116 (0xFFFFDE0FC7D16010, 0xFFFFF80EB84B6028, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR

I'm running the latest NVidia driver and since the computer is brand new, I'm wondering if I got a sketchy piece of hardware. This issue happens infrequently, so its hard to reproduce. Not sure where to even begin trying to track down the problem.

Some things I've tried so far:

memtest86 - Left it go for one full pass with no errors
CPU/Memory stress test using Intel Extreme Tuning Utility for about 30 min
Furmark GPU stress test for about 30 min

All of the above does not seem to trigger any issues. Nothing is overclocked in the UEFI or otherwise. Running everything at stock. When running stress tests I keep a close eye on temps with HWMonitor and everything appears to be staying cool.

Any thoughts, ideas, or guidance would really be appreciated.

Thanks

zbook · 20 Dec 2017

Hi eggbert74 ,

Welcome to Ten Forums BSOD forum.

There was 1 BSOD mini dump.
When debugged it display 1 definitive hardware driver:
nvlddmkm.sys
The bugcheck was 116.
The logs displayed other bugchecks: 117, 141
VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.

For all tests/steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.

1) Please update the system specs in the "My Computer" section:
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)

2) Open administrative command prompt and type or copy and paste:
3) sfc /scannow
4) dism /online /cleanup-image /restorehealth
5) chkdsk /scan
6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
7) Make sure that there is no over clocking while troubleshooting.

8) Sometimes there are problems in the bios that produce bsod.
9) To ensure that there are no improper bios settings please reset the bios.
10) Sometimes there can be failure to boot after resetting the bios.
11) So please make sure your files are backed up.
12) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

13) And please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

14) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

15) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 32 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
If the test duration is too long you can remove 16GB RAM and test 16 GB RAM at one time to be able to test the MB multichannel capability
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

A VIDEO_TDR_ERROR always relates to the system's graphics card (TDR = Timeout Detection Recovery).
This could be down to a number of reasons including:
drivers
heat
power to the card
a faulty PCI-e slot
defective GPU

Troubleshooting steps:
Try later and/or earlier drivers
Measure the GPU's temperatures at idle and under load
Ensure the GPU is free from dust build up and that the fan is working correctly
Reseat the GPU and check all connections are securely made
Check PSU voltages in BIOS
Try a different card in the system

16) NVIDIA nvlddmkm.sys
The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.
The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.
If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
Official Display Driver Uninstaller DDU Download
Display Driver Uninstaller Download version 17.0.7.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA

17) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
Aim for 1 hour testing.
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
Abort testing as needed for temperature changes, freezing, display artifacts, etc.
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Performance Maintenance Tutorials
Make sure that you use the Microsoft snipping tool to post images of each into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 General Tips Tutorials

18) What are the BIOS 3.3, 5 and 12 voltage values?
What are the CPU voltage and frequency?

19) Please run
CPU-Z | Softwares | CPUID
CPU-Z | Softwares | CPUID
open it and make screenshots of the following tabs
CPU
Mainboard
Memory
SPD*
Graphics

*SPD shows the details of each stick, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each stick.
Please post each screenshot in your next reply/replies.

20) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials

21) For any BSOD please post a new zip:
BSOD - Posting Instructions - Windows 10 Forums

Code:

Event[2201]:  Log Name: System  Source: Microsoft-Windows-Kernel-Boot  Date: 2017-12-15T20:19:09.758  Event ID: 29  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-47ISD8P  Description: Windows failed fast startup with error status 0xC0000001.

Code:

Event[2191]:  Log Name: System  Source: Display  Date: 2017-12-15T19:28:45.543  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-47ISD8P  Description: Display driver nvlddmkm stopped responding and has successfully recovered.Event[2192]:  Log Name: System  Source: Display  Date: 2017-12-15T19:29:11.818  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-47ISD8P  Description: Display driver nvlddmkm stopped responding and has successfully recovered.Event[2193]:  Log Name: System  Source: Display  Date: 2017-12-15T19:32:19.427  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-47ISD8P  Description: Display driver nvlddmkm stopped responding and has successfully recovered.

Code:

12/16/2017 1:19 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffffde0fc7d16010
P3: fffff80eb84b6028
P4: ffffffffc000009a
P5: 4
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\121517-6828-01.dmp
\\?\C:\Windows\TEMP\WER-14281-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4094.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4095.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40A5.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_116_f6ef26cf2c8c6d13ec82472f8ad24113d27e3_00000000_cab_031040a2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 02e606ac-6678-407a-a8a9-73320cf37be2
Report Status: 4
Hashed bucket:

Code:

12/16/2017 1:19 AM    Windows Error Reporting    Fault bucket 0x116_TdrBCR:4:C000009A_Tdr:9_IMAGE_nvlddmkm.sys_Pascal_DmaCopy0, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 228cedd4-4315-4243-9ff6-562cdbb19beb

Problem signature:
P1: 116
P2: ffffde0fc7d16010
P3: fffff80eb84b6028
P4: ffffffffc000009a
P5: 4
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\121517-6828-01.dmp
\\?\C:\Windows\TEMP\WER-14281-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4094.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4095.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER40A5.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_116_f6ef26cf2c8c6d13ec82472f8ad24113d27e3_00000000_cab_22047464

Analysis symbol: 
Rechecking for solution: 0
Report Id: 02e606ac-6678-407a-a8a9-73320cf37be2
Report Status: 268435456
Hashed bucket:

Code:

12/16/2017 12:29 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 84a3bd74-a939-4f5d-9b00-0ad8e66bed63

Problem signature:
P1: 117
P2: ffffde0fc839e4a0
P3: fffff80eb7c0c584
P4: 0
P5: 2894
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1928.dmp
\\?\C:\Windows\TEMP\WER-545250-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A8C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A9C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A9D.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_d45bc2b0cf63f1a862d8263a7f3f4eb78de73437_00000000_cab_135cb9f2

Analysis symbol: 
Rechecking for solution: 0
Report Id: eb27d6ca-2e7c-4ff1-8cc2-d1356a67b938
Report Status: 268435456
Hashed bucket:12/16/2017 12:29 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: bab4ff75-4d45-4b1c-a4a4-f564eca8d908

Problem signature:
P1: 117
P2: ffffde0fc7cd64a0
P3: fffff80eb7c0c584
P4: 0
P5: 17d4
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1929.dmp
\\?\C:\Windows\TEMP\WER-571562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE26.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE28.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE39.tmp.txt
\\?\C:\Windows\Temp\WERE624.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_ddb199ef64929b0c33ae94cf5157d99ebb8154_00000000_cab_29013e84

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5ca24b16-d794-41ea-9675-9e281fa6d7a3
Report Status: 268435456
Hashed bucket:
12/16/2017 12:32 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: c527ad10-99bf-4653-beca-33eeab8d8451

Problem signature:
P1: 117
P2: ffffde0fc7c564a0
P3: fffff80eb7c0c584
P4: 0
P5: 17bc
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1932.dmp
\\?\C:\Windows\TEMP\WER-759218-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9EDA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9EEA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9EEB.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_73cd4f88f42b79eea823287b9e188449a2a1cf6_00000000_cab_12e3fc1d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 00610fc1-d708-4641-8c11-b8acd87ca734
Report Status: 268435456
Hashed bucket:
12/15/2017 10:07 PM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: f2133b3c-df49-4734-82de-a4d78bd6c27b

Problem signature:
P1: 117
P2: ffffdb00bf14b010
P3: fffff80be1f9c584
P4: 0
P5: 444
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1706.dmp
\\?\C:\Windows\TEMP\WER-585000-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2F80.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2F80.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2F81.tmp.txt
\\?\C:\Windows\Temp\WER7F47.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_e858d1c904f2120d764bc47661d7bc45d3c670_00000000_cab_10d59bb7

Analysis symbol: 
Rechecking for solution: 0
Report Id: 98a1ddcf-5de7-4c1e-b7b3-12fa9002eb7c
Report Status: 268435456
Hashed bucket:

Code:

Name    NVIDIA GeForce GTX 1060 3GBPNP Device ID    PCI\VEN_10DE&DEV_1C02&SUBSYS_373A1458&REV_A1\4&25438C51&0&0008
Adapter Type    GeForce GTX 1060 3GB, NVIDIA compatible
Adapter Description    NVIDIA GeForce GTX 1060 3GB
Adapter RAM    (1,073,741,824) bytes
Installed Drivers    C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll
Driver Version    23.21.13.8859
INF File    oem28.inf (Section136 section)
Color Planes    Not Available
Color Table Entries    4294967296
Resolution    1920 x 1080 x 60 hertz
Bits/Pixel    32
Memory Address    0xDE000000-0xDF0FFFFF
Memory Address    0xC0000000-0xD1FFFFFF
Memory Address    0xD0000000-0xD1FFFFFF
I/O Port    0x0000E000-0x0000EFFF
IRQ Channel    IRQ 16
I/O Port    0x000003B0-0x000003BB
I/O Port    0x000003C0-0x000003DF
Memory Address    0xA0000-0xBFFFF
Driver    c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvlddmkm.sys (23.21.13.8859, 16.24 MB (17,025,992 bytes), 12/15/2017 9:58 PM)

Code:

nvlddmkm nvlddmkm.sys Tue Jun 27 15:02:17 2017 (5952B9C9)