BSOD when playing games

[rumbleiv]

I have been getting BSOD frequently. It usually only happens when I am playing games such as: Rust and League of Legends. I get them multiple times a day.

 

[Arc]

Hi rumbleiv.

It appears that it is BSODing not only in games but also in other applications too (like Skype); and with various different bugcheck codes.

[COLOR=Red]BugCheck 1E[/COLOR], {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeWaitForMultipleObjects+bb )

Followup: MachineOwner
------------------------------------------------------------------------------
[COLOR=Red]BugCheck 3B[/COLOR], {c0000005, fffff80002e7f6ca, fffff88008217760, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+2aa )

Followup: MachineOwner
-------------------------------------------------------------------------------
[COLOR=Red]BugCheck 7F[/COLOR], {8, 80050031, 6f8, fffff80002f0114e}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : amdppm.sys ( amdppm+37f2 )

Followup: MachineOwner
---------------------------------------------------------------------------------
[COLOR=Red]BugCheck 7F[/COLOR], {8, 80050031, 6f8, fffff80002eb014e}

Probably caused by : memory_corruption ( nt!MiUnlockProtoPoolPage+42 )

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

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, 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.

 

[rumbleiv]

Is it okay to do my usual things while DV is on? such as play games?

EDIT: Did the memtest thing and when I tried to boot my USB from my BIOS all i got was a black screen with a white _ blinking.

 

[rumbleiv]

bump would like to get this working tonight so i can run it overnight

 

[Arc]

If you cannot boot into the desktop after enabling DV, boot into safe mode and disable DV.

Then free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Now reboot into normal mode. Enable verifier again. Make it sure that you are not selecting any driver provided by "microsoft", "macrovision", "brother" and "unknown". Hopefully this time DV will work perfectly.

With DV enabled, run the computer normally (though it will become slow and laggy). Specially do the most crash prone actions. Try to replicate the previous BSODs.

 

[rumbleiv]

If you cannot boot into the desktop after enabling DV, boot into safe mode and disable DV.

Then free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Now reboot into normal mode. Enable verifier again. Make it sure that you are not selecting any driver provided by "microsoft", "macrovision", "brother" and "unknown". Hopefully this time DV will work perfectly.

With DV enabled, run the computer normally (though it will become slow and laggy). Specially do the most crash prone actions. Try to replicate the previous BSODs.

It's not DV that wasn't working, it's the memtest thing that wasn't working. it just showed a blank screen with a blinking _

 

[rumbleiv]

should i just skip straight to dv

 

[Arc]

I am not understanding what you are saying. Are you typing form a phone? Can you complete the sentences?

 

[rumbleiv]

You told me this to test the ram modules using the memtest. I put the files onto an empty USB however when I tried booting the USB, I got a blank black screen with a flashing underscore. Should I just skip the memtest and go straight to the driver verify?

 

[Arc]

No ... memtest is important.

If you cannot make a bootable USB, use a CD.