The instruction at 0x000000000FD13ED2 referenced memory at 0x0000000000000001. The memory could not be read.

Toggle sidebar Toggle sidebar
S

SlayerWezz

Commendable
Mar 16, 2016
46
0
1,530
I have been having this issue quite a bit and only notice it while playing Arma 3 and to be honest, I am getting sick of it since it closes the game for me. How so I fix this problem and what exactly does it mean? Google wasn't of much help since it wanted me to install software that I then have to pay to fix illegitimate errors. I have Windows 10, 16GB of RAM. All my drivers are up to date.

This is the error message: The instruction at 0x000000000FD13ED2 referenced memory at 0x0000000000000001. The memory could not be read. Click ok to terminate the program.
 
Solution
jasonkaler
"what exactly does it mean? "
Well, the CPU executes code that's in memory. At memory address 0x0FD13ED2 there is an instruction telling the CPU to read memory address 0x0000000000000001
That memory address is not valid in the security context of the application that's executing.
An address value of 1 is definitely in system space and should not be accessed by anything other than the windows kernel, and perhaps not even by the kernel at all.

This indicates that it is most likely a driver issue, or an app issue. If it only happens in one game, then it's the game at fault. If it happens in more games, then it's the driver.
Also, just because its the latest driver, doesn't mean it's 100% bug free.

Just a random shot in the dark, but try...
Sort by date Sort by votes
jasonkaler

jasonkaler

Distinguished
Nov 22, 2011
514
12
19,365
"what exactly does it mean? "
Well, the CPU executes code that's in memory. At memory address 0x0FD13ED2 there is an instruction telling the CPU to read memory address 0x0000000000000001
That memory address is not valid in the security context of the application that's executing.
An address value of 1 is definitely in system space and should not be accessed by anything other than the windows kernel, and perhaps not even by the kernel at all.

This indicates that it is most likely a driver issue, or an app issue. If it only happens in one game, then it's the game at fault. If it happens in more games, then it's the driver.
Also, just because its the latest driver, doesn't mean it's 100% bug free.

Just a random shot in the dark, but try take out some ram and see if that helps.
If that doesn't help, try an older video driver. Who knows, it may just be a new bug that was introduced lately.
It's worth a try.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom