Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Trying to fix my computer from DPC_WATCHDOG_VIOLATION BSODs


  • Please log in to reply
8 replies to this topic

#1 Frostfire

Frostfire

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:40 AM

Posted 19 February 2018 - 09:36 PM

As mentioned in the posting instructions, I am running:

  • An HP Pavillion 500-054 PC
  • Windows 8.1
  • 64-bit operating system / x64-based processor
  • Originally Windows 8 upgraded to Windows 8.1 officially (and automatically)
  • A computer that is 4 years old now
  • From what I can remember, the OS was pre-installed by the manufacturer and was never re-installed
  • AMD A8-5500 APU with Radeon™ HD Graphics

Some background, this is a computer that I re-purposed into a home theatre with Kodi, as well as using the Launcher4Kodi to load Kodi prior to Windows Explorer. A few days ago it started to suffer from BSODs. A surefire method I had of causing the BSOD to occur was by opening a browser (Chrome, Firefox) however the same error also occurs if I simply leave the computer on for a long enough period of time. As of current time I have disabled the Launcher4Kodi meaning that it loads normally into the proper shell, however this has not helped preventing crashing. Due to the high instability of that computer as well as how it cannot keep a wired internet connection in Safe Mode with Networking I am using another computer to ask for help, with information about the computer with a problem having been brought over via USB drive.

 

