erick1326a Posted April 29, 2017 Report Share Posted April 29, 2017 Hi all, When I try to play this game, it crashes when it reaches 100% on my loading screen( Details: unhandled exception (Access violation reading 0x00003210) Location: unknown:0 (?) Call stack: (error while dumping stack: No stack frames found) errno = 0 (No error reported here) OS error = 0 (no error code was set) Thanks for help! crashlog.dmp crashlog.txt Quote Link to comment Share on other sites More sharing options...
Stan` Posted May 6, 2017 Report Share Posted May 6, 2017 Hello @erick1326a, Welcome to the forums, and thanks for your bug report. Here is the call stack of the crashlog: Spoiler > atioglxx.dll!690bf64d() Unknown [Frames below may be incorrect and/or missing, no symbols loaded for atioglxx.dll] pyrogenesis.exe!CPostprocManager::ApplyBlurDownscale2x(unsigned int inTex, unsigned int outTex, int inWidth, int inHeight) Line 249 C++ pyrogenesis.exe!CPostprocManager::ApplyBlur() Line 351 C++ pyrogenesis.exe!CPostprocManager::ApplyPostproc() Line 502 C++ pyrogenesis.exe!CRenderer::RenderSubmissions(const CBoundingBoxAligned & waterScissor) Line 1569 C++ pyrogenesis.exe!CRenderer::RenderScene(Scene & scene) Line 1875 C++ pyrogenesis.exe!CGameView::Render() Line 489 C++ pyrogenesis.exe!Render() Line 232 C++ pyrogenesis.exe!CGame::ReallyStartGame() Line 322 C++ pyrogenesis.exe!ProgressiveLoad() Line 203 C++ pyrogenesis.exe!Frame() Line 308 C++ pyrogenesis.exe!RunGameOrAtlas(int argc, const char * * argv) Line 527 C++ pyrogenesis.exe!SDL_main(int argc, char * * argv) Line 567 C++ pyrogenesis.exe!main_utf8(int argc, char * * argv) Line 126 C pyrogenesis.exe!wmain(int argc, unsigned short * * wargv, unsigned short * wenvp) Line 151 C [External Code] pyrogenesis.exe!CallStartupWithinTryBlock() Line 364 C++ kernel32.dll!767033aa() Unknown Looking at that and the fact your graphics card is not that recent "ATI Mobility Radeon HD 6370" I would suggest you to update drivers if you haven't done already (I think you'll find them in the legacy section of Amd's website), also, disable GLSL and PostProcessing should fix that error. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.