Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD- stop code: Dpc_Watchdog_Violation


  • Please log in to reply
2 replies to this topic

#1 L_1_N_C

L_1_N_C

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:19 PM

Posted 11 December 2017 - 11:30 AM

      I suspect that my GPU(GTX780) may be a brick now but if anyone could shed a little light on my situation it would be appreciated. This all started when I experienced a hangup while playing a game called Ark:sotf this weekend, (survival game running UnrealEngine4) afterwards I was unable to launch any game without getting these hangups that require a hard restart/shutdown and displayed a solid random color or a grayed out screen. I assumed it was a driver issue and while installing fresh drivers my machine got to a point where it would no longer boot into windows and instead BSOD with the "DPC_WATCHDOG_VIOLATION" error message.

 

     After many hours of safe-mode troubleshooting

  `drivers, 

  `running multiple passes of memtest86 (USB),

  `sfc / scannow

  `chckdsk C: /R

  `stopping & starting: -wuauserv -cryptSvc -bits -msiserver. (Via- Admin cmd) 'because windows updates

   were freezing',

  `changing power setting in Nvidia CP

  `re-flashing the bios on both my MB & GPU, 

I decided to do a clean Windows Install. Now every time I attempt to install any Nvidia driver with or w/out GeForceExperience my machine will BSOD error code "DPC_WATCHDOG_VIOLATION" with a few short black horizontal artifacts/lines. I cannot think of any further action to take considering that I can't even get a driver on the card now. I'm considering biteing the bullet and buying a 1050 to hold me over while I save up the $ for a 1080.

 

http://speccy.piriform.com/results/xWZ1nnQuPCewbDnvY4ESdsp

Attached Files


Edited by L_1_N_C, 12 December 2017 - 10:30 AM.


BC AdBot (Login to Remove)

 


#2 L_1_N_C

L_1_N_C
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:19 PM

Posted 11 December 2017 - 11:33 AM

**I managed to get the latest Nvidia driver (388.59) to install early this morning however the BSOD's still persist and stops windows from booting**



#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:19 PM

Posted 13 December 2017 - 02:01 PM

Sorry for the delay in responding - I'm having some severe eye problems now

 

Your UEFI/BIOS (version F8) dates from 2017.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 2 Windows Update hotfixes installed.  Most build 16299 (1709/Fall Creators Update) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

This device has problems in Device Manager:

 

USB Input Device    USB\VID_1E71&PID_170E\5D893480333    This device cannot start.

This is most likely an NZXT CAM v3 (a USB device).  Please:

- uninstall the software for this device and physically remove it from the system.

- then reboot the system

The CAM driver dates from 2008 and is likely NOT compatible w/Windows 10.

If it's needed, please

- download a fresh copy of the latest, W10 compatible version of the software for this device

- then follow the instructions for installing the device.

If unable to find a version that states that it's compatible w/W10, please DO NOT install it again.

 

The memory dumps seem to point to a hardware issue, most likely with your video card.

 

Please try to clean install your video drivers:

 

Please uninstall your video drivers and all the nVidia/AMD/Intel VIDEO (not chipset) software from your system
- If uninstalling the AMD video drivers, you may also want to run the AMD Clean Uninstall utility (free from here:  http://support.amd.com/en-us/kb-articles/Pages/AMD-Clean-Uninstall-Utility.aspx )
Then use this free tool to remove any traces of the drivers:  http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then reboot and check Windows Update (allow it to install video drivers):  https://support.microsoft.com/en-us/help/15054/windows-7-automatically-get-recommended-drivers-updates-hardware

Test to see if this helps and post back with the results.

Then, if that works and you need the nVidia drivers - feel free to download and install the latest, W10 compatible video drivers from http://www.nvidia.com/Download/index.aspx
Then, if that works and you need the AMD drivers - feel free to download and install the latest, W10 compatible video drivers from http://support.amd.com/en-us/download
Then, if that works and you need the Intel drivers - feel free to download and install the latest, W10 compatible video drivers from http://downloadcenter.intel.com (you can also usually download these drivers from the manufacturer's website)

If that doesn't fix it, then start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please run ALL of the tests and let us know the results.  We'll move on from there.

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Mon Dec 11 01:21:06.711 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121017-6140-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:06:34.453
*** 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 timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 133, {1, 1e00, fffff8004c883370, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8004c883370
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  F8
  BIOS Release Date             07/06/2017
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z270X-Gaming 5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 11 00:54:57.965 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121017-6156-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:50:36.703
*** 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 timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 133, {1, 1e00, fffff80203c79370, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80203c79370
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  F8
  BIOS Release Date             07/06/2017
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z270X-Gaming 5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 11 00:03:45.401 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121017-6265-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:04:48.140
*** 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+1d2d1d )
BugCheck 133, {1, 1e00, fffff8020388d370, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8020388d370
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  F8
  BIOS Release Date             07/06/2017
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z270X-Gaming 5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 10 23:02:25.699 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121017-6093-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:13:18.437
*** 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 timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 133, {1, 1e00, fffff80106a89370, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80106a89370
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  F8
  BIOS Release Date             07/06/2017
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z270X-Gaming 5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 10 22:48:17.776 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121017-5828-01.dmp]
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Built by: 16299.15.amd64fre.rs3_release.170928-1534
System Uptime:0 days 0:48:11.515
*** 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 timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 133, {1, 1e00, fffff802e8407370, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff802e8407370
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-7700K CPU @ 4.20GHz"
MaxSpeed:     4200
CurrentSpeed: 4200
  BIOS Version                  F8
  BIOS Release Date             07/06/2017
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z270X-Gaming 5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Dec 11 01:21:06.711 2017 (UTC - 5:00)**************************
CAM_V3.sys                  Sat Jul 26 09:29:37 2008 (488B26C1)
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
intelppm.sys                Thu Sep 22 06:43:11 2011 (4E7B113F)
e2xw10x64.sys               Tue Jan 26 18:58:16 2016 (56A80818)
ccSetx64.sys                Thu May  5 18:33:33 2016 (572BCA3D)
e1d65x64.sys                Tue Jul 26 12:48:21 2016 (57979455)
SYMEFASI64.SYS              Wed Aug  3 01:50:18 2016 (57A1861A)
iqvw64e.sys                 Tue Aug 23 21:52:09 2016 (57BCFDC9)
TeeDriverW8x64.sys          Wed Aug 31 18:45:52 2016 (57C75E20)
Ironx64.SYS                 Fri Sep  2 17:44:25 2016 (57C9F2B9)
SRTSPX64.SYS                Fri Sep  2 21:56:42 2016 (57CA2DDA)
SYMEVENT64x86.SYS           Thu Sep  8 15:47:29 2016 (57D1C051)
RfeCo10X64.sys              Fri Sep  9 16:37:34 2016 (57D31D8E)
iaStorA.sys                 Tue Sep 13 10:45:46 2016 (57D8111A)
SRTSP64.SYS                 Tue Sep 13 21:14:58 2016 (57D8A492)
SYMNETS.SYS                 Wed Sep 14 22:43:10 2016 (57DA0ABE)
RTKVHD64.sys                Tue Oct 18 07:20:52 2016 (58060594)
cpuz143_x64.sys             Mon May 22 04:17:51 2017 (59229EAF)
IDSvia64.sys                Wed Jul 26 16:25:09 2017 (5978FAA5)
BHDrvx64.sys                Wed Sep  6 19:34:58 2017 (59B08622)
eeCtrl64.sys                Sat Sep 30 22:07:21 2017 (59D04DD9)
EraserUtilRebootDrv.sys     Sat Sep 30 22:07:22 2017 (59D04DDA)
nvlddmkm.sys                Tue Dec  5 14:28:19 2017 (5A26F353)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 11 00:54:57.965 2017 (UTC - 5:00)**************************
SYMNETS.SYS                 Tue Apr 12 19:47:43 2016 (570D891F)
Ironx64.SYS                 Wed May  4 08:56:49 2016 (5729F191)
SYMEFASI64.SYS              Thu May 12 15:21:02 2016 (5734D79E)
SYMEVENT64x86.SYS           Mon May 23 16:42:54 2016 (57436B4E)
SRTSP64.SYS                 Wed May 25 23:16:06 2016 (57466A76)
SRTSPX64.SYS                Wed May 25 23:18:13 2016 (57466AF5)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 11 00:03:45.401 2017 (UTC - 5:00)**************************
BHDrvx64.sys                Wed May  4 22:11:06 2016 (572AABBA)
IDSVia64.sys                Fri May 20 00:04:20 2016 (573E8CC4)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec 10 23:02:25.699 2017 (UTC - 5:00)**************************
nvlddmkm.sys                Tue Jul 18 18:00:50 2017 (596E8512)


http://www.carrona.org/drivers/driver.php?id=CAM_V3.sys
http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=e2xw10x64.sys
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=iqvw64e.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
RfeCo10X64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=cpuz143_x64.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=IDSVia64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users