[Solved] UMS crashes when turning monitor off

[jojo2424]

Hi there. I am using the latest UMS(Windows) for this.

I start my server, hit monitor power button, check my PS3 and notice the DLNA server is having an error. I go to turn my monitor back on and UMS has crashed and I have to re-open the program.

Now here is the kicker, if I let the monitor go to sleep on it's own after 2 minutes, UMS will NOT crash. I am not sure what is happening. Any insight? I did attach the debug log from TRACE logs but as its crashing I am not sure you will even see anything, but who knows.

And just for some more info, I have always since the PS3 media server version days turned my monitor off myself when streaming to my PS3. I thought this only started since the most recent updates but I uninstalled it and tried a really old version from 2020 and it happens there too.

Would having a second monitor connected be a cause for this phenomenon?

[mik_s]

I don't see how the monitor being turned off would be the cause of it crashing, unless it is something on the OS that is crashing.
I had a scan of your logs and did not see anything obvious about a crash.
How exactly does it crash? Is there anything different with your monitor like built in USB? How is it connected(HDMI, DP, USB)?
Your zip file does not include the confs so I can't see if it is one of your settings.

[jojo2424]

So this is my setup.

Rtx 3080 graphics card. Display port to hdmi cable goes to my Dell monitor. Hdmi to hdmi goes to my TV. So 2 monitor setup.

I start UMS, turn my PS3 on and check to see that it sees the server. It does so I just hit the power off button to turn my Dell monitor off. Then on the PS3 the dlna error message pops up and it can't see it anymore. Once I turn Dell monitor back on I notice UMS has crashed and I need to start it again.

I have tried with a solo monitor as well and it still does it as well.

Barring nuking my windows install and formatting etc, I am not sure what is going on either.

[rhayy]

Maybe look at the event viewer log to get more information about the crash.

[jojo2424]

So I just tested it again and checked event viewer right after. These 3 errors happened for it.

Source Application Error (Event ID 1000 (Task Category 100))
Faulting application name: javaw.exe, version: 17.0.4.1, time stamp: 0x991d3543
Faulting module name: dxcore.dll, version: 10.0.19041.546, time stamp: 0xb2f5fd5a
Exception code: 0xc0000409
Fault offset: 0x0000000000020fa7
Faulting process id: 0x426c
Faulting application start time: 0x01d8f890c8d29afd
Faulting application path: C:\Program Files (x86)\Universal Media Server\jre17\bin\javaw.exe
Faulting module path: C:\Windows\SYSTEM32\dxcore.dll
Report Id: aa0cc8d4-8b0c-4015-8313-b25509b98c17
Faulting package full name:
Faulting package-relative application ID:

Windows Error Reporting (Event ID 1001)
Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: javaw.exe
P2: 17.0.4.1
P3: 991d3543
P4: dxcore.dll
P5: 10.0.19041.546
P6: b2f5fd5a
P7: 0000000000020fa7
P8: c0000409
P9: 0000000000000003
P10:

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_javaw.exe_eb71e5f1deceefd77022751fe24c9925eb45068_11fb8c20_bdb5faf1-7919-4803-8228-8916ce359d90

Windows Error Reporting (Event ID 1001)
Fault bucket 1998872519163989561, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: javaw.exe
P2: 17.0.4.1
P3: 991d3543
P4: dxcore.dll
P5: 10.0.19041.546
P6: b2f5fd5a
P7: 0000000000020fa7
P8: c0000409
P9: 0000000000000003
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER11E.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_javaw.exe_eb71e5f1deceefd77022751fe24c9925eb45068_11fb8c20_bdb5faf1-7919-4803-8228-8916ce359d90

Analysis symbol:
Rechecking for solution: 0
Report Id: aa0cc8d4-8b0c-4015-8313-b25509b98c17
Report Status: 268435456
Hashed bucket: a7a94f984c6fae5d0bbd6bf7380f4e39
Cab Guid: 0


Looks like it is Java crashing?

Also here is the trace log. I didn't realize the first one wasn't it when I looked in UMS folder. But since its crashing I ended up just hitting the pack before it happened since the log doesn't seem to get updated when its crashing like this for me.

[mik_s]

I don't know enough to figure this one out. That extra info from the event viewer was a good idea though.
As far as I can tell it is something to do with dxcore.dll, which is part of directX but have no idea why it would crash when the monitor is turned off.

I think this is something the devs will have to investigate. There are a couple of locations of some windows debug files that may help them listed there. Could you post them too?

One thing you might be able to try is to disable the GPU acceleration in UMS. Go to the transcoding settings tab an under "Common transcoding settings" section, uncheck "Enable GPU acceleration" in the video setting tab below. Next in the "FFmpeg Video" section set "GPU decoding acceleration method" to none.
See if that makes any difference and if not return those back to default.

[rhayy]

I don't know how to investigate more but it is related to dxcore.dll.

Did that happen after some Windows update ?

[jojo2424]

@mik_s

Here is the log windows error report made. Also I checked those two settings and they were already set to what you had asked for.


@rhayy

I noticed that too about the dxcore.dll --- Did /sfc scan and /Dism to no luck for fixing the issue. If that DLL has anything to do with games too I am not noticing issues with those so not sure how it is interacting with java exactly when the monitor gets turned off.

As for windows update, I recently updated to latest W10 version I suppose but all this with UMS started before that.

[jojo2424]

Just wanted to put an update out here. So I was randomly testing some things and found that if I run UMS in administrator mode, turning my monitor off (me pushing the button) will not have it crash. Now I also tested that if UAC is off, UMS will also not crash (with or without administrator on). I guess when I reinstalled Windows 10 earlier this year I left UAC on and never turned it off like I usually do.

So in the end, looks like it is Windows User account control that is causing these problems. Still odd that the monitor sleeping wouldn't trigger UAC to kill the program(s), but my physically turning it off does.

Just wanted to let you all know that ATM it seems fixed for me.

[mik_s]

Thanks for the update.
I had posted an issue on GitHub so the Devs can have a look as I have no idea how this can happen.
The UAC thing might be a clue to a hidden bug somewhere. Maybe something on your system needed admin access to update a file or setting and turning off UAC allowed that to happen. Could you try turning UAC back on and see if it starts crashing again?

I would not turn UAC off totally though, best to keep it at the default level. I know it is annoying but it could prevent something malicious running without you knowing.