Mod > Information > Nexus Info (MO2 stops responding).

[ChristopherC71]

The problem:

When looking at any mods property within a Skyrim AE profile to review Nexus info MO2 stops responding. This is a Windows 11 desktop less then 1 week from fresh win11 setup. As this is a fresh start thought the move from Vortex to MO2 was a good time. I also tried an install of 2.5.1. rc2 with the same results.

To Reproduce:

Steps to reproduce the behavior:

1. Go to any Skyrim AE mod right click for menu and select "Information"
2. Click on 'Nexus Info' tab
3. No longer able to do any other action then close out window.

Environment:

• Mod Organizer Version that exhibits the issue: 2.5.0
• Last Mod Organizer Version that did not exhibit the issue (if applicable): n/a
• Desktop OS/version used to run Mod Organizer: Windows11 Pro 23H2 22631.3155

Details:

Link to Mod Organizer logs:

Right click on the log window at the bottom of MO2, set log level to debug, restart Mo2 and reproduce the problem.
To access the log files you can press the Open folder icon over the modlist and select "Open MO2 Logs folder".

USVFS:

Create a GIST which is a paste of your latest USVFS log, and link them here.
Do NOT paste your full USVFS logs here, as it will make this issue very long and hard to read!
If you are reporting a bug, always include the USVFS logs!

https://gist.github.com/ChristopherC71/b9434132b3ba440f65087143c8695c15

MO Interface:

Create a GIST which is a paste of your mo_interface logs, and link them here.
Do NOT paste your full mo_interface logs here, as it will make this issue very long and hard to read!
If you are reporting a bug, always include the mo_interface logs!

https://gist.github.com/ChristopherC71/b89aa4e1366dea812407fd3f26458656

[ChristopherC71]

This might be tied to an open GL driver issue. I am digging into reverting this path.

Faulting application name: ModOrganizer.exe, version: 2.5.0.0, time stamp: 0x65640dd8
Faulting module name: atio6axx.dll, version: 31.0.21910.5, time stamp: 0x6564c9cf
Exception code: 0xc0000005
Fault offset: 0x0000000000bdc885
Faulting process id: 0x0x974
Faulting application start time: 0x0x1DA640CA585BBEF
Faulting application path: Q:\Modding\MO2\ModOrganizer.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\u0399660.inf_amd64_d7fa3539ce499e50\B399655\atio6axx.dll
Report Id: cdf55fc2-6ac6-488e-9f98-780ef7c250c3
Faulting package full name:
Faulting package-relative application ID:

[ChristopherC71]

Ok, confirmed this issue was tied to the above error. I downgraded to amd-software-pro-edition-22.q4-win10-win11-nov15.exe and functionality is restored. Issue when googled focuses on the Open GL atio6axx.dll as a dll with issue. I had tried MO2 v2.4.3 and found the same issue so decided to start digging into my windows logs. Not sure if this will be terribly helpful to others until AMD gets their dll fixed.

[ChristopherC71]

I reported this to AMD but I do see a lot of other apps having issues with that DLL file.

https://community.amd.com/t5/graphics-cards/opengl-atio6axx-dll-causing-application-crash/m-p/667205#M105317