Dune: Awakening

Dune: Awakening

Bluescreen on launch
First try to launch i was able to get partway through creating a character when the PC bluescreened.

Since then I have tried to launch it about 6 times, having added admin privileges to launcher and executable, bluescreen soon after pressing launch on the launcher.

Here are some windows logs

*****
The propres à l’application permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DAWNSTAR\chris SID (S-1-5-21-3237212613-2401819639-984871345-1001) from address LocalHost (avec LRPC) running in the application container Non disponible SID (Non disponible). This security permission can be modified using the Component Services administrative tool.
*****

A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

****

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be (0xfffff8063bc001a3, 0x09000007f4690121, 0xffffb50d45311390, 0x000000000000000b). A dump was saved in: C:\WINDOWS\Minidump\051025-9406-02.dmp. Report Id: a83d24fe-ea7c-440f-b612-9cdd6d716c98.

****

The driver \Driver\WUDFRd failed to load.
Device: HID\VID_0B0E&PID_24C7&MI_03&Col01\9&280500b3&0&0000
Status: 0xC0000365

****
< >
Showing 1-11 of 11 comments
Zylli May 9 @ 5:42pm 
Blue screen errors are usually indicating some sort of hardware issue or very serious driver problem. The easiest way to eliminate software as the potential culprit is to reinstall or refresh Windows.

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/
Aurore May 9 @ 5:54pm 
My suspicion is it's something to do with battleye. I dont have this issue with any other games.
Dimossa May 10 @ 8:46pm 
same issue, first game that does to my system...
Aurore May 11 @ 2:25am 
Originally posted by Dimossa:
same issue, first game that does to my system...

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.
Originally posted by Aurore:
Originally posted by Dimossa:
same issue, first game that does to my system...

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.
Mordessa May 11 @ 4:22am 
Originally posted by Kashra Fall:
Originally posted by Aurore:

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?
Shintai May 11 @ 4:28am 
Originally posted by Mordessa:
Intel never fixed it?

Intel just released the 0x12F microcode with a "we really promise we fixed it now".
Originally posted by Shintai:
Originally posted by Mordessa:
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?
Shintai May 11 @ 4:39am 
Yes, and for 0x12F they have to wait for their mobo vendors to supply new BIOSes.
Aurore May 11 @ 6:05am 
Well, I have fixed the problem. But it isn't going to help any of you I'm afraid.

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.
Aurore May 11 @ 7:15am 
Update: The game did bluescreen but after playing for 45 minutes or so. Same or similar windows logs messages.
< >
Showing 1-11 of 11 comments
Per page: 1530 50