Hard reboot when using VcXsrv on Windows 10 build 2004
Brought to you by:
marha
Menu
▾
▴
#126 Hard reboot when using VcXsrv on Windows 10 build 2004
So i recently updated to the latest Windows 10 build 2004. Before, I had been using VcXsrv for over a year to run X11 programs both remotely and from WSL, without any trouble.
After I updated to 2004, starting any X server (VcXsrv is my preferred one, but Ming and the integrated server of MobaXterm have teh same problem) with clipbiard sharing on will hard-reset my machine after a minute or two. I am not 100% sure disabling clipboard sharing fixes the problem entirely, but it looked that way.
There is no BSOD, no error message, nothing, the machine just hard resets to BIOS. Of course there is at least some Windows bug involved, since no user-space program should be able to do this, but I figured I should report it here as well as with MS, just for visibility. I have since rolled back to 1909 since I need this machine for actual productivity.
As you can imagine, this is nigh impossible to debug, since the moment it happens, everything is gone, and even logs won't hit the disk. I will try to replicate this on a VM, but I have little hope that it will work, since my gut tells me the GPU and/or its drivers might be involved. I will update this ticket if-when I find new information. Last resort, reinstall my machine from scratch, update to 2004 and see if it helps.
So I took the plunge and reinstalled my machine from scratch, and did all updates up to 2004 without installing anything besides Chrome. Then I activated WSL, and WSL2, plus did the 0x1cb kernel update so I could activate WSL2. Started VcXsrv, and boom, hard reboot.
Again, I am sure there is some bug on the Windows side here, since no program should eb able to cause such an error. But then again, VcXsrv clearly does something that is the root cause, since without it, the machine is stable.
works for me so far in
Edition Windows 10 Pro
Version 20H2
Installed on 28.09.2020
OS build 19042.685
Experience Windows Feature Experience Pack 120.2212.551.0
didnt use a Xserver for quite some years so i cant tell if this is now resolved or it's some other issue on ur end
For what it's worth, with the most recent cumulative update for 2004 (KB4579311) it seems the crash has gone away. I have been running typical day-long sessions with an X server running and my Debian switched to WSL2 without issue for about a week now.
I'm having a very similar problem with VcXsrv 1.20.8.1 on Windows 10 Pro 10.0.19041: my computer (Dell Precision laptop) will BSOD to a screen with a QR code and frowny face, then reboot into another screen with a QR code and start beeping like mad. Hard reset via the power button is the only thing that gets me back up and running.
I thought it was a problem with the laptop itself until I realized that it never happened when I didn't have VcXsrv running. Same version of VcXsrv running on a different laptop with Windows 10 Enterprise 18362.19h1_release 190318-1202 never causes problems.
I'll test it later with the latest version of VcXsrv to see if it continues. Thought I'd add this to the discussion in case anyone knows what the common denominator is.
Just a quick update on this, for what it's worth: my "problem" laptop upgraded its firmware automatically and I upgraded to the latest version of VcXsrv and I still experienced this problem.
Two more things: (1) I forgot to mention that the BSOD occurs after a few hours of using VcXsrv just fine---in fact, it works great; and (2) the BSOD happened even though I exited VcXsrv. If I never launch VcXsrv, I never have a problem. And on my "other" laptop described above, I can keep it running indefinitely with no problems. Very strange indeed.
Last update: turns out that the problem laptop is still BSOD'ing from time to time, so VcXsrv either has nothing to do with it, or is a non-essential contributing factor.