Skse trampoline h 186 failed to handle allocation request что делать

14.10.202305.07.2022 admin 0 Comments

SSE Engine Fixes

Hello just switched over from LE to SE and I have been following step by step but I get this as a code

what did I do wrong, can you help. Thanks in advance.

tortuga76 wrote: Hello just switched over from LE to SE and I have been following step by step but I get this as a code

what did I do wrong, can you help. Thanks in advance.

src\main.cpp(86): [info] Engine Fixes v5.4.1.0
src\main.cpp(89): [info] loaded config successfully
src\SKSE\Trampoline.cpp(56): [info] Default Trampoline => 0B / 2048B (00.00%)

In response to post #84547003. #84549213, #84551593, #84551948 are all replies on the same post.

I upgraded today to SKSE 2.00.19 from 2.00.18, and updated RaceMenu / Papyrus Extender.

I updated SSE Engine fixes part 1 through mod organizer 2.

Extracted d3dx9_42.dll, tbb.dll, and tbbmalloc.dll into steamapps\common\Skyrim Special Edition.

Here’s my d3dx9_42.log from steamapps\common\Skyrim Special Edition\d3dx9_42.log

Any idea on why this is happening? The error is «SKSE/Trampoline.h(186): Failed to handle allocation request»

Wolfpack49 wrote: Read through the entire 2nd sticky and make sure you have all the required apps installed.

Still getting 186. I think if I can’t figure it out, I’ll just do a fresh install again from scratch. Appreciate any help 🙂

Okay! It’s a bit late where I am, but I’ll get on that tomorrow. Appreciate the help!

edit: I rolled back to 5.3.5 and everything is working fine.
I think 5.4.1 just isn’t working for me.

In response to post #84552113. #84552188 is also a reply to the same post.

tortuga76 wrote: Hello just switched over from LE to SE and I have been following step by step but I get this as a code

what did I do wrong, can you help. Thanks in advance.

src\main.cpp(86): [info] Engine Fixes v5.4.1.0
src\main.cpp(89): [info] loaded config successfully
src\SKSE\Trampoline.cpp(56): [info] Default Trampoline => 0B / 2048B (00.00%)

Oh, eh I just made the assumption he’s having the same issue I (and apparently multiple other people) am having.

I am pretty certain I have this mod and all the files it’s dependant on installed correctly. I’m having the same issue with ‘I’m walking here’ and ‘Quick Loot RE’. All three were working perfectly until I updated to the latest version of SKSE.
All three are dependant on the address library for (unless I’m mistaken which is possible) version independence from SKSE.
All three are returning errors within vortex advising it’s likely not compatible with the version of the script extender.

Launching through SKSEVR in MO2 I get the following error and CTD

In response to post #84566498. #84566803 is also a reply to the same post.

Jacksgrin wrote: Launching through SKSEVR in MO2 I get the following error and CTD

Well thank you for the prompt reply

In response to post #84566498. #84566733 is also a reply to the same post.

Jacksgrin wrote: Launching through SKSEVR in MO2 I get the following error and CTD

Wolfpack49 wrote: Engine Fixes doesn’t work with SKSEVR, only SKSE64.

Well thank you for the prompt reply

In response to post #84549778. #84549858, #84550128, #84550628, #84550763, #84555148 are all replies on the same post.

xDrejnaughtx wrote: Literally just crashes the game on clicking on skse64 through mo2.

jtjrawlins wrote: I think it might have something to do with the ‘address library’ this is reliant on. Anything dependant on it brings up an error message in vortex after trying to start the game.

Wolfpack49 wrote: Read the entire 2nd sticky.

jtjrawlins wrote: Please clarify? As far as I can tell nothing in that post relates to this issue.

jtjrawlins wrote: Oh, eh I just made the assumption he’s having the same issue I (and apparently multiple other people) am having.

In response to post #84552113. #84552188, #84552423 are all replies on the same post.

tortuga76 wrote: Hello just switched over from LE to SE and I have been following step by step but I get this as a code

what did I do wrong, can you help. Thanks in advance.

Источник

Skse trampoline h 186 failed to handle allocation request что делать

maybe this is a lesson about not using cracked games next time.

Verify game files. Maybe there is a corrupted game file. That’s all i got for someone who try using a crack version.

If that does not work refer to this guide to see if there is anything else that may be effecting your game:
https://steamcommunity.com/sharedfiles/filedetails/?id=2266129651
Help for Skyrim SE | Modded & Vanilla (discussion thread for above)
https://steamcommunity.com/app/489830/discussions/0/2997669078628942026/
(also from pinned topic Helpful Links and References, Section 5, General Troubleshooting)

Yeah i have tried a clean reinstall and i’m still not able to create a new game

Did you delete the data folder when you did it?
I ask because I see too many cases were people see tthe guide and say «yeah, I’ve done that» without reading it.

Hello everyone I need some help with skyrim I wanted to play skyrim so i decided to search if can play it for free since it is an old game and downloaded a torrent file claiming to be skyrim so i downloaded and i couldn’t run the game anyways i decided to buy the game from steam and when i click on new game it give me that iconic skyrim cry and it immeditly crashes I searched for past three days for no avail and i asked on skyrim offical support website(Bethesdas website but that is beside the point) and i asked the skyrim Reddit for help but i tryed almost everything i found please help me (and yes I meet all the reqiuerments for skyrim and yes only skyrim is crashing I can even play cyperpunk)

There a no sites with free versions, just sites which lure you in. To download something else mostly. Run your virus scanner check for trojans.

Did you delete the data folder when you did it?
I ask because I see too many cases were people see tthe guide and say «yeah, I’ve done that» without reading it.

uhhh I didn’t create a save data(cuz I crash when i try to make one), sooo i delete the data folder then launch the game right?

yes, the data folder is where the files from mods are stored, so by deleting the data folder you get rid of any files that somehow haven’t been removed. So when you launch the game again it should be working, you can always verify the master files before you start the game to be 100% sure.

This whole post is top tier kek

yeah no it didn’t i deleted all files and reinstall the game i guess i’ll refund it

Ok, so that confirms you did the clean reinstall correctly, sorry that I stuck to that, as I say I’ve seen too many were the person said they did it but didn’t..

Also sorry that you aren’t getting anywhere, hope you the best of luck.

Источник

Please log in or register

To enjoy the benefits of Nexus Mods, please log in or register a new account

.NET Script Framework’s Common Crashes and Fixes: Online Version

GENERAL ADVICE
A key suggestion to eliminate most crashes is to MAKE A BASHED PATCH. Bashed patches help to retain certain data that could be lost from improper conflict resolution from multiple patches and mods. There are many tutorials out there on how to make one, but my favorite is by Wazalang: https://www.youtube.com/watch?v=BVn0VelT-ic. However, please skip the merged patch tutorial. There are better ways of achieving this. Bashed patches should be the FIRST thing you have before assessing your crash log as not having it paints a false picture of what is really causing one’s issue.

