General Discussions

[mike-eee]

Hello All,

I am running into a heck of an issue, and I believe it is AMD-related.  The issue, in particular, is related to using Hyper-V in Windows 10, starting with 1903.

The problem is that BSODs will occur randomly while the machine is left unattended, resulting in a bugcheck that points to what is called a Synthetic Watchdog Timeout.

I have been on numerous forum boards and have gotten zero solutions to this problem.  Some brave souls have attempted to assist, but nothing substantiative has resulted in fixing this issue. 

The only way to fix this issue thus far is to restore back into 1809 where zero BSODs occur and everything works wonderfully as expected.

However, at some point, 1809 will become unsupported so this is starting to light a fire of anxiety under me.

My hunch is that it is AMD-related.  FWIW I am using a Ryzen 2700x (which is amazing, btw).  And in fact, I am not even 100% sure it is AMD-specific, except that a comment was made on one of the forums I reached out to that BSODs were occurring.

So, I am reaching out here to maximize awareness.  My hope is that perhaps a representative of AMD can reach out to the Hyper-V group and see if they can identify fix this problem.  I am not sure if that is even possible, but again I am to the point of desperation and hope is all I have.

Here are some resources that provide more information:

Synthetic Watchdog Timeout: What is a Bug Check 0x1CA: SYNTHETIC_WATCHDOG_TIMEOUT – Ask Bob 

The reported issue to MSFT directly: https://aka.ms/AA6ekem 

Reddit: https://www.reddit.com/r/HyperV/comments/djqnhk/encountering_bsods_on_windows_10_hyperv_host/ 

Technet 1: https://social.technet.microsoft.com/Forums/en-US/814bd3ec-6cfd-4801-ae33-dff513ee0846/bsod-on-hyper...

Technet 2 (The first one was moved without explanation so had to create another): BSOD on Hyper-V Host after Upgrading to 1903 

Twitter Thread: Mike-EEE on Twitter: "Are there any #HyperV resources in my #MSFT network? I and a few others are ru... 

Any guidance/recommendations/connection/pointers would be greatly appreciated!

[mike-eee]

Thank you to the moderators that approved this post and the subsequent edit.  Much appreciated. 

Happy New Year.

[elstaci]

This Tech site specializes in BSODs and is managed by Microsoft Windows specialist. I would log in and post your question there. They have their own diagnostic software that you will be asked to run to gather information when it BSODs.

Here is the Website: BSOD, Crashes, Kernel Debugging | Sysnative Forums 

[mike-eee]

Ah thank you for that, elstaci‌!  I totally forgot to put that in my list above and did open a thread there at one point already:

Getting my B*** Kicked by BSODs on the Daily | Sysnative Forums 

It was through that site that I learned of TechBench that allowed me to download 1809 to get away from the BSODs.  1809 is really the only answer that we've found to this issue thus far.

[goodplay]

You might want to also try posting on https://www.tenforums.com/virtualization/

Can't say if thread on page 2 is of any interest to your issue......

[mike-eee]

OK cool... I was unaware of that forum, thank you for pointing it out.  FWIW someone else on the technet forum is having some luck with using the latest AMD drivers.  I did try using the latest AMD drivers with 1903 and had zero luck.  1909 might be a different issue, I am hoping.  Here's the current plan of attack:

BSOD on Hyper-V Host after Upgrading to 1903 

I appreciate your and everyone else's suggestions and insight here!

[hardcoregames_]

I found VirtualBox to be better than Hyper-V for my needs. That's my 2 bits worth.

[mike-eee]

Whoa!  I was not aware of this... only VMWare.  This appears to be a free, community-based project, correct?  This might be a viable direction if we get to the point that 1809 becomes unsupported.

[hardcoregames_]

mike-eee wrote:

Whoa!  I was not aware of this... only VMWare.  This appears to be a free, community-based project, correct?  This might be a viable direction if we get to the point that 1809 becomes unsupported.

I use VMs with windows 95 and 98 which are blocked by Hyper-V but they work with VirtualBox

VirtualBox is a gamers friend as the GPU is available for games that do not work with Windows 10 properly

[mike-eee]

Wow... what about GPU during regular Windows use?  The thing I hate about Hyper-V (besides the fact that it randomly BSODs starting in 1903 ) is that its rendering is atrocious in client VMs.  Scrolling web pages between the host machine and VM client machines is painfully differential.

[hardcoregames_]

I use VirtualBox localhost but I suggest using a remote desktop and see if your network latency is acceptable

[mike-eee]

Oh yeah... I use Virtual Machine Connections which is all localhost.  Wouldn't have it any other way.

[hardcoregames_]

i am saving up for more hardware and i may setup a different machine for remote desktop to virtual machines

hyper-v does not work on many laptops so this motivated me to use VirtualBox which does not care

[mike-eee]

Doh... after all that, it looks like this is happening on Intel machines, too:

Bert Kassies on Twitter: "Same problem with Hyper-v here. 1809 fine. 1903 and 1909 BSODs. My host ha... 

Oh well.. at least I got to meet some cool peeps on here.

[mike-eee]

Hey all... wanted to add a quick reply here that this ended up being an undisclosed bug on MSFT's side that was eventually fixed in a KB.  Starting with 18363.752 to be exact.  Doesn't really matter as all new installs seem to have it and everything now works as expected.  Very happy and relieved!  Thank you to all here who took the time to reply to this thread and to offer their thoughts.  It is very cool of you!  Stay safe out there.