Can't start some games and .exe, Exception code: 0xc0000005

Hi so im having this problem where some games i started appear at the Task Manager for around 10 seconds, and closes itself without any error message. The programs ran perfectly fine before on this PC. This is the error log for one of the program:

Log Name: Application
Source: Application Error
Date: 15/02/2012 03:02:37
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: NOBU12PK.exe, version: 1.0.0.0, time stamp: 0x4732cbf8
Faulting module name: NOBU12PK.exe, version: 1.0.0.0, time stamp: 0x4732cbf8
Exception code: 0xc0000005
Fault offset: 0x00000f67
Faulting process id: 0x11b0
Faulting application start time: 0x01cceb4b36d8122c
Faulting application path: C:\Users\Edwin\Desktop\Nobunaga12\NOBU12PK.exe
Faulting module path: C:\Users\Edwin\Desktop\Nobunaga12\NOBU12PK.exe
Report Id: 751f1a38-573e-11e1-ab1d-002215f017f8

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

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

If you have raid > update its Driver.


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+



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.

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

EddyK89 said:

Hi so im having this problem where some games i started appear at the Task Manager for around 10 seconds, and closes itself without any error message. The programs ran perfectly fine before on this PC. This is the error log for one of the program:

Log Name: Application
Source: Application Error
Date: 15/02/2012 03:02:37
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: NOBU12PK.exe, version: 1.0.0.0, time stamp: 0x4732cbf8
Faulting module name: NOBU12PK.exe, version: 1.0.0.0, time stamp: 0x4732cbf8
Exception code: 0xc0000005
Fault offset: 0x00000f67
Faulting process id: 0x11b0
Faulting application start time: 0x01cceb4b36d8122c
Faulting application path: C:\Users\Edwin\Desktop\Nobunaga12\NOBU12PK.exe
Faulting module path: C:\Users\Edwin\Desktop\Nobunaga12\NOBU12PK.exe
Report Id: 751f1a38-573e-11e1-ab1d-002215f017f8

Do what JMH suggests FIRST but we can tell you a lot more if we have the actual DMP file.

HI i've ran Memtest, it shows that there is no problem with my RAM. Would like to avoid going blue screen if possible..how do i let you guys see the DMP file?

Also, i tried going into Safe mode, and i can't run the same programs.

Just ran SFC/Scannow. No violation reported.

EddyK89 said:

.how do i let you guys see the DMP file?

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.

How many passes for memtest?

What about driver verifier?

@Zigzag: I made 6 passes on memtest. As for the driver verifier, i've set it up like you suggested, but so far there has been no crashes.

@JMH: I've set Startup and Recovery Settings as per your instruction, but the folder windows\minidump does not exist (its not in there as a hidden file too). Am i suppose to go into safemode to access it or am i supposed to wait until the system crash?

There are several reasons that may prevent you from having a DMP file in the usual places.

If your control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.

EddyK89 said:

@Zigzag: I made 6 passes on memtest. As for the driver verifier, i've set it up like you suggested, but so far there has been no crashes.

@JMH: I've set Startup and Recovery Settings as per your instruction, but the folder windows\minidump does not exist (its not in there as a hidden file too). Am i suppose to go into safemode to access it or am i supposed to wait until the system crash?

Memtest seems ok.

Verifier may not be "verifying" the driver that is causing the problem. If it doesnt work within 36 hours we can make adjustments.