Skyrim Memory Patch - fixing ILS, uGrids CTD, freezes

[Rubicon]

For Oblivion can implement such an idea?

[Nearox]

I am still crashing sometimes, though less than before. I'm using the DLL provided by Neovalen at the STEP forums. Allso using his SR:LE guide, with no additions or modifications. Other users report being able to run it with your patch without any issues, but this is not the case for me unfortunately... VRAM limit is not reached at all (game runs at around 1500mb out of 2048mb max vram of my card hd6950) and I use enboost 0.221.

1 --- I've tried with memblock1 settings 512MB and 384MB, but whichever one I set makes no difference.

2 --- If I read VMMAP correctly then my game only needs approx 290mb max. Meaning 384MB should still be plenty, but it happens just as freuently with 512mb (approx every 30minutes).

3 --- The crashes happen at or near cell borders.

4 --- In the minidumps generated, there is never a mention of the type of crash that you describe in the OP (see last minidump below).


VMMAP reading just before the crash (with 384MB memblock 1 setting):



My SKSE Minidump Report from the last crash:

Code: Select all

Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.

Show DivPrimary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
kernel32.dll version: 6.1.7601.18229 (win7sp1_gdr.130801-1533)
Machine Name:
Debug session time: Wed Jan 22 08:19:51.000 2014 (UTC - 5:00)
System Uptime: not available
Process Uptime: 0 days 0:04:28.000
  Kernel time: 0 days 0:00:32.000
  User time: 0 days 0:04:51.000
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2
Unable to load image C:\Skyrim\sweetfx_d3d9.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sweetfx_d3d9.dll
*** ERROR: Module load completed but symbols could not be loaded for sweetfx_d3d9.dll
*** WARNING: Unable to verify timestamp for d3d9.dll
*** ERROR: Module load completed but symbols could not be loaded for d3d9.dll
Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\045c9588954c3662d542b53f4462268b\mscorlib.ni.dll, Win32 error 0n2
*** WARNING: Unable to verify checksum for mscorlib.ni.dll
Unable to load image C:\Skyrim Tools\SPM\EasyHook32.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for EasyHook32.dll
*** ERROR: Module load completed but symbols could not be loaded for EasyHook32.dll
*** WARNING: Unable to verify timestamp for XAudio2_6.dll
*** WARNING: Unable to verify timestamp for atiumdag.dll
*** ERROR: Module load completed but symbols could not be loaded for atiumdag.dll
*** WARNING: Unable to verify timestamp for atiumdva.dll
*** ERROR: Module load completed but symbols could not be loaded for atiumdva.dll
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP: 
KERNELBASE!RaiseException+58
751dc41f c9              leave

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 751dc41f (KERNELBASE!RaiseException+0x00000058)
   ExceptionCode: e06d7363 (C++ EH exception)
  ExceptionFlags: 00000001
NumberParameters: 3
   Parameter[0]: 19930520
   Parameter[1]: 0e83fac0
   Parameter[2]: 01238294
unable to find C-Runtime symbols, even with unqualified search

PROCESS_NAME:  TESV.exe

ERROR_CODE: (NTSTATUS) 0xe06d7363 - 

EXCEPTION_CODE: (NTSTATUS) 0xe06d7363 - 

EXCEPTION_PARAMETER1:  19930520

EXCEPTION_PARAMETER2:  0e83fac0

EXCEPTION_PARAMETER3:  01238294

CHKIMG_EXTENSION: !chkimg -lo 50 -d !KERNELBASE
    751dc428-751dc42c  5 bytes - KERNELBASE!CloseHandle

	[ 8b ff 55 8b ec:e9 b3 19 b7 e1 ]
5 errors : !KERNELBASE (751dc428-751dc42c)

MANAGED_STACK: !dumpstack -EE
No export dumpstack found

FAULTING_THREAD:  000009b4

ADDITIONAL_DEBUG_TEXT:  Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

LAST_CONTROL_TRANSFER:  from 00f59bf2 to 751dc41f

BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS_MEMORY_CORRUPTION_PATCH_NOSOS

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS_MEMORY_CORRUPTION_PATCH_NOSOS

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_MEMORY_CORRUPTION_PATCH_NOSOS

