Solved BSOD when opening certain games (DMP Included).

[Problematics]

Hi there.

I've started getting some random BSOD messages while playing a game called Vindictus. I don't get this error when playing other games like Skyrim or BF3. I only started getting this BSOD lately. I've included my DMP File for more information since I can only give so much. Please help me pinpoit the problem, thanks!

EDIT : I forgot to add the specs.

- x86 (32-bit) or x64 ?
*** x64 Ultimate
- the original installed OS on the system?
*** Same as above
- an OEM or full retail version?
*** OEM
- OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)?
*** Less than 3 months
- What is the age of OS installation (have you re-installed the OS?)
*** Less than 3 months

 

[zigzag3143]

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.





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.

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



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.

 

[Problematics]

Done with Memtest, didn't came up with errors after running it for sometime. Going to try out Driver Verifier next.

 

[Problematics]

Update :

Done both tests. I've also found out what seems to be causing it. I've recently installed Nvidia's new driver 295.73 and it has been causing my screen to be glitchy at some parts some times. So I uninstalled the driver and reinstalled back the one that came with the video card and I haven't got the BSOD yet after that. (Haven't received any errors from the game after that as well).

I'll update again if another BSOD happens.