0x00007FF8D8F0371A referenced memory at 0x0000000000000000. The memory could not be written.

What is this and how do I fix it?

It comes up arbitrarily, during any task or app. 50% of the time it freezes the machine.

What is it and how do I fix it?

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

need some details as what version of the Insiders/Preview does this happen with, what is your system?
I'm a unpaid independent Advisor/volunteer

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Also you need to post only once.
-----------
If this answers your question - Then mark it so. Then others may find it.
---------------
Around computers
since 1952
lacrumb

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello SibeMan

It looks like a memory problem to me, try rebooting and check the memory in BIOS.

Just sayin' .....

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The system I am working on, is Win 10 Home, build 14393
MS User since DOS 2.0
Netware CNA/CNE
Windows Insider since 2015
#1- Win 10 Pro V.1803, B.1725.10 and STOPPED
#2- Win 10 Pro V.1809, B.18305.1 and GOING!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

need some details as what version of the Insiders/Preview does this happen with, what is your system?

Win 10 Home, Build 14393

MS User since DOS 2.0
Netware CNA/CNE
Windows Insider since 2015
#1- Win 10 Pro V.1803, B.1725.10 and STOPPED
#2- Win 10 Pro V.1809, B.18305.1 and GOING!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Sorry, been working on this machine for a week, 12-14 hrs a day and have a tendency to forget who I asked what forum On the bright side, you only have to answer once! ;-)

MS User since DOS 2.0
Netware CNA/CNE
Windows Insider since 2015
#1- Win 10 Pro V.1803, B.1725.10 and STOPPED
#2- Win 10 Pro V.1809, B.18305.1 and GOING!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Been there, done that. No help. Have also run chkdsk, sfc /scannow, all the troubleshooters, and now reinstalling Windows from the 14393.ISO, but even that is having issues, Keyboard only works with some apps and not others after this error and freeze up.
MS User since DOS 2.0
Netware CNA/CNE
Windows Insider since 2015
#1- Win 10 Pro V.1803, B.1725.10 and STOPPED
#2- Win 10 Pro V.1809, B.18305.1 and GOING!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I will send the system specs as soon as I can get control of the Settings or Control Panel, neither of which are responding currently. I am running a system recovery scan with Seagate Tools app, to see if there are missing files or damaged clusters. I am kind of limited on what tools are available. 3rd Party apps will run, and I can get an elevated command prompt, but not much else. The tools in the ISO setup are limited and do not seem to do anything useful. 

Thanks

DN

MS User since DOS 2.0
Netware CNA/CNE
Windows Insider since 2015
#1- Win 10 Pro V.1803, B.1725.10 and STOPPED
#2- Win 10 Pro V.1809, B.18305.1 and GOING!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Can we get your event viewer logs?

Please read this wiki to find out how to find and upload your event viewer logs

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
http://www.zigzag3143.com/

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks ZZ, but I do not think you understand, I have no access to anything, Nothing in the control panel, settings, admin tools, accessories, etc. I know HOW to upload an Event File, I just have no way to access it. Where is the Wiki that says

"The instruction at 0x00007FF8D8F0371A referenced memory at 0x0000000000000000. The memory could not be written. Click on OK to terminate program [and then do THIS to fix the problem]

Back to BASIC DOS

IF, THEN, ELSE

IF- The instruction at 0x00007FF8D8F0371A referenced memory at 0x0000000000000000. and

IF- The memory could not be written. 

THEN- [You have THIS problem and must do THIS to fix it]

IF -[THIS does not work]

ELSE Click on OK to terminate program [and then do THIS to fix the problem]

Programming still uses BASIC deep in its language but falls short in its analyzation and resolution so we get:

IF - [The instruction at 0x00007FF8D8F0371A referenced memory at 0x0000000000000000.

THEN- The memory could not be written. 

ELSE- Click on OK to terminate program.

But no [and then do THIS to fix the problem]

So IF it can read 'the instruction', and knows that THEN The memory could not be written, Why is it that HAL9000

DOES NOT KNOW WHAT ELSE THIS COMBINATION REQUIRES TO BE ELIMINATED?

Instead we get:

IF-The memory could not be written. 

THEN- Click on OK to terminate program.

ELSE- Buy a MAC!

I will never understand how the Windows OS can identify problems, assign them error codes, but has no chart or catalog the describes what must be done to recover from the error!

ZZ-   IF-I can get access to the Event Viewer

        THEN- I will upload it to you to decipher and possibly offer a fix

         ELSE- I will again do what I tried to do in the first place and reinstall Windows 10 from the 14393 ISO. (That is if my daughter does not again insist I roll back her Windows.OLD OS where she can run her Windows 7 and live happily ever after.) I am just one of those stubborn old bastards who has been building these hunks of iron (now plastic) since cassette tapes were both 'Hard drive' and 'memory', until they built a 7lb doorstop of an actual 5MB 'Hard Drive' , with a huge case for the massive drive and its huge power supply, and the rule of the day was 'GIGO' and anything that went wrong was your own fault, and you just had to read what your wrote in the code line where you put the 'GI' causing the 'GO' and fixed it!!  But I digress... 

Does anyone know what this is saying, and how to fix it?

The instruction at 0x00007FF8D8F0371A referenced memory at 0x0000000000000000. The memory could not be written. Click on OK to terminate program

Thank you all for your indulgence in my rant. I have been working on this machine since last Sunday (8/14)

8-12 hours a day, just to bring this machine to its original working status that was wiped out by the update to 14393, and took out the boot sector, rearranged all the volumes (It made the card reader Drive c:), wiped out all the backups on the external storage drive, and repartitioned it to a single volume with nothing on it.... I could go on for days on what it did, but you get the picture. In the words of the great governor of California, "Ahh'l be Bahk" ad infinitum!

MS User since DOS 2.0
Netware CNA/CNE
Windows Insider since 2015
#1- Win 10 Pro V.1803, B.1725.10 and STOPPED
#2- Win 10 Pro V.1809, B.18305.1 and GOING!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated April 19, 2024 Views 503 Applies to: