Windows 10 WHEA UNCORRECTABLE ERROR when playing COD: Cold War

[finalbillybong]

When playing COD: Cold War I keep getting BSOD's at random times. Some times just after loading the game sometimes I can play a few matches. Weirdly this is only happening with COD: Cold War and no other game I currently play (Cyberpunk, PUBG, COD: MW). I have checked the Event Viewer and always see 'Dump file creation failed due to error during dump creation.' under Windows Logs > System. Zip from SysnativeFileCollectionApp Diagnostics can be found here: https://bit.ly/2M320cs

 

Windows System Diagnostics has been running for half an hour now so i'm not sure if it's going to finish but I shall update this post with the .zip if it does.

 

Specs:

• Core i5 9600K - Currently No OC
• MSi RTX 2080 Ventus V2 - Currently No OC
• Gigabyte Z390 Gaming M Rev 1.1
• 16Gb DDR4 Cosair Vengence
• WD Black PC SN700 NVMe 500GB boot drive
• Samsung SSD 850 EVO 500 GB storage
• KINGSTON SV300S37A120G strorage
• 650W Bronze Cosair
• Windows 10 Pro 64 bit Retail

 

Things I have tried to diagnose:

 

• Ran memtest86+ over night (8 passes) - no errors
• Ran Prime95 for about 10 hours - no errors
• Checked all drivers are up-to-date.
• Check S.M.A.R.T of all hard drives. All OK.
• Flashed BIOS to latest version
• Reset BIOS to defaults
• Removed all OC's on GPU and CPU
• Reset XMP profile to default.
• Full clean Windows 10 reinstall form USB installation media
• Run SFC and DISM. All OK.

 

My CPU and GPU temps seem fine. CPU got up to 70c running Prime95 and GPU does not go above 65c when gaming.

 

While searching aorund for BSOD's related to COD: Cold War I have seen other suggestions for game settings of which I have tried all of them including running game in DX11 and turning off V-Sync amoungs others.

 

I am at an absolute lose as to what to do next.

[Applefreak]

5 minutes ago, finalbillybong said:

When playing COD: Cold War I keep getting BSOD's at random times. Some times just after loading the game sometimes I can play a few matches. Weirdly this is only happening with COD: Cold War and no other game I currently play (Cyberpunk, PUBG, COD: MW). I have checked the Event Viewer and always see 'Dump file creation failed due to error during dump creation.' under Windows Logs > System. Zip from SysnativeFileCollectionApp Diagnostics can be found here: https://bit.ly/2M320cs

 

Windows System Diagnostics has been running for half an hour now so i'm not sure if it's going to finish but I shall update this post with the .zip if it does.

 

Specs:

• Core i5 9600K - Currently No OC
• MSi RTX 2080 Ventus V2 - Currently No OC
• Gigabyte Z390 Gaming M Rev 1.1
• WD Black PC SN700 NVMe 500GB boot drive
• Samsung SSD 850 EVO 500 GB storage
• KINGSTON SV300S37A120G strorage
• 650W Broze Cosair
• Windows 10 Pro 64 bit Retail

 

Things I have tried to disagnose:

 

• Ran memtest86+ over night (8 passes) - no errors
• Ran Prime95 for about 10 hours - no errors
• Checked all drivers are up-to-date.
• Check S.M.A.R.T of all hard drives. All OK.
• Flashed BIOS to latest version
• Reset BIOS to defaults
• Removed all OC's on GPU and CPU
• Reset XMP profile to default.
• Full clean Windows 10 reinstall form USB installation media

 

My CPU and GPU temps seem fine. CPU got up to 70c running Prime95 and GPU does not go above 65c when gaming.

 

While searching aorund for BSOD's related to COD: Cold War I have seen pther suggestions for game settings of which I have tried all of them including running game in DX11 and turning off V-Sync amoungs others.

 

I am at an absolute lose as to what to do next.

Could be corrupted driver or corrupted system files. This error also appears if components overheat due to OC. You can try sfc /scannow and then DISM (you need to look that one up) to replace the system files. Depending on your internet connection, this will take between 30 minutes to a couple of hours.

[finalbillybong]

29 minutes ago, Applefreak said:

Could be corrupted driver or corrupted system files. This error also appears if components overheat due to OC. You can try sfc /scannow and then DISM (you need to look that one up) to replace the system files. Depending on your internet connection, this will take between 30 minutes to a couple of hours.

Yes tried that already, I forgot to add it to OP. I've tried so many things, clearly I can't remember them all First pass of SFC found corrupt files but was unable to fix the DISM then downloaded new files, second pass of SFC said all was OK. I will update OP.

[Applefreak]

4 minutes ago, finalbillybong said:

Yes tried that already, I forgot to add it to OP. I've tried so many things, clearly I can't remeber them all First pass of SFC found corupt files but was unable to fix the DISM then downloaded new files, second pass of SFC said all was OK. I will update OP.

If you can rule out drivers and the os, you can try memtest64 to check your ram. I have seen this issue recently on an old Q6700k board as well. The CPU was fine but the board was done for. It got too hot because of lazy cleaning. Same could happen with overclocks and bad case airflow. One more thing to try is to replace the power supply. Your PSU is the bare minimum for that graphics card. Maybe it can no longer provide enough amps.

[finalbillybong]

1 minute ago, Applefreak said:

If you can rule out drivers and the os, you can try memtest64 to check your ram. I have seen this issue recently on an old Q6700k board as well. The CPU was fine but the board was done for. It got too hot because of lazy cleaning. Same could happen with overclocks and bad case airflow. One more thing to try is to replace the power supply. Your PSU is the bare minimum for that graphics card. Maybe it can no longer provide enough amps.

OK, Ill have a look at memstest64, is it much different to 86+ which I have already run? I will also replcae the power supply with something a little more beefy. Thanks.

[Applefreak]

Just now, finalbillybong said:

OK, Ill have a look at memstest64, is it much different to 86+ which I have already run? I will also replcae the power supply with something a little more beefy. Thanks.

Not sure, I think the principle is the same.