Random crash and blue screen ...

[Vessmir]

I get random crash ...
The game freeze (and i keep hearing in loop the last millisecond of sound that was playing) and the blue screen appear after +- 30sec then my pc reboot ...
I can get these crashes at any times sometimes after hours of gameplay some other times after just 20 - 30 min. And sometimes i can be fighting, or leveling my characters in the menu or just exploring out of combat. It really seem random ... And no overheating warning from my bios during reboots...
I did try a lot to fix it already ... My G drivers, c++ redistributable and windows 10 are all up to date. I cleaned the registry, run the game without steam in administrator mode, set quality to low ... nothing work :(

[Sador]

BSOD are something hardware or driver related most likely. You may want to check out why it's actually giving you the BSOD (either through the eventviewer or a tool like WhoCrashed) to see what's causing it. Either way, it's not related to the game itself.

[Vessmir]

Yes it is, because i have a lot of others games and they don't crash like this

[Sador]

Originally posted by Vessmir:

Yes it is, because i have a lot of others games and they don't crash like this

While that seems like a logical conclusion, that's not really how that works unfortunately.

[Lordlard69]

I have the same issues. Its caused by a memory leak somewhere, and many are in the same boat. if your hardware isn't failing and you don't have a corrupted graphics driver, you too probably have the same issue.

Unfortunately, it wont go away until they patch it, as it is caused by a memory leak. You can buy yourself more time,and potentially get rid of the blue screen by increasing the virtual memory in windows to a higher number for the page file. I set mine to 35gb, and i get about two hours before it crashes.

just google how to change virtual memory in windows. The values are in megabytes. manually set the min and max at the same number(pick a high number based on HDD size, general rule is 1.5*ram, but more wont necessarily hurt) Then make sure read only is unchecked from the file attributes as well. hope it helps

[LaskaMan]

Well, if were a memory leak most everyone on the same operating system would have this issue. What OS version are you using?
I'll watch the memory when I start it again using task manager. But this really does not feel like a standard memory leak type issue. More likely it is using some advanced graphic features that other games may not use that is triggering BSOD due to something wrong with the driver installation or a sensitivity to a particular driver having any file corruption.
I have not had a *single* bsod on windows 10 x64 up to date patched with the latest graphics drivers.

[LaskaMan]

It might help to also list out what graphic cards people have in case it is a particular card driver issue. In which case they may need to go to the hardware company and have them tweak their driver in the next update. That kind of thing happens all the time.
I am using NVidia RTX 3080.

[Vessmir]

I have windows 10 x64, GeForce GTX 1080Ti, Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz 3.50 GHz and 16gb of RAM. Drivers and Windows are up to dates. And in the Event Viewer i can see : Critical The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. And it never do this with anything else than this game ...

[Lordlard69]

I also have windows 10(x64), with 16gb and a absolute crap tier gt 730 and amd processor. kingmaker runs fine, Wrath runs fine on medium with no slowdown or lag. just crashes after jumping in resource usage, sometime bluescreen, sometimes not. crash was happening every few minutes, but adding more virtual memory changed it to every few hours. This with game breaking bugs has been an exercise in frustration.

It might be an optimization problem on lower end systems too, perhaps some newer systems have workarounds in their architecture that prevents the crash, and wasn't known until they got a larger section of hardware profiles.

[Viper]

BSOD is an OS crash. The OS layer and app layer are isolated from each other Therefore it cannot be the game and has to be something that is in that layer of operation. That would be the hardware itself. The OS itself ( corrupted system files ) or the interface between them ( The drivers ). Run WhoCrashed to see and get some hints about what is causing it...if your sure it actually is a BSOD..which would flash a blue screen with an error on it for a few seconds and immidiatelly reboot your PC.

[Sador]

This game is surprisingly heavy on machines. Disabling SSR and HBAO in the graphic settings might help, as they put less stress on your PC and thus your PC might be able to handle it better as a result.

It can be unclear as well: for example, I had a PC that worked entirely fine until I started a specific game, and then after 10-20 minutes my PC would crash. Turns out the power supply was faulty (but not in a "not booting anymore" kinda way) and that caused the problem... Even though GPU or fans would've been a more likely problem. It can be tricky to diagnose unfortunately.

[Viper]

This is the procedure for checking your system file integrity with Windows System FIle Checker:
1
Make sure you've installed the latest updates for Windows 10, and then restart your machine. To find out more, read Update Windows 10.
2
In the search box on the taskbar, type Command Prompt, and right-click or press and hold Command Prompt (Desktop app) from the list of results. Select Run as administrator, and then select Yes.
3
Type DISM.exe /Online /Cleanup-image /Restorehealth (note the space before each "/"), and then press Enter. (Note: This step may take a few minutes to start and up to 30 minutes to complete.)
4
After you see a message that says "The operation completed successfully," type sfc /scannow (note the space between "sfc" and "/") and press Enter.
5
After you see a message that says, "Verification 100% complete," type exit.

[Lordlard69]

True, but memory access violations caused by apps can cause the kernel to crash, if they try to write paged memory to a non paged area, usually caused by a memory leak in either the code or the driver, and since nvidia is on a unified driver architecture, and multiple people have had the same problem with different OS and Components, it would indicate a problem with the engine or the code. Might not be a memory leak perse, but a shader returning a null value, until it overtakes the resources. Unity is notorious for being weird about memory.

[Viper]

Originally posted by Lardblood69:

True, but memory access violations caused by apps can cause the kernel to crash, if they try to write paged memory to a non paged area, usually caused by a memory leak in either the code or the driver, and since nvidia is on a unified driver architecture, and multiple people have had the same problem with different OS and Components, it would indicate a problem with the engine or the code. Might not be a memory leak perse, but a shader returning a null value, until it overtakes the resources. Unity is notorious for being weird about memory.

maybe but with one or 2 reported occurences. I would tend to suspect a PC problem first. I have never had or seen a BSOD that was caused by an app. I had one several years ago being caused by a flaky HDD..and another longer ago being caused by a lose memory stick. First they should verify it actually is a BSOD. Your PC rebooting does not mean BSOD. IF there was no error screen between that was blue obviously it was not.

[Lordlard69]

Originally posted by Viper:

Originally posted by Lardblood69:

True, but memory access violations caused by apps can cause the kernel to crash, if they try to write paged memory to a non paged area, usually caused by a memory leak in either the code or the driver, and since nvidia is on a unified driver architecture, and multiple people have had the same problem with different OS and Components, it would indicate a problem with the engine or the code. Might not be a memory leak perse, but a shader returning a null value, until it overtakes the resources. Unity is notorious for being weird about memory.

maybe but with one or 2 reported occurences. I would tend to suspect a PC problem first. I have never had or seen a BSOD that was caused by an app. I had one several years ago being caused by a flaky HDD..and another longer ago being caused by a lose memory stick. First they should verify it actually is a BSOD. Your PC rebooting does not mean BSOD. IF there was no error screen between that was blue obviously it was not.

Mine was a blue screen, access violation, first time. IRQ not equal to or less than zero, second time. First one was caused by paged write violation. Second one the video driver crashed. Ran diagnostics, verified files, and increase virtual memory allocation, for first one. second one re downloaded and installed driver. This fixed the bsod issues, but game still crashes every hour or two. the crash logs indicate errors in light map definition, skeletons, and trying to load a null shader. This is followed by a crash and stack dump. Which is why i think it is related to the engine or graphics processing. The Bsods are probably symptoms of a cascade of errors behind the scenes, i sent my crash logs, so hopefully if it is on them they get it fixed in patches.

[GerbilForce]

Hey, same exact problem here, and everything is absolutely 100% updated/intact/not faulty on my end, trust me ive checked and double checked. This is the only game that causes it. The only thing ive found that helps, somewhat, is running the game in windowed mode on potato settings. This buys me a few hours, maybe, before it inevitably crashes and burns.