After a few hours gaming, the next boot ends in BSOD

Hello All,

I am strugling with frequent BSOD.

Description: After a few hours of playing (FPS) at the next boot I get BSOD, corrupt registry, memory management error, etc, various stop codes. Windows repair cant help.

What usually helps is: i.e: remove one stick of memory (no matter which one) or adjust memory timing (no matter which direction), or reload previous system image.

After win7 is started again everything is fine, I can put back the memory stick and I can play again hours.

Sometimes, if I let system repairs to do its job then at the end I get a lot of corrupted files a lot of chkdsk fix, then some application does not start because of memory address violation error......the end is always a system image reload.


I tested the memories with memtest86+ (4 hours) and nothing (if everything was ok before) but when the BSOD starts I got errors if both stick in it, no errors with single stick.

I am really desperate now....RAM? MOBO ?

I would rule out the videocard as during the playing no issues at all (intense FPS game BF3).

Last BSOD report attached.

Many thanks for view my problem.

My rig:

ASROCK M3A770DE
AMD Phenom II X4 3.4 GHz Processor Black Edition
2x2gb OCZ OCZ3OB1600LV4GK RAM
WD 250 GB HDD
Zotac ZT-50102-10P GF GTX 580 AMP! 1536MB GDDR5
Corsair CMPSU-850TXV2UK Enthusiast Series TX850 V2

Algoritmus

With only one DMP it is hard to spot trends

Yours is memory management probably a driver

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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).

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.

Hello ZIGZAG,

Here is the next one (verifier was on).

Thanks for your help, really appreciated.

Algo

and an other one...

Algoritmus said:

Hello ZIGZAG,

Here is the next one (verifier was on).

Thanks for your help, really appreciated.

Algo

Since both verified and unverified point to memory management you should run memtest to verify your ram.

I still think it is a driver but lets eliminate the ram as a possibility.

*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+

Thanks.

I have replaced the ram modules, we will see how it goes.

Algoritmus said:

Thanks.

I have replaced the ram modules, we will see how it goes.

Good idea and let us know if you need help

Hello,

BSODs again ......I have attached the logfile, but the I am unable to create perfmon report, see attached perfmon.txt for error message. At the moment windows is seems to failling apart as every single operation is crashing. i.e.: explorer during copy, browser can not start, restart takes 5 minutes then after win loaded pc reset itself....and the best thing is that yesterday I played 3 hours without any problem....

since the last BSoD there were two more....the last one was in safe mode: memory management...I will attach the reports if I can get in ......no It is just died......bad pool header during running the reporting tool (jcgriff2).....and sudden shutdown again while I am typing (on my laptop)......horribly....

now I can not boot into even safe mode...BSoD system service exeption...try to do a repair....