BSOD after connecting 2nd monitor

txknud · 27 Jun 2017

I have had the same error (DPC_WATCHDOG_VIOLATION) popping up for over a month. I have had a tech out 3 times changing the video card, PSU, fan, motherboard, and memory, have been on the phone with Microsoft techs multiple times as well. I have checked the drivers with driver support recommended by Microsoft, run diagnostics from the Dell site, as well as refreshed windows 4 times. The last time I wiped my computer I had only one monitor connected. I verified each monitor worked individually as well as the monitor cables individually on each monitor. Computer stayed on, no problems for several hours. I connect a second monitor and 5-10 minutes after starting I receive the bsod with the same error. At this time what I am getting is that it is a software issue from the Dell techs and it is a hardware issue from the Microsoft techs and it seems the techs as well as myself are at a loss...literally, my computer is useless.
I am attaching the file as requested and pray someone can help with this problem.
Thank you very much for any assistance provided.
Attachment 141409

BSODHunter · 28 Jun 2017

Hi,

Code:

0x00000133:    DPC_WATCHDOG_VIOLATION (27.06.2017 07:59:05) [Windows 10] 
 
CAUSED BY:     nvlddmkm.sys [1.05.2017] * nVidia Video drivers * => http://www.nvidia.com/Download/index.aspx  
 
PROCESS:       System 
 
 
============================================================================================================== 
 
 
0x00000133:    DPC_WATCHDOG_VIOLATION (27.06.2017 07:48:25) [Windows 10] 
 
CAUSED BY:     nvlddmkm.sys [1.05.2017] * nVidia Video drivers * => http://www.nvidia.com/Download/index.aspx  
 
PROCESS:       System

Code:

2017-06-26T16 41:21.695  Display driver nvlddmkm stopped responding and has successfully recovered.: .  
2017-06-27T00 42:15.093  Display driver nvlddmkm stopped responding and has successfully recovered.: .  
2017-06-27T00 42:16.255  Display driver nvlddmkm stopped responding and has successfully recovered.: .  
2017-06-27T01 59:25.922  Display driver nvlddmkm stopped responding and has successfully recovered.: .

As u can see the nvidia driver is shown as the cause in those two bsod dumps. Eventlog is showing me GPU drivers errors too. The question is now if the driver itself is the culprit or something else which is crashing the nvidia driver.

First step would be trying another driver version. Try an older one from 2016. But use DDU for reinstall

Display Driver Uninstaller: How to use
Display Driver Uninstaller (DDU) is a small software that can help the user to uninstall the display driver from the users PC. It can uninstall the driver for all the lead display chip developers, viz. Nvidia, AMD and Intel.

txknud · 28 Jun 2017

THANK YOU, THANK YOU, THANK YOU!!! I hope I'm not jinxing anything, but...I watched a whole movie, played a game, and...NO CRASH!!! You made my night! I could hug you right now I'm so happy! I'm going to start downloading all my software now. Microsoft and Dell needs to consult with YOU!
While I did not uninstall the drivers listed, this did make me think to actually look on the NVIDIA website for drivers available. There were two newer drivers than the one I had, so much for DriverSupport providing the latest and greatest drivers. I will be writing to Microsoft Driver Support to let them know the headache they caused me

Again, thank you! It has been a month of headache for an easy fix, I should have come here sooner.

txknud · 28 Jun 2017

Ok, so I spoke too soon. It is not happening as often but maybe once a day now. Ran the bsod debug tool and attached the results.
Thank you for any help.

Attachment 141570

BSODHunter · 28 Jun 2017

I wrote nothing because I found it good to wait a few ours. But it seems the nvidia driver is not the cause (not directly).

Can you provide us with the kernel memory dump please? Its located in C:\Windows\MEMORY.DMP.
You can upload it to an cloud service like dropbox or onedrive.

zbook · 28 Jun 2017

Code:

BugCheck 133, {1, 1e00, fffff8002bffd348, 0}*** 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+1aa9ed )

Code:

BugCheck 133, {1, 1e00, fffff800ecffd348, 0}*** 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+4e5ddc )

Code:

BugCheck 133, {1, 1e00, fffff801487e6348, 0}*** 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+1aa0c9 )

Code:

BugCheck 133, {1, 1e00, fffff800ecc76348, 0}*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

Code:

BugCheck 133, {1, 1e00, fffff803d3be2348, 0}*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : memory_corruption

nvlddmkm.sys

nVidia Video drivers

http://www.nvidia.com/Download/index.aspx
Get from OEM for laptops

Code:

ScriptedDiagFailure

Code:

HDAUDIO\FUNC_01&VEN_10DE&DEV_0040&SUBSYS_10DE095B&REV_1001

RealtekDEV_0662
HDAUDIO\FUNC_01 Drivers Download for Windows 10, 8, 7, XP, Vista

Code:

LKD_0x1A1_WIN32K_CALLOUT_WATCHDOG_nt!IopLiveDumpEndMirroringCallback

Code:

