Re: [PC] Instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

Hi @DMGG1994, First of all, thank you for your detailed response. Please see below:

• In my initial post (which details every step I've taken), I ran every test available on Memtest86, and left it over night. Pass on all fronts.
• You've mentioned filling the RAM beyond 95% - what application are you using to achieve this?
• Page file is on and managed by Windows.
• No other game, or application has any issues. Including video editing, upscaling, music editing software. I have about 20 games installed and have many others that I've played over the past 2 years of using this device and I haven't experienced any issues. Battlefield 2042 is the one exception to this.
• I can't be partitioning C:, I'll loose the space unless the drive is reformatted again. I've already done this three times attempting to diagnose the issue and I'm done with messing around with the Operating System / Disks / RAM.
• The game has run perfectly fine in the past, I am almost adamant that it is an issue with how the game handles memory. I can run it first time 97% of the time, but then attempting to run it after that results in a crash file.

Hi,

I see you have bugged Nvidia drivers version 545.84 , install version 545.92 . On version 545.92 BF2042 is working much better on 545.92 than 545.84 (on 545.84 i had first time from 4 years blue screens).

try RealBench , it has an option to select how much RAM is to be occupied during the stress test of the entire computer (options are 4, 8, 16, 32, 64 and 128 GB of Ram). I don't know the program specifically for testing Ram itself, so I won't tell you the name even if I wanted to.

Spoiler

The BF2042 game is very poorly optimized, I admit, and has many bugs.

From what I read in your first post, the black screen of BF2042 generates the error you mentioned. So before you do the stress test, try this:

I solved the black screen by removing the DXCACHE of Nvidia graphics, at the link below, post #463 I described how to remove them:

https://answers.ea.com/t5/Technical-Issues/S6-Stuck-on-Black-Screen-during-Pre-or-End-of-Round-gt-Requires/m-p/13190832#M55576

After deleting faulty NVIDIA DXCACHE (not the folder but the files inside), the game stopped generating a black screen for me.

Since it's a black screen in the game and not a blue screen of death, I'm 100% sure it's not RAM or another component.. BF2042 black screen is its famous error.

GL

Hi @DMGG1994,

• "I see you have bugged Nvidia drivers version 545.84 , install version 545.92 . On version 545.92 BF2042 is working much better on 545.92 than 545.84 (on 545.84 i had first time from 4 years blue screens).
  • I have since updated NVIDIA Drivers to 546.01, 31/10/23 - Is this advice still relevant?
• I'm now downloading and will soon be running RealBench.
• I will attempt your instructions on removing NVIDIA DXCACHE files.
• Thank you again for confirming it's not hardware. @Rokebo73 please take note.
  As to why I left Memtest86 test on overnight - I didn't know how long it would take, I use my device frequently during the day and wanted to be thorough.
  Memtest86 wasn't constantly performing tests I'm sure; it had a PASS screen indicating it had finished at some point.

Thanks again for clear correspondence and help! I'll update this space soon 🙂.

Hi  @hotproperty11 

First, delete the DXCACHE created by Nvidia, then start the stress test, in my opinion, deleting the old faulty DXCACHE will help, Nvidia will create the correct cache again and BF2042 should work. If that doesn't help, then do a stress test on your computer and load the memory by at least 95%. There is no point in performing stress tests beforehand unless you rule out the hypothesis of faulty DXCACHE generated by NVIDIA drivers.

It's hard for me to comment on version 546.01 since I haven't installed it. I saw that you mentioned version 545.84, which caused a lot of problems for me, so I mentioned it. If you currently do not have blue screens of death on version 546.01, in my opinion there is no point in updating your drivers.

I haven't had BSOD problems for 4 years (the computer really was stable, too stable), and suddenly the BSOD occurred after updating the NVIDI drivers to version 545.84 (BF2042 ordered me to update, and on the day I bought BF2042, the latest faulty drivers in version 545.84 were available, so I downloaded them xd), After removing the older version of Nvidia drivers using DDU in windows save mode and installing new ones, the never-occurring blue screen of death appeared, so it was clear that the fault was with the drivers. After updating to version 545.92 (then the latest version), the BSOD disappeared. (I didn't update the BIOS or Windows - which was really unnecessary here and could only create new problems)

