Hello and welcome to the forum!
It would help greatly if you could follow the
BSOD Posting Instructions, run the data collection tool there and upload the zip file. That gives us all of the troubleshooting data we're likely to need.
There is one common thread running through all your dumps; they all fail with a STACKPTR_ERROR. These are memory pointers that point to a structure called a stack - they are used for storing temporary data. This error indicates that a stack pointer is no longer pointing at the proper memory address. Often this is a driver foul-up and sometimes it's a RAM error. Since your system is fine with Hyper-V disabled we can probably discount a RAM problem, so we're looking for a driver that fouls-up only when running under Hyper-V. This is going to be a third-party driver of course, Microsoft drivers have been so well and so extensively tested that they can be considered faultless.
There is a second common theme that runs through most of your dumps; there is a network access taking place. In addition in some dumps I can see storage drive accesses and graphics driver accesses as well - it looks as though most dumps failed during a video streaming operation? The graphics driver nvlddmkm.sys is referenced in some dumps, but the version of this driver you have is very current...
Code:
0: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff801`298a0000 fffff801`2d2c8000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Thu Jan 18 08:57:27 2024 (65A8CBD7)
CheckSum: 03903636
ImageSize: 03A28000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
However, a couple of dumps also specifically reference your LAN driver (rt640x64.sys)...
Code:
6: kd> lmvm rt640x64
Browse full module list
start end module name
fffff802`9fd90000 fffff802`9fea8000 rt640x64 T (no symbols)
Loaded symbol image file: rt640x64.sys
Image path: rt640x64.sys
Image name: rt640x64.sys
Browse all global symbols functions data
Timestamp: Tue May 11 06:30:41 2021 (6099FA61)
CheckSum: 0011EFE0
ImageSize: 00118000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
This driver, as you can see, is getting quite old now, so it's not impossible that this driver is the cause of the system hangs that cause your BSODs. Even though this driver is only specifically referenced in only two dumps it will have been called in all of the dumps that were performing a networking operation (and that's most of them).
I took a look at your motherboard website to see whether there was an updated driver there, and MSI do not support Windows 10 on this motherboard, only up to Windows 7, so there is no later driver. You're running Windows 10 on unsupported hardware, so you might expect to have some issues.
I did wonder whether you might be able to source an updated driver from
Realtek (it's a driver for a Realtek 8136/8168/8169 adapter) but a quick search seems to suggest that only Windows 7 drivers are available for this LAN adapter. Where did the driver you have come from? Are there any optional Windows updates for your LAN adapter? Be very wary of using tools like DriverEasy to find updated drivers, they are not reliable.
If you have a WiFi adapter available, even a USB adapter, you might try using that instead of the LAN adapter to see whether that's stable with Hyper-V. That would at least help to confirm whether it's the LAN adapter that is at fault. If you try this then first disable the LAN adapter (in Device Manager) and then reboot, so that the rt640x64.sys driver is not loaded.
In any case, please upload the SysnativeBSODCollectionApp output, there may be more clues in there.