Fault bucket 0x133_ISR_dxgkrnl!DpiFdoLineInterruptRoutine

dxgkrnl.sys

DirectX Graphics Kernel

Windows Update

dxgmms2.sys

DirectX Graphics MMS
OS: Win10TP

Windows Update

Code:

Faulting application name: Battle.net Helper.exe

The graphics driver or the graphics card appear to be the one of the problems (nvlddmkm, dxgkrnl and dxgmms2).
The other problem signature appears to be the HDAudio driver which on google search is related to Realtek.

Open administrative command prompt and type or copy and paste:

1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)

2) sfc /scannow

3) dism /online /cleanup-image /restorehealth

4) chkdsk /scan

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 copy > paste into the thread

5) Uninstall all Realtek drivers and reinstall

6) Uninstall all Nvidia drivers again and reinstall again

7) Run memtest86+ version 5.01 for at least 8 runs.
This may take hours so plan to run it overnight.
http://www.memtest.org/https://answe...f-ecc7b7ff6461

When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.

8) Make sure that there is no over clocking while troubleshooting.

Sometimes there are problems in the bios that produce bsod.
The bios in your computer: BIOS Version/Date American Megatrends Inc. P2.00, 9/4/2015
Please check to see if this is the most up to date version.

To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios. So please make sure your files are backed up. Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free
And please create a restore point.

9) Once the bios is reset and there is no overclocking:
Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer

10) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials: FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials

All of these test should be done with the bios reset and no over clocking.
For each of the above tests please record maximum temperatures.
And please make sure that you use the Microsoft snipping tool to post images of each into the thread.

txknud · 07 Jul 2017

Sorry this took so long but had some interruptions.
Dell installed a new hard drive and provided a usb with a clean install of Windows 10.
Ran another BSOD test and attaching as well

Microsoft 10 v1703
OS Build 15063.413

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

I was not able to get memtest86+ to work for some reason.
I used the Windows ram test version and all tested good.

C:\WINDOWS\system32>winver

C:\WINDOWS\system32>sfc/scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online/cleanup-image/restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Error: 87

The online/cleanup-image/restorehealth option is unknown.
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>DISM.exe/?

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

DISM.exe [dism_options] {Imaging_command} [<Imaging_arguments>]
DISM.exe {/Image:<path_to_offline_image> | /Online} [dism_options]
{servicing_command} [<servicing_arguments>]

DESCRIPTION:

DISM enumerates, installs, uninstalls, configures, and updates features
and packages in Windows images. The commands that are available depend
on the image being serviced and whether the image is offline or running.

GENERIC IMAGING COMMANDS:

/Split-Image - Splits an existing .wim or .ffu file into multiple
read-only split WIM/FFU files.
/Apply-Image - Applies an image.
/Get-MountedImageInfo - Displays information about mounted WIM and VHD
images.
/Get-ImageInfo - Displays information about images in a WIM or VHD
file.
/Commit-Image - Saves changes to a mounted WIM or VHD image.
/Unmount-Image - Unmounts a mounted WIM or VHD image.
/Mount-Image - Mounts an image from a WIM or VHD file.
/Remount-Image - Recovers an orphaned image mount directory.
/Cleanup-Mountpoints - Deletes resources associated with corrupted
mounted images.
WIM COMMANDS:

/Apply-CustomDataImage - Dehydrates files contained in the custom data image.
/Capture-CustomImage - Captures customizations into a delta WIM file on a
WIMBoot system. Captured directories include all
subfolders and data.
/Get-WIMBootEntry - Displays WIMBoot configuration entries for the
specified disk volume.
/Update-WIMBootEntry - Updates WIMBoot configuration entry for the
specified disk volume.
/List-Image - Displays a list of the files and folders in a
specified image.
/Delete-Image - Deletes the specified volume image from a WIM file
that has multiple volume images.
/Export-Image - Exports a copy of the specified image to another
file.
/Append-Image - Adds another image to a WIM file.
/Capture-Image - Captures an image of a drive into a new WIM file.
Captured directories include all subfolders and
data.
/Get-MountedWimInfo - Displays information about mounted WIM images.
/Get-WimInfo - Displays information about images in a WIM file.
/Commit-Wim - Saves changes to a mounted WIM image.
/Unmount-Wim - Unmounts a mounted WIM image.
/Mount-Wim - Mounts an image from a WIM file.
/Remount-Wim - Recovers an orphaned WIM mount directory.
/Cleanup-Wim - Deletes resources associated with mounted WIM
images that are corrupted.

IMAGE SPECIFICATIONS:

/Online - Targets the running operating system.
/Image - Specifies the path to the root directory of an
offline Windows image.

DISM OPTIONS:

/English - Displays command line output in English.
/Format - Specifies the report output format.
/WinDir - Specifies the path to the Windows directory.
/SysDriveDir - Specifies the path to the system-loader file named
BootMgr.
/LogPath - Specifies the logfile path.
/LogLevel - Specifies the output level shown in the log (1-4).
/NoRestart - Suppresses automatic reboots and reboot prompts.
/Quiet - Suppresses all output except for error messages.
/ScratchDir - Specifies the path to a scratch directory.

