You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Heres the log keeps crashing when I go into the town hall in Nipton and then going up the road to the ambush point as well both give the same crash logg
Exception C0000005 caught!
Calltrace:
Error initializing symbol store
0x00AA55A6 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBDB98)
0x00994D5F ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBDCCC)
0x0097DFA5 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF08)
0x008A05D4 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF24)
0x00991E47 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF48)
0x008C7E38 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF50)
0x008C71A8 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF5C)
0x008C7764 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF68)
0x00AA64E0 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF70)
0x766E00C9 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF80)
0x77A67B1E ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFFDC)
0x77A67AEE ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFFEC)
UNABLE TO IDENTIFY MODULE CONTAINING THE CRASH ADDRESS.
This can occur if the crashing instruction is located in the vanilla address space,
but it can also occur if there are too many DLLs for us to list, and if the crash
occurred in one of their address spaces. Please note that even if the crash occurred
in vanilla code, that does not necessarily mean that it is a vanilla problem. The
vanilla code may have been supplied bad data or program state as the result of an
issue in a loaded DLL.
The text was updated successfully, but these errors were encountered:
Heres the log keeps crashing when I go into the town hall in Nipton and then going up the road to the ambush point as well both give the same crash logg
Exception C0000005 caught!
Calltrace:
Error initializing symbol store
0x00AA55A6 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBDB98)
0x00994D5F ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBDCCC)
0x0097DFA5 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF08)
0x008A05D4 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF24)
0x00991E47 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF48)
0x008C7E38 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF50)
0x008C71A8 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF5C)
0x008C7764 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF68)
0x00AA64E0 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF70)
0x766E00C9 ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFF80)
0x77A67B1E ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFFDC)
0x77A67AEE ==> ¯(°_o)/¯ (Corrupt stack or heap?) (0x11BBFFEC)
Instruction pointer (EIP): 00AA55A6
REG | VALUE
eax | 00000008
ebx | 3B114708
ecx | 00000010
edx | 00000000
edi | 00AA64D0
esi | 00AA64D0
ebp | 11BBDB98
0x00000000 | 0x11BBFDBC | 0x11BBDC18 | 0x11BBFDB0
0x0000000C | 0x11BBDBC8 | 0x11BBDB8C | 0x009AA4A3
0x00000010 | 0x00000008 | 0x00000000 | 0x00000000
0x00000000 | 0x11BBDCCC | 0x00994D5F | 0x00000008
0x00000004 | 0x65D69E82 | 0x11BBDC20 | 0x11BBDD04
0x49000FA0 | 0x11BBDC20 | 0x0040FC72 | 0x0B007068
0x00000008 | 0x00000000 | 0x00010280 | 0xFFFEFD7F
0x00000001 | 0x00000000 | 0x00000000 | 0x00000000
0x00000000 | 0x00000000 | 0x00000000 | 0x00000007
0x00000006 | 0x00000040 | 0x00000000 | 0x00000000
0x00000000 | 0x00000000 | 0x00000000 | 0x00060100
0x00000000 | 0x00000000 | 0x00000000 | 0x00000006
0x00010000 | 0x01C00000 | 0x11BBDC54 | 0x00AA5EFC
LISTING MODULE BASES ...
UNABLE TO IDENTIFY MODULE CONTAINING THE CRASH ADDRESS.
This can occur if the crashing instruction is located in the vanilla address space,
but it can also occur if there are too many DLLs for us to list, and if the crash
occurred in one of their address spaces. Please note that even if the crash occurred
in vanilla code, that does not necessarily mean that it is a vanilla problem. The
vanilla code may have been supplied bad data or program state as the result of an
issue in a loaded DLL.
The text was updated successfully, but these errors were encountered: