Windows 10: The Instruction at 0x1013D472 or 0x000000001013D472 referenced memory could not be written

Hello guysSo My windows was updating yesterday the normal windows update check after it updated i closed the PCToday when i opened my PC i started to get a bunch of "Application Error" from most of the programs i have on my pc this is the error messageit is not only dllhost.exe most of the other programs gave me the same error message and i can't open them i tried opening cmd as admin to run sfc /scannow but it gave me the same error and after like 10 min the Cmd opened and i ran the commandit found corrupt files and repaired them but still the error is not gone

:)

 

The instruction at 0x00007FFA8fe381c4 referenced memory at 0x0000000000000050. The memory could not be read. PC will not boot

This is a Dell Inspiron laptop, Windows 10. System will not boot. Getting error:

The instruction at 0x00007FFA8fe381c4 referenced memory at 0x0000000000000050. The memory could not be read

Any suggestions on resolving this problem would be appreciated.

 

The instruction at referenced memory could not be written

I recently upgraded to windows 10, and when I turn off or restart the computer, I get this message :

It's stopping the computer from turning off, and its asking me to terminate the program.

How do I fix this issue, or at least hide the message so I dont have to terminate manually the program?

 

"Instruction referenced memory" error on signoff

I've seen older posts (mostly during the Windows 10 preview period) on this same topic so I thought I'd check back.

I do these steps:

All apps are closed.

From the desktop I press Alt-F4

From the Shutdown Windows dialog box I change to "Signoff" and press Enter

I get a popup that read The instruction at -------7c7c32 referenced memory at 0xfffffffffff. The memory could not be read. Click on ok to terminate the application. I click ok and it signs off ok.

I JUST installed Windows 10 last night. I did a clean install from DVD. I have Build#10586. This is a custom desktop (not a laptop or tablet).

Is there a fix for this yet?