[SOLVED] BSOD: DPC_WATCHDOG_VIOLATION in Windows 8

R

revenuebuilder

Member
Joined
Jun 20, 2012
Posts
22
Hey guys, I keep getting a BSOD with DPC_WATCHDOG_VIOLATION. Hoping someone can help figure out what's causing it- I've attached my logs.

Specs:
Operating System: Windows 8 Release Preview 64-bit (6.2, Build 8400) (8400.winmain_win8rc.120518-1423)
Language: English (Regional Setting: English)
System Manufacturer: MICRO-STAR INTERNATIONAL CO.,LTD
System Model: MS-7597
BIOS: Default System BIOS
Processor: AMD Athlon(tm) II X2 250 Processor (2 CPUs), ~3.0GHz
Memory: 8192MB RAM
Available OS Memory: 8192MB RAM
Page File: 2285MB used, 10513MB available
Video Card: ATI Radeon Sapphire HD 5670

It almost seems like I get the bluescreen after a certain amount of inactivity- if I leave the computer alone for more than a couple minutes, I'll come back to a BSOD.

Thanks for the help!
 

Attachments

All the required files are there but the DMP files. We really do need them

Did you run the data collection app as "admin"?

If so you can manually upload the DMP files using this method. By the way welcome to Sysnative

Ken




We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible. Please attach the DMP files to your next post not to post one.

If you are overclocking STOP



You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
Click to expand...
To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
Click to expand...
 
Thanks for the quick reply. Just noticed that I do not have a /Minidump folder, so I changed the stuff in System Properties, going to reboot now. I'm assuming the BSOD will happen again soon, so I'll upload the dump once it's generated. Thanks again for the help, really appreciate it!
 
Well, just as I suspected would happen... The BSOD hit again... but when it went to the blue screen, it said "Windows is recording information..." or something to that effect, and there's a progress bar that just stays stuck at 0%. And the minidump folder still wasn't created.

So it looks like for whatever reason, the computer is freezing/crashing, going to the Windows 8 BSOD (I'm assuming that's what it is), and then it just sits at 0% forever (I waited atleast 30 minutes and it never moved). So now I'm stuck. Any ideas?

It looks like this, but it says "Windows is recording information for recovery" or something like that, with a progress bar.
6149662567_7e4137fb09.jpg
 
Hi -

