Re: Origin preventing windows shutdown windows 10

@WhenKittensATK

Could you specify which post fixed your issue? I want to make sure to have that post visible for all players.

The crash can be fixed in various ways for those having messed up systems... but the Origin client preventing Windows shutdown (and no crash), slowing down shutdown, is a universal issue reproducible on every Windows 10 + Origin installation. This can't be fixed by users since it's a bug in Origin software design...

@Straatford87

From user: BeerGogglesFTW

The error with Origin only occurs when I'm running an application called "HsMgr Application" in the Windows startup programs.

I have 2 "HsMgr Application"s in the startup programs that look the same from the Task Manager (Same name)... When I look to the files they're different though:

C:\Windows\SysWOW64\HsMgr.exe

C:\Windows\System\HsMgr64.exe

This file: C:\Windows\SysWOW64\HsMgr.exe is the one I disabled from startup. Now Origin doesn't crash when I shut down.

From the looks of it through some google searches, these files are related to my ASUS Xonar Soundcard... So I'm not a fan of disabling them. I could be hindering my sound-card for the sake of preventing an Origin error.

I doubt I can expect a solution from ASUS, my drivers are the latest and from October 2015. So, I would think the only chance for a real solution would be from EA/Origin since that is the only program I can get this error from.

@WhenKittensATK

Thank you for referencing to that post.

To clarify; did you experience the failure to shut down? Or the memory access violation?

@Straatford87 I got the memory error during shutdown same as the first post.

Hello,

Still having the issue and Nothing has been fixed for me with the last updates. Some people on the thread seem to say that it had been fixed by Origin updates and I would like to know how they did it.

Having an Asus sound card too but it does not cause any problem with programs such as Steam or Battle.Net. So it is clearly a problem with Origin client.

Thank you.

Ofcourse. Its not done yet. Problem still is on my hardware too. Two computers. Two with Windows 10 (one Home and one Pro). Both with Xonar cards.

I've been having the same Error message since origin done there main update - (the one that change the way it looked) 

I have just clean installed my PC W10 x64 16DDR and I have a asus Xonar card in my PC also ---

Funny thing my PC seem to close down fine with Origin open for the first couple of Shut down -- and now I'm getting the same error message -- again -- like before the clean install -- 

If this can be fixed as its a PAIN --- to have to stand by your PC and click a Button to get you PC close ---

Or is there anyway to revert BACK to the OLD Origin Drivers -- so that it resolve this problem for the time being --- will you look into this and fix it? 

The ERROR i'm getting is the Memory Error as stated in this post chain.  Which in turn is causing the PC not to shut down --- = it then pops up an Origin Error message that you have to click for the PC to be able to Close down.  

Many thanks 

apex40000

My workaround was the following:

1) Close Origin if you have it Open

2)  Right-click on the Origin Shortcut. --> Properties

3) Compatibility---> Choose Windows XP

4) Now run Origin again,

5) It will now download a new (old) client, since it thinks it's running Windows XP.

6) Let it finish and once you got into the client go to "Origin->Application Settings" and uncheck "Keep Origin up to date"

Now close the client, follow steps 2+3 but remove the "compatibility" flag. Your client will now run in native mode, but keep the old version. While it still slows shutdown for me, no nasty error-message is displayed; whit this client you can choose to have origin close automatically when the game application is closed.

Really bad software right there and one of the reasons why PC gaming is still lacking in comparison to consoles on a "User Experience"-level.

FIX IT EA!

System:

Core i7 2600K

16GB Ram

GTX 970

Asus Xonar X1 (PCI-Soundcard) <--- Software for this is the conflicting part alright. (Hsmgr,exe/hsmgr64.exe <---- Needed for legacy EAX supprt)

3 YEARS LATER and this crap is still happening. DAfuq?