D
Deborah85
I have a Surface Pro 4 (Window version 1703, OS Build 15063.1387) that did have a surface type cover that was not working. I tried every fix I could research. I finally cured the problem by rebooting from an image file on a usb. The image file was downloaded from the official surface pro 4 website. This action reset the entire computer. The surface type cover is now working. However, I am now getting a DPC Watchdog Violation, which appear to be most often caused by a driver failing or incompatibility of an old driver.
So I used driver verifier to stress all the non-Microsoft drivers. I did the following in order: 1) started driver verifier in an elevated command prompt, 2) picked created customized settings for code developers, 3) then clicked on select driver names from list, 4) enabled all non-Microsoft drivers, 5) click finish, 6) rebooted system and waited for BSofD to happen. I got the blue screen of death almost instantly due to the stress on all non-Microsoft drivers. At this point, the computer would not restart without crashing immediately. So I booted to safe mode and reset the driver "verifier" program to default. Now it starts without immediately crashing.
I have opened the minidump file and read it. It points to the following information:
Bug check code c4
Process Name system
Symbol name nt! IOPProcessWorkItem+fb
Module name nt
Image name ntkrnlmp.exe
Image path ntkrnlmp.exe
File version 10.0.15063.1387
Can someone possibly tell me which driver is causing the problem and how I repair or replace the bad driver to stop the DPC Watchdog Violation.
If you prefer or cannot diagnose the problem from the information above, I have a minidump file that could be read by an expert from this crash incident that was just formed. I can send it to someone to take a look at. It should identify which driver is causing the problem.
Thank you very much in advance for your help.
Deborah
Continue reading...
So I used driver verifier to stress all the non-Microsoft drivers. I did the following in order: 1) started driver verifier in an elevated command prompt, 2) picked created customized settings for code developers, 3) then clicked on select driver names from list, 4) enabled all non-Microsoft drivers, 5) click finish, 6) rebooted system and waited for BSofD to happen. I got the blue screen of death almost instantly due to the stress on all non-Microsoft drivers. At this point, the computer would not restart without crashing immediately. So I booted to safe mode and reset the driver "verifier" program to default. Now it starts without immediately crashing.
I have opened the minidump file and read it. It points to the following information:
Bug check code c4
Process Name system
Symbol name nt! IOPProcessWorkItem+fb
Module name nt
Image name ntkrnlmp.exe
Image path ntkrnlmp.exe
File version 10.0.15063.1387
Can someone possibly tell me which driver is causing the problem and how I repair or replace the bad driver to stop the DPC Watchdog Violation.
If you prefer or cannot diagnose the problem from the information above, I have a minidump file that could be read by an expert from this crash incident that was just formed. I can send it to someone to take a look at. It should identify which driver is causing the problem.
Thank you very much in advance for your help.
Deborah
Continue reading...