Skyrim BEX Crash Solutions (WIP)

[ElmoTheMuppet]

Hi, I want to share some tips that can help reduce or possibly eliminate the BEX event crashes experienced by some users.

One or more of the solutions below may solve some of the AppHangB1 type crashes.

 

Problem signature:
Problem Event Name: BEX
Application Name: TESV.exe
Application Version: 1.9.32.0
Application Timestamp: 51437ce5
Fault Module Name: TESV.exe
Fault Module Version: 1.9.32.0
Fault Module Timestamp: 51437ce5
Exception Offset: 00b53759
Exception Code: c0000417
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.48

-------------------------------------------------

The solutions that I'm posting have been tested in the following environment:

.Game: Skyrim Legendary Edition (Steam Purchased)

.Operating System used: Windows 7 Pro 64bit (Aero Enabled)

.CPU used: i7 4790k

.Graphics Card used: Nvidia GTX 970

.RAM capacity: 8GB

.Number of Monitors: 2 (Gaming only on primary monitor)

.Location of Steam games (Including Skyrim) directory: Installed outside of Program Files directory (Separate drive)

.Mod Manager used: Mod Organizer

.Video Mode used: Borderless Fullscreen (aka Fullscreen Windowed)

.ENB used: ENBoost only

.Sheson Memory Patch Method: SSME

.SKSE is installed (Memory Patch disabled)

 

*Note*

Here are the executables I use often with Skyrim: ModOrganizer.exe , skse_loader.exe , TESV.exe , SkyrimLauncher.exe , enbhost.exe , LOOT.exe

- none of these executables are running in compatibility mode for an older operating system or environment settings.

- During the testing, there were times where I had difficulty to reproduce the crash, so I had OBS running in the background to increase those occurrences(via x264 encoding stress on CPU).

 

Possible Solutions:

1. This solution has been posted before by other users: Add TESV.exe to DEP (Data Execution Prevention) exclusion list.

- Click on Start Menu -> Right click on Computer --> Click on Properties --> Click on Advanced system settings --> Click on "Advanced" tab --> Under "Performance" click on Settings --> Click on "Data Execution Prevention" tab --> Select "Turn on DEP for all programs and services except those I select" --> Then add TESV.exe to the list.