—————————————————————————————————————————————————————————————————-
Random Crashes
—————————————————————————————————————————-
SkyrimSE.exe+A0D789
*This is a random crash that is associated with animation mods or tweaks in ai. Advice is to look at when it occurs and target mods that you know affect this. Some people have noticed this occurs when certain dragons melee stomped with their tail(Fix on the Ultimate dragons page if used).
FIX: While the fix may vary depending on the situation of your crash, if you have DAR, then it is possible that is a load order conflict within DAR that leads to crash. Specifically, there may be another mod using the same animation folder number or overwriting animations from lower folder numbers. This can easily be fixed by changing the numbers of the folders to a much higher number(higher priority) that isn’t assigned already.

General Animation Crashes (SkyrimSE.exe+Axxxxx)
*This is essentially a general statement highlighting the idea that crash logs with this outline tend to be animation mods. The main way to deal with these crashes are to find whatever animation mod is causing the issue and deal with it accordingly.

Ultimate Dragons Stomp Crash
When combating a dragon with the Ultimate Dragons mod enabled
Stack: NiParticleSystem(Name: `CandleFlame01`) OR CandleFlame generally mentioned
*This is a known crash related to the stomping behavior and animation for Ultimate Dragons.
FIX: As stated previously, this is a known crash with an official fix. However, this fix won’t work if you regenerate Nemesis after installing. Make sure to regenerate Nemesis BEFORE updating the mod with the fix. This will unfortunately have to be done each time you regenerate Nemesis, so keep the file handy in your download tab.

(SkyrimSE.exe+67B88B) on thread xxxx!
Callstack: ‘AnimationGraphManagerHolder’ mentioned somewhere
*People have mentioned this is an animation graph crash. However, I am not really sure what this could entail besides an un-updated FNIS.esp, a broken animation, too many animations, or an improper load order. NEEDS further testing
ADVICE: Make sure to update your animation registry through FNIS or Nemesis. Many forget to do this after getting or updating an animation mod. Additionally, it is vital you enable your FNIS.esp and NOT delete it when using Nemesis. Nemesis, like FNIS, creates a plugin file which are both named FNIS.esp.

SchlongsOfSkyrim.dll+xxxx
*This can occur if you try to change your load order or eslify one of your mods with the Schlongs of Skyrim mod installed.
FIX: Load your save before the change in load order and reschlongify all your armors in the MCM. On the safe side, you can reset the mod as well. Make a save after and proceed with load order change. If you are unable to load your save prior to changing your load order, you can try hiding your schlongsofskyrim.dll file temporarily, loading your game, and proceed with the instructions stated above. Make sure you unhide your dll file right after.

nvwgf2umx.dll+xxxxxx
*This crash is associated with your NVIDIA drivers. Make sure they are up to date. If that doesn’t work, try updating your windows drivers. Some have also said this can occur if you P.C doesn’t fill out all the requirements needed to run Skyrim(P.C too weaksauce). Only assume this after trying out all stated options.

0x0 on thread xxxx
*This is usually associated with an engine issue(out of the scope of what the log could properly read). Certain mods can bring this issue to light but might not necessarily be a bad mod. This would need superb sleuthing to find the issue. So far, this has occurred with face lighting mods. Specifically, Facelight Plus has also been known to have CTDs with this issue and has been recommended to switch to a converted Oldrim version without Autoconversation-Illuminate(one without the facelight feature). Many are pointing to face illumination mods as a probable cause for this specific issue and is likely to get amended by a future update in SSE Engine Fixes!! stay tuned.

Possible relevant objects: ShadowSceneNode(Name: `shadow scene node`) BSFadeNode(Name: `skeleton.nif`) NiCamera(Name: `WorldRoot Camera`)
*This crash(AKA The Shadow Scene Crash) has been known to appear with a combination of lighting, camera, and behavior issues. People have mentioned facelight mods to also be a cause for this issue. I have had this issue numerous times in the past, however, and haven’t used a facelight at all. This issue may be resolved in a future update in SSE Engine Fixes!! stay tuned.
WORKAROUND: Simply deleting any mods with facelight could be of help as that has been a source of multiple types of CTDs in this guide so far

SkyrimSE.exe+D6DDDA
Stack: BSResource::anonymous_namespace::LooseFileStream* OR BSResource::ArchiveStream* OR BSResource::CompressedArchiveStream** mentioned somewhere
*This occurs when you don’t have enough virtual memory on your disk drive OR you have a corrupt texture amidst one of your mods. Many have tested both causes out and they appear to be indistinguishable when observing the crash log. If you think you have enough virtual memory already enabled, then the first line of action would be to sleuth out which mod texture is causing the issue. The stacks mentioned above can help you with this investigation. If it mentions LooseFileStream, it will most likely mention which texture is the corrupt one. This can help funnel down which mod is overwriting this texture. If you are having a hard time finding the mod of question, then you can search in your entire mod folder using windows file explorer to find which mod has this texture. As for the stacks ArchiveStream and CompressedArchiveStream, these refer to a BSA that may have this corrupt texture. This is a bit harder to track down, but there is method you could try attempting. If you suspect a mod of causing this crash, try extracting the BSA and see if the crash repeats with LooseFileStream mentioned rather than the previous ArchiveStream. Once you’ve tracked down which texture may be causing the issue, you can try clean disabling the mod and see if the crash repeats. If it doesn’t, then congratulations. From here, you can try cleaning the mod using CAO or disabling it in general. If it isn’t a texture issue, then you can attempt to increase your virtual memory. This can be done by increasing your pagefile size for your hard disk(Google or Bing how to increase pagefile size). I would recommend creating your pagefile on an SSD as that is significantly faster and less stuttery.

skee64.dll+xxxxx OR skse64_x_x_xx.dll
AND
Stack: Mentions XPMSEWeaponStyleScaleEffect.psc and agud_system.psc somewhere in the log
OR
Possible Relevant Objects: BGSHazard(Name: `Fire`, FormId: 00057A8C, File: `Skyrim.esm`)
*This is a known issue associated with XPMSE or a result of a heavily scripted playthrough while using autosaves or quicksaves. Even if you don’t have all geared up, this crash has been known to occur. Too much information about this bug to list here so I will refer this link: https://www.nexusmods.com/skyrimspecialedition/articles/1372
FIX: Link for fix: https://www.nexusmods.com/skyrimspecialedition/mods/44252?tab=description; Also, make sure SKSE and racemenu is up to date if you haven’t done so already.
If this doesn’t fix your issue, we can assume it is the latter(save/script issue). My prevention advice in the «Famous Crash on Save Bug» largely addresses this issue. Before that, if your game crashed on save, make sure to delete any temp files it may have created in the save folder.

Occurs when starting SKSE(Not found in the NETSCRIPT LOG but rather a popup message)
«SKSE/Trampoline.h (186): Failed to handle allocation request»
*This can occur from a poor installation of SSE engine fixes or simply from the mod organizer not reading the dll properly.
FIX: Restarting mod organizer or your PC can fix this. If it still doesn’t work, try reinstalling SSE Engine Fixes properly or Microsoft Visual C++ again.

