Posted September 29, 2018
A random crash to desktop when playing UFO Aftermath, usually after an hour of play (though it crashed on the title screen once, too — not included).
Here are three crashlogs:
UFO:AM release 1.4
]crash 1
Application crashed: access violation reading from address 0x0000000C!
SymInit search path: G:\games\GOG\UFOs\Aftermath
SymGetSymFromAddr:487, addr:0x006C3709
SymGetSymFromAddr:126, addr:0x72657375
SymGetSymFromAddr:126, addr:0x06C70846
StackWalk:126
]crash 2
Application crashed: access violation reading from address 0x0000000C!
SymInit search path: G:\games\GOG\UFOs\Aftermath
SymGetSymFromAddr:487, addr:0x006C3647
SymGetSymFromAddr:126, addr:0x72657375
SymGetSymFromAddr:126, addr:0x06C70846
StackWalk:126
]crash 3
Application crashed: access violation reading from address 0x0000000C!
SymInit search path: G:\games\GOG\UFOs\Aftermath
SymGetSymFromAddr:487, addr:0x006C3709
SymGetSymFromAddr:126, addr:0x72657375
SymGetSymFromAddr:126, addr:0x06C70846
StackWalk:126
======================================
So it looks like a bug in the kernel. Anyone else have this problem?
[Windows 7 (32bit) Home Premium, 2GB RAM, Intel integrated graphics]
Here are three crashlogs:
UFO:AM release 1.4
]crash 1
Application crashed: access violation reading from address 0x0000000C!
SymInit search path: G:\games\GOG\UFOs\Aftermath
SymGetSymFromAddr:487, addr:0x006C3709
SymGetSymFromAddr:126, addr:0x72657375
SymGetSymFromAddr:126, addr:0x06C70846
StackWalk:126
]crash 2
Application crashed: access violation reading from address 0x0000000C!
SymInit search path: G:\games\GOG\UFOs\Aftermath
SymGetSymFromAddr:487, addr:0x006C3647
SymGetSymFromAddr:126, addr:0x72657375
SymGetSymFromAddr:126, addr:0x06C70846
StackWalk:126
]crash 3
Application crashed: access violation reading from address 0x0000000C!
SymInit search path: G:\games\GOG\UFOs\Aftermath
SymGetSymFromAddr:487, addr:0x006C3709
SymGetSymFromAddr:126, addr:0x72657375
SymGetSymFromAddr:126, addr:0x06C70846
StackWalk:126
======================================
So it looks like a bug in the kernel. Anyone else have this problem?
[Windows 7 (32bit) Home Premium, 2GB RAM, Intel integrated graphics]
No posts in this topic were marked as the solution yet. If you can help, add your reply