Wulfga

I've followed all your advice- that's what the couple-day pause was. I reviewed the BIOS line by line, removed all of the overclocking (broke my RAID array at 2am on accident) reinstalled everything fresh, and have consistently had the same issue. With the rolled back driver to 531.41 and your INI edit, it's (veeerrrrrryyyy slowly) working. I owe you a beer. For the record, I genuinely think there's something in the new Nvidia drivers that are breaking it. RenderSingle=1 on the current drivers did not work. If it were to ever come up again, RenderSingle=1 on nVidia driver version 531.41 worked fine for me. I do have an absolute mountain of other NVIDIA tools for CUDA, etc, so this might be unique to folks creating animations and doing complex AI work, can't say for sure, but it just finished with all overclocking in place and no changes except the single INI edit and the driver rollback. Cheers. [20:33] Removing temporary files [20:33] Waiting for Texconv to convert 2 textures [20:34] TexGen completed successfully [20:34] Exit TexGen, zip and exit, check log or restart? Thanks for putting up with me.

Ahh, that's fair. I had (I promise) set that to 1, but I did a fresh install of all DynDOLOD software and didn't set it back. I DO THINK I FOUND PART OF THE PROBLEM. When I completely uninstalled my Nvidia drivers rather than just doing fresh installs etc., it went WAAAY farther than I've ever seen it go before, and I finally got an "OpenGL version too low" error much farther in than normal. [02:52] Error: OpenGL: H:\Modding\Tools\DynDOLOD\TexGen_Output\Textures\dlc01\lod\dlc01dawnguardcastle01lod framebuffer objects unsupported. I'm currently backing down through versions of the driver trying to find one that works. 531.41-desktop-win10-win11-64bit-international-dch-whql just failed, 531.61 failed previously. I'll add your "1" now for consistency. Thanks for catching that. (attachments from no driver test where I let Windows 11 handle the GPU) I'll test the RenderSingle=1 right now. TexGen_SSE_log.txt bugreport.txt

Thank you for squaring me away enough to get a bug report in. Was finally able to get far enough for one to generate on one of my attempts. In 40 or so runs this is the first time I've been able to generate a debug log. I PM'd you the bug report because honestly, it's got a decent amount of personal info in it, but I'd really like to not give up on this after all the time spent. To anyone else who might know anything about this error, I absolutely can't get past this strange DLL error: Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33 Faulting module name: nvoglv64.dll, version: 31.0.15.3598, time stamp: 0x646dfba9 Exception code: 0xc0000005 Fault offset: 0x0000000001550f2a Faulting process id: 0x0xD40 Faulting application start time: 0x0x1D997D3012B155A Faulting application path: H:\Modding\Tools\DynDOLOD\TexGenx64.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3c2bd4a1ec6d228e\nvoglv64.dll Report Id: 31970090-ec36-4d74-b85b-fcaf1cfc50f9 Faulting package full name: Faulting package-relative application ID: I really don't want to give up on this, but no one has both the knowledge and the patience to get me past it. Intel i9 13900k, RTX3070ti, completely fresh drivers, Alpha-128 Dyn from Nexus and the Alpha-36 Resources that the website links to. I'm sure this is somehow my fault but I've exhausted my ability to try more things. Ran SFC and DISM, both fine, I'm just at a loss. Added the Realtime log (had to zip it, it's huge) TexGen_SSE_realtime_log.7z

