Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Here is a thread on the Driver/WUDFRd error, which seems to confirm hardware issues:
https://reddit.com/r/pcmasterrace/comments/1alssc4/lastgasp_attempt_at_a_fix_the_driver_driverwudfrd/
What CPU are you using? Just curious as I have heard some suggestions that it may affect those with higher end 13th and 14th gen intel cpu's. Just speculating though. I've looked at other Unreal 5 games, and none of them blue screen my pc, but there are stability issues with many of them and unreal 5 seems to not like 13900k and 14900k intel cpu's.
It's not specifically UE5, it's just UE5 is common to do shader caching, which pushes your CPU to 100% load for a brief time. This exposes a problem in the voltage that intel never fixed and causes the computer to crash. You have to do tune your settings in the bios to play games like that on those processors.
Intel never fixed it?
Intel just released the 0x12F microcode with a "we really promise we fixed it now".
Wasn't it placed into motherboard BIOS updates so the users needed to manually do a BIOS update to fix things?
I decided to try and fix the apparent access violations by taking full ownership of the system drive away from trustedinstaller to my admin account. This ♥♥♥♥♥♥ up windows 11, and so I reinstalled it.
The game now works just fine. No more blue screens.
However reinstalling windows does so many things, it's impossible to know what actually fixed the issue.
Good to know it wasn't hardware however.