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

@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 😃

@hotproperty11  ya did a fresh / new windows install.
Could ya post a dxdiag again please.
Thanks

Is there a way to cool youre memory with an external fan just to test if it do anything, example:

hahah dont forget this unicorn got a lot of different colors and effects ! 🙂🙂 

Cheers

@Rokebo73 

• I'm not reinstalling Windows any more, that isn't the issue and I use my PC for things other than diagnosing BF2042 errors 😃.
• Fresh DXDIAG attached.
• If I get time I have a desk fan that I could orientate towards it, but again I don't feel it is anything hardware related.
• You're right, I'm more of a solid colour guy. Would look great in a deep solid red/purple 🙂 👍

@hotproperty11  are ya able to set dual/single channel option for memory in the bios ?

navigate to the "Advanced" tab.

Look for the "Memory Configuration" or "DRAM Configuration" option, and select it.
Locate the "Memory Channel" option, and change it from "Single" to "Dual."
Save your changes and exit the BIOS by pressing the "F10" key.

let us know, cheers

Bios update , cool 😉

ps did ya visual check at CPU / socket and memory for any damage/burn spots ect ect ect ?

i also asking if there is maybe some hardware compatible issues ????

cause there is issues with asus software/drivers (check bsod topic) , also ya use auraled controller and icue, should be compatible (and white listed) ????
But since this latest bf2042 update many issues with asus software/drivers to run bf2042 ???? !!!

Maybe some issues with Unified Virtual HID ????

nice display monitor btw and studio monitor 🙂

@Rokebo73 

• No such option under Advanced (attached screenshot) and couldn't locate these options in the 5950x BIOS. Googling didn't return anything helpful either.
• Visual checks were performed on all equipment at the start, no concerns with any physical part of the device. I'll update initial post to reflect that.
• Please link items that you want me to reference, I've maybe had three or four BSOD's, none Battlefield related.
• No driver issues or conflicts present on device.
• Unified Virtual HID is Universal Remote, and app used for controlling Windows from Android; I've uninstalled it as I never use it on this device but I can't see that being the issue unless we're now talking about the Anti Cheat causing the problem. Which I don't think it is, but will try.
• Thanks, these displays are serving me well so far 🙂

Post #47, @hotproperty11  wrote:

,Please link items that you want me to reference, I've maybe had three or four BSOD's, none Battlefield related.''

@Rokebo73 , read slower or better, why are you sending him a link about BSOD related to BF2042, when he clearly writes that the BSOD was not caused by the game?

Black screen and BSOD are two completely different problems!

Do you want to help him or harm him, because something will soon turn off too much and it will suffer from a BSOD or cooling stop, as one user here experienced after turning off the AsIO2.sys driver.

Post #156

https://answers.ea.com/t5/Technical-Issues/Blue-Screen-of-Death-after-closing-BF2042/m-p/13194290#M55644

@hotproperty11 

I don't have this option either, PC BIOS's automatically have dual-channel mode for RAM enabled, because few people provide single-channel RAM, even if you install single-channel RAM, the correct BIOS will detect it, but this is not a recommended configuration (better work efficiency is on dual-channel RAM).

Currently, your VCORE is exemplary, I am full of admiration that everything works at such a low voltage.

GL

@DMGG1994 Dude !!!

I quato"i will not say its youre issues , but maybe it could change/fix or give some ideas about the issue ya got."

Cheers

@Rokebo73 

What problem i have?

@hotproperty11 

Users started reporting that the black screen disappeared after patch 6.2. Are you still having the problem?

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

I can confirm that issue is still present for me; is 6.2 released yet? I'd like to note this seems to be focusing on the black screen pre / end round - whilst that was happening for me (when I can load into the game), my problem exists mostly when attempting to boot into the game. Today I played a couple of games, quit, attempted to load back in 15 mins later > hanging black window.

@hotproperty11 

Today BF2042 downloaded a patch again.

Then report here that you still have the black screen problem.

https://answers.ea.com/t5/Technical-Issues/S6-Stuck-on-Black-Screen-during-Pre-or-End-of-Round-gt-Requires/td-p/13066604/page/54

Try to remove DXCACHE again in the same way as before, but additionally remove them from the locations listed below (I found them today) (the files are in the folder, do not delete the folder itself!):

(delete them to the trash so that you can restore them in case of any problem)

Do not remove DXCACHE only from the two locations I have given now - it will not help, you also need to remove them from APPDATA as before.

C:\Windows\System32\config\systemprofile\AppData\Local\NVIDIA\DXCache

C:\Windows\System32\config\systemprofile\AppData\LocalLow\NVIDIA\PerDriverVersion\DXCache

Set the maximum size of the cache folder to 10 GB in the nvidia directory.

GL