Windows 7: Starcraft 2 BSOD after 10-30 minutes

jordon106 · 22 Apr 2011

System specs:
Windows 7 ultimate x64 bit
Processor: AMD Phenom(tm) II X4 965 Processor (4 CPUs), ~3.4GHz
Memory: 8192MB RAM
DirectX Version: DirectX 11
Card name: ATI Radeon HD 4290
Harddrive: SAMSUNG HD103SJ ATA Device

MiniDump attached to the post:

Thanks in Advanced,
Jordon.

zigzag3143 · 22 Apr 2011

Quote: Originally Posted by jordon106

System specs:
Windows 7 ultimate x64 bit
Processor: AMD Phenom(tm) II X4 965 Processor (4 CPUs), ~3.4GHz
Memory: 8192MB RAM
DirectX Version: DirectX 11
Card name: ATI Radeon HD 4290
Harddrive: SAMSUNG HD103SJ ATA Device

MiniDump attached to the post:

Thanks in Advanced,
Jordon.

Hi Jordon

These were caused by a memory double fault exception (probably caused by a driver)

I would run memtest to test the ram and driver verifier to find which driver it is

1- Memtest

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

2-driver verifier

Quote:

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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

jordon106 · 22 Apr 2011

Quote: Originally Posted by zigzag3143

Quote: Originally Posted by jordon106

System specs:
Windows 7 ultimate x64 bit
Processor: AMD Phenom(tm) II X4 965 Processor (4 CPUs), ~3.4GHz
Memory: 8192MB RAM
DirectX Version: DirectX 11
Card name: ATI Radeon HD 4290
Harddrive: SAMSUNG HD103SJ ATA Device

MiniDump attached to the post:

Thanks in Advanced,
Jordon.

Hi Jordon

These were caused by a memory double fault exception (probably caused by a driver)

I would run memtest to test the ram and driver verifier to find which driver it is

1- Memtest

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

2-driver verifier

Quote:

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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Hey Zigzag, ive done the driver verifier just now and it done a bsod on start, then restarted couldnt even see what it said really something about driver taking up to much memory? then on restart it all ran fine and has been now for 2 hours.. and ive been putting it under pressure on starcraft 2, im sure i will get a bsod sooner or later though, anything else you would suggest? are my drivers not updated enough?

Thanks, Jordon.

zigzag3143 · 22 Apr 2011

Lets wait until Driver Verifier crashes. When it does please upload the resultant DMPS.

jordon106 · 22 Apr 2011

Quote: Originally Posted by zigzag3143

Lets wait until Driver Verifier crashes. When it does please upload the resultant DMPS.

this is the first dump file it put out when the login screen came and it BSOD the first time i restarted after verifier.

Thanks, Jordon.

jordon106 · 23 Apr 2011

just got another BSOD here it is.

zigzag3143 · 23 Apr 2011

Quote: Originally Posted by jordon106

just got another BSOD here it is.

This one was driver verified and was caused by your video 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.

Code:

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


Loading Dump File [C:\Users\K\Desktop\042311-22479-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0204e000 PsLoadedModuleList = 0xfffff800`0228be50
Debug session time: Sat Apr 23 13:34:35.397 2011 (GMT-4)
System Uptime: 0 days 4:26:26.458
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a014f0f4a0, 0, fffff88007c1d2eb, 2}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b )

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

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: fffff8a014f0f4a0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88007c1d2eb, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800022f60e0
 fffff8a014f0f4a0 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b
fffff880`07c1d2eb 488b38          mov     rdi,qword ptr [rax]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x50

PROCESS_NAME:  SC2.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800dffc0a0 -- (.trap 0xfffff8800dffc0a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a014f0f4a0 rbx=0000000000000000 rcx=0000000000000473
rdx=0000000007840380 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007c1d2eb rsp=fffff8800dffc230 rbp=fffff8800dffca40
 r8=fffffa800a0f9380  r9=0000000000000002 r10=0000000000000025
r11=0000000080011cc0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x39b:
fffff880`07c1d2eb 488b38          mov     rdi,qword ptr [rax] ds:0003:fffff8a0`14f0f4a0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000213d8f2 to fffff800020be740

STACK_TEXT:  
fffff880`0dffbf38 fffff800`0213d8f2 : 00000000`00000050 fffff8a0`14f0f4a0 00000000`00000000 fffff880`0dffc0a0 : nt!KeBugCheckEx
fffff880`0dffbf40 fffff800`020bc82e : 00000000`00000000 00000000`00000000 fffff6fc`00000000 fffff6fb`7e2803d0 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`0dffc0a0 fffff880`07c1d2eb : c7687d8a`c76ae961 c76ffe80`c76ffe80 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0dffc230 fffff880`07c033e7 : fffffa80`0858d901 fffffa80`0786e560 00000000`07840380 fffff880`000000dc : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x39b
fffff880`0dffc320 fffff880`07d55f12 : 43e00000`00000000 00000000`00000200 fffff880`0dffca40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`0dffc370 fffff880`07d556d7 : fffff8a0`00000001 fffff8a0`0d4d09a0 fffff880`0dffc9f0 00000000`00000003 : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`0dffc980 fffff960`0022de7e : 00000000`0846e6b0 00000000`00000200 00000000`00000600 fffff8a0`0dbaa000 : dxgkrnl!DxgkRender+0x3e7
fffff880`0dffcbf0 fffff800`020bd993 : fffffa80`095d9840 00000000`000002d4 00000000`00000000 fffffa80`0a1c84c0 : win32k!NtGdiDdDDIRender+0x12
fffff880`0dffcc20 00000000`7388143a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0846e688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7388143a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b
fffff880`07c1d2eb 488b38          mov     rdi,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0x50_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b

BUCKET_ID:  X64_0x50_VRF_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b

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

jordon106 · 24 Apr 2011

Hi there Zigzag,

i reinstalled the video card driver and removed all traces with the program suggested but still come accross the dxgmms1.sys bsod among others i think, dont have the files to hand but what would you suggest? which drivers should i install im lost hehe.

Thanks, Jordon.

zigzag3143 · 24 Apr 2011

Quote: Originally Posted by jordon106

Hi there Zigzag,

i reinstalled the video card driver and removed all traces with the program suggested but still come accross the dxgmms1.sys bsod among others i think, dont have the files to hand but what would you suggest? which drivers should i install im lost hehe.

Thanks, Jordon.

If you removed the past driver like this

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.

And installed the newest driver for the video card (ATI Radeon HD 4290) from them and you are still getting the directX BSOD's you may have a card problem, heat, power, etc.

I would run system file check to verify and repair you OS

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

Might also want to re-install direct X

jordon106 · 25 Apr 2011

Hey Zigzag,

i have done the SFC /SCANNOW, and used driver sweeper to uninstall the old drivers and put the new drivers on with no change, i havnt tried to uninstall Direct X and update it yet but this is defiantly something i will do, also the SFC /SCANNOW showed no errors and all was well.

Thanks, Jordon.

Windows 7: Starcraft 2 BSOD after 10-30 minutes

Starcraft 2 BSOD after 10-30 minutes problems?