I purchased a new microsoft surface book with windows 10 last week. $3k Works perfectly with the exception of during MWO game play I will frequently get a blue screen reporting a DPC_WATCHDOG_VIOLATION.
Windows has all the updates, all my drivers are up to date and dxdiag shows no problems across the board. I have 16g of memory and over 250g of available ssd space. I've taken it back to Microsoft and they have also confirmed I have all drivers and patches up to date.
Then...the cherry on top ... when I disconnect, even if I return to the match and get the top score; I get penalized on my next match sometimes waiting as long as 5 minutes. I crash about 1 game in 5, but about 1 in 2 if I get the time penalty.
Microsoft computer, Microsoft game, not so micro or soft shaft up my rear.
2
Dpc_Watchdog_Violation
Started by Dalberon, Apr 09 2016 01:43 PM
4 replies to this topic
#2
-
-
- Bridesmaid
- 637 posts
Member
- LocationLondon
Posted 11 April 2016 - 09:14 AM
This isn't a Microsoft game.
The watchdog violation errors that show up from a cursory Google all seem to be driver-related. Hard to say whether you're experiencing an unfortunate edge-case driver issue on a relatively new piece of hardware or something MWOish.
If you're getting a time penalty more often than you disconnect, then I think either you're disconnecting early for other reasons, or you're doing enough team damage to take a penalty of that instead. I don't think there's another way...
The watchdog violation errors that show up from a cursory Google all seem to be driver-related. Hard to say whether you're experiencing an unfortunate edge-case driver issue on a relatively new piece of hardware or something MWOish.
If you're getting a time penalty more often than you disconnect, then I think either you're disconnecting early for other reasons, or you're doing enough team damage to take a penalty of that instead. I don't think there's another way...
#3
-
-
- The Angel
- 47 posts
Member
- LocationIreland
Posted 14 April 2016 - 08:07 AM
This might be fixed be simply just disabling "Fast Startup".
http://www.windows10...e-fast-startup/
http://www.windows10...e-fast-startup/
Edited by Doughbag, 14 April 2016 - 08:10 AM.
#4
-
- The Patron
- 1 posts
Rookie
- LocationOklahoma
Posted 22 April 2016 - 08:41 AM
did a bit of googling, if your motherboard has an intel chipset/intel ssd/intel anything this page might help. Also, it may even help if its not an intel related issue. Hope to get you back in game and good luck.
http://www.thewindow...n-in-windows-10
**Reread OP and realized he got a Surface, That has a very choped down version of a mobile graphix chip.
you may need to run the game all the way down at bare minium settings and slowly take it up until you feel comfortable with your resoultion and framerates. The drivers on the surface may also need to be updated but you are on your own with that, I do not have a surface at the moment to play around with it.
http://www.thewindow...n-in-windows-10
**Reread OP and realized he got a Surface, That has a very choped down version of a mobile graphix chip.
you may need to run the game all the way down at bare minium settings and slowly take it up until you feel comfortable with your resoultion and framerates. The drivers on the surface may also need to be updated but you are on your own with that, I do not have a surface at the moment to play around with it.
Edited by Cataire, 22 April 2016 - 08:44 AM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