SkyrimSE.exe+D02C2C OR SkyrimSE.exe+5999C7
Stacks: Mentions a reference to Monster Mod.esp
*Monster Mod has been known to cause numerous issues, bugs, and CTDs even with the unofficial bug fix. There have been recent updates that try its best to curb any potential crashes. Common advice also notes using the esp rather than the esm as that has not been properly updated (A good rule amongst modders is to always do a full reinstall rather than a merge when you can as a lot I can change and incompatibilities can ensue). However, I would honestly stay away until there has been all possible crashes are fixed for the time being. You have been warned.

SkyrimSE.exe+12FDD00
Probable Callstack: BSShader::unk_12FDCC0+40 mentioned FIRST or with the HIGHEST PRIORITY
*This is associated with a broken nif file. Unfortunately, it is hard to discern which mod is the issue since the log is created after the nif file has been processed. In cases like these, a broken nif can even lead to NO CRASH LOG BEING GENERATED AT ALL!!
FIX: When put in this situation, one can systematically root out the cause of the issue by disabling each mod in one’s load order and starting a new test save to replicate the issue, or running CAO(Cathedral Assets Optimizer) over all your mods. While the second option can fix the issue, it can also bring issues of its own, depending on the level of optimization you choose in CAO. Not only is the first option more accurate, but it will help others be aware of faulty meshes or nif files that plague this mods. The downside is the time it takes to deal with the issue. Therefore, I suggest disabling about 10 mods each test save from the bottom of the load order up. If you are lucky enough to know which surrounding area contains the nif file that is broken, it can be much easier to relocate to that location every save file to ensure the CTD’s appearance.

Dialogue Mods using Honed Metal
*Essentially, certain dialogue mods, most notably Your Own Thoughts or Swift Service, breaks the dialogue mechanics of Honed Metal, causing CTDs
FIX: Simply finding out which dialogue mod is causing the issue and then deleting it would suffice. I recommend switching to the new port of Honed Metal as the old SSE port is an outdated mod with missing dlls and broken scripts (The LE version, on the other hand, I also recommend). Some people have mentioned enabling tbbmalloc as true in SSE Engine Fixes as a way to fix this issue. Unfortunately, this option has since been removed.

Sacrilege and Mods that have crafting without animations
*Essentially, this CTD occurs when feeding as a vampire with Sacrilege enabled. If you were then to craft an item that doesn’t have an animation (mods like Honed Metal, Hunterborn, Campfire, etc.), a CTD occurs. EnaiSiaion describes the situation as follows: «Skyrim seems to have a bug somewhere that causes furniture activations to «remember» things from the previous animation. I imagine there would be no issue if the new furniture plays an animation of its own and overrides the memories. If it doesn’t, it may try to recall the feed animation, but it’s a paired animation and there’s no target, so it crashes.»
FIX: The Mod author has put out an update, reverting the feeding animation back to vanilla. This may fix the issue. Needs Confirmation!!

Skyrim Immersive Creatures(SIC) Pups and Cubs CTD
Possible Relevant Objects: Any Wolf Pup or known Cubs from SIC
*Essentially, this is a crash that occurs when you get near or around these little cute animals. This is a bug that has plagued both SIC and SIC official patch.
FIX: Officially, there is no fix. yet. So far, an unofficial fix has been implemented in HellLizard’s Enemy Variation Wenches(EVW) and Dynamic Customizable Soundtrack(DCS). Further discussion with the mod author points to a problem that arises from the AI packages that the pups refer to. It doesn’t work properly and causes the CTD. Reverting back to vanilla AI fixes the issue and stops it from occurring. I have had EVW since its inception and can confidently state it works, however confirmation from others would be helpful. Until an official fix is uploaded, there IS a way of doing it yourself. Simply edit all the _00LvlWolfPup, _00LvlBearCubs, and _00LvlSabreCatCubs under Non-Player Character(Actor) in xEdit by changing the Template Flag to allow Use AI packages. There should be a total of 8 entries to modify. With these changes, there is no need to turn off additional spawns. There are quite a few other crashes from this mod, so I suggest running both SIC and SIC official patches under CAO with medium optimization to fix any other issues that may arise.

Artesian Cloaks of Skyrim CTD
Stack: mentions «clothes\cloaksofskyrim\xxxx\xxx.nif» somewhere
*If you have Artesian Cloak, chances are you may have had this crash. It plagues multiple of the hdt-modified capes from Cloaks of Skyrim. It is broken and has been recognized by the author to be broken.
FIX: The author has made a patch for Cloaks of Skyrim Retextured that fixes this exact issue. You would need to have Cloaks of Skyrim Retextured, but the crash will stop happening. If you don’t want to get this retexture mod, one suggestion would be to remove the Cloaks of Skyrim patch by Artesian Cloaks of Skyrim. Another suggestion posed by a user Moosmupfel would be to duplicate a similar mesh to the cloak causing the crash and copying the appropriate texture path to the file in Nifskope.

SmoothCam.dll+xxxxx
*This is a CTD involving the mod SmoothCam. I have had this issue occasionally myself and seems to happen quite randomly.
FIX: Since this mod is a beta, there is some issues in terms of compatibility that could be worked out. My suggestion is if you are having this crash, try disabling some of the compatibilities options in the MCM. The compatibility for Improved Camera, at least for me, was the main source of this crash and unticking that patch stopped this from occurring. If you have enabled or disabled anyone of the patches in the MCM, try experimenting to see if one of them may the cause of your crash.

SkyrimSE.exe+7428B1
*This CTD seems to be caused by the Equipment Durability System mod but it is also possible for this to be attributed to other perks/spell mods that interfere or modify characters when holding weapons. Some have noted this occurs when enchanted weapon breaks. It’s also possible that this may have a conflict with another mod, but this would need further testing and input from other users.
FIX: A possible fix involving the mod SSE Engine Fixes has been posted in the comment section of this Crash Compilation and would need further testing to affirm it works.

SkyrimSE.exe+D2B923
*This is a crash that I have seen from many script logs as of late, but no known cause or fix has been found. There seems to be a bigger issue at hand, and I am hoping more people come out with this crash and what attributable scenario or action caused this CTD to occur. So far, my guess is this could be a save issue. Some have reported this to be caused by Save System Overhaul(SSO) while others who don’t have this mod has this CTD occur when going to bed using Alternate Start-LAL after creating their character(a process that ends with the creation of an autosave).

