Watchdog issue with HP Laptop 15s-eq3019nu (6X8G8EA)

P

Phantom961

Member
Joined
Nov 28, 2024
Posts
14
Hello, i'm encountering strange issue Watchdog happening at random intervals. For example: today when i wake him it was black screen and had to manually turn it off. My thoughts are either 24H2 is bugged as hell or driver from AMD cause this issue which i don't know how to tell AMD to fix it.

Specs:
Windows 11 24H2
Ryzen 5 5625U with Vega igpu.
16gb ram ddr4.
SSD: 1tb.

Steps i tried:
Clean reinstall laptop: not working.
Scan one by one ram with memtest and karhu ram test: No errors.
SSD: 100% health status S.M.A.R.T latest firmware.
Clean installed latest AMD 24.9.1 which btw driver that support 24H2 is 24.6.1 is not available on AMD website to download for my APU.
Removed battery, run laptop without battery.

Watchdog and other dmp files: Easyupload.io - Upload Files and Share Them Easily
 
Last edited:
I STRONGLY suggest you edit that Speccy text file to remove your Windows product key! This is why we ask you to publish a link.

I also note that you have Malwarebytes installed but disabled. If you're not using Malwarebytes then please fully uninstall it.

Has this problem only existed since you upgraded to 24H2? Did you allow Windows Update to upgrade to 24H2 or did you upgrade by some other method? Was the upgrade trouble-free, or did you have any issues with it at all?

The one dump in the upload, dated 28th Nov 2024, was a 0x14F bucgcheck (PDC_WATCHDOG_TIMEOUT) indicating that a device failed to respond when coming out of Modern Standby. This is the state that modern laptops enter when they sleep, so the first thing I'd like you to do is to confirm that your laptop supports Modern Standby....
  1. Open an elevated command prompt and enter the command powercfg /availablesleepstates
  2. The response will list all the available sleep states on your laptop, please copy that entire output and post it on here.
