BSOD everytime I try to play any games.

Seahawk, have you run Memtest86+? If not, please download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7. Boot from the CD, and leave it running for at least 7 passes.

Here the error codes from your latest two dump files. Both are hardware error codes.

STOP 0x00000116: VIDEO_TDR_ERROR

Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Please read these two threads for information on stop error code 116: [2-Int] STOP 0x116: VIDEO_TDR_ERROR troubleshooting

https://www.sevenforums.com/crashes-d...tml#post280172

Here are the dumps:

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_DMP.zip\Windows7_BSOD_jcgriff2\081010-20280-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e91e50
Debug session time: Tue Aug 10 00:51:05.175 2010 (GMT-4)
System Uptime: 0 days 0:21:28.314
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, a2000000, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )

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

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 00000000a2000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  a

LAST_CONTROL_TRANSFER:  from fffff8800433422f to fffff80002cc4600

STACK_TEXT:  
fffff880`02f1b468 fffff880`0433422f : 00000000`00000119 00000000`00000001 00000000`a2000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b470 fffff880`05336eb9 : fffff880`02f1bb10 00000000`a2000000 00000000`00000000 00000000`00000000 : watchdog!WdLogEvent5+0x11b
fffff880`02f1b4c0 fffff880`053371c3 : fffffa80`0b463000 fffff880`02f1b5c0 00000000`000011ac fffff880`02f1b5c0 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`02f1b4f0 fffff880`05336f76 : fffffa80`000093e1 fffff880`0533a75c fffffa80`0b463000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x23b
fffff880`02f1b540 fffff880`0523e13f : fffffa80`09e64040 fffffa80`0614cba8 00000000`00000002 fffffa80`064378e0 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`02f1b570 fffff880`040407ab : fffffa80`0c0fec20 fffffa80`09e714c0 fffffa80`09e58340 fffffa80`0b47a000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`02f1b5a0 fffffa80`0c0fec20 : fffffa80`09e714c0 fffffa80`09e58340 fffffa80`0b47a000 00000000`00000002 : atikmpag+0x47ab
fffff880`02f1b5a8 fffffa80`09e714c0 : fffffa80`09e58340 fffffa80`0b47a000 00000000`00000002 000093e1`a2000000 : 0xfffffa80`0c0fec20
fffff880`02f1b5b0 fffffa80`09e58340 : fffffa80`0b47a000 00000000`00000002 000093e1`a2000000 00000001`00000000 : 0xfffffa80`09e714c0
fffff880`02f1b5b8 fffffa80`0b47a000 : 00000000`00000002 000093e1`a2000000 00000001`00000000 fffff880`04daf484 : 0xfffffa80`09e58340
fffff880`02f1b5c0 00000000`00000002 : 000093e1`a2000000 00000001`00000000 fffff880`04daf484 00000000`00000000 : 0xfffffa80`0b47a000
fffff880`02f1b5c8 000093e1`a2000000 : 00000001`00000000 fffff880`04daf484 00000000`00000000 fffffa80`0b47a000 : 0x2
fffff880`02f1b5d0 00000001`00000000 : fffff880`04daf484 00000000`00000000 fffffa80`0b47a000 fffffa80`0b47ab10 : 0x93e1`a2000000
fffff880`02f1b5d8 fffff880`04daf484 : 00000000`00000000 fffffa80`0b47a000 fffffa80`0b47ab10 00000000`00000000 : 0x1`00000000
fffff880`02f1b5e0 00000000`00000000 : fffffa80`0b47a000 fffffa80`0b47ab10 00000000`00000000 00000000`000093e1 : atikmdag+0x359484


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`05336eb9 c744244053eeffff mov     dword ptr [rsp+40h],0FFFFEE53h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_DMP.zip\Windows7_BSOD_jcgriff2\081010-16270-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e93e50
Debug session time: Tue Aug 10 16:15:38.440 2010 (GMT-4)
System Uptime: 0 days 0:35:29.580
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0e349e8c0, 0, fffff80002cefcba, 5}

Unable to load image \SystemRoot\system32\DRIVERS\SiWinAcc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SiWinAcc.sys
*** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys

Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0e349e8c0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002cefcba, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efe0e0
 fffff8a0e349e8c0 