- Since I was desperate, I tried to add all the executables I can find within the Skyrim directory to the list (enbhost.exe etc. but some of them can't be added).

 

2. Since my Steam Games library was installed on a separate drive, there is no need to run the executables as an administrator.

- I had to remove those privileges from ModOrganizer.exe , TESV.exe, skse_loader.exe, SkyrimLauncher.exe, enbhost.exe.

- If you need to troubleshoot with administrative privileges, go ahead. Just remember to revert back when you're finished, or leave it as it is, if it's working properly.

 

3. I recommend adding your Steam Games Library (Skyrim included) to your antivirus exceptions/ignore list.

 

4. You should use Sheson Memory Patch.

- If you're not an SKSE user, install SSME.

- If you're an SKSE user, you can activate the Sheson Memory Patch via an SKSE.ini.

- If you're an SKSE user and you don't like SKSE.ini method, install SSME.

 

5. Double check your Plugin Load Order and your Mod Install Order.

- LOOT is great at sorting Load Order, but there maybe times where a mod plugin may not be in the best place. Make sure to read mod description for proper load order.

- Certain mods like HDT Physics and XPMSE (Skeleton Mod) should be installed carefully:

# Install Order:

first .SKSE

..... .HDT Physics Extension

..... .Body type (Example: CBBE)

last .Skeleton (Example: XPMSE)

------------------------------------------

.Example Install Order:

https://i.imgur.com/q6Q5GHt.png

.Example Install Order (other mods installed):

https://i.imgur.com/mq24zov.png

 

6. Disable any overlay programs or screen capture app. (Example: Nvidia Shadowplay, Bandicam, XSplit, Fraps, MSI Afterburner, OpenBroadcasterSoftware)

 

7. Update your graphics driver or Directx End-user Runtime

 

8. Don't pirate.

 

9. A corrupted file, save or mod. *Edit*

- There is a chance that while you were attempting to download files or mods, the quality of the connection between you and the server may have messed up your download.

Sometimes it isn't the connection. The server that was hosting your file may have experienced physical damage to their hardware, or some software related issue that lead to the corruption of the hosted file(s).

You may need to re-download your file from a different server location, and possibly avoid your mod manager's download manager, just in case.

 

10. Playing with a controller / gamepad / XBox 360 controller connected to a faulty USB port.

- Try disconnecting your controller / gamepad from your computer, or connect it to a different USB port (a USB port closer to the motherboard maybe preferable).

 

11. Your INI files may have been edited incorrectly.

- Backup your Skyrim.ini and SkyrimPrefs.ini (located in Documents/My Games/Skyrim/)

- Make sure both Skyrim.ini and SkyrimPrefs.ini are no longer in Documents/My Games/Skyrim/ .

- Run the Skyrim Launcher and it will regenerate new Skyrim.ini and SkyrimPrefs.ini files.

 

 

12. There maybe some errors occurring silently in the background while your trying to play.

- Click on the Start menu and type the following into the search box: Event Viewer

- Press Enter

- Maximize the Event Viewer window so you can see everything clearly.

- Near the top, look at the section that looks like the following: http://i.imgur.com/x6F6Zkn.png

Event Type

+Critical

+Error

+Warning

- You want to start from top to bottom: Critical --> Error --> Warning

- If your computer ever shut off during a power outage, it will be logged in the Critical section.

- BEX or AppHangB1 type crashes will be logged in the Error section.

Picture A: http://i.imgur.com/M2dVUS8.png

Picture B: http://i.imgur.com/bORmg2t.png

- In Picture B, if you go through the list, you will find other errors and some of them may not mention TESV.exe.

- However, you may find that those other errors are occurring around the time of your crashes.

Picture C: http://i.imgur.com/9sKm1P0.png

- In my case, Picture C shows the culprit of most of my crashes. igfxCUIService.exe was looking for my CPU's integrated graphics but failed due to the integrated graphics being disabled in my BIOS.

- Your situation may be different, but keep an eye on the Event Viewer as it may be the key to solving some of your weird crashes.

 

This topic is work in progress. If you come across any other solutions, post them here.

To be continued...

Edited October 7, 2015 by ElmoTheMuppet

[ElmoTheMuppet]

9. A corrupted file, save or mod.

- There is a chance that while you were attempting to download files or mods, the quality of the connection between you and the server may have messed up your download.

Sometimes it isn't the connection. The server that was hosting your file may have experienced physical damage to their hardware, or some software related issue that lead to the corruption of the hosted file(s).

You may need to re-download your file from a different server location, and possibly avoid your mod manager's download manager, just in case.

[ElmoTheMuppet]

10. Playing with a controller / gamepad / XBox 360 controller connected to a faulty USB port.

- Try disconnecting your controller / gamepad from your computer, or connect it to a different USB port (a USB port closer to the motherboard maybe preferable).

[ElmoTheMuppet]

11. Your INI files may have been edited incorrectly.

- Backup your Skyrim.ini and SkyrimPrefs.ini (located in Documents/My Games/Skyrim/)

- Make sure both Skyrim.ini and SkyrimPrefs.ini are no longer in Documents/My Games/Skyrim/ .

- Run the Skyrim Launcher and it will regenerate new Skyrim.ini and SkyrimPrefs.ini files.

 

 

12. There maybe some errors occurring silently in the background while your trying to play.

- Click on the Start menu and type the following into the search box: Event Viewer

- Press Enter

- Maximize the Event Viewer window so you can see everything clearly.

- Near the top, look at the section that looks like the following: http://i.imgur.com/x6F6Zkn.png

Event Type

+Critical

+Error

+Warning

- You want to start from top to bottom: Critical --> Error --> Warning

- If your computer ever shut off during a power outage, it will be logged in the Critical section.

- BEX or AppHangB1 type crashes will be logged in the Error section.

Picture A: http://i.imgur.com/M2dVUS8.png

Picture B: http://i.imgur.com/bORmg2t.png

- In Picture B, if you go through the list, you will find other errors and some of them may not mention TESV.exe.

- However, you may find that those other errors are occurring around the time of your crashes.

Picture C: http://i.imgur.com/9sKm1P0.png

- In my case, Picture C shows the culprit of most of my crashes. igfxCUIService.exe was looking for my CPU's integrated graphics but failed due to the integrated graphics being disabled in my BIOS.

- Your situation may be different, but keep an eye on the Event Viewer as it may be the key to solving some of your weird crashes.

 

[imagesetal]

***UPDATE 19/04***

 

Hi everyone,

 

After running the game without "Continue Game No Crash" I remember why I tried it in the first place, the crashing around Markarth is a big problem if you don't use this mod. Also I somehow got a single BEX Error after removing it so it isn't fully responsible. Strange thing is, whatever I've done since uninstalling or removing the mod, it's reinstalled and the BEX crashes haven't returned, not sure if it's the order you install stuff, or something else I tried.

 

I'm sure creating a mod to try and patch some Oldrim crashing isn't easy, and I don't want anyone to get the wrong idea and not try "Continue Game No Crash" so I'm updating you all that I'm back to using it. My current set-up is this, and *SEEMS* the most stable on my hardware...

 

Relevant Mods:

"SKSE ini pre-download for lazy users - INI settings"

"Continue Game No Crash"

"OneTweak"

 

(NOT USING Safety Load or Stable uGrids to Load)

 

 

Relevant enblocal.ini Settings: (only when different from ENBoost v6.1)

ExpandSystemMemoryX64=false

DataSyncMode=0

PriorityMode=3

EnableVSync=true

Relevant Crash Fixes' crashfixplugin.ini:

UseOSAllocators=0

AlignHeapAllocate=0

Hopefully you can start with settings similar to these to obtain a relatively stable Oldrim set-up. Not sure what was affecting "Continue Game No Crash" before or if somehow removing and reinstalling it has helped my earlier issues, but seems to be working as intended now.

Cheers,

David :-)

 

 

 

 

 

 

 

