BSOD while playing Steam games?

Always send the most current dump files.

Still looks like a driver. Was the computer running really rough with the verifier on?

Great do it for 36 hours. Use the computer as always. Then send all the dumps. If it does not give an answer, then at least we know it is time to look elsewhere.

You are very welcome.

No luck

Code:

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

Loading Dump File [C:\Users\Richard\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\VSTH60JY\SF_01-09-2012\SF_01-09-2012\083012-34928-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Invalid directory table base value 0x0
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image Unknown_Module_00000002`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000002`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000002`00000000
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e99670
Debug session time: Thu Aug 30 00:26:27.687 2012 (GMT-4)
System Uptime: 0 days 13:03:17.529
Unable to load image Unknown_Module_00000002`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000002`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000002`00000000
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP: 
+0
00000000`00000000 ??              ???
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002ccbbbe to fffff80002cd4190
STACK_TEXT:  
fffff800`00b9b3e8 fffff800`02ccbbbe : fffffa80`082e4018 00000000`000186a0 fffff800`00b9bb60 fffff800`02cff160 : 0xfffff800`02cd4190
fffff800`00b9b3f0 fffffa80`082e4018 : 00000000`000186a0 fffff800`00b9bb60 fffff800`02cff160 00000000`00000000 : 0xfffff800`02ccbbbe
fffff800`00b9b3f8 00000000`000186a0 : fffff800`00b9bb60 fffff800`02cff160 00000000`00000000 fffff800`02cfee2d : 0xfffffa80`082e4018
fffff800`00b9b400 fffff800`00b9bb60 : fffff800`02cff160 00000000`00000000 fffff800`02cfee2d fffff800`02eda770 : 0x186a0
fffff800`00b9b408 fffff800`02cff160 : 00000000`00000000 fffff800`02cfee2d fffff800`02eda770 fffff800`02e172f0 : 0xfffff800`00b9bb60
fffff800`00b9b410 00000000`00000000 : fffff800`02cfee2d fffff800`02eda770 fffff800`02e172f0 fffff800`02c55000 : 0xfffff800`02cff160

STACK_COMMAND:  kb
SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME:  Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP:  0
BUCKET_ID:  CORRUPT_MODULELIST
Followup: MachineOwner

You will see that it is inconclusive
It was not caused by the verifier. If you used it for 36 hours, could mean hardware. Test memory.
Run for 8 passes.
Then test each stick in a good slot for 6 passes.
If you have dual channel, the results may be incorrect, if shows pass.
Guide to using Memtest86+ - Geeks to Go Forums