Environment
- Mod Organizer version: 2.5.2
- OS: Windows 10.0.28000.2113 amd64, locale zh-CN
- Install type: portable
Summary
MO2 2.5.2 crashes immediately on startup after a reboot. This happens with both an existing portable instance and a freshly extracted clean MO2 2.5.2 portable copy.
A MO2 2.5.0 portable copy on the same machine still starts successfully.
Affected copies
Crashing:
D:\TAKEALOOK\ModOrganizer.exe
- Version: 2.5.2
- Size: 5,028,352 bytes
D:\Mod.Organizer-2.5.2\ModOrganizer.exe
- Version: 2.5.2
- Size: 5,028,352 bytes
- Freshly extracted clean copy, no existing
ModOrganizer.ini, no logs directory produced before crash
Working comparison:
D:\SteamLibrary\steamapps\common\Fallout 4\MO\ModOrganizer.exe
- Version: 2.5.0
- Size: 4,923,904 bytes
Crash details from Windows Event Viewer / WER
For the clean 2.5.2 copy:
- Faulting application:
ModOrganizer.exe
- Application version:
2.5.2.0
- Faulting module:
ModOrganizer.exe
- Module version:
2.5.2.0
- Exception code:
0xc0000005
- Exception offset:
0x000000000001b675
- Event type:
APPCRASH
There was also a related AutoVerifierV2 WER entry for the same executable and same exception/offset. That report listed C:\Windows\SYSTEM32\verifier.dll as a loaded module, but verifier /querysettings reports no verified drivers and no active rule classes.
Timeline / observations
- The existing
D:\TAKEALOOK instance was able to start earlier the same day and wrote mo_interface.log up to 2026-06-17 10:32.
- The system rebooted later.
- After reboot, MO2 2.5.2 began crashing immediately on startup.
- A clean newly extracted MO2 2.5.2 portable copy also crashes before producing any MO2 log files.
- MO2 2.5.0 still starts on the same machine.
Last useful MO2 log from the existing instance
The last successful log from the existing instance includes normal startup and game detection:
starting Mod Organizer version 2.5.2 revision 9c130cbf in D:/TAKEALOOK, usvfs: 0.5.6.1
using game plugin 'Skyrim Special Edition' ('SkyrimSE', variant Steam, steam id '489830') at D:/TAKEALOOK/Stock Game
The clean 2.5.2 copy does not create a logs directory before crashing.
Notes
I have local .dmp files from both the existing instance and the clean 2.5.2 instance, but I am not attaching them publicly because they may contain local paths or process memory. I can provide dumps privately or in the format maintainers prefer if needed.
Environment
Summary
MO2 2.5.2 crashes immediately on startup after a reboot. This happens with both an existing portable instance and a freshly extracted clean MO2 2.5.2 portable copy.
A MO2 2.5.0 portable copy on the same machine still starts successfully.
Affected copies
Crashing:
D:\TAKEALOOK\ModOrganizer.exeD:\Mod.Organizer-2.5.2\ModOrganizer.exeModOrganizer.ini, no logs directory produced before crashWorking comparison:
D:\SteamLibrary\steamapps\common\Fallout 4\MO\ModOrganizer.exeCrash details from Windows Event Viewer / WER
For the clean 2.5.2 copy:
ModOrganizer.exe2.5.2.0ModOrganizer.exe2.5.2.00xc00000050x000000000001b675APPCRASHThere was also a related
AutoVerifierV2WER entry for the same executable and same exception/offset. That report listedC:\Windows\SYSTEM32\verifier.dllas a loaded module, butverifier /querysettingsreports no verified drivers and no active rule classes.Timeline / observations
D:\TAKEALOOKinstance was able to start earlier the same day and wrotemo_interface.logup to2026-06-17 10:32.Last useful MO2 log from the existing instance
The last successful log from the existing instance includes normal startup and game detection:
The clean 2.5.2 copy does not create a
logsdirectory before crashing.Notes
I have local
.dmpfiles from both the existing instance and the clean 2.5.2 instance, but I am not attaching them publicly because they may contain local paths or process memory. I can provide dumps privately or in the format maintainers prefer if needed.