Hi everyone,

 

I came across a very strange BEX error. It would ONLY affect the game while it was loading, if it got in never seen another BEX error and very few crashes overall (less than 1 every 6 - 7 hours). Am running a very heavily modified game (200+ mods) and recently switched from an AMD setup (Core i7-3770k, 16GB RAM, AMD R9 390X with 8GB VRAM, Windows 7) where I never once saw a BEX error, even with the same mods.

 

I tried Safety Load, SKSE Memory Patch, Crash Fixes (v.11) Memory Patch and various other things to try fixing it. I also tried ENBoost alone and with NVLA ENB enabled. It would generally always crash the first time I tried to load a game, and the majority of the time load fine the second time. It seemed to be getting worse though, either with getting further into the playthrough or with the save game getting larger. I tried Save Game Cleaner as well.

 

It got to the point where I might have to try loading the game 4 or 5 times in a row before it would eventually go. Finally I traced it back to a mod called "CONTINUE GAME NO CRASH". I'd been using it on my AMD system for something and have never any problems then. Since removing this mod the regular crashing (it is Oldrim after all, although the crashes are very rare now) doesn't seem to be any worse and the game loads perfectly now, no BEX errors since. I'll append the appropriate information below, but hopefully that helps others with the same issue, however rare it may be. :-)

 

 

Current Hardware:

Windows 7 with DEP Disabled at Boot

Asus ROG Z270F Motherboard

Intel Core i7-7700k at 4.2GHz (Not Overclocked)

32GB Corsair RAM at 3200MHz (Not Overclocked)

Asus ROG GeForce 1080 with 8GB RAM

 

Latest nVidia Drivers (381.65 at time of writing)

Antivirus and Windows Defender Disabled while Playing

Steam Overlay Disabled

nVidia Shadowplay Disabled

LOOT Run Every Time I Change a Mod

 

 

Relevant enblocal.ini Fields:

[MEMORY]

ExpandSystemMemoryX64=false

ReduceSystemMemoryUsage=true

DisableDriverMemoryManager=false

DisablePreloadToVRAM=false

EnableUnsafeMemoryHacks=false

ReservedMemorySizeMb=384

VideoMemorySizeMb=23990

EnableCompression=false

AutodetectVideoMemorySize=false

[THREADS]

DataSyncMode=0

PriorityMode=3

EnableUnsafeFixes=false

[WINDOW]

ForceBorderless=false

ForceBorderlessFullscreen=false

Mods I've learned to Avoid (the hard way):

SkyBirds/Birds of Skyrim/Birds and Flocks (especially Birds and Flocks seems broken)

Wet and Cold (never attributed directly to any crashes in fairness, but huge strain on the Papyrus Scripting Engine)

Footprints (similar to Wet and Cold, but this one I do think caused more crashes)

Locational Damage/Stable uGrids to Load/Immersive Beds/Deadly Spells Impacts (all either Obsolete, Resource Hogs or Broken)

Thanks for Reading,

Good Luck Getting Stability until SKSE64 is Released.

Don't Give Up, Heavily Modded Oldrim can run almost 10 hours without a crash, even on older hardware (my laptop only has GTX 760M)

[biper87]

In my case (I'm using SKSE.ini, hdt and about 170 mods and still have some crashes) sometimes help SaveTool. Open your save and reset Havok