Looking around on the internet for information on BSODs caused by ntoskrnl.exe (that's what WhoCrashed told me is the problem anyway) told me that sptd.sys and AMD Overdrive are potential causes of the problem. The former got on my computer back when I had DAEMON Tools Lite installed on it, however that program has been long gone from my computer for a while now. As for the latter, I've seen suggestions to disable it using the AMD Control Center, however I was unable to find any actual options to do so. (I have also never tried overclocking the computer, I don't know how to do that to begin with.) If these are the issues with my computer then I need to know alternative means of getting rid of them.

 

I do not know why these issues ever happened nor do I know if I have the ability to rollback to a previous restore point, as I never tried making those. As a result of how the computer is too unstable right now I have refrained from trying to backup the data on it as I do not know when it will be prone to crashing, and as a result I am highly averse to a factory reset unless it is absolutely necessary.

 

The Sysnative output below are the results that remain after I closed the application manually due to how it remained on "Waiting for tasks to complete..." for over 10 minutes.

 

Attached Files


Edited by Frostfire, 19 February 2018 - 09:38 PM.


BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,971 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:40 PM

Posted 20 February 2018 - 11:04 PM

Hi,

 

Please update your Ralink RT5390R 802.11bgn Wi-Fi Adapter driver.

 

Thanks.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 Frostfire

Frostfire
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:40 AM

Posted 21 February 2018 - 06:07 PM

Due to how the manufacturer's website was not cooperating with me I had to attempt installing drivers from a relatively recent support question on the manufacturer's support forums.

https://h30434.www3.hp.com/t5/Notebook-Wireless-and-Networking/WiFi-Adapter-Ralink-RT5390R-802-11bgn-Windows-8-1/td-p/6382828

 

After moving that file to the computer with the problem via USB, I updated the driver using the file downloaded there (there was in fact a previous version to replace as recognized by the program, at least) I then experienced another BSOD from the DPC_WATCHDOG_VIOLATION via the same trigger as before, opening my internet browser.

 

I don't even know if I updated the right thing, but due to how the computer with the problem has such trouble trying to use the internet only such roundabout methods are available to me.


Edited by Frostfire, 21 February 2018 - 06:12 PM.


#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,971 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:40 PM

Posted 22 February 2018 - 11:11 AM

Can you upload the latest dump file? (Go to C:\Windows\Minidump and copy the latest dump file to your desktop. Zip it up (use .ZIP) and upload it here.) In the mean while, please test your RAM and HDD:


Edited by bwv848, 22 February 2018 - 11:11 AM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 Frostfire

Frostfire
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:40 AM

Posted 23 February 2018 - 03:08 PM

I ran the disk diagnostics and the memory diagnostics, however if there are any exports of the results to be made I did not know how to make them or where they are. At most for now I can simply tell you that both tests had no errors and went the whole way through, the only thing I don't know is if using 1 out of the 4 CPUs detected by memtest was sufficient.

 

Here is the minidump file.

 

 

Attached Files



#6 Frostfire

Frostfire
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:40 AM

Posted 26 February 2018 - 10:18 PM

Due to my growing impatience I'm considering doing a factory reset on my machine, presuming that if my computer could stay on in safe mode for long enough to do the entire hard drive diagnostics test it may also be able to do so while backing up to an external HDD.

 

That said something I don't know is as to if that would actually do anything when it comes to fixing my issues. I'm no master of computers and I don't understand why an outdated driver could even cause these issues if I were to presume the rest of the computer also stayed the same. (though for all I know it was a windows update that happened while I was sleeping that changed everything) if it's too difficult to pinpoint the issue now I was wondering as to what I should try to do to ensure stability after I would end up starting over.



#7 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,971 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:40 PM

Posted 28 February 2018 - 11:19 AM

Sorry for the wait. The latest crash appears to be identical to the previous ones. From the raw stack, we have

1: kd> !dpx
Start memory scan  : 0xffffd001f5391568 ($csp)
End memory scan    : 0xffffd001f5392000 (ISR Stack Base)

0xffffd001f53915c0 : 0xfffff80081063cd0 : hal!HalpKInterruptHeap+0xcd0
0xffffd001f53915d0 : 0xfffff80081063cd0 : hal!HalpKInterruptHeap+0xcd0
0xffffd001f53915f8 : 0xfffff8008112e6f1 : nt!KeClockInterruptNotify+0x91
0xffffd001f5391618 : 0xfffff8008114aa8b : nt!KiIpiProcessRequests+0x37b
0xffffd001f5391628 : 0xfffff8008112f3ea : nt!KeAccumulateTicks+0x9a
0xffffd001f5391638 : 0xfffff8008114bbb3 : nt!KiCallInterruptServiceRoutine+0xa3
0xffffd001f5391668 : 0xfffff8008112f3ea : nt!KeAccumulateTicks+0x9a
0xffffd001f5391678 : 0xfffff800811d53da : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
0xffffd001f5391680 : 0xfffff80081063c30 : hal!HalpKInterruptHeap+0xc30
0xffffd001f5391688 : 0xfffff8008114aa8b : nt!KiIpiProcessRequests+0x37b
0xffffd001f5391690 : 0xfffff80081063cd0 : hal!HalpKInterruptHeap+0xcd0
0xffffd001f53916d0 : 0xfffff80081063cd0 : hal!HalpKInterruptHeap+0xcd0
0xffffd001f53916f8 : 0xfffff8008112e76e : nt!KeClockInterruptNotify+0x10e
0xffffd001f5391748 : 0xfffff8008642e456 : dxgmms1!VidSchiProcessIsrCompletedPacket+0x296
0xffffd001f5391788 : 0xfffff8008642cd8c : dxgmms1!VidSchiUpdateCurrentIsrFrameTime+0x3c
0xffffd001f53917b8 : 0xfffff8008112f3ea : nt!KeAccumulateTicks+0x9a
0xffffd001f53917c8 : 0xfffff8008114aa8b : nt!KiIpiProcessRequests+0x37b
0xffffd001f5391808 : 0xfffff80081063c30 : hal!HalpKInterruptHeap+0xc30
0xffffd001f5391818 : 0xfffff80081017ac5 : hal!HalpTimerClockIpiRoutine+0x15
0xffffd001f5391820 : 0xfffff80081063cd0 : hal!HalpKInterruptHeap+0xcd0
0xffffd001f5391848 : 0xfffff8008114bbb3 : nt!KiCallInterruptServiceRoutine+0xa3
0xffffd001f5391888 : 0xfffff800811d53da : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
0xffffd001f5391890 : 0xfffff80081063c30 : hal!HalpKInterruptHeap+0xc30
0xffffd001f53918b8 : 0xfffff800811d58a7 : nt!KiInterruptDispatchNoLockNoEtw+0x37
0xffffd001f53918d8 : 0xfffff800811d58b4 : nt!KiInterruptDispatchNoLockNoEtw+0x44
Unable to load image \SystemRoot\system32\drivers\dlkmd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dlkmd.sys
*** ERROR: Module load completed but symbols could not be loaded for dlkmd.sys
0xffffd001f5391948 : 0xfffff8008112f3ea : nt!KeAccumulateTicks+0x9a
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
0xffffd001f5391a48 : 0xfffff8008110062b : nt!KxWaitForSpinLockAndAcquire+0x1f
0xffffd001f5391a78 : 0xfffff800810fa754 : nt!EtwGetInterruptTimeStamp+0xb4
0xffffd001f5391a98 : 0xfffff8008114bc52 : nt!KiCallInterruptServiceRoutine+0x142
0xffffd001f5391ad8 : 0xfffff800811d5198 : nt!KiInterruptSubDispatch+0x108
0xffffd001f5391b08 : 0xfffff800811d5427 : nt!KiInterruptDispatch+0x37
0xffffd001f5391b28 : 0xfffff800811d58b4 : nt!KiInterruptDispatchNoLockNoEtw+0x44
0xffffd001f5391b48 : 0xfffff800810fba07 : nt!EtwpLogKernelEvent+0x297
0xffffd001f5391c08 : 0xfffff800810fa4fc : nt!EtwTraceKernelEvent+0x80
0xffffd001f5391c58 : 0xfffff800812b0cd6 : nt!PerfInfoLogUnexpectedInterrupt+0x5e
0xffffd001f5391c98 : 0xfffff800811d6bbe : nt!KiIsrLinkage+0x43d
0xffffd001f5391cd0 : 0xfffff80081368101 : nt!KiInitialPCR+0x101
0xffffd001f5391cd8 : 0xfffff8008101658f : hal!HalSendSoftwareInterrupt+0xc0
0xffffd001f5391d98 : 0xfffff800810157ed : hal!KeStallExecutionProcessor+0x18f
0xffffd001f5391dc8 : 0xfffff8008571fa6c : ndis!NdisMQueueDpcEx+0xec
Unable to load image \SystemRoot\system32\DRIVERS\netr28x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
0xffffd001f5391e28 : 0xfffff800810fc382 : nt!KeInsertQueueDpc+0x62
0xffffd001f5391e58 : 0xfffff800810fba07 : nt!EtwpLogKernelEvent+0x297
0xffffd001f5391ec8 : 0xfffff800856c6b5f : ndis!ndisMiniportMessageIsr+0xaf
0xffffd001f5391f38 : 0xfffff80081010f32 : "hal!_guard_check_icall_fptr <PERF> (hal+0xf32)"
0xffffd001f5391f68 : 0xfffff8008114bc32 : nt!KiCallInterruptServiceRoutine+0x122
0xffffd001f5391fa8 : 0xfffff800811d5198 : nt!KiInterruptSubDispatch+0x108
0xffffd001f5391fd8 : 0xfffff800811d5427 : nt!KiInterruptDispatch+0x37
You can see quite a few third-party drivers listed, including netr28x.sys again. We also see two other drivers: dlkmd.sys and atikmdag.sys; atikmdag is your AMD graphics driver and I believe dlkmd is a DisplayLink driver.

I would suggest your remove your DisplayLink software temporarily.

Indeed it's quite shameful that HP doesn't have any drivers (and BIOS updates too) for your desktop on their website. Have you tried contacting them?

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#8 Frostfire

Frostfire
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:40 AM

Posted 28 February 2018 - 02:43 PM

I did not try contacting them directly since I did not really expect customer support to be very indulgent for somewhat dated products.

 

I have actually already gone on with the factory reset, but it is good to know that the problem is with the drivers and that I can check if I still have them later in case they might cause issues again. I currently have no need to use the DisplayLink software on that computer so I presume I will not need to reinstall it at any predictable point soon. 



#9 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,971 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:01:40 PM

Posted 28 February 2018 - 03:15 PM

Sounds good! Sometimes a reinstall is the fastest way out. Let me know if you get another crash again.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users