Hey!
Has anyone else encountered this issue after recent Windows updates, where the computer starts rebooting for no apparent reason while working in VR? Even in the editor? Eventvwr.msc reports error 1801. Any ideas on how to fix this? Eventvwr.msc says something about secure boot, but I have secure boot enabled in the BIOS. I don’t really understand what’s causing this error.
Hey there @AnstasyiA! Welcome to the community! Error 1801 is generally a secure boot key error, but this shouldn’t be related to UEVR and generally shouldn’t immediately reboot.
If under high load your computer reboots, it’s possible that you may be maxing out your PSU or overheating. Are there any other related errors in event viewer?
I’m noticing other users are having the 1801 error lately but it is usually a red herring to their actual issue.
Hello. Thanks for the reply. No, there are no other errors. This happens even in an empty, newly created UE project. Due to the inability to fix this error, my project has almost completely stalled.
Does the error have a bit at the end The operation completed successfully.? I’m still not sure it’s related. Do you get forced to reboot during heavy resource use as well?
Disclaimer: One or more of these links are unaffiliated with Epic Games. Epic Games is not liable for anything that may occur outside of this Unreal Engine domain. Please exercise your best judgment when following links outside of the forums.
I’m not sure I understood the question correctly, but there’s no such error message. I’ll send you the full error message (some parts will be in non-English). Error message:
Обновленные сертификаты безопасной загрузки доступны на этом устройстве, но еще не применены ко встроенному ПО. Ознакомьтесь с опубликованными рекомендациями, чтобы завершить обновление и сохранить полную защиту. Сведения о подписи этого устройства приведены ниже.
DeviceAttributes: BaseBoardManufacturer:ASUSTeK COMPUTER INC.;FirmwareManufacturer:American Megatrends International, LLC.;FirmwareVersion:FA507NV.316;OEMModelBaseBoard:FA507NV;OEMManufacturerName:ASUSTeK COMPUTER INC.;OSArchitecture:amd64;
BucketId: 3db5e8d0cbbf22c6b6e19bcba905d169f2fe4622697a13da4b49885f38b9a7f1
BucketConfidenceLevel: Under Observation - More Data Needed
UpdateType:
Дополнительные сведения см. на странице Windows Secure Boot certificate expiration and CA updates - Microsoft Support.
Yes, the system also reboots if I’m connecting VR and UE5 at the same time. If I don’t connect the VR, the reboot doesn’t occur.
I don’t believe your secure boot keys are related to the crashing, but we can resolve that to verify this before continuing if you’d like. Otherwise, we could take a look at stress testing to see if it’s power/hardware related if there’s no visible errors once this is resolved.
Follow the link in the error to get the instructions and get the certification keys up to date manually. Which should resolve this specific error.
Disclaimer: One or more of these links are unaffiliated with Epic Games. Epic Games is not liable for anything that may occur outside of this Unreal Engine domain. Please exercise your best judgment when following links outside of the forums.
I installed all four certificates. And after I tried running the card with VR in the editor, and the computer still restarted, but this time there was no error 1801. Instead, 6008 appeared, and then 41. I also want to rule out anything related to the power supply, because the computer doesn’t even have time to warm up before this error occurs. And everything works fine in VR games. I also noticed that the computer restarts precisely after I connect via VR, meaning I can keep SteamVR and UE5 open, and this error won’t appear, but as soon as I connect VR to the computer, something happens almost immediately and the computer silently restarts.
Technically power issues don’t need to warm up, 41/6008 are what I expected to see initially. This usually happens when something hardware wise is being odd, but in rarer cases some software can trigger this, and we might have to consider that in this case since I believe the FA507NV is the Asus TUF A15, a laptop, correct? This (mostly) rules out power misconfiguration.
Since it happens when you access VR and Unreal at once, I’m going to guess that it’s possibly something involving rendering. Does it come with the “Asus Armoury Crate” utility? If so, what is the GPU mode set to? I have read reports that in some instances anything but “Ultimate” can cause issues when the MUX swaps under heavy immediate load, but it’s a bit different than your crashing.
Disclaimer: One or more of these links are unaffiliated with Epic Games. Epic Games is not liable for anything that may occur outside of this Unreal Engine domain. Please exercise your best judgment when following links outside of the forums.
Yes, my laptop is Asus TUF gaming a15 with armoury crate software. When I work with UE5 and VR especially, I always have turbo mode on.
That’s odd! So since it’s still giving the kernel power and power loss errors, it’s less likely to be software related. I had an issue before with my previous laptop that when running heavy software with my VR headset connected would trip the over current protection somewhat inconsistently, but it would result in a full and immediate restart when it happens.
What VR headset are you using? Is there a wireless mode or a different port possible to test this theory?
I have a Pico 4. I was already thinking that maybe the problem was with the way I connected to the PC. I always connected through a virtual desktop streamer, and after problems arose, I downloaded the official Pico Connect app, but nothing changed.
Hmmm. This is a tough one. Does toggling GPU hardware acceleration change anything? Does the restart occur when the cable is connected or just as the software is launched?
GPU acceleration doesn’t affect it. The connection method doesn’t affect it either. The reboot happens at a completely random moment. In fact, I recently discovered that even UE5 isn’t to blame, because the same thing happens in other engines. I think the only solution is to wait for a Windows update with a fix.
I had assumed it wasn’t just the engine at play originally. The power cycling on high resource usage is definitely a problem. Hardware or software issues that can cause hard failures like that are difficult to diagnose.
If you do manage to ascertain where the issue is coming from, definitely let me know.
1 Like