Computer keeps crashing when playing games

[Ahyslop]

I have a custom built PC that keeps causing my games to crash, especially MMO's. I have tried all of the troubleshooting tips such as making sure all of the drivers are up to date and use CC cleaner for registry issues. However it continues to crash, if anyone else has had the same issue and have fixed it I would like to know how.

Specs
Windows 8 Pro
AMD FX(tm)-4100 Quad core Processor
Nvidia Geforce GTX 560
MB - Sabertooth 990FX R2.0
12gb ram
750gb HD

 

[Nikhil Das]

Is it happening for all of the games? Check event viewer for details.( eventvwr.msc ). Could be of many things, memory issue, driver conflicts. It would be easy for you to trobleshoot it using event viewer. Go to run and type eventvwr.msc and under Windows >> Application, logs will be there. Check it.

 

[Ahyslop]

If anyone can make any sense from this error report when WoW crashed onto desktop.
http://pastebin.com/gaZCUicd

I have googled the error 132 and have tried many of the troubleshooting tips people are suggesting but nothing is working. This isnt the only game that crashes, Rift and Archeage also crash randomly to desktop. Non-MMO games don't crash at all however.

 

[Paul NZ]

Upload the dmp files somewhere and post the link, if it's restarting / crashing

 

[Vynavill]

The memory address generating the error is linked to a module of the Nvidia libraries, but they seem to be up to date. Can you try downgrading to a previous version? Or looking for a newer beta, if there's one available?

 

[Ahyslop]

Thank you for your replies

@Paul NZ
Here is a report from when WoW crashed
http://pastebin.com/gaZCUicd

And a report when Archeage crashed

16:26:29> <CRITICAL EXCEPTION>
16:26:29> Exception Code: 0xC0000005
16:26:29> Exception Addr: 0x0023:0x6c04fe43
16:26:29> Exception Description: EXCEPTION_ACCESS_VIOLATION
Attempt to read from address 0xefb9e92c
The memory could not be "read"
16:26:29> Virtual Memory Usage: 2083Mb
16:26:29> Dumping X86 registers
16:26:29> eip=00000000, esp=00000000, ebp=00000000
16:26:29> edi=00000000, esi=00000000, eax=00000000, ebx=00000000, ecx=00000000, edx=00000000
16:26:29> =============================================================================
16:26:29> Starting stack-walking
16:26:29> nvwgf2um.dll>__unknown__(0):NVAPI_Thunk()
16:26:29> nvwgf2um.dll>__unknown__(0):NVAPI_Thunk()
16:26:29> nvwgf2um.dll>__unknown__(0):NVAPI_Thunk()
16:26:29> nvwgf2um.dll>__unknown__(0):OpenAdapter10()
16:26:29> nvwgf2um.dll>__unknown__(0):NVAPI_Thunk()
16:26:29> nvwgf2um.dll>__unknown__(0):NVAPI_Thunk()
16:26:29> nvwgf2um.dll>__unknown__(0):NVAPI_Thunk()
16:26:29> KERNEL32.DLL>__unknown__(0):BaseThreadInitThunk()
16:26:29> ntdll.dll>__unknown__(0):RtlInitializeExceptionChain()
16:26:29> ntdll.dll>__unknown__(0):RtlInitializeExceptionChain()
16:26:29> ntdll.dll>__unknown__(0):RtlInitializeExceptionChain()
16:26:29> Ended stack-walking...
16:26:29> =============================================================================

@Vynavil I have tried but I am still crashing

 

[Vynavill]

Aaand ArcheAge brings another player in...
OpenAdapter10 is related to Dx10/Direct3D10. I suppose they're up to date, aren't they? Even so, just to stay safe, you should try downloading the latest web installer and see if it updates/repairs anything. It is in the middle of the stack, so there's a low probability it's that one causing the issue, but it's not like you can ignore it either 😛

