BSOD when playing games, IRQL_NOT_LESS_OR_EQUAL

This happens to games I play, most recently Blacklight Retribution.

I have ran memtest86+ (said it passed), chkdsk (no errors), uninstalled nvidia drivers using DDU and reinstalling the stable driver, made sure my RAM was securely locked in, and can't figure it out.

I ran FurMark to see if my graphics card was overheating and it stayed at 74C (my cards max temp is 98C).

Alot of the games I play will crash to desktop or BSOD with IRQL_NOT_LESS_OR_EQUAL.

My Steam folder is installed on my other internal hard drive (not the one with the Windows 7 install).

I thought it could've been my PSU so I went out and bought a 850W one.

Im beginning to become really frustrated as I just built this computer, primarily for gaming.

I did a fresh Windows install earlier today hoping it would help but I'm still getting this same problem.

I wonder if its a program I installed but have no idea.

Any help would be greatly appreciated. I'm tearing my hair out at this point.

EDIT: Crashed again overnight, I was downloading Guild Wars 2 and was sleeping so I couldn't see the BSOD.
Crashed again with SYSTEM_SERVICE_EXCEPTION while playing Guild Wars 2
Also again with MEMORY MANAGEMENT while playing Blacklight Retribution

Hi sinisterideals.

First, 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.

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

Code:

BugCheck A, {fffff880091a4830, 0, 1, fffff800030aa740}

Probably caused by : memory_corruption ( nt!MiDeletePteRun+50 )

Followup: MachineOwner
-------------------------------------------------------------------------------------
BugCheck 50, {ffffe8a00f6122f0, 0, fffff800033c5867, 7}

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+e7 )

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

It appears to be a hardware issue, and the notion goes to the GPU initially.

Alongwith memtest 86+, take the following tests too .....

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

Stress test the CPU.
Hardware - Stress Test With Prime95

Also ...... are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

And, what is the wattage of the PSU?
_________________________________________________

Code:

BugCheck 3B, {c000001d, fffff80002a88986, fffff8800aa48cd0, 0}

Probably caused by : hardware ( nt!KeFlushMultipleRangeTb+1f6 )

Followup: MachineOwner
--------------------------------------------------------
BugCheck 50, {ffffea800d4056c0, 0, fffff8800fd9b40c, 7}

Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+398 )

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