cancel
Showing results for 
Search instead for 
Did you mean: 

RADAR_PRE_LEAK_64 reports in event viewer - problem with rams?

sde444
Level 10
Hi. So first my pc.

My rams are Kingston Hyperx 16gb 2x8 DDR4, 6700K,Asus Z170-P, SSD Crucial Bx100 256GB and Windows 10.

Everytime i am opening some application which is fine and opening. But on event viewer i get : RADAR_PRE_LEAK_64 errors. Applications are opening fine but windows 10 reporting this as RADAR_PRE_LEAK_64 in event viewer.
If games not crashes and i have that logs in event viewer do something, or leave it alone?



I have that radar errors in event viewer almost everytime when i am opening some game or benchmark , thats all. But not crashing.

Example from BlackOps3:





Like i said i dont have crashes , but only that warnings on event viewer. Thats all. Should i worry? Something with rams, ssd? Should i check memtest86 or that will be waste of time?
383 Views
7 REPLIES 7

TeMagic
Level 7
Your PC is exhausted, box needs new CPU and Motherboard. The Z170-P is all tear and has mutated the CPU. You should claim warranty on the motherboard, since yours is a TOA.
Conspiracy is nothing!

TeMagic wrote:
Your PC is exhausted, box needs new CPU and Motherboard. The Z170-P is all tear and has mutated the CPU. You should claim warranty on the motherboard, since yours is a TOA.


What you mean? Its something with motherboard, cpu ? Or what you talking about?


I run memtest86 for 5 hours and no errors.


Yes but why sometimes GTA V.exe, 3dmark.exe ,not only Black Ops 3,and other apps trigger that entry in event manager. ??

Nate152
Moderator
Hi guys

The RADAR_PRE_LEAK_64 is caused by a program that has a memory leak, in this case it's Black Ops 3, if you're not experiencing any problems you can ignore it.

Nate152 wrote:
Hi guys

The RADAR_PRE_LEAK_64 is caused by a program that has a memory leak, in this case it's Black Ops 3, if you're not experiencing any problems you can ignore it.


Just BS.
Conspiracy is nothing!

Nate152
Moderator
Hmmm... I'm not sure but something is triggering it.

You could try a system restore to a point where it wasn't happening or if it's not too big of a deal do a windows reinstall and see if it goes away.

Nate152 wrote:
Hmmm... I'm not sure but something is triggering it.

You could try a system restore to a point where it wasn't happening or if it's not too big of a deal do a windows reinstall and see if it goes away.


So its something with hardware ?

Nate152
Moderator