Windows 10 VM BSOD on load (gaming), stable ran natively

Software & Operating Systems VFIO
1

I recently reinstalled Windows as I had some janky “no bloat” version installed before. It was running completely fine except for the fact that I couldn’t install Microsoft Store or set a default browser on it. Everything else was perfect. But in the end I got sick of it and decided to install a proper Windows 10 build. As soon as I did, the problems started. If I run a game in my VM, it BSODs. Sometimes on launch, sometimes 30 seconds into the game, sometimes a few minutes into the game. The host does not crash. Running the Win10 install is completely stable. I’ve tried downgrading the kernel, qemu, and even the Windows 10 build itself.
neofetch:

OS: Arch Linux x86_64
Kernel: 5.4.8-arch1-1
Uptime: 1 day, 11 hours, 25 mins
Packages: 1874 (pacman)
Shell: bash 5.0.17
Resolution: 3840x2160
DE: Xfce
WM: Xfwm4
WM Theme: Default
Theme: Adwaita-dark [GTK2], Breeze [GTK3]
Icons: Adwaita [GTK2], breeze [GTK3]
Terminal: alacritty
CPU: AMD Ryzen 7 2700X (16) @ 3.700GHz
GPU: NVIDIA GeForce GTX 980 Ti
GPU: AMD ATI Radeon RX 470/480/570/570X/580/580X/590
Memory: 24972MiB / 32104MiB

Windows 10 Build (currently): 1809

My VM xml: http://ix.io/2pdh
dmesg output: http://ix.io/2pdf
Windows Event Viewer Critical Error XML:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
  <EventID>41</EventID>
  <Version>6</Version>
  <Level>1</Level>
  <Task>63</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8000400000000002</Keywords>
  <TimeCreated SystemTime="2020-06-14T23:35:01.760705900Z" />
  <EventRecordID>1944</EventRecordID>
  <Correlation />
  <Execution ProcessID="4" ThreadID="8" />
  <Channel>System</Channel>
  <Computer>DESKTOP-9M6QAL4</Computer>
  <Security UserID="S-1-5-18" />
  </System>
- <EventData>
  <Data Name="BugcheckCode">59</Data>
  <Data Name="BugcheckParameter1">0xc0000006</Data>
  <Data Name="BugcheckParameter2">0x0</Data>
  <Data Name="BugcheckParameter3">0x0</Data>
  <Data Name="BugcheckParameter4">0x0</Data>
  <Data Name="SleepInProgress">0</Data>
  <Data Name="PowerButtonTimestamp">0</Data>
  <Data Name="BootAppStatus">0</Data>
  <Data Name="Checkpoint">0</Data>
  <Data Name="ConnectedStandbyInProgress">false</Data>
  <Data Name="SystemSleepTransitionsToOn">0</Data>
  <Data Name="CsEntryScenarioInstanceId">0</Data>
  <Data Name="BugcheckInfoFromEFI">true</Data>
  <Data Name="CheckpointStatus">0</Data>
  </EventData>
  </Event>

EDIT: I also just saw this:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="volmgr" />
  <EventID Qualifiers="49156">161</EventID>
  <Level>2</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2020-06-14T23:35:01.625164200Z" />
  <EventRecordID>1941</EventRecordID>
  <Channel>System</Channel>
  <Computer>DESKTOP-9M6QAL4</Computer>
  <Security />
  </System>
- <EventData>
  <Data>\Device\HarddiskVolume4</Data>
  <Binary>000000000100000000000000A10004C000000400010000C000000000000000000000000000000000</Binary>
  </EventData>
  </Event>

Maybe looks like a power delivery issue? I’d appreciate any input or farts in the wind. I haven’t been able to get much help elsewhere.

2

It appears that kernel error 41 and that volmgr error happen together every time.

3

I forgot to mention that the VM runs fine otherwise. Only crashes when I try to game.

4

I can’t offer much help with the passthrough but have you analyzed your dumps at all?

5

Is there any chance that these games have anticheat or DRM that is causing this?

Also, have you tried ignoring msrs on the host?

6

Adubs, I couldn’t get a dump as the BSOD would be stuck at 0% (I turned off auto reboot on BSOD). Cake, I had the ignore msrs thing turned on, and no anti-cheat. I found the problem, though. For some reason my NVME drive is iffy. I tried a different drive and it worked. But it’s strange because it works fine booted natively. Must be something to do with the funkiness of the drive with my kernel.

1 Like