Launching Conan causing hard crash of PC

Conan Exiles PC Discussion PC Bug Reports
, ,
1

Game mode: Online Private
Type of issue: Crash
Server type: PvP
Region: America
Mods?: No
Edition: Steam

Bug Description: Launch of game causes hard crash of PC. The launcher opens and runs fine. As soon as you click “Launch,” PC goes to blue screen and restarts. One error stated that the game was attempting to write over read-only files.

PC was recently updated to Windows 11 prior to reinstallation of Conan. No other games thus far are having this problem.

Steps to Reproduce:

Please provide a step-by-step process of how the bug can be reproduced. Please be as detailed as possible; the more details, the easier it will be for us to find and fix the bug:

  1. Step 1 Run the Funcom launcher.
  2. Step 2 Click Launch.
  3. Step 3 Watch computer crash and burn.
  4. Step 4 Uninstall and reinstall game, verify files, ensure graphic drivers are UTD, etc
  5. Step 5 Repeat
3

Have you tried to give the launcher admin privileges to see if that solves the problem. It may not but it’s a shot anyway. I don’t think it’s gonna hurt anything if you do want to try.

4

The Windows 11 update was pushed by Microsoft on this PC, with no indication that it was only for “insiders.” And like I said, no other games are having this issue thus far.

5

Yes, we have tried that as well to no avail. Thank you for the suggestion, though!

6

Another suggestion would be to look at the error logs in Windows to see if there is any clues there.

EDIT: There should be no problem with W11 at all.

7

Thank you. I’m not super computer savvy, as many on here seem to be, but it seems now like maybe there is a security issue of some kind. Last crash said it was a Kernel security check error, and battleye was disabled on the launcher as a default. Trying to see if that is the problem.

8

Well, if you need to get there you should be able to right click on the start menu and go to Event Viewer. From there go to Windows logs And check out the 4 top categories there. It may shed a bit of light.

10

I will take a look at that next time! I fixed it by going scorched earth (not really) and rolling back to Windows 10, which fixed it. I still want to figure out the problem, though, cause it will bug me. lol

Thank you for helping and not being condescending about it. I appreciate it, truly! I feel dumb in the presence of tech savvy people…heh.

11

Why not troubleshoot the problem to see if it’s fixable under the current o/s. Glad you solved it.

13

It’s related to Windows 11 update KB5008215 and Windows 10 update KB5008212. Uninstalling these fixes the issue for now.

Any response from Funcom addressing this issue?

14

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.