Issue with synthetic watchdog timeout and hypervisor error during BSOD
Issue with synthetic watchdog timeout and hypervisor error during BSOD
Hello, friends.
I set up a fresh version of Win 11 Pro. While working, I often face the issues described earlier:
Synthetic watchdog timeout (amdppm.sys)
stop code hypervisor error
Initially the system freezes, then the BSOD appears. The hypervisor error usually happens when closing an app, such as Google Chrome.
I changed the RAM but it didn’t help. Virtualization is turned on in BIOS. However, Hyper-V is disabled in the Win component settings. I attempted to enable the verifier, but it didn’t resolve the problem and no further details were shown during the BSOD. Turning it on seemed to increase errors and significantly slow down the computer.
I’ve looked through similar discussions on this forum, but no solution was found. I’ve been dealing with this computer for a long time and feel really frustrated. Could you assist me in fixing this?
Windows 10 Kernel Version 26100 MP (8 cores) Free x64
2014 CPU speed 4014MHz
2016 BIOS
Previous issue driver: RTKVHD64.sys – Tue Jun 14 03:51:52 2016
Realtek HD audio driver contained a flaw causing it to react to DMA requests from other devices, leading to crashes. This often affected the NVIDIA GPU sound driver. It’s advisable to update or disable this driver if you don’t need it.
If sound isn’t reaching your monitor via the GPU through the HDMI cable, consider disabling the NVIDIA sound driver; this seems unrelated to hypervisor issues and likely tied to older BIOS or CPU settings. A quick inspection of other bug fixes may help.
Note: Windows build and files appeared intact.
3: kd> !sysinfo machineid
Machine ID Details from Smbios 2.7, DMIVersion 0, Size=2511
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 2901
Release Date = 05/04/2016
Manufacturer: To be filled by O.E.M.
Product Name: To be filled by O.E.M.
Family: To be filled by O.E.M.
Version: To be filled by O.E.M.
SKU: SKU
Board Manufacturer: ASUSTeK COMPUTER INC.
Board Product: SABERTOOTH 990FX R2.0
Board Version: Rev 1.xx
3: kd> !sysinfo cpuinfo
CPU details: ~MHz = REG_DWORD 4014
Component info: REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration data: REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0
Identifier: REG_SZ AMD64 Family 21 Model 2 Stepping 0
Processor name: AMD FX-8370 Eight-Core Processor
Update status: 0
Vendor ID: REG_SZ AuthenticAMD
Thus far, most bugchecks remain consistent. One issue involves a timer not being triggered. Check the BIOS to verify the system time and date are accurate. There could be a basic problem where the battery backup on your motherboard failed. It might be a CR2032 battery placed directly on the board, which typically lasts around five years. Because your system is quite old, you might try booting into BIOS and inspecting the voltage levels if the BIOS displays them. Expected values are 3.3V, 5V, and 12V (approximately ±5 to 10 percent from the reference). I recommend starting with the voltage readings; it seems the chip support is triggering a bugcheck due to low-level code calls outside a recognized driver. There may be CPU patches available for older processors. At 0: kd> !sysinfo cpumicrocode Initial Microcode Version: 00000000:06000852 Cached Microcode Version: 00000000:00000000 Processor Family: 15 Model: 02 Stepping: 00 Note: Cached microcode version not detected! I didn’t notice a microcode DLL being loaded for known CPU problems. The system instructed the CPU to shut down, which is the behavior of the AMD primary processor module driver. It should be installed alongside the CPU chipset package from AMD. It appears you’re using the generic Microsoft version. FileVersion: 10.0.26100.2454 (WinBuild.160101.0800) Edit: Verify system time and power supply voltages in BIOS. On an older machine, dust accumulation on the CPU, GPU, PSU, and motherboard can be conductive. Reminder: Your CPU isn’t listed in the supported list for Windows 11. You may want to confirm this, but I believe CPUs from 2016 were among the first supported. https://learn.microsoft.com/en-us/windows...
The 2032 battery on the motherboard seems to be failing or nearing replacement. If it hasn’t been changed, it’s been there for 14 years and has performed well.
Johnbl appreciated your response! I also considered the sound driver option. However, at the time of the last failure, I had removed the Realtek driver. This is the most recent update available so far.
The BIOS time is accurate and comes directly from Windows, which I understand correctly. I purchased this motherboard two months ago—it’s not brand new. The seller mentioned he replaced the battery. If the BIOS time doesn’t reset when power is turned off, does that indicate the battery is fine? Or should I consider buying a new one instead?
I downloaded Realtek drivers from the Asus website, but they are only for Windows 10. Unfortunately, I couldn’t find any other drivers for the built-in sound card. If I install new drivers from Realtek during setup, they cause errors. Without drivers, the front panel with the headphone jack doesn’t function properly.
The seller claimed to have swapped it out earlier, and I assumed that if the BIOS timing doesn't clear, everything is okay. I wondered if this suggests a weak battery.
i would keep using the battery because it's essential for the motherboard to work correctly.
i would remove the old battery, wait roughly three minutes, and then insert the new one. this will reset the BIOS to its default settings, eliminating any unintended modifications made by the seller.
I changed the BIOS settings multiple times. Both using the battery and with the jumper.
Update all your drivers as well
https://www.asus.com/uk/supportonly/sabe..._download/