STACK_TEXT:  
00000000 00000000 memory_corruption!KERNELBASE+0x0


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  memory_corruption!KERNELBASE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  ** Pseudo Context ** ; kb

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_MEMORY_CORRUPTION_PATCH_NOSOS_e06d7363_memory_corruption!KERNELBASE

BUCKET_ID:  APPLICATION_FAULT_WRONG_SYMBOLS_MEMORY_CORRUPTION_PATCH_NOSOS_memory_corruption!KERNELBASE

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/TESV_exe/1_9_32_0/51437ce5/KERNELBASE_dll/6_1_7601_18229/51fb1116/e06d7363/0000c41f.htm?Retriage=1

Followup: MachineOwner

[Malizeus]

@Nearox

As far as i can tell, it looks like your crash fix is not active. Its still using default 256/256. Also it looks like you should set it atleast to 512/384.

[Nearox]

@Nearox

As far as i can tell, it looks like your crash fix is not active. Its still using default 256/256. Also it looks like you should set it atleast to 512/384.

Edit:
okay, i'm not sure is default 256/256 or 246/128?

Thanks for your reponse. I am pretty sure the fix is active, because with the default dll the first and 2nd address code show as 256/256 but in the screenshot you can clearly see the first address code is now 384mb. Also the 2nd block only has 150mb approx commited out of 256mb. Moreover the skse_steam_loader.log has the message that it is enabled.

Not sure where you get your numbers from, unless I am the one reading it wrong.

[Malizeus]

Made a typo there..

Okay sorry, i see you've expanded the address a bit and i didnt notice it. My bad. Anyway, looks like it should work. No idea why its still crashing...

[thalixte]

@Nearox

As far as i can tell, it looks like your crash fix is not active. Its still using default 256/256. Also it looks like you should set it atleast to 512/384.

Edit:
okay, i'm not sure is default 256/256 or 246/128?

Thanks for your reponse. I am pretty sure the fix is active, because with the default dll the first and 2nd address code show as 256/256 but in the screenshot you can clearly see the first address code is now 384mb. Also the 2nd block only has 150mb approx commited out of 256mb. Moreover the skse_steam_loader.log has the message that it is enabled.

Not sure where you get your numbers from, unless I am the one reading it wrong.

Have you tried the new universal patch (from Tase, uriel24 or me) that uses mempatch.dll ?

[Nearox]

Thalixte, I haven't actually. Not sure what it is you or the others have changed compared to the original dll, and how each of your compiles compare vis-a-vis the one's from another?

Regardless, I'll give them a try though, thank you

[Nearox]

Alright I've tried all the 3 versions but all seem to just result in 256/256 on my system. Using the appropriate SKSE.ini values.

