DynDOLOD is being terminated prematurely, suddenly closes

[VulKun]

I can use 2.98 but i cant use 3 alphax. Still doesnt work for me. Just closing itself and there is no bugreport or something. I tried everything but nothing change 

[Surtensoita]

26 minutes ago, sheson said:

The log and debug you are uploading seem to show DynDOLOD was started and then cancel was clicked.

Do not start the program again after there was an error, so the debug log is not being replaced.

Ah, my bad then. In that case, I'm not getting any logs but the same two as before with the new .exe either, and I tried adding realtimelog=1 to the .ini you mentioned (and later to DynDOLOD.ini because worth a shot I guess) and still no logs.

[sheson]

9 hours ago, Surtensoita said:

Ah, my bad then. In that case, I'm not getting any logs but the same two as before with the new .exe either, and I tried adding realtimelog=1 to the .ini you mentioned (and later to DynDOLOD.ini because worth a shot I guess) and still no logs.

When you add a line realtimelog=1 under  [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini the there should be a DynDOLOD_SSE_realtime_log.txt in the log folder.

Also check the Windows event log.

You might want to update MO2 to the latest version.

[Surtensoita]

53 minutes ago, sheson said:

When you add a line realtimelog=1 under  [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini the there should be a DynDOLOD_SSE_realtime_log.txt in the log folder.

Also check the Windows event log.

You might want to update MO2 to the latest version.

omg, updating mo2 actually made it work. I'm now ashamed to have made you lose your time with this, thank you VERY much for your help and the amazing tool you have created.

[sheson]

15 minutes ago, Surtensoita said:

omg, updating mo2 actually made it work. I'm now ashamed to have made you lose your time with this, thank you VERY much for your help and the amazing tool you have created.

No problem! It is such an obscure problem. So this is a good reminder to really check such details in the logs as well.

[jimmywon34]

DynDOLOD doesn't finish when i run it, crashes/exits out with no warning. when it did give me the warning about Plockton's mod i made sure to disable it and run it again(with no success).

[sheson]

On 7/2/2022 at 5:04 PM, jimmywon34 said:

DynDOLOD doesn't finish when i run it, crashes/exits out with no warning. when it did give me the warning about Plockton's mod i made sure to disable it and run it again(with no success).

Delete all files in the log folder, so we are not confused by old log messages. Then run again. If no log or debug and no bugreport.txt in the same folder as the *.exe is created, it might mean the process is killed prematurely by the OS or antivir maybe.

In that case, check the Windows Event log for related log messages. Use google to find explanations about Windows OS tools and features. For example https://www.m-files.com/user-guide/2018/eng/faq_checking_windows_event_logs.html

[jimmywon34]

3 hours ago, sheson said:

Delete all files in the log folder, so we are not confused by old log messages. Then run again. If no log or debug and no bugreport.txt in the same folder as the *.exe is created, it might mean the process is killed prematurely by the OS or antivir maybe.

In that case, check the Windows Event log for related log messages. Use google to find explanations about Windows OS tools and features. For example https://www.m-files.com/user-guide/2018/eng/faq_checking_windows_event_logs.html

after deleting everything in the logs folder and attempting to run it again ther ewere only two files that came back into the logs folder, DynDOLOD_SSE_Dynamic_LOD.txt and DynDOLOD_SSE_Object_LOD.txt. checked the windows event and yes there is an error in there with dyndolod.exe and texconvx64.exe under the application tab(in windows event viewer).

Edited July 2, 2022 by jimmywon34

[sheson]

On 7/2/2022 at 8:14 PM, jimmywon34 said:

after deleting everything in the logs folder and attempting to run it again ther ewere only two files that came back into the logs folder, DynDOLOD_SSE_Dynamic_LOD.txt and DynDOLOD_SSE_Object_LOD.txt. checked the windows event and yes there is an error in there with dyndolod.exe and texconvx64.exe under the application tab(in windows event viewer).

You can doubleclick a message and then use the Copy button in order to paste it. The pure text is enough, no need for the XML code.

[jimmywon34]

54 minutes ago, sheson said:

Great. The rules will be included in the next Alpha version.

You can doubleclick a message and then use the Copy button in order to paste it. The pure text is enough, no need for the XML code.

you mean this ?

 

DynDOLODx64.exe

3.0.0.0

62adfbb8

usvfs_x64.dll

0.4.4.0

5d431c85

c0000005

00000000000408d8

1bc

01d88e421114b51d

F:\DOwnloads\SSE Mods\DynDOLOD 3.00-68518-Alpha-95-1655651317\DynDOLOD\DynDOLODx64.exe

D:\Mod Organizer 2\usvfs_x64.dll

8a4cae4b-38b8-4342-a71e-6076ec07d882   or this?    Log Name:      Application Source:        Application Error Date:          7/2/2022 11:33:13 AM Event ID:      1000 Task Category: (100) Level:         Error Keywords:      Classic User:          N/A Computer:      DESKTOP-R34D984 Description: Faulting application name: DynDOLODx64.exe, version: 3.0.0.0, time stamp: 0x62adfbb8 Faulting module name: usvfs_x64.dll, version: 0.4.4.0, time stamp: 0x5d431c85 Exception code: 0xc0000005 Fault offset: 0x00000000000408d8 Faulting process id: 0x1bc Faulting application start time: 0x01d88e421114b51d Faulting application path: F:\DOwnloads\SSE Mods\DynDOLOD 3.00-68518-Alpha-95-1655651317\DynDOLOD\DynDOLODx64.exe Faulting module path: D:\Mod Organizer 2\usvfs_x64.dll Report Id: 8a4cae4b-38b8-4342-a71e-6076ec07d882 Faulting package full name:  Faulting package-relative application ID:  Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">   <System>     <Provider Name="Application Error" />     <EventID Qualifiers="0">1000</EventID>     <Version>0</Version>     <Level>2</Level>     <Task>100</Task>     <Opcode>0</Opcode>     <Keywords>0x80000000000000</Keywords>     <TimeCreated SystemTime="2022-07-02T18:33:13.5603899Z" />     <EventRecordID>255079</EventRecordID>     <Correlation />     <Execution ProcessID="0" ThreadID="0" />     <Channel>Application</Channel>     <Computer>DESKTOP-R34D984</Computer>     <Security />   </System>   <EventData>     <Data>DynDOLODx64.exe</Data>     <Data>3.0.0.0</Data>     <Data>62adfbb8</Data>     <Data>usvfs_x64.dll</Data>     <Data>0.4.4.0</Data>     <Data>5d431c85</Data>     <Data>c0000005</Data>     <Data>00000000000408d8</Data>     <Data>1bc</Data>     <Data>01d88e421114b51d</Data>     <Data>F:\DOwnloads\SSE Mods\DynDOLOD 3.00-68518-Alpha-95-1655651317\DynDOLOD\DynDOLODx64.exe</Data>     <Data>D:\Mod Organizer 2\usvfs_x64.dll</Data>     <Data>8a4cae4b-38b8-4342-a71e-6076ec07d882</Data>     <Data>     </Data>     <Data>     </Data>   </EventData> </Event>

[sheson]

2 hours ago, jimmywon34 said:

you mean this ?

 

DynDOLODx64.exe

3.0.0.0

62adfbb8

usvfs_x64.dll

0.4.4.0

5d431c85

c0000005

00000000000408d8

1bc

01d88e421114b51d

F:\DOwnloads\SSE Mods\DynDOLOD 3.00-68518-Alpha-95-1655651317\DynDOLOD\DynDOLODx64.exe

D:\Mod Organizer 2\usvfs_x64.dll

8a4cae4b-38b8-4342-a71e-6076ec07d882   or this?    Log Name:      Application Source:        Application Error Date:          7/2/2022 11:33:13 AM Event ID:      1000 Task Category: (100) Level:         Error Keywords:      Classic User:          N/A Computer:      DESKTOP-R34D984 Description: Faulting application name: DynDOLODx64.exe, version: 3.0.0.0, time stamp: 0x62adfbb8 Faulting module name: usvfs_x64.dll, version: 0.4.4.0, time stamp: 0x5d431c85 Exception code: 0xc0000005 Fault offset: 0x00000000000408d8 Faulting process id: 0x1bc Faulting application start time: 0x01d88e421114b51d Faulting application path: F:\DOwnloads\SSE Mods\DynDOLOD 3.00-68518-Alpha-95-1655651317\DynDOLOD\DynDOLODx64.exe Faulting module path: D:\Mod Organizer 2\usvfs_x64.dll Report Id: 8a4cae4b-38b8-4342-a71e-6076ec07d882 Faulting package full name:  Faulting package-relative application ID:  Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">   <System>     <Provider Name="Application Error" />     <EventID Qualifiers="0">1000</EventID>     <Version>0</Version>     <Level>2</Level>     <Task>100</Task>     <Opcode>0</Opcode>     <Keywords>0x80000000000000</Keywords>     <TimeCreated SystemTime="2022-07-02T18:33:13.5603899Z" />     <EventRecordID>255079</EventRecordID>     <Correlation />     <Execution ProcessID="0" ThreadID="0" />     <Channel>Application</Channel>     <Computer>DESKTOP-R34D984</Computer>     <Security />   </System>   <EventData>     <Data>DynDOLODx64.exe</Data>     <Data>3.0.0.0</Data>     <Data>62adfbb8</Data>     <Data>usvfs_x64.dll</Data>     <Data>0.4.4.0</Data>     <Data>5d431c85</Data>     <Data>c0000005</Data>     <Data>00000000000408d8</Data>     <Data>1bc</Data>     <Data>01d88e421114b51d</Data>     <Data>F:\DOwnloads\SSE Mods\DynDOLOD 3.00-68518-Alpha-95-1655651317\DynDOLOD\DynDOLODx64.exe</Data>     <Data>D:\Mod Organizer 2\usvfs_x64.dll</Data>     <Data>8a4cae4b-38b8-4342-a71e-6076ec07d882</Data>     <Data>     </Data>     <Data>     </Data>   </EventData> </Event>

There seems to be an issue with usvfs_x64.dll from MO2. That's related to the virtual file system.

Update MO2 to the recent version.

[VulKun]

Yes its me again. and still dyndolod closing itself. And yes there is no message log or something..What should i do really dont know and yes i watched tutorials

[sheson]

On 7/4/2022 at 4:20 PM, VulKun said:

Yes its me again. and still dyndolod closing itself. And yes there is no message log or something..What should i do really dont know and yes i watched tutorials

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search and https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

DynDOLOD does NOT close itself. When DynDOLOD closes itself (e.g. is being shutdown properly), it writes logs and/or bugreport.txt. Since that does not happen, it means that DynDOLOD is being terminated by the OS or other 3rd party programs having a problem.

It seems you never uploaded the event logs. Based on the little information that was provided so far and similar cases, update MO2.

[VulKun]

1 hour ago, sheson said:

Read the first post. "Use search to find similar questions and answers."

DynDOLOD does NOT close itself. When DynDOLOD closes itself (e.g. is being shutdown properly), it writes logs and/or bugreport.txt. Since that does not happen, it means that DynDOLOD is being terminated by the OS or other 3rd party programs having a problem.

It seems you never uploaded the event logs. Based on the little information that was provided so far and similar cases, update MO2.

I did never update mo2 since 2020..lets see then

[VulKun]

Bruh its working.. Why didnt think before. But thanks for everything for now

[IX_Flipyap]

After a short amount of time Dyndolod will close its self but MO2 insists its still running and gives me an option to unlock it.