Also, since you're on w8 you shouldn't be affected, but you should check among your installed updates if you have the KB2670838 (gently dubbed by the community as "The evil update"). It's mainly a W7 update aimed at improving 3D performance with IE10 (not to mention it's a prerequisite for it), which actually breaks the Dx10 library...
If you have it, uninstall it, reboot, and hide it from the updates list, then proceed at updating whatever else it asks.

[off-topic] I wish everything gave out such a useful thing as a stack trace...

 

[Ahyslop]

Aaand ArcheAge brings another player in...
OpenAdapter10 is related to Dx10/Direct3D10. I suppose they're up to date, aren't they? Even so, just to stay safe, you should try downloading the latest web installer and see if it updates/repairs anything. It is in the middle of the stack, so there's a low probability it's that one causing the issue, but it's not like you can ignore it either 😛

Also, since you're on w8 you shouldn't be affected, but you should check among your installed updates if you have the KB2670838 (gently dubbed by the community as "The evil update"). It's mainly a W7 update aimed at improving 3D performance with IE10 (not to mention it's a prerequisite for it), which actually breaks the Dx10 library...
If you have it, uninstall it, reboot, and hide it from the updates list, then proceed at updating whatever else it asks.

[off-topic] I wish everything gave out such a useful thing as a stack trace...

Thanks for the reply

I have searched my windows update history but have not found that update

I have also attempted to download/update/repair DirectX but it says I have the latest version installed.

Maybe something that might help to diagnose this issue - When I go into "dxdiag" from search it says this
http://gyazo.com/6ff8017601a24ee6cbfff1ae840cc95b

 

[Vynavill]

Well, this is something with the Direct3D libraries after all (as expected after the ArcheAge stack trace)...

Try this. Open up dxdiag, and press yes at that window.
Once it pops up, go to the "Display" tab. Make sure that the "Notes" box reports no issues and that all 3 hardware acceleration options are active (DirectDraw, Direct3D, AGP).

Should it feature any difference, download the June 2010 DirectX 9c redistributable (the full package, not the web-installer) and install it, as some libraries don't come packaged with the DX10/11 web installer and are actually needed for it to work correctly in some games, not to mention it overwrites all 9c libraries, repairing any damage that might have occurred to them.
Also, you should make sure your hardware acceleration options are all enabled. Usually, you find them by right clicking on your desktop, selecting "Resolution", "Advanced options" and then "Troubleshooting".
If the driver supports those settings, you'll find HW acceleration there; otherwise it might be in the Nvidia control panel or might not be available at all (driver hardcodes them, especially happens if you have a beta driver or very rarely with WHQL drivers)

 

[Ahyslop]

Well, this is something with the Direct3D libraries after all (as expected after the ArcheAge stack trace)...

Try this. Open up dxdiag, and press yes at that window.
Once it pops up, go to the "Display" tab. Make sure that the "Notes" box reports no issues and that all 3 hardware acceleration options are active (DirectDraw, Direct3D, AGP).

Should it feature any difference, download the June 2010 DirectX 9c redistributable (the full package, not the web-installer) and install it, as some libraries don't come packaged with the DX10/11 web installer and are actually needed for it to work correctly in some games, not to mention it overwrites all 9c libraries, repairing any damage that might have occurred to them.
Also, you should make sure your hardware acceleration options are all enabled. Usually, you find them by right clicking on your desktop, selecting "Resolution", "Advanced options" and then "Troubleshooting".
If the driver supports those settings, you'll find HW acceleration there; otherwise it might be in the Nvidia control panel or might not be available at all (driver hardcodes them, especially happens if you have a beta driver or very rarely with WHQL drivers)

Dxdiag looks ok -
http://gyazo.com/c1197d29a31db96761861dd90e1957ae

Will download the Directx now, is this the right download?
http://www.microsoft.com/en-gb/download/confirmation.aspx?id=8109

Thank you

 

[Vynavill]

Yeah, that's the right one. Dxdiag is ok, but try installing that anyway. It's not guaranteed it'll fix the issue, but it'll fix any pre-requisite library from 9c that may have been broken.

 