For more information about these DISM options and their arguments, specify an
option immediately before /?.

Examples:
DISM.exe /Mount-Wim /?
DISM.exe /ScratchDir /?
DISM.exe /Image:C:\test\offline /?
DISM.exe /Online /?

C:\WINDOWS\system32>chkdsk/scan
The type of the file system is NTFS.
Volume label is OS.

Stage 1: Examining basic file system structure ...
349952 file records processed.
File verification completed.
11186 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
485780 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
67915 data files processed.
CHKDSK is verifying Usn Journal...
40328184 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

2860426 MB total disk space.
112155316 KB in 270935 files.
207748 KB in 67916 indexes.
0 KB in bad sectors.
549202 KB in use by the system.
65536 KB occupied by the log file.
2750160 MB available on disk.

4096 bytes in each allocation unit.
732269153 total allocation units on disk.
704041087 allocation units available on disk.

C:\WINDOWS\system32>

Attachment 142919
Attachment 142920
The BIOS is up to date
The attached pictures are of the before and during of the FurMark Stress Test.
BSOD occurred 3:07 into the test.

*Edit: I forgot to mention, this all only happens after I attach a second monitor

Thank you for any help provided

txknud · 07 Jul 2017

@bsod Hunter
I was unable to find the .dmp files requested.
I did a search on my pc and no luck.
Sorry

zbook · 07 Jul 2017

Code:

7/6/2017 5:26 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 2dcb9098-e524-4997-9200-3c7048c61dfb

Problem signature:
P1: 141
P2: ffffc582bf7e8010
P3: fffff8039949c584
P4: 0
P5: 28e0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170706-1225.dmp
\\?\C:\Windows\Temp\WER-7615671-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER411B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER411B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER412C.tmp.txt
\\?\C:\Windows\Temp\WER672E.tmp.WERDataCollectionStatus.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 29f06171-cc8e-45ba-987e-8f6abeab2579
Report Status: 268435456
Hashed bucket:

Please report the steps that you had performed to uninstall and reinstall Nvidia drivers.
Did you use the Dell web site with you computers serial or product number and operating system?
Or did you use the Nvidia web site?

Are you over clocking?
Did you reset the bios?
Is the bios up to date?

Find a flash drive that you are able to format.
Follow the steps on this web site to perform the Memtest86+ for 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
If you have any difficulty please report in the thread.

Code:

Event[1395]:  Log Name: System
  Source: volmgr
  Date: 2017-07-07T14:30:57.036
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-65QN978
  Description: 
Dump file creation failed due to error during dump creation.

The bsod minidump did not appear in the recent zip file.
Make sure dumps are optimally configured to save.
Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure uncheck automatically restart See this link: BSOD Finding and fixing them - Microsoft Community: BSOD Finding and fixing them - Microsoft Community

Download and install Whocrashed: http://www.resplendence.com/whocrashed
Click analyze and post the latest information into the thread.
Click on tools > crash dump test > ACCEPT > report into the thread whether is was able to process the dump test

txknud · 08 Jul 2017

Process of uninstalling and reinstalling NVIDIA drivers:
Downloaded DDU. Rebooted to safe mode and selected clean and restart (It was set to NOT install drivers).
After restart, I went to NVIDIA’s web site and downloaded the most current driver for the GTX 690 for Windows 10 64-bit. Version 384.76 Release 2017.6.29.
Selected the download and saved the driver to my NVIDIA folder and began an express install. After install, I opened the GEFORCE Experience to ensure latest driver was installed.

I am not overclocking. I reset the bios prior to reinstalling Windows 10 with the usb provided by Dell.
The bios is up to date based on the Dell website. The bios is A11 and A11 is the driver available for download.

Using a freshly formatted usb, I downloaded Memtest86+ V5.01 (27/09/2013) auto-installer for USB key onto my computer and installed memtest to the usb drive. It stated it was bootable.
I ensured the boot up option was set to usb first and restarted my computer. It went straight to my startup screen, no tests were run.
So I downloaded the iso zip file and burned it to a cd, ensured boot up option was set to cd/dvd, and still no luck.

I reset my system properties, unchecking the automatically restart.

I downloaded the whocrashed and checked analyze initially and it had nothing to report. My computer crashed twice more without restarting (I manually restarted) since I started the whocrashed and it showed no report.

I conducted the intentional crash through whocrashed and I did get a new stop code of 0xdeaddead, but the computer would not restart and after 30 minutes I restarted it.
I ran WhoCrashed, clicked Analyze and it listed the crash dump directory C:\WINDOWS\Minidump, crash dumps are enabled on my computer, but no valid crash dumps found.

Created another DM Log and attached.

Attachment 143005

BSOD after connecting 2nd monitor

BSOD after connecting 2nd monitor

@BSODHunter