FAULTING_IP: 
nt!MmMapViewInSystemCache+3a
fffff800`02cefcba 4c8b20          mov     r12,qword ptr [rax]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800d448100 -- (.trap 0xfffff8800d448100)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0e349e8c0 rbx=0000000000000000 rcx=fffff8a0040f0fc0
rdx=fffffa80060e6e20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cefcba rsp=fffff8800d448290 rbp=fffff80002f00700
 r8=fffff8800d448438  r9=fffff8800d448440 r10=0000000000000000
r11=fffffa80063a66c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MmMapViewInSystemCache+0x3a:
fffff800`02cefcba 4c8b20          mov     r12,qword ptr [rax] ds:fffff8a0`e349e8c0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d45801 to fffff80002cc6600

STACK_TEXT:  
fffff880`0d447f98 fffff800`02d45801 : 00000000`00000050 fffff8a0`e349e8c0 00000000`00000000 fffff880`0d448100 : nt!KeBugCheckEx
fffff880`0d447fa0 fffff800`02cc46ee : 00000000`00000000 fffff880`009e7830 fffff800`02cd2a00 fffff880`009e7180 : nt! ?? ::FNODOBFM::`string'+0x40ecb
fffff880`0d448100 fffff800`02cefcba : fffffa80`0c769110 fffff800`02d37e90 00000000`00000000 fffff880`0d448310 : nt!KiPageFault+0x16e
fffff880`0d448290 fffff800`02cef2d7 : 00000000`00000000 fffff880`009e7830 fffff880`0d448438 fffff880`012e731a : nt!MmMapViewInSystemCache+0x3a
fffff880`0d448400 fffff800`02ce5170 : fffffa80`00000000 00000000`06520000 fffff800`02cd2a35 fffff880`00000000 : nt!CcGetVacbMiss+0x177
fffff880`0d4484c0 fffff800`02fe48d2 : 00000000`06500000 00000000`06520000 fffff880`0d448590 fffff880`0d448620 : nt!CcGetVirtualAddress+0x1b0
fffff880`0d448550 fffff880`01448fc0 : fffff8a0`00000000 00000000`00000005 00000000`00000000 00000000`00000001 : nt!CcCopyRead+0x132
fffff880`0d448610 fffff880`0144d303 : fffff8a0`080a4c70 fffff8a0`080a4c70 fffff880`0d448840 fffff880`0d448700 : Ntfs!NtfsCachedRead+0x180
fffff880`0d448670 fffff880`0144ff78 : fffffa80`064d0e40 fffffa80`065ac010 fffff880`0d448800 fffffa80`063f8d00 : Ntfs!NtfsCommonRead+0x583
fffff880`0d448810 fffff880`012e123f : fffffa80`065ac3f8 fffffa80`065ac010 fffffa80`063f8d30 00000000`00000001 : Ntfs!NtfsFsdRead+0x1b8
fffff880`0d4488c0 fffff880`012df6df : fffffa80`070f9360 fffffa80`065ac3f8 fffffa80`070f9300 fffffa80`065ac010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0d448950 fffff880`0133f02e : 00000000`00000000 fffff800`02cd11c1 fffffa80`0644cbc0 00000000`00000000 : fltmgr!FltpDispatch+0xcf
fffff880`0d4489b0 00000000`00000000 : fffff800`02cd11c1 fffffa80`0644cbc0 00000000`00000000 fffffa80`00000000 : SiWinAcc+0x102e


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
16 errors : !nt (fffff80002cef6c3-fffff80002cef77b)
fffff80002cef6c0  e9  b9  fd *f2  ff  90  90  90  90  90  90 *3f  48  89  5c  24 ...........?H.\$
fffff80002cef6d0  18  55  56 *37  41  54  41  55  41  56  41 *50  48  81  ec  00 .UV7ATAUAVAPH...
fffff80002cef6e0  01  00  00 *19  33  f6  45  33  c0  c7  44 *64  54  14  00  00 ....3.E3..DdT...
fffff80002cef6f0  00  44  89 *20  24  50  83  f9  40  0f  87 *7e  03  00  00  41 .D. $P..@..~...A
...
fffff80002cef740  44  24  40 *56  48  8b  1c  25  20  00  00 *51  0f  ba  25  f0 D$@VH..% ..Q..%.
fffff80002cef750  5e  16  00 *3c  45  8b  ce  45  8d  7e  01 *a9  82  f9  e2  04 ^..<E..E.~......
fffff80002cef760  00  4c  8b *db  24  48  01  00  00  44  8b *b1  24  40  01  00 .L..$H...D..$@..
fffff80002cef770  00  41  8a *00  44  01  bb  00  4b  00  00 *5e  8d  54  24  30 .A..D...K..^.T$0

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

I am still finding sptd.sys on your system. Even though this driver is updated, please uninstall it as was previously suggested while we are troubleshooting. We need to eliminate any potential source of conflict. Uninstall; do not update.

Please uninstall Eset while you are troubleshooting. Eset has been know to cause BSOD's on some Win 7 systems. Replace it with Microsoft Security Essentials. Once you get your system stable, you can try Eset again. However, I recommend that you stay with MSE.

You also still have outdated drivers:

AWOPFilterDriver.sys Thu Jun 25 09:54:47 2009 - I have no idea what this driver is affiliated with. You can navigate to C:\Windows\System32\Drivers and rename it from AWOPFilterDriver.sys to AWOPFilterDriver.bak This may disable some hardware. If so, you can simply rename it back to .sys.

intelsmb.sys Wed May 13 03:31:00 2009 - System Management Bus 2.0 (SMBus) Driver is a driver file from company Intel Corporation belonging to product Intel(R) SMBus Controller. Update this driver.

IOCBIOS.SYS Thu Jul 09 13:47:22 2009 - Overclocking Device Driver is a driver file from company Intel Corporation belonging to product Intel(R) Extreme Tuning Utility Performance Tuning Driver. If you are overclocking, stop and return settings to stock. Either update this utility on uninstall it.

SI3132.sys Wed Oct 03 14:39:29 2007 - this driver is extremely obsolete. It is a driver for Silicon Image SiI 3132 SATALink. Controller for Windows. Update this driver or uninstall the software/hardware it is affiliated with.

SiRemFil.sys Wed Jun 20 15:42:10 2007 - this driver is extremely obsolete. Filter driver for Silicon Image SATALink controllers belongs to the software SATALink External Device Filter by Silicon Image, Inc. Update or uninstall the software.

SiWinAcc.sys Thu Jun 14 20:02:02 2007 - this driver is extremely obsolete. Windows Accelerator Driver belongs to the software SATALink Accelerator Driver or SiWinAcc or SATALink Windows Accelerator by Silicon Image, Inc. Update or uninstall the software.

Follow all of my suggestions above and report back.

Hi,
Frankly, I don't know how to read the result but I saw this message a lot in the result "FATAL ERROR: Rounding was 0.5". I did some reading online and found that your CPU isn't stable and it could be due to overclocked (I know you said that you didn't overclock, but overclocking can give you that kind of error. You've said that you went to BIOS and set everything to optimal default setting, now please uninstall any overclocking software in your computer as Carl suggested above.

IOCBIOS.SYS Thu Jul 09 13:47:22 2009 - Overclocking Device Driver is a driver file from company Intel Corporation belonging to product Intel(R) Extreme Tuning Utility Performance Tuning Driver. If you are overclocking, stop and return settings to stock. Either update this utility on uninstall it.

One minidump blame your graphic card:

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Can you borrow a graphic card to try on your system?

BUGCHECK SUMMARY:

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff88004f5cf02, fffff88006fd7ab8, fffff88006fd7320}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiIncrementContextReference+16 )

Followup: MachineOwner
---------
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntoskrnl.exe ( nt+70740 )

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

Exception code fffffc000005 is memory exception. Can you please perform memtestx86 on cold boot please?

Regard,

Tuan

seahawkrox said:

CarlTR6 said:

Seahawk, have you run Memtest86+? If not, please download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7. Boot from the CD, and leave it running for at least 7 passes.

I ran this while I was sleeping. 7 passes at a little over 8 hours. No errors found.
I noticed that I have 9gb of ram, but under system at the control panel it says:
Installed memory (RAM): 9,00GB (5,99GB usable).
When I performed the memtest86 it also said I had 6GB of ram. Do you know why?

For the Silicon Image drivers, those are the latest ones. I downloaded from their website yesterday and the "date modified" of the files are from 2007.
I uninstalled sptd.sys and it isn't in my system anymore.
I had removed ESET already.

I am not overclocking anything on this computer, everything is default.
Let me try to play the another game again to get a BSOD.

Besides the games the system is running very smoothly, no BSOD while doing regular tasks, just when I try to play a game.

At least you have eliminated RAM as the source of the problem.

If Silicon Image does not have drivers later than 2007, that software is obsolete and not compatible with Win 7. Completely uninstall it. Those 2007 drivers are showing up in the dumps.

SI3132.sys Wed Oct 03 14:39:29 2007
SiRemFil.sys Wed Jun 20 15:42:10 2007
SiWinAcc.sys Thu Jun 14 20:02:02 2007

You will need to find software compatible with Win 7 to replace it.

Very good. Thanks for the update. I am glad you are running smoothly. Don't forget about those old drivers; they can come back to bite you. :)