BSOD Errors - Tried everything i could

[arjun111]

Hey there kind folks,
i am not super smart when it comes to computers but i am fairly okay at following steps,i have been facing bsod from past 5-6 days and have surfed endlessly on the net trying to do anything and everything i think i could but it hasnt been worth till now,so this is where i give up and request you guys to give me a hand

PC Config:
Win7 Ultimate
AMD Phenom II X6 1100T clocked at 3.30 GHz
ASUSTeK Computer INC. M4A88T-M Rev X.0x
8 GB total memory type DDR3
NVIDIA GeForce GTX 560
Harddrive ST500DM002-1BD142 from 465.76 GB SATA III
Realtek PCIe GBE Family Controller

I almost everytime get a BSOD while playing any game
Here is the stuff i have tried:
*Chkdsk
*Memory Test
*Updated drivers
*Error Checking
*Checking RAM individually by taking them out
*I have enabled Driver Verifier
*Uninstalled common BSOD causing softwares that i could find

I have added bsod viewer files & DM log in attatchments

I am open to experiments/suggestions,and thank you for taking the initiative to help me much appreciated

 

[Arc]

Hi arjun111. There are versatile bugchecks.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

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

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

If those tests do 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.
_________________________________________

BugCheck 4A, {7fefebc51fa, 2, 0, fffff880028dcca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

BugCheck 3B, {c0000005, fffff8000307bcfc, fffff88008b60c10, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeInsertQueueApc+18 )

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

BugCheck 1A, {5002, fffff70001080000, 2e3, a50002e2fffffffe}

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

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