Jump to content
IGNORED

Random Crash To Desktop (CTD) - Might be HDT-related


Alan47

Recommended Posts

Hello everyone,

 

I'm in the Skyrim modding community for quite a while now. I'm using Mod Organizer and LOOT to keep everything nice and clean, and *most* of the time, Skyrim runs without trouble. As of late, I sometimes randomly crash to desktop (without any error message, of course), so I started to look for the cause. I don't know if every crash has the same cause, but my hdtSkyrimMemPatch.log file tells me the following about my latest crash:

 

hdtSkyrimMemPatch
[07/05/14 16:57:32]INFO: Queue OK
[07/05/14 16:57:32]INFO: SKSEPlugin_Load
[07/05/14 17:33:18]ERROR: Fatal error occured
[07/05/14 17:33:18]ERROR: Code : 0xc0000005
[07/05/14 17:33:18]ERROR: Flag : 0x00000000
[07/05/14 17:33:18]ERROR: Module : 
[07/05/14 17:33:18]ERROR: Address : 0x004d4eb9
[07/05/14 17:33:18]ERROR: Module Address : 0x77c0bc60
[07/05/14 17:33:18]ERROR: AccessViolation, try to read 0x00000074 failed
[07/05/14 17:33:18]ERROR: Call Stack (Skyrim ignored the frame pointer register (ebp) so it may not correct) :
[07/05/14 17:33:18]ERROR: TESV : 0x004d4eb9
[07/05/14 17:33:18]ERROR: Thread local Havok memory heap:
[07/05/14 17:33:18]ERROR: Temp memory allocator:0x01bb1314
[07/05/14 17:33:18]ERROR: Temp memory allocated:-1
[07/05/14 17:33:18]ERROR: Temp memory in used:-1
[07/05/14 17:33:18]ERROR: Temp memory available:0
[07/05/14 17:33:18]ERROR: Temp memory total available:-1
[07/05/14 17:33:18]ERROR: Temp memory largest block:-1
[07/05/14 17:33:18]ERROR: Heap memory allocator:0x01bb1314
[07/05/14 17:33:18]ERROR: Heap memory allocated:-1
[07/05/14 17:33:18]ERROR: Heap memory in used:-1
[07/05/14 17:33:18]ERROR: Heap memory available:0
[07/05/14 17:33:18]ERROR: Heap memory total available:-1
[07/05/14 17:33:18]ERROR: Heap memory largest block:-1
[07/05/14 17:33:18]ERROR: Debug memory allocator:0x01bb1314
[07/05/14 17:33:18]ERROR: Debug memory allocated:-1
[07/05/14 17:33:18]ERROR: Debug memory in used:-1
[07/05/14 17:33:18]ERROR: Debug memory available:0
[07/05/14 17:33:18]ERROR: Debug memory total available:-1
[07/05/14 17:33:18]ERROR: Debug memory largest block:-1
[07/05/14 17:33:18]ERROR: Solver memory allocator:0x01bb1314
[07/05/14 17:33:18]ERROR: Solver memory allocated:-1
[07/05/14 17:33:18]ERROR: Solver memory in used:-1
[07/05/14 17:33:18]ERROR: Solver memory available:0
[07/05/14 17:33:18]ERROR: Solver memory total available:-1
[07/05/14 17:33:18]ERROR: Solver memory largest block:-1
[07/05/14 17:33:19]ERROR: Minidump saved in hdtSkyrimMemPatch.dmp
 
 
Even though I am a programmer myself, I find it hard to read this info. Basically it's an access violation error (a wrong pointer somewhere) that occurred in an Havok thread. I couldn't find much information about this particular address 0x00000074, other than that it seems to be some kind of command register.
 
Anyone got any idea how to fix this? I'm using HDT PE version 14.28. This crash happened randomly when walking around, nothing special happened in-game as far as I could tell (i.e. no level change, no costume change etc.). My skeleton is groovtama's from the LL download page.
 
 
Thanks,
 
 
Alan
Link to comment
  • 1 month later...
Guest Mogie56

NULL or 0 is reserved for the OS

