APPCRASH exception code c0000005

I run Windows 7 Pro and I am constantly being kicked out of games. This also happens on XP. On XP I am dumped on the desktop without warning or error messages. On Win7 at least I get error messages. To try and remedy the problem I have replaced my video card, tested my ram individually, updated all drivers including the chipset and bios and got a new power source. This happens with most of the games I try to play including but not limited to:

Dungeon Defenders
Dark Age of Camelot
Elder Scrolls V: Skyrim
Heroes of Might and Magic V
Dead Island
Magicka
Overlord
Overlord II
The Witcher 2
League of Legends
World of Tanks



Problem signature:
Problem Event Name: APPCRASH
Application Name: game.dll
Application Version: 1.111.0.0
Application Timestamp: 4f1effe6
Fault Module Name: game.dll
Fault Module Version: 1.111.0.0
Fault Module Timestamp: 4f1effe6
Exception Code: c0000005
Exception Offset: 0038e910
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 257d
Additional Information 2: 257d8f504c598531c429b24cac277ae5
Additional Information 3: 0cad
Additional Information 4: 0cadf29471eab500e26712b1113c6d32

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Computer Specs:
Motherboard: ECS GF8200A (v1.0)
Ram: 4gb G.SKILL ram DDR2 1066
Video card: geforce 460gtx
Processor: AMD athlon 64 x2 6400+
HD: Western Digital Caviar SE 320gb


I've tried everything, I appreciate any help.

Nix131,

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Thank you for your prompt response. This is not a BSOD error. On windows XP it just dumps me on the desktop without warning or error message. On Win 7 it dumps me on the desktop with one or more error messages.

I followed your instructions to enable minidump. I then played two of the problematic games until they crashed. I then restarted into safe mode with networking and searched for the minidump file, none exist. I am not currently overclocking and I do have show hidden files enabled.

You won't get any DMP files via Safe Mode...

We suggest you run these two tests.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Using Driver Verifier to identify issues with Windows drivers for advanced users

yesterday i began receiving this message. how can this be fixed. itunes opens and the window immediately pops up that the program has stopped working.

Problem signature:
Problem Event Name: APPCRASH
Application Name: iTunes.exe
Application Version: 10.5.3.3
Application Timestamp: 4f14cc3d
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17651
Fault Module Timestamp: 4e211319
Exception Code: 80000003
Exception Offset: 0001280c
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

I have the same problem on games which was caused by graphics so i have install DirectX. After the installation the problem was gone.