SkyrimSE.exe+12F5590
*This issue, from my experience and multiple testimonies from other members of the community, points to an unupdated facegen file for a specific NPC. Facegen issues can appear in different forms from crashing like this to complete freezing as mentioned below. This crash will be recurrent and as long as the character is present, it will crash.
FIX: The fix is as simple as regenerating the facegen file for that specific npc or the entire mod as a whole using Creation Kit. The difficult part, however, is identifying the mod in question. In Relevant Objects, it will point to a specific head attributed to a specific race. For example, BSDynamicTriShape(Name: `MaleHeadNord`) points to a Nord Male that would be causing the crash. Another method that has been called to my attention is using the HDT-SMP log file in the documents folder. At the end of the log, it will list the last npc that was loaded prior to the crash. This could be a great place to start when identifying the cause of your CTD, should you have the HDT-SMP mod. If you can identify the npc and what mod it originates from or could be affecting their appearance(assuming it is a vanilla npc), then you can use Creation Kit to regenerate the facegen. There are numerous instructions on how to regenerate facegen files on the internet, so don’t be afraid to do some research.

SkyrimSE.exe+132BEF
*This is yet another crash that, from multiple testimonies, seems to be linked with a head mesh. Similar to the crash mentioned above, a face or head mesh from an NPC is corrupted, improperly exported, or is loaded with a malignant conflict and is causing the CTD. Mods like Ordinary Women, for example, require that both the mod order(the mod pane on the left in MO2) and the load order (mod pane on the right) takes precedence when using the mod. This means both should be loaded after any other mods that modify these meshes.
FIX: The fix will vary since the cause of the head mesh corruption or conflict will differ between each mod. The first like of action would be to work out any potential mod conflicts that may arise from the modification of said head part. Like the previous crash entry, to identify which NPC is leading to the crash, simply use your HDT-SMP log located in your documents folder under Skyrim Special Edition and navigate to the bottom of the page. There it would list the name of the NPC the game tried to load but failed. Once identified, figure out which mods modify that character and reorder your load order and mod order accordingly to make sure that absolutely nothing overwrites it. Using a mod like NPC Plugin Chooser can prevent this kind of conflict from occurring as it allows you to responsibly organize the different appearance mods you have assuming you struggle doing this on your own. If it comes out to not being a conflict issue, then it may be corrupted or has not had their facegen properly regenerated through Creation Kit. If there is an update that fixes the mesh for that specific mod, you should try to obtain that first. If that fails, try manually regenerating the mod through Creation Kit. If that doesn’t work, other options would be trying to fix this yourself using CAO or any other methods you may be aware of. If all fails, best line of action would be to disable said mod until further workup is issued by mod author.

SkyrimSE.exe+C0EB6A
This can arise from Skyrim’s native memory manager acting inefficient. This has been replaced in SSE Engine Fixes with the «Use OS Allocators» patch that is part of the Memory Manager entry.
FIX: Enable MemoryManager under Patches in SSE Engine Fixes.

SkyrimSE.exe+8BDA97
*So far, this seems to occur when activating similar tweaks in SSE Engine Fixes and SSE Display Tweaks. In general, it would be a good idea to skim through what you are activating in both mods and make sure to disable one or the other if you find a conflict of interest. This conflict can lead to other issues and has shown evidence of other crashes besides the one just mentioned.

SkyrimSE.exe+5E1F22
*This crash arises before reaching the Skyrim Main menu. This is simply due to a missing master in your load order. Mod Organizer(MO) indicates when a mod has a missing master unlike Vortex, however, sometimes it can malfunction. Simply put, MO can fail to update its system that a mod is missing from the load order. Other times, MO can simply not load up the mod in question even if it is enabled in your load order.
FIX: The main thing to do is to acquire the mod that is missing and verify that it is enabled in your load order. If you have the mod and your problems still persist, try resetting or restarting MO to see if a missing master indication appears. If it doesn’t, sometimes restarting the computer does the trick.

SkyrimSE.exe+C1315C
*This crash occurs before the start menu once again and can arise from messing with the controlmap.txt file associated with the game. Many mods modify this file and it is possible for it to be formatted wrongly, or modified in a way that brings up the crash. If you modify it manually, make sure to check that certain lines are properly formatted to be read as a comment or part of the code.
—————————————————————————————————————————————————————————————————-
Complete Freeze or Hanging
———————————————————————————————————————————-
*This is described as the game freezing for an indefinite period of time with the BGM still playing and no way to move or exit the game. Only way out of this situation would be through task manager. This is a tricky issue that many in the community are still unsure what to make of it. Many have either given up or have found their own solutions to this issue. Granted, solutions and cause of freeze will differ amongst each other, and I therefore invite a conversation regarding this topic.
MY EXPERIENCE: My experience with this issue has, so far, garnered towards FACEGEN FILES that were not generated properly. Usually, this would cause blackface. However, if it is a custom npc, possibly with their own proportions or race like mine did, then this could cause a crash if files were updated but not regenerated through CK by the mod author. Unfortunately, since there is no crash log, the only way to hunt down this issue is to find an area where you can replicate the save, then proceed by disabling plugins in chunks(preferably 10 mods), until the issue doesn’t reappear.
COMMUNITY EXPERIENCE: There has been very few testimonials on what other things could cause this:
Overlay Shaders: Mods like Wet and Cold or R.A.S.S could be the cause of this issue. This could arise from a conflict issue with other mods that have a similar function or possibly the engine unable to handle multiple overlays at once. This is a topic I hope will get more addressed in the community soon.
——————
Pelagius Wing Freeze: This is a well known issue in LE that hasn’t been fixed in SE. Essentially, upon being transported into the Mad Pelagius mind, having more than a 999 count of a specific item could induce a freeze. This, of course, can be alleviated by reducing the count to a number below this. This type of freeze may also occur in situations or quests that are similar to this one in which your total inventory has to be modified (This specific theory has not been tested but should not come as a surprise if it occurs).
——————
Overclocking: This is something that can be overlooked when hunting CTDs but overclocking can reproduce this freeze. This tends to present itself with possibly a black screen before returning back to the game with a freeze and background music playing. Sometimes, a black screen may not appear and the freeze will just occur. Obviously, the best way to curb this issue is to decrease your overclock settings and test in game to see if the issue appears again. I have personally always had issues playing Skyrim with an overclocked GPU and the few times that I’ve tried would result in heavy CTDs, PC restarts, or game freezes.

——————————————————————————————————————————————————————————————————
No Crash Log
————————————————————————————————————————————
This is a problem that has plagued the community for quite sometime now and there are various, various causes that this could occur. Simply put, this CTD occurs and results in no crash log being created in the process. This CTD has been known to occur a bit differently for most people as some have described a slight 5 second freeze before crash or an abrupt and immediate crash without any forewarning.
Corrupted Nifs: I have stated previously in this compilation that corrupted nifs could result in no crash log depending on what file and how corrupted it is. This is quite unfortunate b/c you have no way of knowing if the nif is the cause or something else.
——————
Game Dimensions: Others have reported this occurring when enabling both fullscreen and windowed at the same time in the Skyrim preferences. Having BethINI prevents you from doing this, but it doesn’t hurt to check if this is something you think you might have changed manually.
——————
NPC Spawn Perk: Supposedly, this has also been attributed to this specific crash and the chance increases with larger spawns of npc. I am curious as to know what mod utilizing Spell Perk Item Distributor (SPID) could be causing this.
——————

