BSOD playing video games / loading video games [MEMORY_MANAGEMENT]

[miqballin]

It doesn't happen often but sometimes it freezes for a second while loading a certain game which works fine on another day and gives BSOD. Sometimes it happens after I've loaded the game and am in the moment of playing. My hardware is more than enough for the games I run and I even run them on low-mid even though I can manage high settings. The games I usually run are CS:GO, League of Legends and Modern Warfare 3 [rarely play; received 1 BSOD while loading it]

I've uploaded my dump files.

Thank you.

 

[Arc]

Hi miqballin.

...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 1A[/COLOR], {41201, fffff6800001aca8, 8080000019905825, fffffa8003e5ded0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+136f2 )

Followup: MachineOwner
---------

According to Carrona.org, STOP 0x0000001A: MEMORY_MANAGEMENThttp://www.carrona.org/bsodindx.html#top
Usual causes: Device driver, memory, kernel

So what you are to do here is

► Enable Driver Verifier.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

► Test the RAM modules.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run it for at least eight passes. Preferably overnight.

Let us know the results, with the subsequent crash dumps, if any.

 

[miqballin]

Thanks for the response Arc. I have a question about the Driver Verifier. So am I selecting ALL the drivers except the ones provided by 'Microsoft Corporation'? Even the '<unkown>' ones? Also, I should do the steps separately correct? Use the computer for 24 hours with Driver Verifier enabled and stop it when I get a BSOD and THEN run the memtest correct?

 

[miqballin]

Received another BSOD [file date: 102612-28579-01.dmp]. I haven't gone through the steps yet because I'm waiting for a response for the previous post. I've attached the dump file for this BSOD. Thanks.

 

[Arc]

According to Carrona.org, STOP 0x0000004E: PFN_LIST_CORRUPT
Usual causes: Device driver, memory

So, a driver verifier is needed there.
For applying driver verifier, do exactly what is stated in the guide Driver Verifier - Enable and Disable.

With verifier enabled, use the computer as usual, let it crash a couple of times, and then upload those dumps.

 

[miqballin]

Alright so I received a BSOD just recently but I realized I forgot to disable the Driver Verifier at the 24 hour mark. I think it went on for 2 days until I received a BSOD. I just disabled the verifier. I've attached the dump file. I will now do the memtest.

 

[Arc]

What I am seeing here that you failed to enable verifier.

Firstly, if verifier is enabled, you must have disabled it at the earliest possible time, as it is disgusting to use the computer with verifier enabled. It becomse very slow and laggy. But you haven't felt anything, that means verifier was not enabled properly.

Secondly, the dump is not showing any stress of verifier enabled, too.

So go for it again, follow it, step by step.
:ar: Driver Verifier - Enable and Disable.

The possibility of the solution of the issue depends on how accurately you are enabling verifier.

 

[miqballin]

Alright. How will I know this time if I did it right?

 

[Arc]

DV will make your system a bit slow, heavy, laggy.

If you find your computer behave in this way, you think that you have enabled DV properly.

 

[miqballin]

It still feels normal like the last time I did it and you mentioned that last time it wasn't enabled properly :/

I don't know what to do. I followed the steps thoroughly.

 

[miqballin]

It has been a while since I posted. I received a BSOD yesterday. While running SF Diag. Tool I also received an error. I have attached a screenshot of it. It seemed like it still collected all the files even with the error showing up.

Any help would be appreciated.

 

[Arc]

It is almost 4 months passed :sarc:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880053e047f, fffff88005be38b8, fffff88005be3110}

[COLOR=Red]Probably caused by : dxgmms1.sys[/COLOR] ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+8f )

Followup: MachineOwner
---------

So it is something to do with the display. Apply the latest version of nVidia display driver.
You may download it directly, from our forum link http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html; or you may opt for the Option 2 of Drivers- Download NVIDIA Drivers for “Automatically find drivers for my NVIDIA products” (it requires java installed).

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Clean up the dust accumulated inside the computer, specially around the air vents and fan grills.

Also, the BIOS may be a good reason of it .....

BiosVendor = American Megatrends Inc.
BiosVersion = 0801   
[COLOR=Red]BiosReleaseDate = 08/20/2010[/COLOR]

Plan to update it.

 

[miqballin]

Thank you for the fast reply.

A few questions;

So I ran the Stress Test with Fumark and closed it (pressed Esc.) when the temperature hit around 90 celcius. That's what I was supposed to do correct?

Also, the BIOS version I have is the latest according to the manufacturer's website (ASUS - - ASUS M4A78L-M)

I have Speccy running at the moment and will take a screenshot in a few hours. As well, I will be running the memtest overnight tonight.

Edit: I already have the latest display driver; updated it a couple days ago.

 

[Arc]

As per the last dump, your display driver is not latest, that one is released on 18th of this month.

If furmark goes upto 90 degrees, there is overheating, and you must need additional cooling mechanism.

About the BIOS, I am not sure.

 

[miqballin]

Received another one yesterday.

The screenshot of Speccy from the other day is attached as well. I haven't run memtest yet because I was busy with some things on the PC but plan to do it real soon.

 

[Arc]

We need the results of the memtest. Also, your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[miqballin]

Received a BSOD with DV enabled. I have attached the .rar file. The memtest results will be posted soon. Apologies for not getting them in quicker. Thank you.

 

[Arc]

No apologies are needed ... you will do it only when you have time to do it.

Anyway, your latest (verifier enabled) crash dump is also kinda weird ...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 19[/COLOR], {20, fffffa80071f4760, fffffa80071f4760, 4000016}

GetPointerFromAddress: unable to read from fffff800030b9100
GetUlongFromAddress: unable to read from fffff800030b91c0

fffffa80071f4760 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...

GetUlongFromAddress: unable to read from fffff80003027a38
[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MiDeleteControlArea+44 )

Followup: MachineOwner
---------

It comes with a bugcheck code 19, that means it is a bad pool header, should be caused by a device driver; but it says tht it is caused by memory corruption.

I guess in this point that yours in a hardware issue, and the memtest will help us to decide the further steps.

 

[miqballin]

Ran memtest overnight. Went for at least a dozen passes, can't remember exactly. At the bottom it stated 'No Errors'.

What should I try next?

Thank you.

 

[Arc]

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Disc Check:

1. Update your SSD's Firmware (skip it, if you are not using a SSD)
2. Reseat the sata and power.
   
   
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Also, you may need to try with another PSU .... as a test.