Exception Address: 006cb7d6 (TESV+0x002cb7d6) Error?

[XunTzu]

Crash dump shows that, after CTD when starting up Skyrim.  Found a similar issue on the forums, but the poster didn't quite say how he/she fixed it.

 

The only mods installed since last working were:

Warzones 2015

Apocalypse magic

Various armor mods

 

Here's the crash dump.

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 (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
kernel32.dll version: 6.1.7601.23677 (win7sp1_ldr.170209-0600)
Machine Name:
Debug session time: Tue Oct 24 05:36:15.000 2017 (UTC - 4:00)
System Uptime: not available
Process Uptime: 0 days 0:01:16.000
  Kernel time: 0 days 0:00:34.000
  User time: 0 days 0:01:16.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:\Games\Steam\gameoverlayrenderer.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gameoverlayrenderer.dll
*** ERROR: Module load completed but symbols could not be loaded for gameoverlayrenderer.dll
*** WARNING: Unable to verify timestamp for hdtHighHeelNative.dll
*** ERROR: Module load completed but symbols could not be loaded for hdtHighHeelNative.dll
*** WARNING: Unable to verify timestamp for hdtPhysicsExtensions.dll
*** ERROR: Module load completed but symbols could not be loaded for hdtPhysicsExtensions.dll
*** WARNING: Unable to verify timestamp for JContainers.dll
*** ERROR: Module load completed but symbols could not be loaded for JContainers.dll
*** WARNING: Unable to verify timestamp for XAudio2_6.dll
*** WARNING: Unable to verify timestamp for nvd3dum.dll
*** ERROR: Module load completed but symbols could not be loaded for nvd3dum.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\System32\D3DX9_43.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for D3DX9_43.dll
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
GetUrlPageData2 (WinHttp) failed: 12029.

FAULTING_IP: 
TESV+2cb7d6
006cb7d6 8b88c4000000    mov     ecx,dword ptr [eax+0C4h]

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 006cb7d6 (TESV+0x002cb7d6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 000000c4
Attempt to read from address 000000c4

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_READ

PROCESS_NAME:  TESV.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  000000c4

READ_ADDRESS:  000000c4 

FOLLOWUP_IP: 
TESV+2cb7d6
006cb7d6 8b88c4000000    mov     ecx,dword ptr [eax+0C4h]

FAULTING_THREAD:  00001798

PRIMARY_PROBLEM_CLASS:  NULL_CLASS_PTR_READ

BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_READ

IP_ON_HEAP:  393ea0e0
The fault address in not in any loaded module, please check your build's rebase
log at \bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FRAME_ONE_INVALID: 1

LAST_CONTROL_TRANSFER:  from 393ea0e0 to 006cb7d6

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
52dffe20 393ea0e0 004ca2a5 00000355 000002e7 TESV+0x2cb7d6
52dffe24 004ca2a5 00000355 000002e7 012e3600 0x393ea0e0
52dffe28 00000000 000002e7 012e3600 012e36b0 TESV+0xca2a5


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  TESV+2cb7d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: TESV

IMAGE_NAME:  TESV.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51437ce5

STACK_COMMAND:  ~46s; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_CLASS_PTR_READ_c0000005_TESV.exe!Unknown

BUCKET_ID:  APPLICATION_FAULT_NULL_CLASS_PTR_READ_TESV+2cb7d6

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/TESV_exe/1_9_32_0/51437ce5/TESV_exe/1_9_32_0/51437ce5/c0000005/002cb7d6.htm?Retriage=1

[XunTzu]

This is the crash log from "Crash Fixes"

 

Crash info:
2017_10_24_09-41-48 - 6CB7D6: V(1); EAX(0); EBX(0); ECX(2F7C1988); EDX(6CB7D0); ESI(2F7C1988); EDI(2F59B9C8); EBP(2); ESP(2151FE24); STACK(4CA2A5 1000004 4F1FD1 4F2283 43F1FA 44377B 699350 699100 699974 A4BB02 A4B4A9 A4B4A0 A4B4A0);

Not so useful info (don't post unless asked):
STACK_FULL(2F7C1988 4CA2A5 355 2E7 12E3600 12E36B0 1000004 18409120 FFFFFFFF 2F59B9C8 C0490FE7 2F59BA44 61 10775F0 2151FE6C 0 2151FE70 32C8A038 184095A4 28CB0014 4 3 0 4F1FD1 0 32C0A760 2CF64B64 12E3600 4F2283 47 2151FEA3 43F1FA 2151FEBC EE 12E3600 12E4058 23A73010 87 107B614 0 0 0 0 0 0 0 0 0 0 0 0 44377B A 10D1069 0 18409120 18409120 2 699350 0 0 18FD80 2151FF94 18FD80 2 699100 0 0 1272F38 1272F44 1272F50 1272F5C 1272F68 1272F74 1272F80 1272F8C 1272F98 1272FA4 5DC7102D 18A5A600 2151FF94 699974 18A5A600 18FD80 A4BB02 0 0 18FD80 0 A4B4A9 7661336A 18FD80 2151FFD4 77C79902 18FD80 56A9D41A 0 0 18FD80 C0000005 7663770F 7663770F 2151FFA0 2151F870 FFFFFFFF 77CB58C5 3EEDEE 0 2151FFEC 77C798D5 A4B4A0 18FD80 0 0 0 0 A4B4A0 18FD80 0);

[Gnafron]

From what I read here and there, some people would not touch Warzones even with a 3 yards stick. When most posts about a mod on the nexus are complaints, that says something. Do not use it unless there is a sure way to fix it yourself.

[XunTzu]

From what I read here and there, some people would not touch Warzones even with a 3 yards stick. When most posts about a mod on the nexus are complaints, that says something. Do not use it unless there is a sure way to fix it yourself.

 

That was old Warzones. New Warzones was rebuilt and taken off the "Do Not Use" list.  Also found out it wasn't the troublemaker.

 

Edit: Tracked down the offending mod, was a player home, but still would like to understand what went wrong.