I guess I did a bad job explaining that part. That window with the scolling text... if that's your debug log, it doesn't save at all when it just errors out and ends abruptly. I only get it to close normally and create the logs I've attached one out of every... maybe 9 attempts. I'm in the hundreds probably. I have removed overclocking from the CPU, yesterday I think. My graphics card memory is overclocked a little but extremely stable. Attached CPU-Z, because running out of ideas. Attached the only additional log file that survived long enough in that temp folder to grab it. Error log from Event Viewer: Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33 Faulting module name: nvoglv64.dll, version: 31.0.15.3598, time stamp: 0x646dfba9 Exception code: 0xc0000005 Fault offset: 0x0000000001550f2a Faulting process id: 0x0x5484 Faulting application start time: 0x0x1D995612705F484 Faulting application path: H:\Modding\Tools\DynDOLOD\TexGenx64.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3c2bd4a1ec6d228e\nvoglv64.dll Report Id: fabd6cbe-c4a7-44ed-9ac3-f7166bb8d365 Faulting package full name: Faulting package-relative application ID: Info log from event: Fault bucket 1897463078308581007, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: TexGenx64.exe P2: 3.0.0.128 P3: 646a6e33 P4: nvoglv64.dll P5: 31.0.15.3598 P6: 646dfba9 P7: c0000005 P8: 0000000001550f2a P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.190bcaf4-91c6-4d6b-aaa4-a1c764e90a88.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.143f5221-3e03-4c96-b9e7-e10fa80b639e.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e5c8fd98-60a4-4bee-9a87-9c3566ef8a34.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.165cd335-cfd1-4050-92c5-b7d3037f165d.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.43564062-c08f-4f02-b8e7-7a71c81d2a0d.tmp.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_TexGenx64.exe_6f6a94369d9c1185cd99bbdf7a6bac316c9e971e_5b7d448d_8f98ccab-d9b2-4a22-81d8-9332586eff8a Analysis symbol: Rechecking for solution: 0 Report Id: fabd6cbe-c4a7-44ed-9ac3-f7166bb8d365 Report Status: 268435456 Hashed bucket: 1dd0260b7426beeeea55249dd5008e8f Cab Guid: 0 WER.297e2947-b1c3-4f61-b940-af707c587f6e.tmp.WERInternalMetadata.xml GHOST-CPUZ.txt

..\DynDOLOD\bugreport.txt Doesn't exist. ..\DynDOLOD\Logs\[DynDOLOD|TexGen_SSE_log.txt (truncate large log files to the entire last meaningful generation beginning with the log message "... starting session ..." ) Had left everything in there since it hadn't crashed the same way twice. Followed exact instructions. Yes, I put a date at the end, let's overlook that. ..\DynDOLOD\Logs\[DynDOLOD|TexGen_SSE_Debug_log.txt (always upload entire debug log) Did that. Doing it again. If issue involves LODGen upload/paste ..\DynDOLOD\Logs\LODGen_[TES5|ENDERAL|SSE|TES5VR|ENDERALSE]_[Worldspace]_log.txt (Doesn't exist yet) Attached my .ini in case there's something egregiously wrong in there. Did what you said, I still get to here (which is farther than I get probably 60% of the time). [00:57] Creating textures [01:15] Creating texture H:\Modding\Tools\DynDOLOD\TexGen_Output\Textures\dlc01\lod\dlc01icewalllod.dds with H:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\Render\Skyrim\Objects\dlc01\lod\dlc01icewalllod.nif I can hear the fans spin up a little, then it stalls out and eventually the screen disappears. It took longer to crash this time but I never got past this line. the TexGen_SSE_log (6-2-2023).txt is the run with your ini edit in place. TexGen_SSE.INI I know this is irritating on both ends. I appreciate you even responding at all, and I've done what I can to minimize how irritating my posts are. I could not handle 504 pages of bug reports and questions- I would lose my mind... so, yeah, thanks. TexGen_SSE_Debug_log.txt TexGen_SSE_log (6-2-2023).txt

Alright, I'm just trying to get through this while I still even want to play Skyrim again. I've done this before on v2, this is my first time with v3. I've been Googling and RTFM'ing this for 3 days and I've made what might be progress but doesn't really feel like it yet. I'm following STEP5 religiously. Step Skyrim Special Edition Guide (stepmodifications.org) Running xTexgen64 yields the attached logs. It normally gets to creating textures and simply ends abruptly without error logs or codes. I've been able to capture a couple though, so I'm hoping I can get through posting this successfully. Attached Event Viewer logs also. Attached my modlist; I'm sure I've botched something, but posting a heat log is less anxiety provoking at work than it is here, so please go easy on me. Reasonably certain I've followed the directions here. I'm past the LODgen step, which went much better after I read the manual a second time and switched to the STEP guide. I gave up completely on ever having grass, the instructions there were more than I was interested in diving into when I can't get through it without. Crash happens right there at the memory drop-off. Running from commandline as suggested in other posts launches the app correctly with no errors. I do have AV, but I went overboard potentially and created a dozen exceptions for everything here. I have PHI/CBI on this box, kinda need at least a basic security layer. It's never bothered anything else but mentioning just in case. I've seen these come up while spending over a day reading the other threads: NVIDIA bits: Please tell me what I've left out, and how I can get through this. Thanks in advance. bugreport2jun23.txt apploginfo.txt applogerror.txt modlist.xlsx