BSOD everytime I try to play any games.

[seahawkrox]

Hello there,
I have a 2 month old Alienware Aurora and I am getting BSOD's within 1-5 minutes of playing Modern Welfare 2 and Battlefield: Bad Company 2.
At first I would get some BSOD's when the pc was sleeping, maybe every other day, but I didn't really care. Since I installed these 2 games I get BSOD's every single time I try to play them. I have updated the video card and network card drivers. I've also updated the BIOS.

My system specs are:
OS: Windows 7 Home Premium 64 bits
CPU: Intel Core i7-920 Processor (8MB L3 Cache, 1MB L2 Cache, 2.66GHz)
Motherboard: Alienware 0H869M
Ram: 9 GB Triple Channel DDR3 1067Mhz (6 DIMMs)
VGA: 2 GB Single ATI Radeon HD 5970, GDDR5
Network card: Killer Xeno Pro

Could you guys please help me?
I've attached the dump files and the system health report.
Thank you in advance.

 

[ttran]

Hi and welcome to SF!

I don't want to say this but this is probably hardware issue after I see a lot of stop code 124 and 50 in the DMPs with hardware is directly being blamed even though we still are unsure what piece of hardware is faulty, might be more than 1.
For the stop code 124, please read this article to know what it means and first basic steps to try:
http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html
Stop code 116 is graphic card issue. First approach is to update the driver. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.
Please read this article for few things to try to fix that stop code as well as some stress tests that are very benefit for you.
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html
SiWinAcc.sys was blamed in one DMP, it is your Silicon Image driver - comes with package for the SIxxx, it's date from 2007 is too old to run window 7 stably.

fffff880`01413000 fffff880`0142d000   SI3132   SI3132.sys   Thu Oct 04 01:39:29 2007 (4703E1E1)
fffff880`0187f000 fffff880`01887000   SiRemFil SiRemFil.sys Thu Jun 21 02:42:10 2007 (46798312)
fffff880`01498000 fffff880`014a1000   SiWinAcc SiWinAcc.sys Fri Jun 15 07:02:02 2007 (4671D6FA)

Even though the following stress tests are mentioned in the articles above, but I will post in again, make sure to run these stress tests:
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Furmak for your graphic card:
Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Now, let's eliminate some software that are known for potentially causing BSODs so that somehow it can make your computer less miserable:
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
Remove Eset Node32 for now and replace by Microsoft Security Essential:
How to uninstall or remove ESET Nod32 antivirus totally?

BUGCHECK SUMMARY:

BugCheck 50, {fffff6fa4006edc0, 0, fffff80002c80e75, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiInPageSingleKernelStack+a1 )

Followup: MachineOwner
---------
BugCheck 1A, {8886, fffffa8006d952a0, fffffa8006d472d0, 201}

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
Probably caused by : SiWinAcc.sys ( SiWinAcc+102e )

Followup: MachineOwner
---------
BugCheck 50, {ffffffff8348184d, 1, fffff80002c70ed6, 5}


Could not read faulting driver name
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+42f98 )

Followup: MachineOwner
---------
BugCheck 7F, {8, 80050033, 6f8, fffff80002c864e2}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
BugCheck 116, {fffffa800957b4e0, fffff880045a7c80, 0, 2}

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
Probably caused by : atikmpag.sys ( atikmpag+6c80 )

Followup: MachineOwner
---------
BugCheck 124, {0, fffffa800bf63038, 0, 0}

Probably caused by : hardware

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

Regard,

Tuan

 

[seahawkrox]

Hello there,
Thank you for all the information so far and for your time.
Basically this is what I've done:
I ran the FurMark test and the MG Video Memory Stress and had no problems on both.
I also ran the stress tests for the memory for 5 passes and everything came back good.
I ran the system file checker and a Hard Drive test and no errors were found.
I updated my vga driver to the latest version using the driver sweeper method you mentioned.
I uninstalled Daemon Tools and updated the SPTD application. Couple other applications I wasn't using were uninstalled also.
I am still getting BSOD when trying to play the games and the bccodes are: 50, 119, 7f and many others.
I am attaching the file with the DMPs, so you can see the newest ones I've had. Could you please take a look?
Thank you very much.

 

[ttran]

updated the SPTD application

Oh no, you don't update it, you uninstall it for me please. After removing Deamon tool, please open the tool I told you to download and click "Uninstall" for me please. You are trying to get rid of sptd.sys, not update it.

Secondly, I've not seen you remove Eset completely, because I still see it in the loaded driver. Please follow the instruction I gave you to completely remove it.

fffff880`01423000 fffff880`0143d000   SI3132   SI3132.sys   Thu Oct 04 01:39:29 2007 (4703E1E1)
fffff880`0187f000 fffff880`01887000   SiRemFil SiRemFil.sys Thu Jun 21 02:42:10 2007 (46798312)
fffff880`014a8000 fffff880`014b1000   SiWinAcc SiWinAcc.sys Fri Jun 15 07:02:02 2007 (4671D6FA)

I haven't seen you update the driver as required, Window 7 won't able to run on system that has driver at least 2 years old.

Final question, DID YOU OVERCLOCK ANYTHING? If so, please go to BIOS (F2 at startup) and hit reset everything to default.

