Error on Windows 10 before restart "The instruction at 0x0000008 referenced memory..

Me too, and I think everyone else.

 

certainly not everyone since "some" get along quite well with new os preview. Look after your hardware or overclocks or such, control your bios and don't always blame on windows

 

You need to login to view this posts content.

 

really, never had such message ever

 

I get the same error when I exit Windows 10. Just rigth before the desktop goes off the screen.
It then restarts normal. This happens with both systems running Windows 10.

 

Only happens on my laptop, haven't had such message running w10 on a desktop

 

ran it on my Surface pro2 without any issues but made a backup of files and returned back to normal though

strange

 

Did not get it, neither VM or real machine (laptop)

 

same here, tried many different boxes now and different oses both architectures and found not a single bug since

edit: no bug that leads to malfunction, not talking about unfinished things in this alpha software !

 

You need to login to view this posts content.

 

Yep, I have it too in VMware...

...according MS it is caused by servicing utility IELowUtil.exe, what sometimes hooks on Explorer.exe (when needed).
That utility connects the sessions of IE, what run on different integrity level. (When you store cookie with IE process at Medium integrity, so you can read it later with IE process at High integrity etc.)

It will be fixed in final RTM (same has happened in W8-0).

 

Same here, appears in VMWare just before shutdown, but not always...

 

Just as others have said. It doesn't happen very often, I'd say 1 out of 10. It comes up right before restarting and it seems to be harmless. It doesn't seem to show up on Event Viewer. This is pre-beta software people.

 

I had the same message in a VM, I've installed Enterprise, and no such error as of yet. I'm sure that error message sent to MS. You can always mention it in in Feedback.

 

I was going to mention it in the feedback app, but it was already there.

 

Had it once twice.

 

I haven't seen such a bug, either--no show-stoppers. I've done a clean install & upgraded another box running 8.1x64 without difficulty (to see if it would work.) These are both desktop machines, though, with 1st-tier components & drivers (laptops are horrid little devices that should be banned...--saying it with a laugh, but I've successfully resisted them for 30 years, save those forced on me at times by various employers that only served to reinforce my avid dislike of the treacherous things.)

Such an error appearing, at least on a desktop, I would say is either a hardware fault being exposed by the software, or else is the result of an application conflict/driver conflict which the OS is incorrectly identifying as a hardware fault, and since more than one person is reporting the identical error message I'd say the latter is more likely.