0xC0000005 is the error code designation for an Access Violation. 0x00000000 is the location that it tried to read (this is our NULL value!). And, 0x77c0bc60 is the arbitrary memory location where SKSEPlugin_Load happened to be running at the time of the crash.

Link to comment

I get that error sometimes. I think it is due to skyrim running out in its memory block. If they did what some did and made a 64 bit exe it would fix the problem 100%. Also I did a fresh run a month back with little to no mods no texture packs. Basic barebones with all dlc's and some armor mods. It ran flawless. The thing it seems to me is skyrim can't keep up cause it being 32 bit.   I could be wrong but try using other mods that has lesser resolution formats and try not to overload your v-ram. It should even out from there. Skyrim is running on a stripped down version of the fallout 3 engine if i'm not mistaken to. So we all remember how bad that engine had flaws.

 

Hope this helps in some way,

 

Tasadeus

Link to comment

Hey guys,

 

thanks for the hints. I'll try to change my memory settings in enblocal.ini down a bit. It happens rarely enough, but when it does, depending on the situation, it can potentially wipe out quite some progress in the game, which makes it annoying. Unfortunately there is no fast way for me to check if a solution works (as the bug appears rarely to begin with).

 

Thanks,

 

 

Alan

Link to comment

Use Notepad,

[General]

ClearInvalidRegistrations=1

[Memory]

DefaultHeapInitialAllocMB=768

ScrapHeapSizeMB=256

[Display]

iTintTextureResolution=2048

 

Place the SKSE.ini in Skyrim\Data\SKSE

The whatsnew Readme in SKSE covers what this does, and lists the default values, I changed the DefaultHeapInitialAllocMB from 512 to 768. The change doubles the Vanilla Memory Block size from 256 to 512 and helps to stop Infinite Loading Screens and greatly reduce Crashes To Desktop.

You can also read about it on the SKSE Thread in the Bethsoft Forums. Shesons Memory Patch led to the features being added to SKSE by an ini.

 

 

Link to comment

Use Notepad,

[General]

ClearInvalidRegistrations=1

[Memory]

DefaultHeapInitialAllocMB=768

ScrapHeapSizeMB=256

[Display]

iTintTextureResolution=2048

 

Place the SKSE.ini in Skyrim\Data\SKSE

The whatsnew Readme in SKSE covers what this does, and lists the default values, I changed the DefaultHeapInitialAllocMB from 512 to 768. The change doubles the Vanilla Memory Block size from 256 to 512 and helps to stop Infinite Loading Screens and greatly reduce Crashes To Desktop.

You can also read about it on the SKSE Thread in the Bethsoft Forums. Shesons Memory Patch led to the features being added to SKSE by an ini.

 

What she said

 

If you search the Boris Thread over at Nexus or the ENB home page, you'll likely find your error is directly due to memory running out and well access denied man no more for you.

 

Link to comment

 

Use Notepad,

[General]

ClearInvalidRegistrations=1

[Memory]

DefaultHeapInitialAllocMB=768

ScrapHeapSizeMB=256

[Display]

iTintTextureResolution=2048

 

Place the SKSE.ini in Skyrim\Data\SKSE

The whatsnew Readme in SKSE covers what this does, and lists the default values, I changed the DefaultHeapInitialAllocMB from 512 to 768. The change doubles the Vanilla Memory Block size from 256 to 512 and helps to stop Infinite Loading Screens and greatly reduce Crashes To Desktop.

You can also read about it on the SKSE Thread in the Bethsoft Forums. Shesons Memory Patch led to the features being added to SKSE by an ini.

 

What she said

 

If you search the Boris Thread over at Nexus or the ENB home page, you'll likely find your error is directly due to memory running out and well access denied man no more for you.

 

 

Bradley translates into Broad Wood :shy:  <-- most appropriate expression :D  

My Avatar has caused Me to be taken for a she before.

Link to comment

Hey guys,

 

sorry for the late response, I'm really busy with work at the moment. I'm looking forward to get into Skyrim Modding again with a completely new mod setup. I'm definitly going to take a look at the options provided by skse.ini for better stability, thanks a lot for the hints!

 

 

Alan

Link to comment

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...