Windows 10: Still looking for a way to continue after Memory Referenced error...

About 737 days ago I had a thread going with this problem.
This is a link to that thread, so I don't have to re-detail the problem.
Continue automatically after Memory Referenced error on shutdown?

In summary: For all the years I have had Windows 10 installed, I have been unable to do an unattended shutdown with any confidence because at random, W10 will pop up that Memory Referenced error dialog during the shutdown process, requiring you to hit OK to shutdown.

And here's my problem: The moment you ask about this, or if you search on it, you find hundreds (if not more) responses to the many postings across support sites - and they all offer or try to offer solutions for the error.
I don't need to fix the error. All I want is a way to tell W10 not to stop on the error. Which is only logical.
Here's the thing:
At the point that the error pops up:
1. There's nothing you can do anyway, other than continue, right?
2. Anyone who knows enough to translate that cryptic gobbledeygook knows enough to use the Event viewer to debug the error.
3. So why not just make like every other serious (real?) operating system and post a message on startup saying, "You had an abnormal termination the last time, go check the Event logs".

So, please, if you respond to this, I'd really appreciate not getting the long list of ways to fix it re drivers and sfc and reset and clean installs, ad infinitum. What I need are suggestions that will help me do a shutdown that I can be confident will shutdown - not sit for three days on a silly error message that (at that point) nobody can recover from anyway.
And for the troubleshooters:
Along the way, I have tried every one of those "fixes". I run and try a lot of odd software, I code, I connect one-off peripherals when troubleshooting things for others.This error has disappeared and reappeared completely at random, obviously with different combinations of system s/w, drivers, applications. And that's OK. I know this is most probably caused by third-party program or driver. So what?
To me, the flaw is in the design construct of the error I'd love someone at MS to have the intelligence to think through the value of stopping a system shutdown for a message that you can only hit ok on.
I run Linux and Apple systems as well, and this would (and does) get laughed at in that world. But I bought my first PC in 1983 and I will always think of myself as primarily a Window person.
This is scaring me because my W7 machine is bullet-proof this way - and yet I will soon lose it to this unreliable OS because MS wants that to happen.
That's just plain dumb. What are we doing here, regressing to a mediocrity mean?
Cheers

:)

 

Continue automatically after Memory Referenced error on shutdown?


Hi,
I have been living in the hope that some update would address this. Now have the Creator's Update but it still is a showstopper.
Ever since I installed Windows 10 originally, my system will halt on that infernal "memory referenced" error at random occasions, during shutdown. This makes my workflow really difficult as I am reliant on unattended operations. The problem is that this is never the same originating application called out in the error message, varying from Box sync to explorer.exe. I've worked my way through many workaround attempts and will keep trying (from the asinine responses om the MS support forums to fairly good advice on this and orther tech sites) - BUT... I need to be away for a few weeks and absolutely need to be able to access my PC remotely. I cannot risk this happening because when it is stuck on the error, connectivity is gone and it needs a manual enter keypress.

Is there any setting or configuration that will allow Windows to continue? Maybe with a timeout on the error or similar?
Or -
Is there any remote tool that will stay connected in that situation to allow me to do the keypress remotely?
Needless to say, I have another PC running Windows 7 that runs flawlessly with unattended operations - I just need this one to behave itself as well.

Thanks.

 

Continue automatically after Memory Referenced error on shutdown?


Hi, I had this happen fairly consistently for quite a while- but not for the last few weeks or more. I recall this being discussed in one thread many months ago, but no resolution. Very frustrating.

It will probably be related to an installed program.

If you search the forum for
"The instruction at"
(literally that string inc. "")
you will find a lot of results to scan through:




Example of one solved:
Windows 10 pro anniversary Explorer.exe Application error at shutdown - Windows 10 Forums
#5

Possible workaround
reciever error at shutdown Solved - Windows 10 Forums
#4

 

Referenced memory error

Hi all,

I have a problem with few PCs. They stop responding/are freezing. I did update all drivers and BIOS, reinstalled Windows and changed graphics card. Non of these work. I did uninstall NVIDIA Driver pack and after that it looks like Windows is crashing. I
get error code Exception Processing Message 0x0000006 Parameters 0x7ff8db971b58 and after while
The instruction at 0x00007ff8dd47f3e1 referenced memory at 0x0000000013585658. The required data was not placed into memory because of I/O error status of 0x000000e

Does anyone know about what the Exception Processing Message 0x0000006 is?

I did check EventViewer and there is a continuous error Event ID: 10016 DistributedCOM.

What I also did:

run diagnostics

chkdsk

updated graphics drivers

disabled sleep

extended turning off hard disk (power settings)

disabled USB selective suspend setting (power settings)