DPC_WATCHDOG_VIOLATION - Windows 10 x64

k1w1neil · Aug 12, 2015

Hi all,
My name is Neil, and this is my first post which serves as both an introduction and a request for help. I live in New Zealand, and currently are into the second year of a degree course in Information and Communications Technology.
My problem has surfaced since my upgrade to Windows 10, 64-bit Home edition; from Windows 7, 64-bit Home Premium. My computer (laptop) crashes with the 'blue screen', and necessitates a "power button off" and then restart. My default browser is Google Chrome, and the errors seem to occur whilst first loading this application.
An error message displaying "Google Chrome has stopped working", with two actions 'Close the program' and 'Debug program' randomly appears. Any action taken, e.g. click "Close Program' has no effect on the open browser.
Any help in this matter would be extremely appreciated.

The 2 required 'zip' files are attached.

Thanks in anticipation,
Neil McNicol
P.S. I am not "shouting" with the title of this thread, merely showing the stop error involved.

Jared · Aug 12, 2015

Not much saved in these files, any chance we could get a Kernel dump?
It's located in C:\Windows\MEMORY.dmp
You will need to compress it and upload it to a file sharing site.

k1w1neil · Aug 12, 2015

Jared said:
Not much saved in these files, any chance we could get a Kernel dump?
It's located in C:\Windows\MEMORY.dmp
You will need to compress it and upload it to a file sharing site.

Jared

The only .dmp files are the ones that were provided in the zip files already, as per the instructions here: https://www.sysnative.com/forums/bs...ng-instructions-windows-10-8-1-8-7-vista.html

Regards,
Neil

Jared · Aug 12, 2015

Then it might be better to try driver verifier as it is most likely a driver causing problems.

https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html

k1w1neil · Aug 12, 2015

Thanks for your replies, Jared.
Today I have had 4 crashes in the space of 40 minutes, after the initial startup. Three of these were 'DPC_WATCHDOG_VIOLATION', and the other one was REFERENCE_BY_POINTER.
With regards your advice to run 'Driver Verifier', I see that it needs to run for 24 hours minimum. Being a student, I need to use my computer to finish and submit an assignment by 9.00am(Friday 14th, NZ time; 9.00PM,UTC), hence I am unable to run 'Driver Verifier' until after that.

Any interim advice would be appreciated.

Regards
Neil

Jared · Aug 12, 2015

k1w1neil said:
Thanks for your replies, Jared.
Today I have had 4 crashes in the space of 40 minutes, after the initial startup. Three of these were 'DPC_WATCHDOG_VIOLATION', and the other one was REFERENCE_BY_POINTER.
With regards your advice to run 'Driver Verifier', I see that it needs to run for 24 hours minimum. Being a student, I need to use my computer to finish and submit an assignment by 9.00am(Friday 14th, NZ time; 9.00PM,UTC), hence I am unable to run 'Driver Verifier' until after that.

Any interim advice would be appreciated.

Regards
Neil

You don't need to run it for 24 hours minimum, it's just recommended.
It's not something that stops your computer use, it's just a change in Kernel management through hooks such as memory allocations, IRQL processing etc.
If it finds something, it'll BSOD the computer like it would crash anyway, but with the culprit in it's sights hopefully.

k1w1neil · Aug 12, 2015

Jared said:
k1w1neil said:

Thanks for your replies, Jared.
Today I have had 4 crashes in the space of 40 minutes, after the initial startup. Three of these were 'DPC_WATCHDOG_VIOLATION', and the other one was REFERENCE_BY_POINTER.
With regards your advice to run 'Driver Verifier', I see that it needs to run for 24 hours minimum. Being a student, I need to use my computer to finish and submit an assignment by 9.00am(Friday 14th, NZ time; 9.00PM,UTC), hence I am unable to run 'Driver Verifier' until after that.

Any interim advice would be appreciated.

Regards
Neil

Click to expand...

You don't need to run it for 24 hours minimum, it's just recommended.
It's not something that stops your computer use, it's just a change in Kernel management through hooks such as memory allocations, IRQL processing etc.
If it finds something, it'll BSOD the computer like it would crash anyway, but with the culprit in it's sights hopefully.

Hi Jared
I may have to rollback to Windows 7. My computer (laptop) is a Sony Vaio and I came across this article Sony is telling users that it's not prudent to upgrade to Windows 10 yet .

In the meantime I will run 'Driver Verifier' and report back.

Regards
Neil

k1w1neil · Aug 12, 2015

Jared
I ran Driver Verifier as per: https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html .
After the required re-boot, another 'blue screen' appeared declaring "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED". I had to revert back to the 'System Restore' point, put in place at the start of said process.
I await further advice.

Regards
Neil
P.S. With respect, how can one so young as yourself (I checked your profile), know what you do to troubleshoot these matters, and be a moderator on this forum?

Jared · Aug 13, 2015

Okay, let's try and get the dump file.
Upload the new one then do the following to change the settings:

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:
C:/Windows/memory.dmp
Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

The problem is that a lot of minidumps are very limited in what they save from the box when your computer is crashes and the information is written to disk. So if the driver is present in the context that was executing when the crash occurred, you'll probably never find it.

Whether you want to keep Windows 10 or not is up to you.
Now that you've done the upgrade I wouldn't bother reverting back only to upgrade again later, it's more hassle than it's worth.
I'm certain we can get to the bottom of this.

I have spent a lot of time troubleshooting these types of problems, first hand as well, so 99% of the time I know what to look for.

k1w1neil · Aug 13, 2015

Jared
Thanks very much for your help with this issue, but time is my 'enemy' at the moment, and I have decide to rollback to Windows 7. I have heeded the warning that I outlined in my previous post, with "Sony Vaio" not having compatible drivers (at present) and will hold off upgrading again until they present suitable drivers.
If I had seen your post (from 1/2 hour ago) earlier, I might have held off and tried to get this sorted. But, I am a student and have an assignment that has to be completed and submitted by 9.00am tomorrow morning.

Again, thanks for your time..
Regards
Neil

Jared · Aug 13, 2015

That was your wish and I respect it.

If you continue to get the issues now with Windows 7, feel free to post back.
Let's hope it fixed the issue for you.

Good luck with your assignment.

Regards,
Jared

Search

Search

DPC_WATCHDOG_VIOLATION - Windows 10 x64

k1w1neil

Member

Attachments

Jared

Sysnative Staff, BSOD Kernel Dump Expert

k1w1neil

Member

Jared

Sysnative Staff, BSOD Kernel Dump Expert

k1w1neil

Member

Jared

Sysnative Staff, BSOD Kernel Dump Expert

k1w1neil

Member

k1w1neil

Member

Jared

Sysnative Staff, BSOD Kernel Dump Expert

k1w1neil

Member

Jared

Sysnative Staff, BSOD Kernel Dump Expert