Generally, recently, after a system restore that I did for another reason unrelated to the game, BF2042 experienced black screens after every match or after every exit from the match. I noticed on the OSD monitor that the game stopped working (it didn't even load anything from the disk, everything just stopped and I had to turn off BF2042 using the task manager or alt +F4). After this fact, I was practically 95% sure that the DXCACHES created by NVIDIA were simply not up to date (since I restored the system to the state from a day ago, it was a real fact that the caches were not adequate to the current state), so I deleted them so that NVIDIA will regenerate the new current cache and BF2042 will not get crashed. After this operation, the game is currently working fine for me, it has already used the Nvidia Cache created by the NVIDIA driver a few times and everything is fine. I hope it will work for you too.

I did not touch the cache generated by BF2042 which are in the documents.

If, after deleting the old Nvidia caches according to the instructions I mentioned in the previous post, you still have a problem with a black screen in BF2042, and the stress tests are positive (you won't get a BSOD or a Windows crash), then I don't know how to help you at this point, you'll just he had to be patient and use ctrl+alt+del to call the windows manager to close the game or do it with alt + F4 until DICE solves this problem, which in my opinion will introduce an algorithm that will ignore incorrect cache if the game it won't read it correctly..

GL

@hotproperty11 

Beaware that if something is wrong with memory and ya do run a test on it, 

test software does not always display an error if something is "broken/faulty/not compatible" ram/cfg ect ect ect !! <-- take note of it 😉

I have seen multiple issues with ram , while test software , mem95 , windows mem diag ect ect ect do not display any error and past everything !!!

Just to exclude ram from errors , ya could borrow mem (thats in youre QVL) from "someone" and try again.

Make sure if ya install memory its in dualchannel mode at youre motherboard.

Also dont forget to reconfig xmp/docp if ya got other mem installed (just for test purpose only) and hope ya find the best settying for the ram ya use !

Cheers

@Rokebo73 I currently have RAM and NVME outside the QVL list and everything works fine, I eliminated the BF2042 black screen using the method described above.

@hotproperty11  If you start replacing RAM sticks with other ones, turn off the XMP profile in BIOS settings before removing them from the motherboard, unless you want to have to remove the battery later to reset the BIOS, because the BIOS may become stupid with the new RAM if it has the profile loaded XMP from previous RAM. And the golden rule is that all RAM sticks must have the same parameters (in theory, the better RAM will slow down its parameters to the worse one, but such configurations tend to generate BSOD).

GL

@DMGG1994   Or just do a clr cmos, by connecting 2 pins at motherboard <<-- check manual !!

Real stress test is running bf2042 hahahaha.
He just should try other ram , just to test if he get this error again.

Sometimes it also could be an error with the ssd.(maybe sata cable ?)
Enough power (PSU) for the system? <<-- Who knows ? Test test and keep testing
I have seen ssd's that could not be formatted anymore, system did stay on it <-- hahaha (even after use of multiple tools)

PS And the golden rule is that all RAM is all from the same batch and in QVL, so if ya buy 2 sticks they should both be in the one and the same box, no 2 boxes (even if it is the same paramer.. ect ect ect).

memory from different batches could cause issues to 😉

Cheers

@hotproperty11 You could also test youre CPU for any errors. (intel for example has an tool to test cpu)

Sometimes reaset everything at motherboard could solve problem, one by one (take everything from motherboard first and clr cmos)

Install mem and GPU then boot system, shutdown, reaseat next hardware (ssd for example just 1) , power system , ect ect ect ect untill everything is "onboard" again !

Cheers again 😉

@Rokebo73 

,,Real stress test is running bf2042 hahahaha.''  LOL

I don't know why you need to reset the BIOS using your method, when removing the battery for 5 minutes gives the same effect 🙂 When I overdid the OC, this method worked, but everyone has their own way. Besides, I wouldn't even risk resetting the BIOS settings by touching two pins next to the battery without removing the battery, the electronics are very delicate.

In the old computer I had 2 pairs of different companies with the same parameters (also outside the QVL list) and everything worked for 8 years of use and still works today, even CoD BO CW & BFV works without any problems, the only problem was a low FPS because the i5-750 already he couldn't cope. But I agree with you that in order to eliminate memory instability 100%, it is recommended to have all 4 RAM sticks the same.

Stress test - in my opinion this is the only way to check whether all components work together and whether the power supply is able to provide the appropriate voltages at the maximum power consumption of the computer. Now that you know this, you should know that all connectors have some type of latches, so the likelihood of a loose cable is slim.

If you saw such SSDs on which the system remained and it was impossible to format them, it probably already used all the writing cells on the SSD or the flash memory was damaged and the user whose computer you were working on was lucky that the SSD went into read-only mode, worse, as if was completely damaged, then data recovery could be a problem, unlike the HDD.

Flash memories are delicate, it doesn't take much for them to get damaged and go into read-only mode (worse if they fail completely, then there is a problem even with data recovery, you can recover data from an HDD even if it is physically damaged, but from flash memory not necessarily)

I also saw an NVME disk that, after writing less than 40 GB, generated bad sectors and was thrown into the trash. After 2 replacements under warranty, I replaced it with a Samsung disk and it still works.

If my method doesn't work, I'll give you the opportunity to help @hotproperty11 .

Cheers and have fun playing.

@DMGG1994  Yeah ssd did got a broken chip, forgot specs from the damaged chip.
Couldnt format or wipe/delete partition anymore.
No diskpart, no partition tool software (even in other pc), nothing , it was readonly indeed, hahaha
I forgot to say that a sata cable could be broken .

why i advise connecting jumpers instead of removing battery, is some people use to much force to just bend that little clip to get battery out.
Or people try to move that clip and scratches motherboard cause the didnt align coresectly (or to much force).

There are so many thing thatt could cause an error, even issues with hardware that causes other hardware to act / behave weird.

Silicon lottery they say, if its cpu , sdd, ram or what ever , something not correctly configured / broken / fauylty could cause an issue(s) ya never expect.

For example, bios reset and system did run ok

Memory not in qvl who give sfc /scannow errors, or pagefile erros. Or game just did run for some minutes and then shut down / or system reboots.

Check older topics where i did support people with memory issues.
Most of them got same errors, but also some weird errors , from bsod till not able to game, Mhz issues , gpu not detectd issues ect ect ect ect
Just by memory issues <-- 😉

Cheers

ps the new boards (chipset z690 / z790) are more sensitve for those memory issues !!

@Rokebo73 

True, the electronics are very advanced, but BF2042 also has a lot of bugs.

I always unlock the battery with my finger. I bend the latch loosely enough to loosen the battery slightly, then pry the battery from the other side, I have never broken/bang this clamp too much. If I did it with a screwdriver or another tool, then what you mentioned could happen.

I only had to remove the battery twice in my life, when I chose the wrong voltage for the OC (too low voltage) and don't worry, I never exceed Vcore 1.3, 1.3 is actually probably the maximum safe voltage in practice, higher voltages are a lottery, something will go wrong or no, especially since the motherboard, even with CPU Vcore Calibration configured, can reach a voltage of 1.35 V at the 1.3 setting, so I don't want to say what can happen at 1.4 and higher 🙂

Once I broke the rule of not exceeding the Vcore voltage of 1.3V, it ended up burning the CPU due to too high voltage. (at Vcore 1.4, the motherboard dropped the voltage above 1.45 for a moment - which killed the processor (i5 8600K)), but since the service gave up and was late with sending back the processor (they exceeded the time limit of 3 weeks xd), I had an argument to change it for an additional fee processor on i7 8700K, and since the service technician was not very knowledgeable, he did not check at all whether I was overclocking the xd processor, but immediately sent it to Intel abroad. I didn't have to overclock the I7 anymore because it can handle even BF2042 without any problems.

I7 8700K at 4.9 GHz managed to achieve Vcore 1.28. I didn't reach 5.0 GHZ, the motherboard holds the voltage too poorly, probably at a voltage above 1.3 5.0 GHz would work, but this time I didn't risk it xd.

After testing how much GHz I could overclock the CPU on my motherboard, I went back to stock clocks and I still play like that to this day.

Changing the subject

I haven't noticed what this player posted here yet

https://answers.ea.com/t5/Technical-Issues/EA-Dice-Please-Fix-This/m-p/13191044#M55631

@DMGG1994 Please don't change the subject, I'm trying to resolve my issue 😎

@Rokebo73 As stated multiple times now I have no issue with any other app or game. Please stop interjecting with invalid advice. It might of worked one or two times elsewhere but here it's not helping one iota. Why would EVERYTHING ELSE but Battlefield 2042 work because of faulty hardware? Provide credentials so I can trust what you're saying or climb down from this tree. If I bought a whole new PC then yes, likely my issue would be resolved. That isn't the point; the point is the developers fixing a broken game so it works across many hardware specifications.

Please note I am -not- a novice at computing (I would of thought my replies and initial post would of given off that vibe, but whatever) so PLEASE stop treating me as such and repeating yourself. I know you are NOT reading my updates properly due to the amount of repetition and wrong information. Thank you.

Let me be very clear, there is absolutely nothing wrong with the hardware. This is definitely an issue with the game.

@hotproperty11  Also you should check other topics i supported people with memory that wasnt compatible.
All games work ok, only in bf2042 they got issues !
And that bf2042 only give issues is probarly about the code is done by those dev's.

Again check older topics where i supported other people with memory issues (alos in this TECH forum).

Same as faulty ram, people did run mem test apps, and told also no errors, but mem was still faulty / not compatible <-- and no errors during mem test.
I cannot tell you how youre silicon acts ! Sorry

ps sometimes ya got luck in this silicon lottery , but sometimes it can be bad also !

Cheers

you could also contact the motherboard manufacture (email them) and ask what they think about/from youre memory cfg.
Then ya got 100% correct answer , if it is compatbile it still can be broken !

@hotproperty11 

Try this method:

Unlock the built-in administrator account and run BF2042 on it - it solved a lot of problems with BFV for me.

What is the difference between the built-in administrator account and a user-created admin account (the so-called standard administrator account)? Mainly one, the difference in write permissions on system partition C.

BFV on a standard admin account had a problem in that it did not have permission to modify the content of files in the "Documents" directory, which meant it could not modify the file (save game progress)

BF2042 also has files in the documents directory, including its DX12 cache ((...)\Documents\Battlefield 2042\cache)

I hypothesize that BF2042 does not have permissions on the standard admin account due to the limitations of writing and modifying NTFS on the C drive to modify the contents of cache files (they are constantly modified after and during the match). Therefore, running the game on the built-in admin account may solve your problem. If a black screen can be caused by faulty Nvidia DXCACHE, so can the BF2042 game cache too. Since I play on the built-in admin account, I have no problems with the BF2042 cache, but you may have them on standard admin account.

Try to run the game using the built-in admin account, maybe your problem will be solved? It won't harm you, you will only lose about 3 GB, because BF2042 will make new cache in the documents of the new user, which will be the built-in Windows Administrator, you can always delete them and return to the old account if that doesn't help. New Nvidia caches will also be created under the administrator account, so nothing will get mixed up.

About a 30% chance that this will solve the problem, but it may turn out that this 30% will do the trick 🙂

GL

I'm very curious if this solves the problem, I hope so.
I have another test method, quite a different test.
Will explain this if the admin change didn't work.
With the test we can hopefully rule out a few things.

ps dot his also in command prompt with admin rights
chkdsk C: /r /scan
this command need some time to complete

Open CMD as admin , type:

C: 

press enter

later

CHKDSK /r /scan

or just

chkdsk C: /r /scan --> Checking the disk without disconnecting it through windows (in online mode) to check whether the file system on the disk is correct, including whether there are no bad sectors without repairing it - will display the report itself. (This is an alternative to CHKDSK /R /F - only it does not fix errors)

Wouldn't it be better to use HD TUNE PRO, go to the error scan tab and scan the disk? the DLC BOOT tool has it (you can also run it normally on the desktop without booting it, but you have to run it as administrator)

Spoiler

It is also worth excluding the disk from the group of suspects, but the probability that it is the culprit is small.

The only question is whether his M.2 drive can withstand this scan (I mean, whether it will overheat). I turned up the graphics fans while scanning the M2 drive for bad sectors in order to cool the M2 drive (I have the M2 drive under the GPU, so this had an impact on its temperature as the graphics caused increased air movement where the M2 drive was mounted xd if the M2 is above the GPU, the GPU will not cool it. It is a good idea to run HWINFO in sensors only mode and monitor whether, for example, the controller does not heat up too much. M2 drives are supposedly protected against overheating, but the principle of limited trust in the manufacturer applies in every field .

When I had bad sectors on an SSD, the system would simply disconnect or display a blue screen of death, no matter what I did to the system, because when Windows "hit" a bad sector, the BIOS automatically cut off the drive and for a while it wouldn't work at all it worked, he didn't see it - a typical symptom of a bad sector..

After locating 1 bad sector at the beginning, I tried to exclude them from the disk map using Ultimate boot CD, but after this operation for any  30 minutes there were over 20 of them, so I gave up and replaced the disk under warranty with another one. Generally, you can try to disable bad sectors, if their number does not exceed 2, there is no point in larger numbers.

GL

Hi @DMGG1994, @Rokebo73 -

• CHKDSK has already been run and no errors found, but have just ran CHKDSK /r /scan:
  • Windows has scanned the file system and found no problems. No further action is required. (cmd_ijg.png)
• HD Tune Pro has been run on all three disks:
  • No damaged blocks. (hdtunepro-3disks.png)
• I'll attempt to run BF2042 in the default Admin profile at some point. Although I'd like to state, even if this works, it isn't a resolution to the issue.
  • Battlefield 2042 needs to be able to run in a non-admin, or the users standard account, like other games

I have updated initial posts in both forums, disks have come up clean with no bad sectors. NVMe & SSD's are not the problem.

@hotproperty11 

So the disks are healthy (what I expected, bad sectors give other symptoms)

Although BF2042 and BFV and other games should work on every account, unfortunately this is not the case (at least for me since Windows 10). I didn't have this type of problem on Windows 7 and older.

Try it, maybe you will have peace with the black screen.

GL

@hotproperty11  Can ya tell me what temps youre memory is running at , if ya do stress test or something similair ?
Ya could use HWINFO64 fot it !

please did ya try to move swapfile/virtual memory already to a other drive (even move bf2042 to other drive please)

https://www.techrepublic.com/article/tech-tip-move-the-swap-file-to-another-drive/

From Samsung SSD 980 PRO 500GB to Samsung SSD 860 EVO 1TB

Youre drives got latest firmware updates ?

https://semiconductor.samsung.com/consumer-storage/support/tools/

Bf2042 is installed at een ntfs drive i assume ?

use event viewer , goto windows logs and find date / time error occured, post result from that log please!

(ps what is the fat32 drive be used for ?)

 
Cheers

@Rokebo73 

Please enlighten me, what does the NVME driver have for the game if HDTUNE and your CHKDSK/scan command did not detect any errors?

What is the benefit of moving the file swap file to another drive, except that if you move it from SSD to HDD it will extend the life of the SSD drive.

What will he gain from moving the BF2042 game to another disk? It will only speed up Windows startup, because the more free space in % the SSD has, the faster it runs.

It's just a game bug and that's it. Until DICE fixes it and releases a patch, it won't do anything. I was lucky that deleted DXCACHE solved my problem, but as you can see, it didn't help most people.

@Rokebo73

• Export from HWiNFO64 in attached screenshot HWiNFO64_HOT_png, no unusual or out of place temperatures
• When writing Samsung firmware to USB, grub bootloader prompts instead of firmware installation prompts which wasn't expected.
  • This isn't the issue regardless as we have tested and know the hard drives are fine, and a game's stability should definitely not be dependant on this.
  • BF20242 has been attempted to run on all drives
  • I don't see how changing the page file drive will help, I have more than enough free space on the NVMe.
  • There is no fat32 partitions, all drives are NTFS
• Event Viewer does not produce an error message, only minidump log in Documents\Battlefield 2042\CrashDumps.
• @DMGG1994 I agree with you; it's a bug.

@hotproperty11  hmmm weird, cuase i see this in youre dxdiag

Drive: C:
Free Space: 273.8 GB
Total Space: 476.2 GB
File System: NTFS
Model: Samsung SSD 980 PRO 500GB

Drive: D:
Free Space: 502.5 GB
Total Space: 953.2 GB
File System: NTFS
Model: Samsung SSD 860 EVO 1TB

Drive: E:
Free Space: 362.5 GB
Total Space: 953.9 GB
File System: NTFS
Model: Samsung SSD 870 QVO 1TB

Drive: G:
Free Space: 260.1 GB
Total Space: 476.2 GB
File System: FAT32
Model: n/a

and nothing for memory temps, see pic.

@Rokebo73 

Is this a hwinfo screenshot from your computer (post #39) ? You obviously have some rich version of a high-end mainboard, since you even have a RAM temperature and voltage meter.

On my computer, it also does not show me detailed data regarding RAM (I don't even have RAM temperature sensors).

My MB is Gigabite Z370 Gaming 5 if you are curious.

G drive has a FAT32 file system, this may cause its model to be detected as unkown. If you look at its screenshot uploaded from HWINFO made by @hotproperty11 , you will see that all drives are recognized correctly (all disc are Samsung drives).

What deserves more attention is its Vcore, which reaches a maximum of just  ~1.5v (super dangerous), and its average Vcore voltage is over 1.31. on my CPU, the maximum voltage set by the motherboard is 1.2 (in set Vcore = auto). His motherboard has a terribly high voltage, unless he overclocked the processor and set such a high voltage to stabilize the OC (although Vcore should not exceed 1.3).

On OC in my CPU from 4.3 GHz to 4.9 GHZ (strong OC), the Vcore voltage did not exceed 1.31.

@hotproperty11 

If you have such voltages on stock, read about the recommended voltages for your processor and set the correct Vcore.

If you have such a voltage to stabilize the OC, you did something wrong (for example, incorrectly set CPU Vcore loadline-calibration. If you did not change anything here, then you have the reason for setting such high voltages. Configure Vcore loadline-calibration correctly and you will be able to lower it significantly Vcore voltage maintain the same CPU clocks.

The question is whether you have disabled turbo mode in the CPU. During OC, the turbo should be turned off (the turbo generates higher voltages, which means that a higher Vcore should be set for the same clocks).

Turbo is unnecessary and should be disabled if you set base clocks higher than turbo on all cores, and overclocking makes no sense if you set base clocks lower than turbo on all cores. (Yes on all cores, because Turbo has higher clocks when Windows uses only 1 core, and lower clocks when it uses all cores at once).

in the CPU you only change the base clocks, God forbid you do it with Turbo clocks.

To sum up, if you overclock the CPU, you turn off the turbo.

If, despite the Vcore loadline-calibration configuration, you exceeded Vcore 1.3, then reduce the clocks, unless you don't care about this processor because, for example, you are planning to change your computer and you already have money saved up for a new PC/CPU)

Too high Vcore does not generate a BSOD, the warning may (doesn't have to) be a computer freeze, and you may have something like I had, where the processor suddenly died without warning when I once exceeded the voltage of 1.45 during OC. In my case, the CPU died after a 1 year.

Consult the topic of Vcore voltages with a friend who deals with voltage settings for the processor, unless you know BIOS, you can do it yourself by trial and error. Unless AMD processors have such high Vcore as standard. I've never had an AMD processor so I may be missing something.

I wouldn't be surprised if such high voltage caused this error (too high voltage can even kill the CPU).

CPUs do not have protection against too high Vcore.

i5 750 (currently old) had 1.28 voltage, but not over 1.48 xD

Spoiler

 GL

@DMGG1994  yes screenshot is from my system

Gigabyte Z690 AORUS ULTRA
Intel Core i9-13900K
Kingston FURY Beast RGB DIMM DDR5-6000 32GB Kit 2*16
Samsung SSD 980 Pro 2TB <- 2x
Gigabyte RTX 4090
Lian Li Fans 10x
Lian Li AIO 360
Lian Li O11 Dynamic EVO Black

And an
Gigabyte Z690 UD AX
Intel Core i7-12700K
Kingston FURY Beast RGB DIMM DDR5-6000 16GB Kit 2*8
Samsung SSD 980 Pro 1TB +1 samsung 870 sata sdd 1tb + 1x samsung 860 sata sdd 500gb
Gigabyte RTX 3080
be quiet! PURE Base 500 FX tower
Be Quiet be quiet! Pure Loop 2 FX 240mm ARGB Water Cooler

And an:
Asus maximus V extreme
16 gb ram
i7 3770k
with some ssd drives
10 fans

the system i game at:

That's what I thought - a top-shelf motherboard. The power supply section for the CPU is very good.

I have Fan 4x Arctic P14 140mm High Speed ​​fans + one factory Silentium PC 120 mm rear fan (which I did not replace)

my case

SilentiumPC Regnum RG4T Pure Black.

For OLD CPU  I7 8700K  (CPU FAN SilentiumPC Fortis 3 HE1425)

GPU Geeforce RTX 2080S

2 x HDD :

• 1x Seagate IronWolf 4TB
• 1x Seagate Ironwolf Pro TB

NVME PCI 3.0 Samsung 980 1 TB

4x RAM GOODRAM IRDM X 16GB 3000MHZ DDR4 CL16 (2X8) DIMM

PSU : Fractal Design 750 W Bronze Plus is enought :D (I know i know cheap china PSU xD)

Thanks @DMGG1994 -

• Some good spots and advice. I have undervolted my CPU as recommended. Very odd as that's how it came through as stock, after multiple CMOS resets! Attached screenshots with applied undervolt.
• Temperatures running lower, have run a stress test and CineBench 2024.
• Same issue still occurs in BF204 unfortunately.

@Rokebo73 That's a mean machine, but looks like a Unicorn has thrown up on it 😃