Article information

Added on

Edited on

Written by

49 comments

0x7FF727011D51 (SkyrimSE.exe+D71D51) on thread 10788!

Hi, I just want to come forward in saying that I too am getting the Unhandled native exception occurred at 0x7FF73B2BB923 (SkyrimSE.exe+D2B923) crashes.

I have narrowed it down to the Phalanx stance animation mod ( https://www.nexusmods.com/skyrimspecialedition/mods/8598 ) as it is consistently only crashing when loading a new cell with it installed.

If any more info is wanted please feel free to let me know, thank you for all that you do.

full crash report here:

Unhandled native exception occurred at 0x7FF73B2BB923 (SkyrimSE.exe+D2B923) on thread 8344!

FrameworkName: NetScriptFramework
FrameworkVersion: 10
FrameworkArchitecture: x64
GameLibrary: SkyrimSE
GameLibraryVersion: 14
ApplicationName: SkyrimSE.exe
ApplicationVersion: 1.5.97.0
VersionInfo: Successfully loaded
Time: 12 Nov 2021 02:22:37.397

Possible relevant objects (0)
<
>

Probable callstack
<
[0] 0x7FF73B2BB923 (SkyrimSE.exe+D2B923) unk_D2B860+C3
[1] 0x7FF73B2BA3F0 (SkyrimSE.exe+D2A3F0) BSTaskManagerThread::Func1_D2A220+1D0
[2] 0x7FF73B19D6BD (SkyrimSE.exe+C0D6BD) StartAddress_0_C0D680+3D
[3] 0x7FFFEA0E7034 (KERNEL32.DLL+17034)
[4] 0x7FFFEAF22651 (ntdll.dll+52651)
>

Registers
<
AX: 0x1F0208AB376 (void*)
BX: 0x1F039B937E0 (IOManager**)
CX: 0x0 (NULL)
DX: 0x1F055324EA000 (u64):[545723683610624]
SI: 0xE60587F7B8 (void*)
DI: 0xE60587F828 (void*)
BP: 0xE60587F7E0 (void*)
SP: 0xE60587F750 (void*)
IP: 0x7FF73B2BB923 (SkyrimSE.exe+D2B923) (void*)
R8: 0xE60587F7B8 (void*)
R9: 0x7FF73BD15BB0 (SkyrimSE.exe+1785BB0) (void*)
R10: 0x7FF73D4B4001 (SkyrimSE.exe+2F24001) (void*)
R11: 0xE60587F700 (BSTaskManagerThread**)
R12: 0x0 (NULL)
R13: 0x1085BD976357 (u64):[18166597509975] (f32):[-0.07391994]
R14: 0x0 (NULL)
R15: 0x1EFF88142C0 (BSTaskManagerThread*)
Flags: 0x10206
XMM0: (double)0 / (float)0
XMM1: (double)0 / (float)0
XMM2: (double)0 / (float)0
XMM3: (double)0 / (float)0
XMM4: (double)0 / (float)0
XMM5: (double)0 / (float)0
XMM6: (double)5.30498947741318E-315 / (float)2
XMM7: (double)0 / (float)0
XMM8: (double)0 / (float)0
XMM9: (double)0 / (float)0
XMM10: (double)0 / (float)0
XMM11: (double)0 / (float)0
XMM12: (double)0 / (float)0
XMM13: (double)0 / (float)0
XMM14: (double)0 / (float)0
XMM15: (double)0 / (float)0
>

Stack
<
[SP+0] 0xFFFFFFFFFFFFFFFE (i64):[-2]
[SP+8] 0x7FF73BD15D68 (SkyrimSE.exe+1785D68) (void*)
[SP+10] 0x1EFF88142C0 (BSTaskManagerThread*)
[SP+18] 0x1EFF87CB340 (void*)
[SP+20] 0x1EFF8564400 (IOManager*)
[SP+28] 0x7FF73B2BA3F0 (SkyrimSE.exe+D2A3F0) (void*)
[SP+30] 0x1F0208AB376 (void*)
[SP+38] 0x0 (NULL)
[SP+40] 0x1F039B937E0 (IOManager**)
[SP+48] 0x1EFF87CB340 (void*)
[SP+50] 0xFFFFFFFFFFFFFFFE (i64):[-2]
[SP+58] 0x7FF73BD158C8 (SkyrimSE.exe+17858C8) (void*)
[SP+60] 0x0 (NULL)
[SP+68] 0x1FF0001FF000 (u64):[35115654705152]
[SP+70] 0xFFFFFFFFFFFFFF00 (i64):[-256]
[SP+78] 0x7FF73D4FBA30 (SkyrimSE.exe+2F6BA30) (void*)
[SP+80] 0x0 (NULL)
[SP+88] 0x0 (NULL)
[SP+90] 0x0 (NULL)
[SP+98] 0x0 (NULL)
[SP+A0] 0x0 (NULL)
[SP+A8] 0x0 (NULL)
[SP+B0] 0x0 (NULL)
[SP+B8] 0x0 (NULL)
[SP+C0] 0x0 (NULL)
[SP+C8] 0x7FF73B19D6BD (SkyrimSE.exe+C0D6BD) (void*)
[SP+D0] 0x0 (NULL)
[SP+D8] 0x0 (NULL)
[SP+E0] 0x4E20 (u16):[20000]
[SP+E8] 0x1EFF88142C0 (BSTaskManagerThread*)
[SP+F0] 0x1EFF88142C0 (BSTaskManagerThread*)
[SP+F8] 0x0 (NULL)
[SP+100] 0x0 (NULL)
[SP+108] 0x7FFFEA0E7034 (KERNEL32.DLL+17034) (void*)
[SP+110] 0x0 (NULL)
[SP+118] 0x0 (NULL)
[SP+120] 0x0 (NULL)
[SP+128] 0x0 (NULL)
[SP+130] 0x0 (NULL)
[SP+138] 0x7FFFEAF22651 (ntdll.dll+52651) (void*)
[SP+140] 0x0 (NULL)
[SP+148] 0x0 (NULL)
[SP+150] 0x0 (NULL)
[SP+158] 0x0 (NULL)
[SP+160] 0x0 (NULL)
[SP+168] 0x0 (NULL)
[SP+170] 0xEA102D6E00000000 (i64):[-1580713518737391616]
[SP+178] 0x0 (NULL)
[SP+180] 0x0 (NULL)
[SP+188] 0x7FFFE8A2C160 (KERNELBASE.dll+10C160) (void*)
[SP+190] 0xE60587E840 (void*)
[SP+198] 0xFFFC0ACBB0380001 (i64):[-1114029955743743]
[SP+1A0] 0x7FFF02B2EC0E (u64):[140733238668302]
[SP+1A8] 0xE60587E840 (void*)
[SP+1B0] 0x0 (NULL)
[SP+1B8] 0x0 (NULL)
[SP+1C0] 0x0 (NULL)
[SP+1C8] 0x0 (NULL)
[SP+1D0] 0x0 (NULL)
[SP+1D8] 0x0 (NULL)
[SP+1E0] 0x0 (NULL)
[SP+1E8] 0x0 (NULL)
[SP+1F0] 0x0 (NULL)
[SP+1F8] 0x0 (NULL)
[SP+200] 0x0 (NULL)
[SP+208] 0x0 (NULL)
[SP+210] 0x0 (NULL)
[SP+218] 0x0 (NULL)
[SP+220] 0x0 (NULL)
[SP+228] 0x0 (NULL)
[SP+230] 0x0 (NULL)
[SP+238] 0x0 (NULL)
[SP+240] 0x0 (NULL)
[SP+248] 0x0 (NULL)
[SP+250] 0x0 (NULL)
[SP+258] 0x0 (NULL)
[SP+260] 0x0 (NULL)
[SP+268] 0x0 (NULL)
[SP+270] 0x0 (NULL)
[SP+278] 0x0 (NULL)
[SP+280] 0x0 (NULL)
[SP+288] 0x0 (NULL)
[SP+290] 0x0 (NULL)
[SP+298] 0x0 (NULL)
[SP+2A0] 0x0 (NULL)
[SP+2A8] 0x0 (NULL)
[SP+2B0] 0x0 (NULL)
[SP+2B8] 0x0 (NULL)
[SP+2C0] 0x0 (NULL)
[SP+2C8] 0x0 (NULL)
[SP+2D0] 0x0 (NULL)
[SP+2D8] 0x0 (NULL)
[SP+2E0] 0x0 (NULL)
[SP+2E8] 0x0 (NULL)
[SP+2F0] 0x0 (NULL)
[SP+2F8] 0x0 (NULL)
[SP+300] 0x0 (NULL)
[SP+308] 0x0 (NULL)
[SP+310] 0x0 (NULL)
[SP+318] 0x0 (NULL)
[SP+320] 0x0 (NULL)
[SP+328] 0x0 (NULL)
[SP+330] 0x0 (NULL)
[SP+338] 0x0 (NULL)
[SP+340] 0x0 (NULL)
[SP+348] 0x0 (NULL)
[SP+350] 0x0 (NULL)
[SP+358] 0x0 (NULL)
[SP+360] 0x0 (NULL)
[SP+368] 0x0 (NULL)
[SP+370] 0x0 (NULL)
[SP+378] 0x0 (NULL)
[SP+380] 0x0 (NULL)
[SP+388] 0x0 (NULL)
[SP+390] 0x0 (NULL)
[SP+398] 0x0 (NULL)
[SP+3A0] 0x0 (NULL)
[SP+3A8] 0x0 (NULL)
[SP+3B0] 0x0 (NULL)
[SP+3B8] 0x0 (NULL)
[SP+3C0] 0x0 (NULL)
[SP+3C8] 0x0 (NULL)
[SP+3D0] 0x0 (NULL)
[SP+3D8] 0x0 (NULL)
[SP+3E0] 0x0 (NULL)
[SP+3E8] 0x0 (NULL)
[SP+3F0] 0x0 (NULL)
[SP+3F8] 0x0 (NULL)
[SP+400] 0x0 (NULL)
[SP+408] 0x0 (NULL)
[SP+410] 0x0 (NULL)
[SP+418] 0x0 (NULL)
[SP+420] 0x0 (NULL)
[SP+428] 0x0 (NULL)
[SP+430] 0x0 (NULL)
[SP+438] 0x0 (NULL)
[SP+440] 0x0 (NULL)
[SP+448] 0x0 (NULL)
[SP+450] 0x0 (NULL)
[SP+458] 0x0 (NULL)
[SP+460] 0x0 (NULL)
[SP+468] 0x0 (NULL)
[SP+470] 0x0 (NULL)
[SP+478] 0x0 (NULL)
[SP+480] 0x0 (NULL)
[SP+488] 0x0 (NULL)
[SP+490] 0x0 (NULL)
[SP+498] 0x0 (NULL)
[SP+4A0] 0x0 (NULL)
[SP+4A8] 0x0 (NULL)
[SP+4B0] 0x0 (NULL)
[SP+4B8] 0x0 (NULL)
[SP+4C0] 0x0 (NULL)
[SP+4C8] 0x0 (NULL)
[SP+4D0] 0x0 (NULL)
[SP+4D8] 0x0 (NULL)
[SP+4E0] 0x0 (NULL)
[SP+4E8] 0x0 (NULL)
[SP+4F0] 0x0 (NULL)
[SP+4F8] 0x0 (NULL)
[SP+500] 0x0 (NULL)
[SP+508] 0x0 (NULL)
[SP+510] 0x0 (NULL)
[SP+518] 0x0 (NULL)
[SP+520] 0x0 (NULL)
[SP+528] 0x0 (NULL)
[SP+530] 0x0 (NULL)
[SP+538] 0x0 (NULL)
[SP+540] 0x0 (NULL)
[SP+548] 0x0 (NULL)
[SP+550] 0x0 (NULL)
[SP+558] 0x0 (NULL)
[SP+560] 0x0 (NULL)
[SP+568] 0x0 (NULL)
[SP+570] 0x0 (NULL)
[SP+578] 0x0 (NULL)
[SP+580] 0x0 (NULL)
[SP+588] 0x0 (NULL)
[SP+590] 0x0 (NULL)
[SP+598] 0x0 (NULL)
[SP+5A0] 0x0 (NULL)
[SP+5A8] 0x0 (NULL)
[SP+5B0] 0x0 (NULL)
[SP+5B8] 0x0 (NULL)
[SP+5C0] 0x0 (NULL)
[SP+5C8] 0x0 (NULL)
[SP+5D0] 0x0 (NULL)
[SP+5D8] 0x0 (NULL)
[SP+5E0] 0x0 (NULL)
[SP+5E8] 0x0 (NULL)
[SP+5F0] 0x0 (NULL)
[SP+5F8] 0x0 (NULL)
[SP+600] 0x0 (NULL)
[SP+608] 0x0 (NULL)
[SP+610] 0x0 (NULL)
[SP+618] 0x0 (NULL)
[SP+620] 0x0 (NULL)
[SP+628] 0x0 (NULL)
[SP+630] 0x0 (NULL)
[SP+638] 0x0 (NULL)
[SP+640] 0x0 (NULL)
[SP+648] 0x0 (NULL)
[SP+650] 0x0 (NULL)
[SP+658] 0x0 (NULL)
[SP+660] 0x0 (NULL)
[SP+668] 0x0 (NULL)
[SP+670] 0x0 (NULL)
[SP+678] 0x0 (NULL)
[SP+680] 0x0 (NULL)
[SP+688] 0x0 (NULL)
[SP+690] 0x0 (NULL)
[SP+698] 0x0 (NULL)
[SP+6A0] 0x0 (NULL)
[SP+6A8] 0x0 (NULL)
[SP+6B0] 0x0 (NULL)
[SP+6B8] 0x0 (NULL)
[SP+6C0] 0x0 (NULL)
[SP+6C8] 0x0 (NULL)
[SP+6D0] 0x0 (NULL)
[SP+6D8] 0x0 (NULL)
[SP+6E0] 0x0 (NULL)
[SP+6E8] 0x0 (NULL)
[SP+6F0] 0x0 (NULL)
[SP+6F8] 0x0 (NULL)
[SP+700] 0x0 (NULL)
[SP+708] 0x0 (NULL)
[SP+710] 0x0 (NULL)
[SP+718] 0x0 (NULL)
[SP+720] 0x0 (NULL)
[SP+728] 0x0 (NULL)
[SP+730] 0x0 (NULL)
[SP+738] 0x0 (NULL)
[SP+740] 0x0 (NULL)
[SP+748] 0x0 (NULL)
[SP+750] 0x0 (NULL)
[SP+758] 0x0 (NULL)
[SP+760] 0x0 (NULL)
[SP+768] 0x0 (NULL)
[SP+770] 0x0 (NULL)
[SP+778] 0x0 (NULL)
[SP+780] 0x0 (NULL)
[SP+788] 0x0 (NULL)
[SP+790] 0x0 (NULL)
[SP+798] 0x0 (NULL)
[SP+7A0] 0x0 (NULL)
[SP+7A8] 0x0 (NULL)
[SP+7B0] 0x0 (NULL)
[SP+7B8] 0x0 (NULL)
[SP+7C0] 0x0 (NULL)
[SP+7C8] 0x0 (NULL)
[SP+7D0] 0x0 (NULL)
[SP+7D8] 0x0 (NULL)
[SP+7E0] 0x0 (NULL)
[SP+7E8] 0x0 (NULL)
[SP+7F0] 0x0 (NULL)
[SP+7F8] 0x0 (NULL)
[SP+800] 0x0 (NULL)
[SP+808] 0x0 (NULL)
[SP+810] 0x0 (NULL)
[SP+818] 0x0 (NULL)
[SP+820] 0x0 (NULL)
[SP+828] 0x0 (NULL)
[SP+830] 0x0 (NULL)
[SP+838] 0x0 (NULL)
[SP+840] 0x0 (NULL)
[SP+848] 0x0 (NULL)
[SP+850] 0x0 (NULL)
[SP+858] 0x0 (NULL)
[SP+860] 0x0 (NULL)
[SP+868] 0x0 (NULL)
[SP+870] 0x0 (NULL)
[SP+878] 0x0 (NULL)
[SP+880] 0x0 (NULL)
[SP+888] 0x0 (NULL)
[SP+890] 0x0 (NULL)
[SP+898] 0x0 (NULL)
[SP+8A0] 0x0 (NULL)
[SP+8A8] 0x0 (NULL)
>

Modules
<
SkyrimSE.exe: 0x7FF73A590000
ntdll.dll: 0x7FFFEAED0000
KERNEL32.DLL: 0x7FFFEA0D0000
KERNELBASE.dll: 0x7FFFE8920000
USER32.dll: 0x7FFFE9E00000
win32u.dll: 0x7FFFE8CE0000
GDI32.dll: 0x7FFFE9740000
gdi32full.dll: 0x7FFFE8D10000
msvcp_win.dll: 0x7FFFE85F0000
ucrtbase.dll: 0x7FFFE8820000
ADVAPI32.dll: 0x7FFFE9120000
msvcrt.dll: 0x7FFFE97E0000
sechost.dll: 0x7FFFE9CA0000
RPCRT4.dll: 0x7FFFE9340000
SHELL32.dll: 0x7FFFEA610000
ole32.dll: 0x7FFFE8FC0000
combase.dll: 0x7FFFE9930000
WS2_32.dll: 0x7FFFE9770000
SETUPAPI.dll: 0x7FFFEA190000
cfgmgr32.dll: 0x7FFFE8ED0000
bcrypt.dll: 0x7FFFE87F0000
OLEAUT32.dll: 0x7FFFE9270000
XINPUT1_3.dll: 0x400000
DINPUT8.dll: 0x7FFFBAF20000
X3DAudio1_7.dll: 0x5DDD0000
binkw64.dll: 0x7FFFD4A20000
WINHTTP.dll: 0x7FFFDF5E0000
IPHLPAPI.DLL: 0x7FFFE7A40000
steam_api64.dll: 0x5DD90000
MSVCP140.dll: 0x7FFFD0D90000
WSOCK32.dll: 0x7FFFE4420000
VCRUNTIME140.dll: 0x7FFFD0D50000
d3dx9_42.dll: 0x7FFFD49C0000
d3d11.dll: 0x180000000
HID.DLL: 0x7FFFE6EA0000
SHLWAPI.dll: 0x7FFFE9DA0000
WINMM.dll: 0x7FFFDF170000
dxgi.dll: 0x7FFFE6EE0000
dbghelp.dll: 0x7FFFDAF60000
VCRUNTIME140_1.dll: 0x7FFFD13F0000
D3DCOMPILER_43.dll: 0x7FFF85760000
d3dx11_43.dll: 0x7FFFBAED0000
CRYPTBASE.DLL: 0x7FFFE7FB0000
IMM32.DLL: 0x7FFFE90F0000
binkw64_.dll: 0x1EF5E210000
skse64_steam_loader.dll: 0x7FFFBAE90000
VERSION.dll: 0x7FFFE33A0000
windows.storage.dll: 0x7FFFE6710000
Wldp.dll: 0x7FFFE8040000
SHCORE.dll: 0x7FFFE94D0000
profapi.dll: 0x7FFFE8530000
inputhost.dll: 0x7FFFD1C00000
CoreMessaging.dll: 0x7FFFE5C10000
PROPSYS.dll: 0x7FFFE3C20000
wintypes.dll: 0x7FFFE51E0000
bcryptPrimitives.dll: 0x7FFFE8BF0000
CoreUIComponents.dll: 0x7FFFE58B0000
ntmarta.dll: 0x7FFFE7400000
kernel.appcore.dll: 0x7FFFE6510000
usvfs_x64.dll: 0x7FFF99B40000
steamclient64.dll: 0x7FFF70380000
CRYPT32.dll: 0x7FFFE8690000
imagehlp.dll: 0x7FFFE91D0000
PSAPI.DLL: 0x7FFFE9C90000
tier0_s64.dll: 0x7FFF71E90000
vstdlib_s64.dll: 0x7FFFB7EC0000
MSWSOCK.dll: 0x7FFFE7DA0000
Secur32.dll: 0x7FFFD1880000
SSPICLI.DLL: 0x7FFFE84B0000
EngineFixes.dll: 0x7FFFB4990000
tbb.dll: 0x7FFFB7E50000
tbbmalloc.dll: 0x7FFF85420000
NetScriptFramework.Runtime.dll: 0x7FFF9FC10000
mscoree.dll: 0x7FFFCFEB0000
mscoreei.dll: 0x7FFFCFE00000
clr.dll: 0x7FFFCF330000
VCRUNTIME140_CLR0400.dll: 0x7FFFD0110000
ucrtbase_clr0400.dll: 0x7FFFCF270000
mscorlib.ni.dll: 0x7FFFCDBA0000
clrjit.dll: 0x7FFFCD760000
amsi.dll: 0x7FFFDE900000
System.ni.dll: 0x7FFFCA500000
System.Core.ni.dll: 0x7FFFC5970000
urlmon.dll: 0x7FFFDCD80000
iertutil.dll: 0x7FFFDCAA0000
srvcli.dll: 0x7FFFDCD50000
netutils.dll: 0x7FFFE7A80000
NetScriptFramework.SkyrimSE.dll: 0x7FFF70260000
skse64_1_5_97.dll: 0x1EF6C000000
AHZmoreHUDInventory.dll: 0x7FFF74720000
BetterJumpingSE.dll: 0x7FFF853C0000
ClassicSprinting.dll: 0x7FFF7B6D0000
ConsoleUtilSSE.dll: 0x1EF699D0000
DisplayEnemyLevel.dll: 0x7FFF746B0000
DynamicAnimationReplacer.dll: 0x1EF73440000
ENBHelperSE.dll: 0x1EF734B0000
Fuz Ro D’oh.dll: 0x1EF73540000
iEquipUtil.dll: 0x1EF735B0000
ImprovedCamera.dll: 0x1EF74250000
InsertAttackData.dll: 0x1EF742C0000
JContainers64.dll: 0x1EF74BB0000
MaxsuCombatEscape.dll: 0x7FFF6FC50000
MaxsuPowerAttackControl.dll: 0x7FFF6FC00000
mfgfix.dll: 0x7FFF6FB40000
MoreInformativeConsole.dll: 0x7FFF6FAD0000
PapyrusUtil.dll: 0x7FFF6F950000
PassiveWeaponEnchantmentRecharging.dll: 0x1EF74A10000
po3_FEC.dll: 0x7FFF6F8A0000
po3_PapyrusExtender.dll: 0x7FFF6F740000
po3_SpellPerkItemDistributor.dll: 0x7FFF6F6D0000
Pronouns64.dll: 0x7FFFB4960000
ShaderTools.dll: 0x7FFF6F630000
D3DCOMPILER_47.dll: 0x7FFF6F1D0000
SimplyKnock.dll: 0x7FFF85730000
skee64.dll: 0x7FFF6EFE0000
SkyrimSoulsRE.dll: 0x7FFF6EF50000
SmoothCam.dll: 0x7FFF6EE20000
SSEDisplayTweaks.dll: 0x7FFF6ED00000
StayAtSystemPageSE.dll: 0x7FFF6EC70000
SurvivalControlPanel.dll: 0x7FFF6EC00000
to_your_face.dll: 0x1EF74B30000
UltimateCombat.dll: 0x7FFF6EBC0000
YesImSure.dll: 0x7FFF6EB10000
zxlice’s ultimate potion animation.dll: 0x7FFF6EAC0000
uxtheme.dll: 0x7FFFE5F90000
gameoverlayrenderer64.dll: 0x7FFF6E8E0000
MSCTF.dll: 0x7FFFE9FB0000
textinputframework.dll: 0x7FFFD2DD0000
d3dcompiler_46e.dll: 0x7FFF6DA40000
d3d11.dll: 0x7FFFE49B0000
nvldumdx.dll: 0x7FFFDE200000
msasn1.dll: 0x7FFFE81D0000
cryptnet.dll: 0x7FFFE1E50000
drvstore.dll: 0x7FFFDFDD0000
devobj.dll: 0x7FFFE8390000
WINTRUST.DLL: 0x1EF4ED70000
CRYPTSP.dll: 0x7FFFE7F90000
rsaenh.dll: 0x7FFFE76B0000
nvwgf2umx.dll: 0x7FFF5BFA0000
nvspcap64.dll: 0x7FFFA0BF0000
NvCamera64.dll: 0x7FFF6D1D0000
XINPUT9_1_0.dll: 0x7FFFE00F0000
WindowsCodecs.dll: 0x7FFFE2880000
dxcore.dll: 0x7FFFE01F0000
d3dcompiler_47_64.dll: 0x7FFF6C0D0000
nvapi64.dll: 0x7FFFCC990000
dcomp.dll: 0x7FFFE5340000
dwmapi.dll: 0x7FFFE6220000
clbcatq.dll: 0x7FFFE9880000
MMDevApi.dll: 0x7FFFE2110000
AUDIOSES.DLL: 0x7FFFE21A0000
powrprof.dll: 0x7FFFE7BB0000
UMPDC.dll: 0x7FFFE7A20000
Windows.UI.dll: 0x7FFFC6750000
WindowManagementAPI.dll: 0x7FFFE2EF0000
twinapi.appcore.dll: 0x7FFFE2BF0000
MessageBus.dll: 0x7FFFBA110000
NSI.dll: 0x7FFFE8F20000
dhcpcsvc.DLL: 0x7FFFE33D0000
XAudio2_7.dll: 0x7FFF6E5E0000
resourcepolicyclient.dll: 0x7FFFE6120000
avrt.dll: 0x7FFFE3470000
DSOUND.DLL: 0x7FFFC8CA0000
winmmbase.dll: 0x7FFFD0130000
wbemprox.dll: 0x7FFFDAB10000
wbemcomn.dll: 0x7FFFDAA50000
wbemsvc.dll: 0x7FFFDE9F0000
fastprox.dll: 0x7FFFDEA90000
dhcpcsvc6.DLL: 0x7FFFE2600000
DNSAPI.dll: 0x7FFFE7A90000
webio.dll: 0x7FFFDEF30000
WINNSI.DLL: 0x7FFFE3460000
rasadhlp.dll: 0x7FFFDEF20000
fwpuclnt.dll: 0x7FFFDF090000
schannel.DLL: 0x7FFFE75D0000
mskeyprotect.dll: 0x7FFFD16F0000
NTASN1.dll: 0x7FFFE8070000
ncrypt.dll: 0x7FFFE80B0000
ncryptsslp.dll: 0x7FFFD1850000
DPAPI.DLL: 0x7FFFE83D0000
>

Plugins (2)
<
bug_fixes
<
Name: «Bug Fixes SSE»
Version: 3
Author: «meh321»
Assembly: BugFixesSSE, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
>

grasscontrol
<
Name: «Grass Control»
Version: 6
Author: «meh321»
Assembly: GrassControl, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
>
>

Источник

Портал agro-sss.ru

Skse trampoline h 186 failed to handle allocation request что делать

SSE Engine Fixes

Skse trampoline h 186 failed to handle allocation request что делать

Please log in or register

.NET Script Framework’s Common Crashes and Fixes: Online Version