BSOD playing SWTOR or Battlefield 3 even after fress Win 7 install

Security Software (this is just to check that it is installed and running properly; nothing needs to be done with this information at this time):

Code:

msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	996	8	200	1380	4/20/2012 4:12 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	3796	8	200	1380	4/20/2012 4:12 PM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	1736	8	200	1380	4/20/2012 4:12 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\pktgumby\SevenForums Files\Windows7_Vista_jcgriff2\Windows7_Vista_jcgriff2\042012-8174-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`03058650
Debug session time: Fri Apr 20 17:11:16.060 2012 (UTC - 6:00)
System Uptime: 0 days 0:17:00.888
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e88b85, fffff88009fb1530, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e88b85, Address of the instruction which caused the bugcheck
Arg3: fffff88009fb1530, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02e88b85 498b08          mov     rcx,qword ptr [r8]

CONTEXT:  fffff88009fb1530 -- (.cxr 0xfffff88009fb1530)
rax=00000001fc250004 rbx=0000000000000000 rcx=fffff90000000a40
rdx=fffdf900c2b6d101 rsi=0000000000000014 rdi=0000000000000021
rip=fffff80002e88b85 rsp=fffff88009fb1f10 rbp=fffff90000000a40
 r8=fffdf900c2b6d100  r9=fffff80002e14000 r10=fffff90000000a40
r11=fffff900c0081058 r12=fffff880042ebcc0 r13=0000000000000000
r14=0000000000000002 r15=000000006f746547
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02e88b85 498b08          mov     rcx,qword ptr [r8] ds:002b:fffdf900`c2b6d100=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  LCDClock.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fbea30 to fffff80002e88b85

STACK_TEXT:  
fffff880`09fb1f10 fffff800`02fbea30 : fffffa80`0be14b30 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16
fffff880`09fb1f20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x950


FOLLOWUP_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02e88b85 498b08          mov     rcx,qword ptr [r8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

STACK_COMMAND:  .cxr 0xfffff88009fb1530 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

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

Your crashes are all Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION which could mean your graphics card drivers are corrupted or out of date. Re-install or install the latest drivers for your display card. Use the following method to re-install the drivers.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Click Control Panel
4. Click Uninstall a program
5. For NVIDIA:
   • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
   • Restart your computer
   • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
   • If any remain of the above, uninstall one at a time
   • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
6. Restart your computer after uninstalling drivers for all display cards
7. Install the latest driver for the display cards once Windows starts

Thank you for taking the time to try and help me, and for at least helping me narrow down my focus.

I am currently running the most recent drivers from Nvidia. I have also tried using older versions as well, but the crashes still occur.

I updated my BIOS to the latest version, and that helped for about a day, but the next day the crashes immediately came back. I am now back to running just one stick of RAM, and again, it appears to be working. However, this has happened in the past and they ended up coming back.

Yep, keeps crashing with one stick of RAM (either one), and with the newest drivers from Nvidia, and even when uninstalling the Nvidia drivers and letting Windows install its own drivers. I am attaching all of the newest crash dump files.

I would recommend some more hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest

Also, when you say you ran MEMTEST, do you mean Memtest86+, or MEMTEST?

• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

I thought I had solved the issue with doing some more driver updates, but no luck. Still crashed. When running a torture test with Prime 95, I was able to get it to crash. I rebooted and ran it again, and it stopped itself showing 1 error this time:
[Fri Apr 27 00:33:42 2012]
FATAL ERROR: Rounding was 0.498046875, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4995117188, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.49609375, expected less than 0.4
Hardware failure detected, consult stress.txt file.

Sound like a hardware problem? I was running the option for "In-place large FFTs (maximum heat, power consumption, some RAM tested).

I was monitoring temps, and CPU and GPU never got much higher than 60C. So it's not a heat issue, but maybe either bad RAM (which showed no errors in Memtest86+) or possibly bad PSU? Looking at Hardware Monitor, it shows my 12V rails to be way below 12V. I've heard software monitors are not very effective in showing the correct voltage. I'm attaching a screenshot of the voltages. I have not done any overclocking with this system yet.

That appears to be likely a CPU problem. It could also be memory related, but highest likelihood is CPU. Do you get any errors with the other Prime95 tests, or only with the large FFTs?

usasma is better at diagnosing the Prime95 messages than I am. See what he had to say for someone with similar errors in post #14 of BSOD "driver_irql_not_less_or_equal" and "irql_not_less_or_equal".

I ran the Intel Processor Diagnostic Tool 3 times, and passed each time. I'm now doing more Prime95 tests while running one stick of RAM at a time. I seem to be having more issues with one stick, so I'm starting to think it is the RAM again.

You say you have more issues with one stick than the other. Does that mean you have issues with each stick regardless of which stick, but you have more issues with one? Or does that mean you have no issues with one stick, but you have issues with the other?

Just want to make sure I am clear on what you mean.