PDA

View Full Version : Surface Pro 11 Snapdragon X Elite 0xc000001d Error


farek.wolfmaster
09-26-2024, 03:01 PM
Hi,

I just bought the Surface Pro 11 with Windows on Arm. My immediate test was to see if I could get EverQuest Project 1999 to run. It didn't go too well and I was seriously thinking of sending it back. After some looking around I found the solution!

My computer:

_______Model_ : Surface Pro 11 - Snapdragon(R) X Elite 12-core X1E80100.
_____Edition_ : Windows 11 Pro
_____Version_ : 24H2
____OS build_ : 26100.1742
__Experience_ : Windows Feature Experience Pack 1000.26100.18.0


At first I could launch the game, via "Launch Titanium.bat". Everything went well up to the point when you've selected the server and pressed "Play EVERQUEST!".

Error message box popup with:

Everquest: Windows - Application Error
The exception Illegal Instruction
An attempt was made to execute an illegal instruction.
(0xc000001d) occurred in the application at location
0x000000006F9805A0.

Click on OK to terminate the program.

See attached file 0xc000001d_error.jpg:
https://www.project1999.com/forums/attachment.php?attachmentid=24137&stc=1&d=1727373287

Basically I couldn't reach the character selection screen...


Solution steps taken to fix this:

Go to your installation in File Explorer.
Mine is installed in C:\Program Files (x86)\EverQuest1999\
Locate eqgame.exe and Right Click -> Choose Properties
This will launch "eqgame.exe Properties" popup window.
Click the Compatibility tab.
Locate the "Windows on Arm" property group with description:
"If this program doesn't run correctly on Windows on Arm, try changing the emulation settings". Click the button "Change emulation settings".
This will launch "Arm emulation settings for eqgame.exe" popup window.
Locate the dropdown box just under the text "For other problems with this programme, try a recommended group of emulation settings or choose individual settings. Changing emulation settings can fix compatibility issues but can make this programme run slower.". Mine had Default selected originally.
Change "Default" to "Safe emulation".
Click "OK" to close "Arm emulation settings for eqgame.exe" popup window.
Click "OK" to apply all changes and close "eqgame.exe Properties" popup window.
Now launch the game again with "Launch Titanium.bat"
This time I was able to logon, choose a character and kill a rat in Innothule Swamp!
Happy days!


See attached file: eqgame_exe_arm_properties.jpg for final changes.
https://www.project1999.com/forums/attachment.php?attachmentid=24140&d=1727376036

Hope this helps remove any doubt, if you're planning on buying a Surface Pro 11 with the new Snapdragon X Elite Arm processor!

Enjoy! :D

Jimjam
09-27-2024, 02:05 AM
Also don’t install eq to Program Files (x86)

It works much better pretty much anywhere else.

farek.wolfmaster
10-17-2024, 11:03 AM
Hi,

After latest Windows Update my EQ started getting black window after I would Alt+Tab out. I tried various things but it's like the client doesn't receive the invalidation of the DirectX context. So it just doesn't draw the game after entering the game again. Luckily I was in a safe spot to /sit and /camp worked fine.

Eventually I decided to get WinEQ2 working. Problem I got was that WinEQ2 doesn't recognize the D3D9On12 mapping layer that comes with the Windows on Arm. I kept getting a popup saying DirectX 9c wasn't installed. So I ended up trying to install
latest DirectX 9....and it worked!
WinEQ2 launched and now rendering is working even after Alt+Tab.

However, running full screen doesn't seem to work. Window just animates like it's going full screen. Then directly goes back to its previous size.

Setting same resolution as desktop works, but UI text is so small. Right now I change desktop resolution and same size on WinEQ2 for readability.

Anyone gotten WinEQ2 + Windows on Arm on smaller screen working well?

To be continued...

NaturalHalfling
07-23-2025, 02:26 AM
Did you ever get the Alt-Tab issue fixed? What if you ran the game in a windowed mode?

edit: oops, nevermind, I read your last post properly and it seems you did do that. Sorry, dumb moment of mine.