Hakuna_Matata Posted November 20, 2021 Posted November 20, 2021 I keep getting sudden CTDs when entering areas with falmer, but only when I'm at higher levels. How do you debug something like that? I tried turning off all falmer and dwemer in creature framework but that did not help. Now I realize that the .NET framework plugin writes semi-useful crash logs, and it says this: Unhandled native exception occurred at 0x7FF974A55181 (XAudio2_7.dll+25181) on thread 11640! Possible relevant objects (1) { [ 44] BSFadeNode(Name: `skeleton.nif`, Owner: `Character(FormId: 00065146, File: `Skyrim.esm`, BaseForm: TESNPC(Name: `Falmer Warmonger`, FormId: FF002FFC))`) } Probable callstack { [0] 0x7FF974A55181 (XAudio2_7.dll+25181) [1] 0x21FB80F5C0 } Turns out apparently Skyrim does not use ASLR and when I google this address and offset I find a mention here in a thread that says I don't have permission to see. So I'm hoping one of you will recognize the problem and can suggest something I can try. The Falmer Warmonger message matches my observations but could be a fluke. How would the skeleton be related to an audio DLL?
Hakuna_Matata Posted November 20, 2021 Author Posted November 20, 2021 Hmm so it turns out I had a data\meshes\actors\falmer\character assets\skeleton.nif and skeleton.hkx. I think they came from XPMSE. I moved them away and my crash went away. Might be a fluke but the game hasn't crashed since.
Hakuna_Matata Posted December 22, 2021 Author Posted December 22, 2021 (edited) Turns out that was not from XPMSE but from More Nasty Critters. I'm also getting the crash when entering a Vigilant area with scamps in it. They appear to be based on falmer. Edited December 22, 2021 by Hakuna_Matata
RamonXick Posted May 31, 2022 Posted May 31, 2022 I'm also got the same log Unhandled native exception occurred at 0x7FFFD5C45181 (XAudio2_7.dll+25181) on thread 15232! FrameworkName: NetScriptFramework FrameworkVersion: 15 FrameworkArchitecture: x64 GameLibrary: SkyrimSE GameLibraryVersion: 18 ApplicationName: SkyrimSE.exe ApplicationVersion: 1.5.97.0 VersionInfo: Successfully loaded Time: 31 May 2022 14:46:10.438 Possible relevant objects (0) { } any idea how to fix this? the only solution for me is to rename XAudio2_7.dll but skyrim has no sound
Inga Rasen Posted May 31, 2022 Posted May 31, 2022 Did you tried to reinstall xp32? Overwrite everything. Can you post the entire NSF crash log?
RamonXick Posted June 18, 2022 Posted June 18, 2022 (edited) CTD almost specific to AE dungeons, like daedric realm and new tiles added by the cause CC got two recurring CTD error Spoiler Unhandled native exception occurred at 0x7FF69342FF43 (SkyrimSE.exe+BFFF43) on thread 24048! FrameworkName: NetScriptFramework FrameworkVersion: 15 FrameworkArchitecture: x64 GameLibrary: SkyrimSE GameLibraryVersion: 18 ApplicationName: SkyrimSE.exe ApplicationVersion: 1.5.97.0 VersionInfo: Successfully loaded Time: 05 Jun 2022 17:50:14.987 Possible relevant objects (0) { } Probable callstack { [0] 0x7FF69342FF43 (SkyrimSE.exe+BFFF43) BSXAudio2DataSrc::unk_BFFF10+33 [1] 0x7FF69342D7DA (SkyrimSE.exe+BFD7DA) BSXAudio2GameSound::Func11_BFD780+5A [2] 0x7FF69341E075 (SkyrimSE.exe+BEE075) unk_BEDEE0+195 [3] 0x7FF693423325 (SkyrimSE.exe+BF3325) unk_BF3270+B5 [4] 0x7FF693424BF0 (SkyrimSE.exe+BF4BF0) BSAudioManagerThread::Func1_BF4B80+70 [5] 0x7FF69343D6BD (SkyrimSE.exe+C0D6BD) StartAddress_0_C0D680+3D [6] 0x7FFFDA14244D (KERNEL32.DLL+1244D) [7] 0x7FFFDB24DF88 (ntdll.dll+5DF88) } and Spoiler Unhandled native exception occurred at 0x7FFFDB745181 (XAudio2_7.dll+25181) on thread 7480! FrameworkName: NetScriptFramework FrameworkVersion: 15 FrameworkArchitecture: x64 GameLibrary: SkyrimSE GameLibraryVersion: 18 ApplicationName: SkyrimSE.exe ApplicationVersion: 1.5.97.0 VersionInfo: Successfully loaded Time: 31 May 2022 13:32:14.527 Possible relevant objects (0) { } Probable callstack { [0] 0x7FFFDB745181 (XAudio2_7.dll+25181) [1] 0x4016CBE4C016CBE4 [2] 0x3FC90FDBBFC90FDB [3] 0x3F490FDBBF490FDB [4] 0xC016CBE400000000 [5] 0xBFC90FDB4016CBE4 [6] 0x7FF63FC90FDB [7] 0x24C017C7F60 [8] 0x24C017C7F60 } Edited June 18, 2022 by RamonXick
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now