I really suspect the graphic card, try to see if you can borrow a friend or somewhere different graphic card to try on yours, because the graphic card driver is still blamed and there are some stop codes that are potentially caused by graphic card. You can try to re-install graphic card driver again. Also update the directx as well:
Download details: DirectX End-User Runtime

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
---------
BugCheck 1A, {41287, 150b00001c, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42be5 )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002c99274, fffff880009a9968, fffff880009a91d0}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002cca805, fffff88003b2a618, fffff88003b29e80}

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )

Followup: MachineOwner
---------
BugCheck 7F, {8, 80050033, 6f8, fffff880016db2b0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
BugCheck C4, {91, 0, fffffa800c148060, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4904 )

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

Please do this and tell me the result:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Good Luck,

Tuan

 

[seahawkrox]

Thanks again for your time.
I uninstalled Eset and PSTD.
I also updated directx and the si3132.sys driver to version 1.0.15.6 but when I open driverview it still shows the version 1.0.15.0.
When I go under device manager I find Silicon Image SiI 3132 SATALink Controller
Driver date: 24/06/09 and Driver version: 1.0.15.6
The other 2 drivers I am having a hard time finding them.
I've looked on google and couldn't find any updates.
After completing all these updates I ran the system file checker and it came back with no errors.
I then tried to play the game again and the pc crashed within 5 seconds.
It didn't record on a dmp file.
The system is running fine, I am only getting BSOD when trying to play the games.

Should I give up and call the manufacter? I am still under warranty, the only problem is that I am currently in Brazil and didn't want to ship the pc back to the US since I am staying here for awhile.

Thank you for your help.

 

[ttran]

Have you tried to go to this website to download the newest driver? I believe they have all you need
Silicon Image - Support

Again, you haven't answer my question: Do you overclock anything? If you are unsure or you don't know, or if you know, just go to BIOS when startup and hit reset everything to default value. The symptom looks like overclocking or Overheating to me.

Use the SpeedFan - Access temperature sensor in your computer to keep track of your computer temperature please

 

[seahawkrox]

Have you tried to go to this website to download the newest driver? I believe they have all you need
Silicon Image - Support

Again, you haven't answer my question: Do you overclock anything? If you are unsure or you don't know, or if you know, just go to BIOS when startup and hit reset everything to default value. The symptom looks like overclocking or Overheating to me.

Use the SpeedFan - Access temperature sensor in your computer to keep track of your computer temperature please

Sorry about that,
I don't overclock anything. I loaded the optimal defaults values on the BIOS. I also have the ATI Overdrive option disabled for the video card.
I installed the SpeedFan software and so far all the temperatures are on the green.
On the Silicon Image website I downloaded the driver for my adapter, but it only updated the SI3132.sys. The other 2 I need to do some more research.
Should I try to change any settings on the BIOS?

I just noticed something, I have 9gb of ram, but under system at the control panel it says:
Installed memory (RAM): 9,00GB (5,99 usable)
Why is that?

Thank you again.

 

[ttran]

No need to change anything in BIOS, you said you did reset to default value, that sounds good.
It's possible that you might need to do a clean install of window 7, but before doing that, please enable driver verifier, then do everything that you like and wait for system to crash. Driver Verifier will flag bad drivers so that we can narrow down the cause. With a tons of stop codes above, it's hard to say which component of system are not working properly.

Follow this instruction:
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Regard,

Tuan

 

[seahawkrox]

I will try that when I wake up.
I will leave GIMPS running while I sleep to see what happens. The temperatures are high already, but so far no erros.
I just noticed something, I have 9gb of ram, but under system at the control panel it says:
Installed memory (RAM): 9,00GB (5,99 usable)
Why is that?
Have a good night.

 

[ttran]

I will ask for you about that because I've used such that large Ram amount. Good night and let us if anything happend

 

[seahawkrox]

Hello there again,
I got a BSOD bccode 50 white running GIMPS.
After it rebooted, windows warned me I might have RAM problems associated with 4 BSOD's I had. Computer restarted again and windows performed a memory check, it was a quick check that didn't return any errors.
I am attaching the dmp files again. The last one is from 08/10/2009 at 5:22 PM.

Thank you for your time again.

 

[CarlTR6]

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.

 

[CarlTR6]

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

http://www.sevenforums.com/crashes-debugging/25912-bsod.html#post280172

Here are the dumps:

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*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
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*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
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.

 

[seahawkrox]

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.

 

[seahawkrox]

I tried to play Battlefield: Bad Company 2 and got 2 BSODs. Could you please take a look at the last 2 dmp files? They are from 08/11/2010 3:52am and 3:57am.

Thank you for you guys time. I really appreciate it.

 

[seahawkrox]

I was running prime95 and I got some errors, my pc restarted but I didn't get a BSOD.
I am attaching the results.txt file.
Any ideas?
Thank you.

 

[ttran]

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:

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

 

[CarlTR6]

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.

 

[seahawkrox]

I solved the problem.
I removed 3 1gb dimms and I am running with only 3 2gb dimms.
So, instead of 9gb I am running my system with 6gb of RAM.
I played 3 hours of battlefield: bad company 2 with no BSODs.
Now I am going to wait to have those 1gb dimms replaced.
Thank you both for all the help.

 

[CarlTR6]

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.