PERFMON reporting -
Code: 
[TABLE="class: block"]
[TR]
[TD="class: h4"][/TD]
[TD="class: info"] [ATTACH=CONFIG]865.vB[/ATTACH]   Device drivers are not 
installed.
[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"]Cause:
[/TD]
[TD="class: info b2"]A driver has not been installed for this 
device preventing it from working properly.
[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"]Details:
[/TD]
[TD="class: info"]The device driver for [COLOR=#FF0000]Coprocessor [/COLOR]has not been 
installed. This device will not be available until the correct device driver is 
installed.
[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"]Resolution:
[/TD]
[TD="class: info b2"]1. Try installing the drivers using Windows 
Update.
[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"][/TD]
[TD="class: info"]2. Install the drivers that are on the installation 
media that came with the device.
[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"][/TD]
[TD="class: info b2"]3. Check with the manufacturer for an updated 
driver.
[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"]Related:
[/TD]
[TD="class: info"][URL="http://go.microsoft.com/fwlink/?LinkID=70093"]Explanation of 
Error Codes Generated by Device Manager[/URL]
[/TD]
[/TR]
[/TABLE]

What does Device Manager show - red/yellow flags?

What version ATI drivers do you have installed?

Regards. . .

jcgriff2
 
There was a yellow flag on the Coprocessor, but I've downloaded and updated the latest ATI drivers for my motherboard since then (since the ZIP files above)- (edit: and it then detected the coprocessor / updated the drivers successfully) and I just rebooted after yet another BSOD. All of a sudden, at random, my mouse/screen will freeze, the system hangs for about 5 seconds, then it goes to this screen (taken with my phone):
UuhNf.jpg
It just sits there, at 0%, forever. And no dump was created, C:\Windows\Minidump folder still doesn't exist.

Note: This problem started happening prior to installing Win8... I noticed it started occurring regularly a few weeks ago to my Win7 64 install- even though I didn't change any hardware or even install any new software, for that matter... I can't figure out what might have triggered this happening. I've tested the HDD and memory and everything comes up clean.
 
You have 2x4GB RAM. Did you add one of the sticks after W8 installation?

The page file appears configured for 4 GB RAM, not 8 GB:
Code: 
AllocatedBaseSize=[COLOR=#FF0000]4608[/COLOR]
Caption=C:\pagefile.sys
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=[COLOR=#FF0000]20110926[/COLOR]222831.106000-420
Name=C:\pagefile.sys
PeakUsage=0
Status=
TempPageFile=FALSE

I would expect to see a 2012 date, not 2011.

Reset virtual memory settings - system managed, all drives.
 
I have a triple monitor setup on a single ATI Radeon card... I did upgrade from 4GB to 8GB of ram a few months ago, but the PC was working fine until a few weeks ago. So sounds like that might be the problem, huh? I'll change virtual memory settings and report back. Thanks for all the help, I seriously appreciate it. I'm at wit's end here :)
 
OK, so I unchecked "Automatically manage", and chose "System managed size" and rebooted. Went back into system properties, and it's still saying 'Total page file size: 4608 MB'. It also would only let me change to 'system managed' on the C: drive, the other drives it defaults to 'No paging file'. Should I manually change the size to 8GB instead?

EDIT: Ok, I forgot to click "Set" on the other drives. Now it's telling me 21014 MB total paging file size, when using the other harddrives. Going to do another reboot (hopefully I don't BSOD while rebooting again)
 
That could be the way Windows 8 sets the page file up... diifferent than W7 & Vista. The page file is where Windows write the dump file info, which later becomes the BSOD dump file.

Was a full kernel dump file created? --> \windows\memory.dmp

When you set the 3 monitors up was it under W8 or W7....?
 
There is no memory.dmp file, so doesn't look like it. I set up the 3 monitors under Windows 7 initially. I should note that I installed Windows 8 as a "fresh install". Wiped my SSD (C:) and installed W8 (did not upgrade). The triple monitors "just worked" under W8.
 
revenuebuilder said:
Rebooted now, and went back into System Properties. It now says "paging file size: 13824 MB". Hopefully this solves the problem!
Click to expand...

I focused in on the page file because in W7 & Vista, the page file base allocation size must be > installed physical RAM.

Regards. . .

jcgriff2
 
Thanks, I'll follow instructions in the thread and report back if I get another BSOD anytime soon and can get a dump. Really appreciate the help, thank you so much for your time.

Best,
Bill
 
Actually, very odd thing just happened... I changed the system recovery to 'kernel memory dump' and it gave me an alert saying:

Windows might not be able to record details that could help identify system errors because your current paging file is disabled or less than 400 MB. Click OK to return to Virtual Memory settings, enable the paging file, and set the size to a value over 400 MB, or click cancel to change your memory dump selection.

Is this just because I changed the paging file as 'system managed'?
 
Also, here's the output of WMI_Recoveros.exe:



AutoReboot=FALSE
Caption=
DebugFilePath=%SystemRoot%\MEMORY.DMP
DebugInfoType=2
Description=
ExpandedDebugFilePath=C:\Windows\MEMORY.DMP
ExpandedMiniDumpDirectory=C:\Windows\Minidump
KernelDumpOnly=FALSE
MiniDumpDirectory=%SystemRoot%\Minidump
Name=Microsoft Windows 8 Release Preview|C:\Windows|\Device\Harddisk0\Partition2
OverwriteExistingDebugFile=TRUE
SendAdminAlert=FALSE
SettingID=
WriteDebugInfo=TRUE
WriteToSystemLog=TRUE








AllocatedBaseSize=4608
Caption=C:\pagefile.sys
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20110926222831.106000-420
Name=C:\pagefile.sys
PeakUsage=0
Status=
TempPageFile=FALSE




AllocatedBaseSize=4608
Caption=F:\pagefile.sys
CurrentUsage=0
Description=F:\pagefile.sys
InstallDate=20091219235609.630800-480
Name=F:\pagefile.sys
PeakUsage=0
Status=
TempPageFile=FALSE




AllocatedBaseSize=4608
Caption=G:\pagefile.sys
CurrentUsage=0
Description=G:\pagefile.sys
InstallDate=20101202025707.562017-480
Name=G:\pagefile.sys
PeakUsage=0
Status=
TempPageFile=FALSE










Caption=c:\ 'pagefile.sys'
Description='pagefile.sys' @ c:\
InitialSize=0
MaximumSize=0
Name=c:\pagefile.sys
SettingID=pagefile.sys @ c:




Caption=f:\ 'pagefile.sys'
Description='pagefile.sys' @ f:\
InitialSize=0
MaximumSize=0
Name=f:\pagefile.sys
SettingID=pagefile.sys @ f:




Caption=g:\ 'pagefile.sys'
Description='pagefile.sys' @ g:\
InitialSize=0
MaximumSize=0
Name=g:\pagefile.sys
SettingID=pagefile.sys @ g:




Is it odd that it still says '4608' for base size, and InitialSize,MaximumSize=0?
 
The overrides look like no page file exists -

Code: 
Caption=c:\ 'pagefile.sys'
 Description='pagefile.sys' @ c:\
 InitialSize=0
 MaximumSize=0
 Name=c:\pagefile.sys
 SettingID=pagefile.sys @ c:

Page file needs to be on OS drive only, which I assume is c: ?
 
Yup, C: is my OS drive. It's a 60GB SSD... as of right now, I set it to system managed on all 3 drives and it looks like it's combining the 3 to make a larger page file. Should I just manually set a larger page file on the C: drive, and switch the other 2 drives back to 'Auto'? If so, I'm unsure as to what to put for a minimum/maximum value.
 
System managed for c: should take care of things for you.

Have you checked for an SSD firmware upgrade at the manufacturer's support site?

Have you tried running with 1 or 2 monitors instead of the 3 to see if BSODs continue?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top