Osu: Can't run osu lazer with error 1114

[zeeterv]

Describe the crash:LoadLibrary with error 1114: A dynamic linkblibrary (DLL) initialization routine failed

*Screenshots or videos showing encountered issue:

*

osu!lazer version:2019.1011.0 and newer

Logs:log.zip

Computer Specifications: Windows 10 pro 64 bit version 1903

[bdach]

Please attach logs from %AppData%/osu/logs, if any present, and additionally Windows Event Viewer info by performing the following steps:

1. Type Event viewer in the Windows search bar (shortcut: Windows+S) and press Enter, or open the Run... button (Windows+R), type in eventvwr and press Enter.
2. The Event viewer window will appear. Expand Windows Logs on the left and choose Application. It might take a while to load.
3. In the Actions pane on the right click Save All Events As..., then choose a location to save to.
4. On the Display Information popup, select the second option, then the checkbox to show all available languages, then English (UK) (US would also do fine).
5. Append the resulting .evtx file to this issue.

[zeeterv]

Added

[frenzibyte]

Can you provide us with your hardware info? also, is your GPU switchable? I have the same problem after the .NET Core 3.0 update in lazer on Intel HD Graphics 3000 switchable with AMD Radeon HD 6630M.

Two things I had found while trying to find what the cause is:

1. This issue happens when running an installed version of osu!lazer or running osu.Desktop in VS 2017 (never got that on Rider 2019.2.2, VS 2019 untested)
2. This issue doesn't occur when running osu!lazer test browser or framework on any IDE (including VS 2017), though haven't tested SampleGame yet..

[bdach]

I've looked through the event viewer logs - unfortunately nothing decisive. Only mention of osu! is a Windows Error Reporting RADAR_PRE_LEAK_64 diagnostic entry, which as far as I can tell from googling doesn't actually mean much.

In light of that, I'd appreciate it if you could also attach DirectX diagnostic info by performing the following steps:

1. Press Windows+R, type dxdiag in the appearing window and press Enter.
2. You could be prompted if you'd want Windows to check if the device drivers are signed - there should be no harm in agreeing to that.
3. In the DirectX Diagnostic Tool window that will appear, click Save All Information... and choose a file to save to.
4. Attach the saved file to this issue.

[smoogipoo]

Seems like this may be related to switchable graphics in any case. You may be able to right-click on the icon and run with a particular GPU, or you'll need to go into your GPU driver software and make sure osu! is set to use the high performance graphics processor.

Additionally, I'd try reinstalling your graphics drivers.

[zeeterv]

DxDiag.txt
Added

[bdach]

The dxdiag output above shows just one card, so save for some Windows hiccup I think this is another Intel issue rather than switchable graphics in general. Driver version seems to be the latest too. Do releases prior to 2019.1011.0 work?

Sort of at a loss what to do next here without an actual machine I can reproduce/debug on, since this error looks like it's bound to be hairy...

[frenzibyte]

The dxdiag output above shows just one card, so save for some Windows hiccup I think this is another Intel issue rather than switchable graphics in general.

You may be wrong here, you don't get switchable graphics info by checking DxDiag (as I tested and found). a good way would be opening the device manager and checking the display adapters.

[zeeterv]

I'm afraid black screen Like making friends

[frenzibyte]

@zeeterv Can you please inform us whether you do have a switchable graphics card or not by doing what I said above, for steps on how to do it (for Windows 10):

1. Press Windows+X, then select Device Manager.
2. Inside the Device Manager window, expand the Display adapters list and screenshot what's inside.

[zeeterv]

[zeeterv]

Detailed-System-Report.zip

[zeeterv]

[zeeterv]

and why i got this

[RoARene317]

and why i got this

For that issue , please contact osu!support and not on github.

[bdach]

After checking with @iiSaLMaN who owns the appropriate hardware it looks like #7088 might fix this too, since after it being applied the app host starts working again. Doing dotnet osu!.dll still doesn't work, but we can't do anything about that without modifying the binary of the dotnet host.

Closing and unlocking; if this does turn up again after the next release, please drop a comment and/or reopen.