Next, I'd like you to generate a sleep study...
  1. Open an elevated command prompt and enter the command powercfg /sleepstudy
  2. An html report will be generated and the response to this command will tell you where to find it (typically it's in C:\WINDOWS\system32\sleepstudy-report.html)
  3. Upload that html file to the cloud with a link to it here.
That should allow us to see whether there were problems with Modern Standby and what caused them.

In addition, I can see in your logs that your graphics driver or graphics card have been having problems. Just before what looks like a manual restart there are a series of graphics related errors and these are all black screen errors. The dumps for these will be saved in the folder C:\Windows\LiveKernelReports\Watchdog, please upload all the dumps you find in there to the cloud with a link to them here.

I can already see that one of these live kernel dumps was apparently caused by the hotkey feature, this is an HP driver that controls many of the special features of the laptop. I suggest you do two things...
  • Download the HP Support Assistant from the HP drivers website for your laptop and use that to see whether any HP drivers (like hotkey) need updating.
  • Download the HP PC Hardware Diagnostics tool and use that to thoroughly test all your hardware.
Also be aware that for WD SSDs in particular, there is a firmware update that is required if you're running 24H2. You can find these firmware updates for whichever SSD you have on the HP driver download site for your laptop. This is probably not related to the black screens you're experiencing but if you have a WD SSD the firmware must be updated.
 
Last edited:
ubuysa said:
I STRONGLY suggest you edit that Speccy text file to remove your Windows product key! This is why we ask you to publish a link.

I also note that you have Malwarebytes installed but disabled. If you're not using Malwarebytes then please fully uninstall it.

Has this problem only existed since you upgraded to 24H2? Did you allow Windows Update to upgrade to 24H2 or did you upgrade by some other method? Was the upgrade trouble-free, or did you have any issues with it at all?

The one dump in the upload, dated 28th Nov 2024, was a 0x14F bucgcheck (PDC_WATCHDOG_TIMEOUT) indicating that a device failed to respond when coming out of Modern Standby. This is the state that modern laptops enter when they sleep, so the first thing I'd like you to do is to confirm that your laptop supports Modern Standby....
  1. Open an elevated command prompt and enter the command powercfg /availablesleepstates
  2. The response will list all the available sleep states on your laptop, please copy that entire output and post it on here.
Next, I'd like you to generate a sleep study...
  1. Open an elevated command prompt and enter the command powercfg /sleepstudy
  2. An html report will be generated and the response to this command will tell you where to find it (typically it's in C:\WINDOWS\system32\sleepstudy-report.html)
  3. Upload that html file to the cloud with a link to it here.
That should allow us to see whether there were problems with Modern Standby and what caused them.

In addition, I can see in your logs that your graphics driver or graphics card have been having problems. Just before what looks like a manual restart there are a series of graphics related errors and these are all black screen errors. The dumps for these will be saved in the folder C:\Windows\LiveKernelReports\Watchdog, please upload all the dumps you find in there to the cloud with a link to them here.

I can already see that one of these live kernel dumps was apparently caused by the hotkey feature, this is an HP driver that controls many of the special features of the laptop. I suggest you do two things...
  • Download the HP Support Assistant from the HP drivers website for your laptop and use that to see whether any HP drivers (like hotkey) need updating.
  • Download the HP PC Hardware Diagnostics tool and use that to thoroughly test all your hardware.
Also be aware that for WD SSDs in particular, there is a firmware update that is required if you're running 24H2. You can find these firmware updates for whichever SSD you have on the HP driver download site for your laptop. This is probably not related to the black screens you're experiencing but if you have a WD SSD the firmware must be updated.
Click to expand...
I can't delete the speccy post can you please delete it.
 
Your laptop does support Modern Standby (the S0 state) however, the sleep study shows that it's only actually been in Modern Standby once; the screen went off at 02:25:44 on 28th Nov and the laptop entered sleep at the same time. It was in sleep (Modern Standby) for 34 mins and 29 seconds and was in the low power state for 99% of that time (98% for the hardware). It came out of sleep (Modern Standby) with the screen still off at 03:00:15. The BSOD occurred 9 hours later, at 12:06:12 (on 28th Nov) and so is unrelated to that one Modern Standby period.

I think we need now to look at those live kernel dumps, so could you upload those for me please? I rather think the black screens are graphics driver related.

BTW. The sleep study did reveal that you have a Western Digital NVMe SSD...
Code: 
Instance Path        PCI\VEN_15B7&DEV_5017&SUBSYS_501715B7&REV_01\4&ac7d6ab&0&0014
Those hardware IDs (VEN_15B7&DEV_5017) are for a WD Black SN770 / PC SN740 256GB / PC SN560 (DRAM-less) NVMe SSD, so I STRONGLY advise you to download and install the firmware update for WD drives from the download site for your laptop. You likely need that firmware update with 24H2.
 
ubuysa said:
Your laptop does support Modern Standby (the S0 state) however, the sleep study shows that it's only actually been in Modern Standby once; the screen went off at 02:25:44 on 28th Nov and the laptop entered sleep at the same time. It was in sleep (Modern Standby) for 34 mins and 29 seconds and was in the low power state for 99% of that time (98% for the hardware). It came out of sleep (Modern Standby) with the screen still off at 03:00:15. The BSOD occurred 9 hours later, at 12:06:12 (on 28th Nov) and so is unrelated to that one Modern Standby period.

I think we need now to look at those live kernel dumps, so could you upload those for me please? I rather think the black screens are graphics driver related.

BTW. The sleep study did reveal that you have a Western Digital NVMe SSD...
Code: 
Instance Path        PCI\VEN_15B7&DEV_5017&SUBSYS_501715B7&REV_01\4&ac7d6ab&0&0014
Those hardware IDs (VEN_15B7&DEV_5017) are for a WD Black SN770 / PC SN740 256GB / PC SN560 (DRAM-less) NVMe SSD, so I STRONGLY advise you to download and install the firmware update for WD drives from the download site for your laptop. You likely need that firmware update with 24H2.
Click to expand...
Give me tutorial how to give you this kernal dumps. My SSD firmware is latest.

Is it this one:
https://www.file.io/IcH6/download/okfdu2UHUV28
 
Last edited:
Phantom961 said:
Give me tutorial how to give you this kernal dumps. My SSD firmware is latest.

Is it this one:
https://www.file.io/IcH6/download/okfdu2UHUV28
Click to expand...
No that's a minidump. Open File Explorer and in the blank path field at the top (to the left of the search box) type %systsemroot% and press enter. You will switch to the system root folder, probably C:\Windows). Scroll down looking for a file called MEMORY.DMP. Upload that file to the cloud.
 
ubuysa said:
No that's a minidump. Open File Explorer and in the blank path field at the top (to the left of the search box) type %systsemroot% and press enter. You will switch to the system root folder, probably C:\Windows). Scroll down looking for a file called MEMORY.DMP. Upload that file to the cloud.
Click to expand...
This file is missing it says.1732907536020.webp
 
Can you open the Run command box (right-click on the Start icon) and enter the command sysdm.cpl, a new window will open. Click the Advanced tab. Click the bottom Settinbgs button (Start-up and Recovery). A new window will open, please post a screenshot of that window.
 
That's not configured properly, it's not the default either.
  • Please change the Write debugging information pull-down menu to 'Automatic memory dump'.
  • Please change the Dump file directory entry to be %SystemRoot%\MEMORY.DMP

The last two options are greyed-out, why? That's not normal at all. The Overwrite any existing file box should be checked but these oiptions should not be greyed-out. ARe you running the Pro or Enterprise version of Windows? If so, have you used the Group Policy Editor at all to make any system changes at all?

Earlier, in post #4, I asked whether this problem has only existed since you upgraded to 24H2? Did you allow Windows Update to upgrade to 24H2 or did you upgrade by some other method? Was the upgrade trouble-free, or did you have any issues with it at all? What we're seeing coulkd well be an incomplete upgrade to 24H2 - a lot depends on how you did that upgrade...
 
ubuysa said:
That's not configured properly, it's not the default either.
  • Please change the Write debugging information pull-down menu to 'Automatic memory dump'.
  • Please change the Dump file directory entry to be %SystemRoot%\MEMORY.DMP

The last two options are greyed-out, why? That's not normal at all. The Overwrite any existing file box should be checked but these oiptions should not be greyed-out. ARe you running the Pro or Enterprise version of Windows? If so, have you used the Group Policy Editor at all to make any system changes at all?

Earlier, in post #4, I asked whether this problem has only existed since you upgraded to 24H2? Did you allow Windows Update to upgrade to 24H2 or did you upgrade by some other method? Was the upgrade trouble-free, or did you have any issues with it at all? What we're seeing coulkd well be an incomplete upgrade to 24H2 - a lot depends on how you did that upgrade...
Click to expand...
1733052700627.webp

No i clean install 24H2 and issue happens at random intervals.
 
Yes, that's what it should look like.

When you clean installed 24H2 from where did you source all the drivers?

Were there any issues with the PC when it was running 23H2 (or whatever version you were on)?
 
ubuysa said:
Yes, that's what it should look like.

When you clean installed 24H2 from where did you source all the drivers?

Were there any issues with the PC when it was running 23H2 (or whatever version you were on)?
Click to expand...
I used windows update as source of drivers, and some where from HP support assistant. Only Igpu drivers where from AMD website.

I don't remember to be honest.
 
Those sources are fine, as long as you didn't use any kind of third-party driver search and install tool.

I note that you are running with mismatched RAM. You have one 8GB stick of Samsung M471A1K43EB1-CWE RAM and one 8GB stick of Samsung M471A1G44CB0-CWE and they are not the same, even though they look it. The internal construction is different and the internal timings are probably different too. I suggest you remove whichever is the later installed stick and see whether it's stable on just the original 8GB. You may well find that it's stable with either stick installed on their own, but it's not stable with them both installed.

RAM should ALWYS be installed via a pack of matched sticks, never as individual sticks.
 
ubuysa said:
Those sources are fine, as long as you didn't use any kind of third-party driver search and install tool.

I note that you are running with mismatched RAM. You have one 8GB stick of Samsung M471A1K43EB1-CWE RAM and one 8GB stick of Samsung M471A1G44CB0-CWE and they are not the same, even though they look it. The internal construction is different and the internal timings are probably different too. I suggest you remove whichever is the later installed stick and see whether it's stable on just the original 8GB. You may well find that it's stable with either stick installed on their own, but it's not stable with them both installed.

RAM should ALWYS be installed via a pack of matched sticks, never as individual sticks.
Click to expand...
Ok, ty.
 

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

Back
Top