Onyx Crashing regardless of show file or PC

Software Version:
NX Console Type or PC OS Version: NX Wing with an NX P.

This really started to get bad this past Weds. For the last 2 weeks I have started to have issues which pushed me to move to version 4.32. At first all seemed well, then nothing but issues.

I have spoke to someone from the tech line and then emailed logs, my show file, pictures of the error causing the crash “OnyxExternalMidi.exe” is 99% of the time the culprit followed by ntdll.ll fault. Atleast that is what it appears as.

I have fully wiped Windows 11 pro, re installed, clean install of everything, drivers completely updated and still crashes. I figured it was the show file so I have been trying to make a quick one for tomorrow’s show but an hour in it did the same thing.

It starts with half the view missing on a side screen, then going to a different function nothing shows up. Cant close or save the file and it closes.

Started with Dylos pages being open and after some edits or cues it would close.

Anyone had this issue? Old and new files closing, screen tearing?

I have a show in 24 hours and I can’t keep onyx open.

Help.

I ment to add I am not using any external midi devices. Which is why the OnyxExternalMidi.exe seemingly causing the crash is so confusing.

The NX wing does have the midi I/o.

Anyone using V4.32 with an NX Wing?

Hey @Austeee -

I don’t have a wing but have some questions based on the post. How many screens are you using with the PC? Are you using the default workspace(s) or do you have your own created? If so, have you tried saving your off again and loading the defaults? Can you confirm the full version number and Obsidian Driver Package from the Windows installed apps menu. Curious is there is a mix match. Also back in the day there was something with making sure DirectX was up to date for DyLOS. I thought they had that sorted out, but some of your issues make it sound like there could be something there. Anyway, not so much an immediate answer, but maybe a way to start ruling things out. Also there used to be TeamViewer to help support log in and take a look.

Hope some of these ideas help,

Watson

1 Like

Appreciate the reply.

I am using 3 screens a majority of the time. 1 in front of the Wing, one in front of the NX P, and a 3rd to the right of me which was typically just for capture/2d/dylos playback.

Both screen in front of the hardware are Touch Screens. System worked pretty flawlessly for the last 3ish months.

I am using my own custom layouts. I hate that I can’t label the playback pages so I add a thin strip above the playback page that I insert the groups tab into and then make the label in the groups page. Starts in the 1001, but no fixtures are in the group, purely a label. I have not tried to go back to default pages, I can try that. But that triggering the OnyxExternalMidi.exe error would be truly something. I will give it a shot, I can just make a copy of my file and use the defaults.

The driver package and the Onyx version are both

4.32.1302.0

I did try the Direct X install and even the C+++ fix to no avail

I have attempted only using 1 screen, 2 screens, Just the NX Wing, and just the NXP with the NX K , all trigger some type of crash .

I have tried the main Onyx PC, our Back up onyx PC and the 3rd which is a generation older I use for ETC Concert to monitor the nodes and all 3 have done the same thing. But, all 3 have been updated and are essentially clones of each other so I would expect them to be the same .

I think I might be making some head way considering I installed it all to my Work pc which is a Surface Pro Laptop and as of now it’s been solid for the last 2 hours. Running capture along side like normal. I have no control of the updates on my work pc since it’s on policy but there is something this pc has or is able to do that the others can not

I am in the middle of a compete re-install of Windows 11 Pro on the main onyx pc, with a fresh downloaded copy of onyx. I put all the factory drivers in a usb so I don’t have to use the internet at all, it worked perfect for months when it was all fresh installed. I can’t help but wonder if the crappy windows updates broke something.

It’s been a long 2 days man

Just an update. I believe I have fixed my issue. I don’t want to speak to soon but after leaving 4 dylos zones up, multiple FX and using 2 touch screens I have not had a single crash in the last 7 hours. In the event viewer the error of ntdll.ll kept popping up. Seems this file causes a lot of issues in the gaming community. A recommendation is to copy that file from a working pc and copy it to the affected pc.

C:\Windows\System32 Is the location of ntdll.ll for anyone’s future reference.

I copied it from my work PC since even after doing a complete and clean install of all software was still causing crashing, I pasted it into the file and boom, no crashing, no screen tearing, no OnyxExternalMidi.exe crashes. Wtf?

So I thought do I have a bad copy of windows 11 pro? I downloaded the creation tool from windows for a fresh copy and once again did a clean install of windows and onyx, never touching the internet, and so far rock solid just like it used to be.

I have since done clean installs on the back up PC and the 3rd network monitor pc and now all 3 seem to be in the clear? Man I hope so. I am pretty sure this all stemmed from last months Windows update.

From here out the machines will be on completly stock software and settings with no updates and no internet. Just not worth the headache.

I will post back after our show tonight and hopefully report no crashes.

Hi @Austeee

Apologies for the delayed response - I have been attending PLASA trade show.

Thank you very much for the update. If ntdll.ll was partially corrupted, that would have caused various system issues, including affecting ONYX.

Hopefully your show ran smoothly after replacing this file.

Edward

Hello Edward,

No worries. Hope you had some fun.

Unfortunately it appears my issues was not solved. And continues to happen on Intel or AMD machines. I am able to work no problem with one screen. The issues seems to stem from adding virtual displays. I have been in contact with Matt and he did send the diagnostics tool. I sent all the information I could, and just sent more since it happened to me just now on a brand new Intel PC. I was able to use the logging tool in the menu during a crash and also send the diagnostic tool image of this intel machine. Along with some images of the event viewer and my show file which has some pretty heavily edited playback pages that might be causing this

I’ve been on a bit of a goose chase, thinking it was one thing, seemed stable, thought I was good, then crash.

The ticket number is #902360 if you are interested since I believe you have access to all that stuff as well, apologies if I’m wrong.

I’m glad I can still work as long as one screen is open but I am in constant fear of onyx crashing and loosing a ton of work.

Thanks for the reply. Hopefully they find something out and know what’s going on.

Thank you very much for sending us all the details. As mentioned in my email, this issue is logged on our system as ONYX-1244, and will be fixed in the next ONYX software update.

Please let us know if you have any questions.

Edward