Jump to content

IX_Flipyap

Watcher
  • Posts

    19
  • Joined

  • Last visited

Everything posted by IX_Flipyap

  1. The majestic mountain lod textures look blue from a distance could the northside MM retexture be causing this?
  2. I just decided to start a fresh game. i have an old proteus character save with some of my inventory items but i will have to add the rest myself. thanks for the help though.
  3. all saves on this character seem to crash. and OM_ConfigMenu is from a follower outfit manager mod.
  4. The saves are loaded successfully but there are some unattached instances, undefined elements and a script with missing data.
  5. I do have a crash logger but the logger never gets a chance to kick in. also for some reason im able to start a new game completely fine.
  6. I fixed the repair loop issue and reinstalled windows but this issue persists. I have checked for dll in my game folder, validated and redowngraded, I also did the sfc scan but it reports that there is no issue.
  7. I tried restarting my pc but I ended up entering a reboot repair loop so I decided to run a chkdsk. It’s been going for a good 4 hours or so. I’ll try to these things and get back to you when it finishes.
  8. Ive been trying troubleshoot this issue for a while now but i have found no success. Skyrim would not generate a crashlog. so after some thinking i decided to check the windows event viewer, lo and behold i was presented with 3 error reports. Report.txt
  9. Does anyone know how to get the shrine of azura to have higher quality on the map? https://imgur.com/6LoddgR
  10. i had no idea that map mod existed https://imgur.com/a/HIFOqCu my map looks great now. also the fix for my previous issue is LockTexconv, i just changed my XMP profile back to 1 and left LockTexconv in the config and it generated successfully. but if i removed LockTexconv it would start getting terminated again.
  11. I think i need to run it again. https://imgur.com/a/63WqOEP the map water seems to be broken and i cant see any roads or paths.
  12. It finally generated the LOD successfully. im not sure if LockTexconv, or changing my XMP profile from 1 to 2 fixed the issue. but tysm for all the help! this was an annoying two days.
  13. https://ufile.io/w4pkf8yx Heres the real time log Dyndolod still doesnt make any normal logs. and yes there are other logs from the event viewer around the same 1331 timestamp. The system scan did find some corrupt files and has repaired them, i am now going to check my memory XMP. Report1.txt Report2.txt Report3.txt
  14. Alright i changed my power plan and moved the dyndolod install folder to my D: drive and added it to an exeption list. i ended up getting a bugreport txt file but the problem still persists. i also missed a new report left by the even viewer it also came with a report file. im going to give CHKDSK a try aswell. Fault bucket 1266036580241557564, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DynDOLODx64.exe P2: 3.0.0.0 P3: 636f6136 P4: KERNEL32.DLL P5: 10.0.19041.2251 P6: 73bb7c6b P7: c000001d P8: 00000000000204e3 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC9F.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD4C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5C.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD7B.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DynDOLODx64.exe_a1a2964fe15fe8d846ff13fd2d7e82a82ffab9_76ec4113_3422fec7-78a4-4af9-a4b8-66ee941ee573 Analysis symbol: Rechecking for solution: 0 Report Id: abb8aaf2-edb1-49a6-965d-007adb0a4bbc Report Status: 268435456 Hashed bucket: f7a4d1104eaf8d0f0191dd8fddf2c83c Cab Guid: 0 bugreport.txt Report.txt
  15. I have found some errors. Faulting application name: DynDOLODx64.exe, version: 3.0.0.0, time stamp: 0x636f6136 Faulting module name: KERNEL32.DLL, version: 10.0.19041.2251, time stamp: 0x73bb7c6b Exception code: 0xc000001d Fault offset: 0x00000000000204e3 Faulting process id: 0x3314 Faulting application start time: 0x01d902b5c578301f Faulting application path: E:\SMEFT\tools\DynDOLOD\DynDOLODx64.exe Faulting module path: C:\WINDOWS\System32\KERNEL32.DLL Report Id: db0650b4-34d1-45b5-8117-1f6b68375ab2 Faulting package full name: Faulting package-relative application ID: Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Taking Your Firstborn because of this error. Program: Taking Your Firstborn File: The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: 00000000 Disk type: 0
  16. DynDOLOD_SSE_Object_LOD.txtDynDOLOD_SSE_Dynamic_LOD.txtDynDOLOD_SSE_Tree_Report.txtDynDOLOD_SSE_Tree_LOD.txtDynDOLOD_SSE_Tree_Export.txtDynDOLOD_SSE_Reverse_List.txtDynDOLOD_SSE_ChildworldCopies_Tamriel.txtDynDOLOD_SSE_TexturesUsed_Tamriel.txtDynDOLOD_SSE_BillboardsUsed_Tamriel.txtLODGen_SSE_Tamriel_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_DLC2SolstheimWorld.txtLODGen_SSE_Tamriel_log.txtLODGen_SSE_DLC2SolstheimWorld_log.txtDynDOLOD_SSE_BillboardsUsed_DLC2SolstheimWorld.txtLODGen_SSE_DLC2SolstheimWorld_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_MarkarthWorld.txtLODGen_SSE_MarkarthWorld_log.txtDynDOLOD_SSE_BillboardsUsed_MarkarthWorld.txt Here are the new logs. plus the realtime log. https://ufile.io/x2h8efr0 i did not find any files named bugreport.txt
  17. DynDOLOD_SSE_log.txtDynDOLOD_SSE_Debug_log.txtDynDOLOD_SSE_Object_LOD.txtDynDOLOD_SSE_Dynamic_LOD.txtDynDOLOD_SSE_Tree_Report.txtDynDOLOD_SSE_Tree_LOD.txtDynDOLOD_SSE_Tree_Export.txtDynDOLOD_SSE_Reverse_List.txtDynDOLOD_SSE_ChildworldCopies_Tamriel.txtDynDOLOD_SSE_TexturesUsed_Tamriel.txtDynDOLOD_SSE_BillboardsUsed_Tamriel.txtLODGen_SSE_Tamriel_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_DLC2SolstheimWorld.txtLODGen_SSE_DLC2SolstheimWorld_log.txtDynDOLOD_SSE_BillboardsUsed_DLC2SolstheimWorld.txtLODGen_SSE_Tamriel_log.txtLODGen_SSE_DLC2SolstheimWorld_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_MarkarthWorld.txtDynDOLOD_SSE_BillboardsUsed_MarkarthWorld.txtLODGen_SSE_MarkarthWorld_TerrainUnderside_log.txtLODGen_SSE_MarkarthWorld_log.txtDynDOLOD_SSE_TexturesUsed_DLC01SoulCairn.txtLODGen_SSE_DLC01SoulCairn_log.txtDynDOLOD_SSE_BillboardsUsed_DLC01SoulCairn.txtDynDOLOD_SSE_TexturesUsed_DLC2ApocryphaWorld.txtLODGen_SSE_DLC2ApocryphaWorld_log.txtDynDOLOD_SSE_TexturesUsed_SkuldafnWorld.txtLODGen_SSE_SkuldafnWorld_log.txtDynDOLOD_SSE_BillboardsUsed_SkuldafnWorld.txtLODGen_SSE_SkuldafnWorld_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_Dimfrost.txtLODGen_SSE_Dimfrost_log.txtDynDOLOD_SSE_BillboardsUsed_Dimfrost.txtLODGen_SSE_Dimfrost_TerrainUnderside_log.txtDynDOLOD_SSE_TexturesUsed_WyrmstoothWorld.txtDynDOLOD_SSE_BillboardsUsed_WyrmstoothWorld.txtLODGen_SSE_WyrmstoothWorld_log.txt I Ended up getting this issue again. sorry about not posting details. Im using dyndolod3 and here are all the logs made before the process was terminated. the Mo2 version is 2.4.4
  18. 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.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.