TheFullTimer Posted September 15, 2018 Share Posted September 15, 2018 (edited) Recently switched to Threadripper 1900X & X399 Designaire. SVM enabled, fresh Unraid installation on USB, everything looks great with any VM except Windows 10. Every single installation will BSOD w/ System Thread Exception Not Handled. This happens after Key Activation & in four different installations it doesn't seem to matter which drivers I install first, nor whether I am using Windows ID or offline. Only thing that comes to mind as I write this is that I've been using Ninite to install applications and I usually BSOD a few reboots after that as I get more setup completed. I am going to take the weekend to think it over. Edited September 16, 2018 by TheFullTimer Removing a line Quote Link to comment
TheFullTimer Posted September 16, 2018 Author Share Posted September 16, 2018 Bump, anyone with this System Thread Exception issue? Quote Link to comment
TType85 Posted September 16, 2018 Share Posted September 16, 2018 When I rolled my wife's windows 10 machine in to my new TR setup I had BSOD issues, I was using an image of her drive. I gave up and just did a fresh install and it's working great. Quote Link to comment
3flappp Posted September 16, 2018 Share Posted September 16, 2018 Which version of windows 10 are you trying to install? I had issues installing the latest version (18XX). I tried redownloading on multiple machines and network, checking the hash, etc. just to make sure. Then I tried an older version (1703) and it worked fine including updating to the latest version. I'm not sure if i'm allowed to link to any sites, however, you should be able to find a list of all the MSDN links for Windows ISOs. Remember to check hashes. Quote Link to comment
david279 Posted September 16, 2018 Share Posted September 16, 2018 Try adding this to your flash config kvm.ignore_msrs=1 Quote Link to comment
testdasi Posted September 16, 2018 Share Posted September 16, 2018 Try starting with only 1 core, install the latest virtio drivers and probably your ninite stuff and then shutdown and add the cores back. Quote Link to comment
TType85 Posted September 16, 2018 Share Posted September 16, 2018 1 hour ago, 3flappp said: Which version of windows 10 are you trying to install? I had issues installing the latest version (18XX). I tried redownloading on multiple machines and network, checking the hash, etc. just to make sure. Then I tried an older version (1703) and it worked fine including updating to the latest version. I'm not sure if i'm allowed to link to any sites, however, you should be able to find a list of all the MSDN links for Windows ISOs. Remember to check hashes. I installed Windows 10 Pro 1803, assigned all the CPU and ram, assigned the disk manually (/dev/disk/by-id/nvme-xxxxxxxxx) Quote Link to comment
TheFullTimer Posted September 17, 2018 Author Share Posted September 17, 2018 (edited) I also clean installed 1803 last week and experienced my issues. I'll find a 17xx image and try that instead. I wonder what was changed that would cause this trouble. I had previously tried installations with a single core and 2gb of ram, and other combinations, but all experienced the bsod after a few installations and reboots. Edited September 17, 2018 by TheFullTimer New paragraph Quote Link to comment
testdasi Posted September 17, 2018 Share Posted September 17, 2018 21 hours ago, TType85 said: I installed Windows 10 Pro 1803, assigned all the CPU and ram, assigned the disk manually (/dev/disk/by-id/nvme-xxxxxxxxx) That might be the problem. NVMe drive shouldn't be passed through via the /dev method. I have stability issue doing it that way. You may want to try passing it through as a PCIe device (the same way you would do with a USB controller or NIC etc.) Quote Link to comment
TType85 Posted September 17, 2018 Share Posted September 17, 2018 1 minute ago, testdasi said: That might be the problem. NVMe drive shouldn't be passed through via the /dev method. I have stability issue doing it that way. You may want to try passing it through as a PCIe device (the same way you would do with a USB controller or NIC etc.) So far it has been stable for me. I have 2 of the same type in there and they have the same vfio id so it is harder to pass through. Quote Link to comment
testdasi Posted September 17, 2018 Share Posted September 17, 2018 4 minutes ago, TType85 said: So far it has been stable for me. I have 2 of the same type in there and they have the same vfio id so it is harder to pass through. That's interesting. Mine crashed my VM every time there's high IO. Quote Link to comment
TType85 Posted September 17, 2018 Share Posted September 17, 2018 14 minutes ago, testdasi said: That's interesting. Mine crashed my VM every time there's high IO. High sequential IO was no issue (copied over 40GB of games and docs) Quote Link to comment
TheFullTimer Posted September 19, 2018 Author Share Posted September 19, 2018 Found what may be the cause for my issue. System Thread Exception Not Handled during my Avast Antivirus installation. Repeated a clean install of Windows 10 and it happens even during a minimal installation of Avast on both 1709 & 1803 Win 10 Pro. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.