Question Check XMP RAM stability

[francisco94]

I've occasionally experienced crashes with the "radar pre leak" error in the Event Viewer. Since it's so sporadic, it could be a software issue, a problem with a specific game, Windows, etc. However, I've read that it can also be due to RAM instability, and this could be because I have XMP enabled (I'm using Intel).

Is there any software that guarantees 100% RAM stability?

Thanks.

 

[CParsons]

I've occasionally experienced crashes with the "radar pre leak" error in the Event Viewer. Since it's so sporadic, it could be a software issue, a problem with a specific game, Windows, etc. However, I've read that it can also be due to RAM instability, and this could be because I have XMP enabled (I'm using Intel).

Is there any software that guarantees 100% RAM stability?

Thanks.

No software can guarantee that but there's some testing you can do to dig in a little further if you wish:

• Disable XMP (or set memory to stock/default RAM frequency/timings) in BIOS and test for a few days, see if crashes go away.
• Use MemTest86 to test memory thoroughly: aim for 2–4 full passes (or more) with no errors.

 

[francisco94]

No software can guarantee that but there's some testing you can do to dig in a little further if you wish:

• Disable XMP (or set memory to stock/default RAM frequency/timings) in BIOS and test for a few days, see if crashes go away.
• Use MemTest86 to test memory thoroughly: aim for 2–4 full passes (or more) with no errors.

Since it's so infrequent and difficult to track, disabling XMP and observing isn't feasible, so I want to "force" the failure with synthetic tests in case it's a hardware issue. I'll try with memtest, thanks.

 

[francisco94]

No software can guarantee that but there's some testing you can do to dig in a little further if you wish:

• Disable XMP (or set memory to stock/default RAM frequency/timings) in BIOS and test for a few days, see if crashes go away.
• Use MemTest86 to test memory thoroughly: aim for 2–4 full passes (or more) with no errors.

I tested the RAM with two default Memtest86 tests (each running four times through each of the 13 or 14 tests), as well as two one-hour memory tests from OCCT and one hour of the TechPowerUp test.

All tests came back without errors, so I understand that everything is fine and that these were just isolated software glitches.

Thanks.

 

[Colif]

radar pre leaks are problems with the games, not necessarily a sign of bad ram. Its a memory leak in the program itself

It’s part of Windows Error Reporting (WER) that monitors for memory leaks or inefficient RAM usage in running applications.
RADAR_PRE_LEAK_64
"Windows has detected a potential memory leak in a 64-bit application."

See top answer here:

RADAR_PRE_LEAK_64 - Microsoft Q&A

My games occasionally freeze or stutter for just a moment, and this happens across multiple games. They don't crash, and I don't notice any other issues. However, I consistently see a 'Windows Error Reporting' event with the name: RADAR_PRE_LEAK_64. Can…

learn.microsoft.com

If the ram has an XMP profile that the BIOS supports, its unlikely to be caused by it. Although XMP is technically an overclock its pretty much standard now.

if it passes memtest it should be fine. Only other test would be run Prime95 and see if you get timing errors as they can be caused by not enough voltage on Ram. Prime95 runs CPU really hot so I wouldn't if heat is a concern.

 

[francisco94]

when I open the Nvidia Control Panel after repeatedly enabling/disabling G-Sync there (I was doing this to force a blue screen in a game). It crashes with an error like "0xc000041d" and ":0xc0000005" in the Event Viewer. (Even so, it's not easy to reproduce.)

Could this be somewhat normal, and am I simply overanalyzing occasional crashes due to software errors, or is my system unstable?

I have an I7-13700Kf/rtx 4080 Super, the motherboard is a Z790-A Wifi, DDR5 32gb ram. The PSU is a Corsair RM1200x SHIFT.

Thanks.

 

[francisco94]

Today I ran the CPU+RAM test in OCCT, then the CPU test in "normal" mode, and then the CPU test again in "extreme" mode. After that, I also ran the VRAM test and memory test.


All passed successfully.

 

[Colif]

0xc000041d

repairing .net could fix that error, its mostly an application error and not hardware related.

0xc0000005

this is an access violation, the program tried to accees memory that it wasn't assigned.

am I simply overanalyzing occasional crashes due to software errors,

possibly.

If you have to force a BSOD and system doesn't crash, maybe there isn't anything wrong with it.

is this windows 10 or 11?
Have you run a SFC or DISM?

if win 10

right click start button
choose powershell (admin)

1. copy/paste this command into window:
2. Repair-WindowsImage -Online -RestoreHealth
3. and press enter
4. Then type SFC /scannow
5. and press enter
6. Restart PC if SFC fixes any files as some fixes require a restart to be implemented

First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

If windows 11, the only difference is you use windows terminal (admin) to run powershell
right click start
choose windows terminal (Admin)
When it starts, if it loads as Command Prompt, click the arrow in the title area and pick Powershell from the drop down menu
follow from step 1.

 

[francisco94]

repairing .net could fix that error, its mostly an application error and not hardware related.


this is an access violation, the program tried to accees memory that it wasn't assigned.


possibly.

If you have to force a BSOD and system doesn't crash, maybe there isn't anything wrong with it.

is this windows 10 or 11?
Have you run a SFC or DISM?

if win 10

right click start button
choose powershell (admin)

1. copy/paste this command into window:
2. Repair-WindowsImage -Online -RestoreHealth
3. and press enter
4. Then type SFC /scannow
5. and press enter
6. Restart PC if SFC fixes any files as some fixes require a restart to be implemented

First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

If windows 11, the only difference is you use windows terminal (admin) to run powershell
right click start
choose windows terminal (Admin)
When it starts, if it loads as Command Prompt, click the arrow in the title area and pick Powershell from the drop down menu
follow from step 1.

I'm using Windows 11, and I can replicate the bug on a different, clean Windows installation.

What I mean is that I suspect it's a bug in the Nvidia control panel.

 

[Colif]

What I mean is that I suspect it's a bug in the Nvidia control panel.

That is totally possible. Nvidia don't have much need to fix their software when they are so dominating in the market.

Can you replicate bug using another Nvidia GPU in another PC? that would further enhance idea its the program.

finding a BSOD and isolating it to the Control panel might be hard, as most would blame the display driver. It depends how much info can be taken from the dump files.
If you get a BSOD, you could ask on Sysnative - follow the instructions in this thread before posting any questions - last time I had a BSOD I asked them...

 

[francisco94]

That is totally possible. Nvidia don't have much need to fix their software when they are so dominating in the market.

Can you replicate bug using another Nvidia GPU in another PC? that would further enhance idea its the program.

finding a BSOD and isolating it to the Control panel might be hard, as most would blame the display driver. It depends how much info can be taken from the dump files.
If you get a BSOD, you could ask on Sysnative - follow the instructions in this thread before posting any questions - last time I had a BSOD I asked them...

I don't have another GPU to test with.

Edited:

However, the blue screen issue was resolved with driver and Windows updates.

The Nvidia control panel crash is a different problem.