One of the errors is in Video Memory Management (STOP 0x10E: BSOD Index) Also, the error next to it also has memory as a cause (STOP 0x109: BSOD Index) as does another one (STOP 0xBE: BSOD Index). Of the rest of the errors, there's a lot of memory issues and issues with your video. Please try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Also, please update this older driver to the latest Win7 version: jraid.sys Mon Nov 03 21:20:09 2008
It's a component of your JMicron RAID controller.
Here's a summary of the BSOD's:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 26 16:13:00.064 2010 (GMT-5)
System Uptime: 0 days 7:45:54.718
BugCheck 3B, {c0000005, fffff88003bc1507, fffff880054cdbf0, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Fallout3.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 27 02:18:51.824 2010 (GMT-5)
System Uptime: 0 days 9:07:41.478
BugCheck 50, {fffff88009106010, 0, fffff88003b87cee, 2}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 28 03:26:44.362 2010 (GMT-5)
System Uptime: 0 days 19:24:54.892
BugCheck 10E, {1f, fffff8a00a9fe5f0, 0, 326f84}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan 28 23:51:47.347 2010 (GMT-5)
System Uptime: 0 days 11:40:00.002
BugCheck 109, {a3a039d89767a899, 0, 3cee2079b59f222a, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 29 11:41:58.347 2010 (GMT-5)
System Uptime: 0 days 2:34:14.002
BugCheck A, {fffffa0000a987a0, 2, 0, fffff80002c8a055}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+1d5 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 29 22:55:40.647 2010 (GMT-5)
System Uptime: 0 days 10:19:39.176
BugCheck 50, {fffffa804d70746c, 0, fffff88003b58944, 5}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckGPUTimeout+0 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 29 23:09:07.586 2010 (GMT-5)
System Uptime: 0 days 0:12:27.240
BugCheck BE, {fffff9600012d2e0, 24a000010a5ba021, fffff880083717c0, b}
Probably caused by : win32k.sys ( win32k!HMFreeObject+6c )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: java.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 30 01:07:50.503 2010 (GMT-5)
System Uptime: 0 days 0:41:55.157
BugCheck 50, {fffffa0003d3f6e8, 0, fffff8800ff94a9c, 7}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+e1a9c )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Fallout3.exe