Not a BSOD - C0000005 error, numerous games

[Zerahn]

Hi there. I upgraded my mobo/CPU a while ago, and started getting 0xC0000005 errors shortly after. I've reformatted the computer about three times now, using Windows 7 Home, both the 32 and 64 bit versions (currently 64-bit is installed). I've run one of them there memory checkers, leaving it on all night, and it came up with nothing. I've replaced the video card with the old one, and I still got the error. It does not BSOD, the game just won't run. The following games are affected:
Steam
WarFrame
Diablo III
Final Fantasy XIV
PCSX2

Unaffected are:
ePSXe
Minecraft
Final Fantasy XI's PlayOnline Viewer

It might be relevant to note that affected programs will run as long as I start them within about a minute of turning on the computer, and they'll stay running until I close out of them and start them back up again, at which point I then get the 0xC0000005 error. Again, if I restart the computer (logging out of the desktop and back in does not work), and start the game within about a minute, it will run.

 

[HarriePateman]

Error Code 0xc0000005 means access violation in memory. In most of the cases this is caused by a faulty RAM. Change your RAM with another one and then test.

 

[Thedoctor44]

To test your RAM for errors run memtest86 for at least 8 passes.
Follow these instructions.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Applications are ran in User-mode, therefore they don't run on privileged code, this is to prevent applications and other programs from altering critical OS system files. When an application tries to access memory that it shouldn't windows generates an 0xc0000005 error. If the application was to run on kernel-mode it would generate an IRQL_NOT_LESS_OR_EQUAL bugcheck. Applications have their own VAD (Virtual Address Space) which is isolated from the rest of the memory, this prevents applications from altering other memory address spaces. The Kernel shares one (VAD) so anything that is ran in kernel-mode has access to everything inside Kernel.
I doubt it's driver related as drivers are ran from inside the kernel so if a driver was to access memory that it wasn't supposed to access it would result in a bugcheck.

 

[Zerahn]

Thanks for the reply, Doc. I had memtest running all night after this first started, I'm sure it went through at least 10 passes and there were no errors reported. Should I try it again to make sure? And if memtest reported no problems, does that mean it's likely to be something other than the memory?

 

[Thedoctor44]

If memtest86 ran for 10 passes and found no errors then it's very unlikely that it's RAM related. Can you please enable Driver Verifier to see if drivers are causing the problem. Please follow these instructions.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Zerahn]

Hey thanks for the suggestion. Driver Verifier was running for a few days though and didn't turn up any problems either. I might mention that I've tried removing both sticks of memory, one at a time, and the issue still occurred. Is it weird that it never happens immediately, and once went for about ten minutes of me hopping back and forth from Diablo 3, FFXIV, and PCSX2 before the error started showing up and everything crashed instantly?

 

[Thedoctor44]

That sounds like a heat issue with your Graphics Card. Download Hw monitor and take a screen shot of your temps when playing games.

www.cpuid.com/softwares/hwmonitor.html‎

 

[Zerahn]

If it were a heat issue with the graphics card, wouldn't it cool down after the games were closed out for a few minutes? I can leave this idling for hours and still have the issue, but as soon as I turn the computer off and back on it's good to go. Granted I haven't checked the temp yet. I had it in to a repair shop back in January and they tested it though. I dunno what they actually determined, they just said to reformat it, which I'd already done three times.

 

[Zerahn]

Alright, it's been like 5 months and I'm back again, I've been avoiding using my computer for anything that caused this error but I'm tired of having a $600 (or however much I put into it) social networking machine.

Thedoctor44, I tried HWmonitor, the temperatures only fluctuated by a degree or two between when I started up the computer and ran Steam the first time, and when I closed it out, ran Steam the second time, and had the crash start occurring. The voltages were all over the place though, but that could be normal for all I know.

It may be relevant to mention that I now have to run EACH program twice for the crash to occur. If I play FFXIV, for example, then close it out and have it crash, I can switch to Steam, run it fine, but then it will crash when I close and reopen it.

I've since discovered how to get Windows 7 to generate crash dumps, and attached is a debug log for each of the five programs I still have that this happens with. Hopefully they help someone, I certainly can't make sense of them.

 

[Zerahn]

Oh and here are those debug logs.

 

[Zerahn]

Anyone...?