Compiled the skse_steam_loader. dll myself and also compiled the skse_loader.exe for non-steam users posted here. Now I do get (once again) a value of 512/256 (or 384/256 if I'd recompile again). Will test if it makes a difference.

[Nearox]

Alright I've tried all the 3 versions but all seem to just result in 256/256 on my system. Using the appropriate SKSE.ini values.

Compiled the skse_steam_loader. dll myself and also compiled the skse_loader.exe for non-steam users posted here. Now I do get (once again) a value of 512/256 (or 384/256 if I'd recompile again). Will test if it makes a difference.

Just ran Skyrim with this until it crashed (approx 30min). Strangely enough, the minidump produces a different error code now than the one I posted here earlier.

VMMAP jsut before the crash:




SKSE minidump:

Code: Select all

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
kernel32.dll version: 6.1.7601.18229 (win7sp1_gdr.130801-1533)
Machine Name:
Debug session time: Wed Jan 22 11:48:05.000 2014 (UTC - 5:00)
System Uptime: not available
Process Uptime: 0 days 0:32:25.000
  Kernel time: 0 days 0:02:30.000
  User time: 0 days 0:31:33.000
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2
Unable to load image C:\Skyrim\sweetfx_d3d9.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sweetfx_d3d9.dll
*** ERROR: Module load completed but symbols could not be loaded for sweetfx_d3d9.dll
*** WARNING: Unable to verify timestamp for d3d9.dll
*** ERROR: Module load completed but symbols could not be loaded for d3d9.dll
Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\045c9588954c3662d542b53f4462268b\mscorlib.ni.dll, Win32 error 0n2
*** WARNING: Unable to verify checksum for mscorlib.ni.dll
Unable to load image C:\Skyrim Tools\SPM\EasyHook32.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for EasyHook32.dll
*** ERROR: Module load completed but symbols could not be loaded for EasyHook32.dll
*** WARNING: Unable to verify timestamp for XAudio2_6.dll
*** WARNING: Unable to verify timestamp for atiumdag.dll
*** ERROR: Module load completed but symbols could not be loaded for atiumdag.dll
*** WARNING: Unable to verify timestamp for skse_1_9_32.dll
*** ERROR: Module load completed but symbols could not be loaded for skse_1_9_32.dll
*** WARNING: Unable to verify timestamp for atiumdva.dll
*** ERROR: Module load completed but symbols could not be loaded for atiumdva.dll
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP: 
TESV+abc0a6
00ebc0a6 cc              int     3

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00ebc0a6 (TESV+0x00abc0a6)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 00000000

PROCESS_NAME:  TESV.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

EXCEPTION_PARAMETER1:  00000000

MANAGED_STACK: !dumpstack -EE
No export dumpstack found

FAULTING_THREAD:  00001024

BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS_NOSOS

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS_NOSOS

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_NOSOS

LAST_CONTROL_TRANSFER:  from 00ebba50 to 00ebc0a6

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
0ea6f218 00ebba50 0ea6f340 f2d46cab 0ea6f2d0 TESV+0xabc0a6
0ea6f2f8 00ebc4a1 0ea6f340 f2d45470 0ea6f320 TESV+0xabba50
0ea6f38c 00e16904 0ea6f3d0 0ea6fa40 0ea6fa40 TESV+0xabc4a1
0ea6f4ac 00de00a3 cdedec10 f1cd84a0 0ea6f6e0 TESV+0xa16904
0ea6f5e0 00de0236 0ea6f640 0ea6f6c0 00000000 TESV+0x9e00a3
0ea6f684 00d4f26c d43ac900 cdedec10 0ea6f810 TESV+0x9e0236
0ea6f758 0058b081 cdedec10 0ea6f810 0ea6fa40 TESV+0x94f26c
0ea6ff04 0073f4e0 e6f2d670 0ea6ff3c 0ea6ff54 TESV+0x18b081
0ea6ff88 764f336a cdcff180 0ea6ffd4 77789f72 TESV+0x33f4e0
0ea6ff94 77789f72 cdcff180 79c89552 00000000 kernel32!BaseThreadInitThunk+0xe
0ea6ffd4 77789f45 00a4b4a0 cdcff180 00000000 ntdll!__RtlUserThreadStart+0x70
0ea6ffec 00000000 00a4b4a0 cdcff180 00000000 ntdll!_RtlUserThreadStart+0x1b


FOLLOWUP_IP: 
TESV+abc0a6
00ebc0a6 cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  TESV+abc0a6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: TESV

IMAGE_NAME:  TESV.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51437ce5

STACK_COMMAND:  ~23s; .ecxr ; kb

FAILURE_BUCKET_ID:  WRONG_SYMBOLS_NOSOS_80000003_TESV.exe!Unknown

BUCKET_ID:  APPLICATION_FAULT_WRONG_SYMBOLS_NOSOS_TESV+abc0a6

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/TESV_exe/1_9_32_0/51437ce5/TESV_exe/1_9_32_0/51437ce5/80000003/00abc0a6.htm?Retriage=1

Followup: MachineOwner

[Malizeus]

I cant post pictures of my own vmmap yet, but something that i notice that is radically different from my own game in vmmap is:

Your heap size is absolutely massive.. mine is 576k, yours is over 600 times larger than mine.
Also i have 0 managed heap...
Everything else looks about the same...

Maybe there is something bloating your game...

Heap
Heaps represent private memory managed by the user-mode heap manager and, like the Private memory type, is charged against the system commit limit and contains application data. Application memory allocations using the C runtime malloc library, HeapAlloc and LocalAlloc, use Heap memory.

I'm no programmer so i have no idea what massive heap size actually means... maybe someone more knowledgeable will take a look at this...