Clock watchdog and DPC watchdog BSoDs happening randomly.

Toggle sidebar Toggle sidebar
F

fatfingers21

Reputable
May 31, 2015
5
0
4,510
I am having BSOD's happen randomly, sometimes it happens while I'm browsing the internet, sometimes when I'm playing a game, and even sometimes when I'm out of the room I will come back to see it with the Blue screen up. The issues always say either: Clock_Watchdog_timeout or DPC_Watchdog_Violation. I have updated my bios, updated every driver I could find. It started about two or three weeks ago and the most recent piece of hardware I added was a hard drive about three months ago. The oldest pieces of hardware in my desktop is the power supply, and two 4GB sticks of RAM, both about came with the old PC I upgraded from aroud February. The power supply and RAM were both purchased in June 2012. Everything else in there is new within the last year.

Nvidia GTX 760
AMD FX-8350 8-core CPU, 4.0 Ghz
970 MSI Gaming motherboard
Hyper212 Cooler Master CPU fan and heatsink
1TB Hard drive, seagate
8GB RAM

Don't know what else to do, Thanks for any help.
 
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
generally you need to provide a kernel memory dump in order to figure out the cause of this problem.

how to make a kernel memory dump:https://support.microsoft.com/en-us/kb/969028

most of the time it will be caused by a CPU core hanging because a USB device is trying to install a device driver and failing (over and over) until a timeout value is reached and windows bugchecks the system because it thinks the CPU core is hung. The kernel memory dump can be used to identify the name of the driver that is failing to install.

most often the fix is to update the BIOS to get UPB fixes, and update the USB chipset drivers from your motherboard vendor. (USB 3.0 drivers or USB 2.x driver from the CPU chipset). This seems to happen most often when people use USB wireless thumb devices but don't pre install a updated device driver for the device and just use the windows default driver. (default driver is pretty bad and should be updated right after you get the network up and running)
 
Upvote 0 Downvote
F

fatfingers21

Reputable
May 31, 2015
5
0
4,510


Alright, The BIOS is updated. Not one hundred percent positive on how to get the chipset drivers. But here is my most recent crash notes: https://docs.google.com/document/d/1ZxCCjnqz0eXJiCz1dEvgrlTCPoLFqHdPBmyXwiTFlok/edit. I really appreciate your time.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
file is not marked public, I can not get access


 
Upvote 0 Downvote
F

fatfingers21

Reputable
May 31, 2015
5
0
4,510


Very Sorry. https://docs.google.com/document/d/1ZxCCjnqz0eXJiCz1dEvgrlTCPoLFqHdPBmyXwiTFlok/edit?usp=sharing
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
I would need the actual kernel memory dump binary file
c:\windows\memory.dmp

you have to change the memory .dmp type from minidump to kernel dump.
how to configure memory dump type:https://www.sophos.com/en-us/support/knowledgebase/111474.aspx
it would also be helpful if you ran cmd.exe and ran
verifier.exe /standard /all

then rebooted and go until you get the next bughceck.
then copy the very large memory.dmp file to a server and post a link.

The text summary of the minidump is not very helpful for this type of problem. Mainly because one common causes of this error is problems with USB drivers and that info is not included in a mini dump but is included with a kernel memory dump along with various error logs.



 
Upvote 0 Downvote
F

fatfingers21

Reputable
May 31, 2015
5
0
4,510


Alright, getting there changed over to complete memorey dump, will be back after next crash. Thanks again for your patience. I'm new-ish to computer building and stuff.
EDIT: Here it is. https://www.dropbox.com/s/p4gjdvz240qwcun/060315-11953-01.zip?dl=0
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
still is a minidump and verifier was not active.
full or kernel memory dumps have a default name and location of
c:\windows\memory.dmp

mini memory dumps have a default location of
c:\windows\minidump\ and have a file name that is based on the date at the time of the dump

the file provided was 060315-11953-01.dmp (mini dump)


run cmd.exe as an admin then run
verifier.exe /standard /all

try and change the memory dump type to full or kernel, save the settings and reboot the machine.

when you bugcheck a kernel memory dump should be around 400 mb, a full memory dump will be around 1.2 GB (maybe larger). Check your machine for this file c:\windows\memory.dmp





 
Upvote 0 Downvote
F

fatfingers21

Reputable
May 31, 2015
5
0
4,510
I finally got it up on dropbox: https://www.dropbox.com/s/ixkvhwdsxqyrfed/MEMORY.zip?dl=0

I would like to add that I haven't had a DPC BSoD in about 5 days. All it is now is Clock_Watchdog.

And im not 100% certain that I did the cmd prompt commands correctly. I opened cmd and type exactly: verifier.exe /standard /all. A new cmd opened and closed over the course of about a half second. Not sure if that was what needed to happen there.


 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
reset BIOS to defaults
you might check for updated drivers:
http://us.msi.com/support/mb/970-GAMING.html#down-driver&Win8.1 64

you might want to find out why there is not a SATA driver listed for windows 8 but there is one for windows 7 for your motherboard. (or find the proper driver)
------
I was just trying to figure out what would have corrupted your system memory, you should
-run memtest86 and confirm you don't have a memory problem with your machine.
- start cmd.exe as an admin and run
sfc.exe /scannow
and confirm your core windows files are not corrupted.

-you might update your storage drivers from your motherboard vendor. (I could not check the version because of the corrupted memory dump)

-you might put your drive data cable on a different storage controller or different port.
- you might run a diagnostics program on your storage. run crystaldiskinfo.exe to read SMART error data from the drive, run seatools to do testing of the drive.
-you might remove any unused hardware from your system, the debug info showed some hardware problems with devices but I could not get the debug commands to work because of the .dmp file corruption. (may be bogus info because of the corrupted .dmp)

-your system was up for 7 mins before it crashed.
your system indicates: 1 bank of 4gb SUPERTALENT02 memory
---------
looks like your system memory dump is corrupted. Based on what I see I would guess you have a problem with a storage driver or maybe a actual storage device.

are you running your storage in RAID?
(I guess you could also have malware infection of your storage driver)

machine info:
BIOS Release Date 12/16/2014
BIOS Version V22.2
Manufacturer MSI
Product 970 GAMING (MS-7693)
Version 4.0

Processor ID 200f6000fffb8b17
Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz

 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom