Originally posted by Hardware Hero™:

Originally posted by Dubgaming:

i dont think it is an overheating issue.

What does the event viewer say? Look for hardware faults critical. Then look at errors just before. Get the stop code and look it up online. Most likely it's hardware related because that's what windows does when it detects an issue that's so bad, it has to crash dump everything right away so you don't lose data.

Here we go with the “it’s your PC” post! How is it his PC when EVERY game is ok! Wow

Disable everything that uses an overlay, nvidia experience, gigabyte HUD, steam overlay, etc.

End process on windows indexer.

No more crashes.

It's not your PC's hardware, it's the game's use of your PC's hardware.

If you were on Windows 95, sure it could be the game. But these days, no application can/should be able to crash OS. So it has to be hardware or driver. They guy above me who suggested to look in the logs was spot on. Start analyzing the problem, eventually you will find something to give you hints.

Originally posted by Mr Blue Playdoh:

Originally posted by Hardware Hero™:

What does the event viewer say? Look for hardware faults critical. Then look at errors just before. Get the stop code and look it up online. Most likely it's hardware related because that's what windows does when it detects an issue that's so bad, it has to crash dump everything right away so you don't lose data.

Here we go with the “it’s your PC” post! How is it his PC when EVERY game is ok! Wow

it's a fact... it's either a hardware problem (like ram or broken ssd or even corrupt driver) or simply dust.
if the ram has some broken fractions it all depends on the load if something causes problems or not.... basicly a game that wont use all the ram can still run fine, while one that uses a lot of ram result in a bluescreen.

Originally posted by BoA Depadumama:

"IRQL not less or equal"

lol, this is obviously a hardware problem and one of the worst since it's not so easy to figure out which of the many possibilities causes it (driver, harddrive, gpu, ram, overheating cpu, etc).
if the shop where you went was actually good the employee would have told you that

Originally posted by Mr Blue Playdoh:

Originally posted by Hardware Hero™:

What does the event viewer say? Look for hardware faults critical. Then look at errors just before. Get the stop code and look it up online. Most likely it's hardware related because that's what windows does when it detects an issue that's so bad, it has to crash dump everything right away so you don't lose data.

Here we go with the “it’s your PC” post! How is it his PC when EVERY game is ok! Wow

Actually there is a good answer for this, it's because not every game hits every piece of a driver or instruction set inside the north or south bridge. So you will occasionally run in to a game that uses an instruction that 99% of other games don't and if there is a fault it will expose it. As a developer for enterprise applications we tend to avoid "funny" stuff and use safe high level languages and API that avoids those 1% areas. Game developers cannot always do this and get what they want accomplished and sometimes have to dip in those instruction sets.

For example if you needed a custom recursion for injecting code during runtime, this is avoided as it can be messy. I can count on one finger I've ever done this in an enterprise environment and it was eventually replaced with much safer code.

As an EA application I would honestly expect that kind of code to be laying around until some tech debt cycles are done. Hell most beta's on AAA titles I've participated in had the same issues that eventually got cleaned out.

You are also going to run in to some "fudge factor" such as a compiled binary on an intel processor might not be the same compiled binary on an amd processor or sparc, etc. This can sometimes cause a mismatch in instruction sets in the binary. It's rare but lawsuits have happened over it, such as that one time intel cpu's purposely added an addition instruction to slow down running on amd cpu's. Fun times.

I have nearly the same build as you, although I'm not running a WC system. What BSOD are you seeing. I see WHEA_UNCORRECTABLE_ERROR typically. I run every other game in my library with out problem. I have also tried essentially everything mentioned. I'm hoping that this is an optimization issue.
EDIT**
My build is and I9-9900KF
RtX 2080
32GB RAM
1Tb SSD

Do either of you have any cpu overclocks or non default settings in your bios?
Also, best if you post in the bugs section so the devs can see the thread.

nope all default and ok ill repost there

and yea Bazir same error

Game auto-saves every 20mins now, maybe this is an issue.

I also got a bsod.
As soon as my friend and I expanded our base, added two smelters and two kilns and entered the copper and bronze age my performance dropped hard and the system went to BSOD.
Never happens on this computer. Clearly unusual.

I uploaded my world save state to discord and he downloaded the files to his computer and hosted, as his PC is beefier than mine. Within an hour we were starting to get the same type of experience. Lag. Not seeing updated locations of one another on screen. etc.

At one point I saw his character running midair above the back fence of our property for a solid 10 seconds. I said wtf are you doing in your game, and he said he had hopped the fence 20 seconds before that to go chop trees.

So for god knows how long, prob a solid 30+ seconds, he showed in my game as pulling an airwalk stunt over the property. It just becomes unplayable. Seeing him swinging at a mob in front of me, but the mob is dying 30 feet away because that is where he actually is standing.

Using an ultimate near one another to share the buff and realizing we were 'near' each other on screen but in reality, too far apart for it to work.

Game needs some tweaks.

Originally posted by Dubgaming:

i dont think it is an overheating issue.

What does the event viewer say? Look for hardware faults critical. Then look at errors just before. Get the stop code and look it up online. Most likely it's hardware related because that's what windows does when it detects an issue that's so bad, it has to crash dump everything right away so you don't lose data.

fix your computer.

WHEA uncorrectable errors are caused only by cpu instability.

no problems here. its only 1 GB i dont see how it can cause issues like the ones reported here. then again i dont know enough about it to say for certain one way or the other. BSOGs are usually related to hardware issues though.