[Ahyslop]

Yeah, that's the right one. Dxdiag is ok, but try installing that anyway. It's not guaranteed it'll fix the issue, but it'll fix any pre-requisite library from 9c that may have been broken.

Still crashing 🙁 -
22:29:20> <CRITICAL EXCEPTION>
22:29:20> Exception Code: 0xC0000005
22:29:20> Exception Addr: 0x0023:0x3301581b
22:29:20> Exception Description: EXCEPTION_ACCESS_VIOLATION
Attempt to write data to address 0x00000001
The memory could not be "written"
22:29:20> Virtual Memory Usage: 3447Mb
22:29:20> Dumping X86 registers
22:29:20> eip=00000000, esp=00000000, ebp=00000000
22:29:20> edi=00000000, esi=00000000, eax=00000000, ebx=00000000, ecx=00000000, edx=00000000
22:29:20> =============================================================================
22:29:20> Starting stack-walking
22:29:20> CryRenderD3D10.dll>__unknown__(0)😛ackageRenderConstructor()
22:29:20> CryRenderD3D10.dll>__unknown__(0)😛ackageRenderConstructor()
22:29:20> CryRenderD3D10.dll>__unknown__(0)😛ackageRenderConstructor()
22:29:20> function=0x393238e0
22:29:20> function=0x39324295
22:29:20> function=0x3931c4a4
22:29:20> function=0x3930ffd4
22:29:20> MSVCR100.dll>__unknown__(0):endthreadex()
22:29:20> MSVCR100.dll>__unknown__(0):endthreadex()
22:29:20> function=0x762286e3
22:29:20> function=0x76f0be99
22:29:20> function=0x76f0be6c
22:29:20> function=0x76f0be6c
22:29:20> Ended stack-walking...
22:29:20> =============================================================================


I have tried to go into my Nvidia Control pannel but its not responding and can't get that to work. I have re-installed it and done a factory restart but still it doesnt work.

 

[Vynavill]

We're back to D3D10 errors...I'm starting to think it's w8, having IE10, and probably the evil update as well, installed.
I don't suppose you could uninstall IE, just to try it out? I mean, it's a ridiculously useless browser compared to...well, anything else...but anyway, I think I've read somewhere it's part of w8's system.

 

[Ahyslop]

We're back to D3D10 errors...I'm starting to think it's w8, having IE10, and probably the evil update as well, installed.
I don't suppose you could uninstall IE, just to try it out? I mean, it's a ridiculously useless browser compared to...well, anything else...but anyway, I think I've read somewhere it's part of w8's system.

Ok i've uninstalled IE, fingers crossed.

Thank you

 

[Ahyslop]

We're back to D3D10 errors...I'm starting to think it's w8, having IE10, and probably the evil update as well, installed.
I don't suppose you could uninstall IE, just to try it out? I mean, it's a ridiculously useless browser compared to...well, anything else...but anyway, I think I've read somewhere it's part of w8's system.

Unfortunately the issue still persists 🙁
here is a crash report from WoW that I hope you can make sense of
http://pastebin.com/3P7j74Gd

 

[Vynavill]

Well, my hunch didn't fall off so far. DX10 disappeared from the error logs, but DX9 and OGL appeared (but then again, why was it using DX10 in the first place?!). However, the thread that caused the exception seems to have no connection to those libraries, but rather just to your video card's drivers.
I'm calling the "bad driver" flag, at this point, although I might be wrong. Try rollbacking drivers now, or even better, use Guru3D's Display Driver Uninstaller to clean them up completely. Should you decide to clean them up entirely, when you actually re-install them, DO NOT take the latest driver, but go back a release version or two, just to play it safe.

If the issue still persists, there's a high probability it's the OS (W8 is known for being annoying with games), and a very low one it's a hardware fault (I personally highly doubt this, but I just can't tick it off the list of possibilities)