BSOD playing Steam Games

nsfryer · 27 Dec 2014

Steam keeps crashing my PC. I have a suspicion it has something to do with the way Steam is transmitting data in online games. I can play anything from DOTA2 to StarMade and encounter the same issue. Thanks in advance for any help!

koolkat77 · 29 Dec 2014

Code:


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


Loading Dump File [C:\Users\admin\Downloads\New folder\nsfryer\SF_27-12-2014\122714-30700-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
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03297890
Debug session time: Sun Dec 28 08:09:02.426 2014 (UTC + 6:00)
System Uptime: 0 days 0:10:32.612
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800030cd9ed, fffff8800b38fef0, 0}

*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by : aswSnx.sys ( aswSnx+3661 )

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

Caused by Avast!. Please remove avast and replace with MSE.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Keep us posted.

nsfryer · 31 Dec 2014

Sorry haven't responded sooner. Haven't been home much the last few days.

Uninstalled Avast, installed MSE and Malwarebytes per instructions, still BSOD :/ . New logs uploaded.

koolkat77 · 31 Dec 2014

Code:

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


Loading Dump File [C:\Users\USER\Downloads\Compressed\nsfryer_30-12-2014\nsfryer_30-12-2014\123014-27768-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
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03009000 PsLoadedModuleList = 0xfffff800`0324c890
Debug session time: Wed Dec 31 10:50:18.745 2014 (UTC + 6:00)
System Uptime: 0 days 0:12:41.932
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {6, fffffa80054fbd28, ffffff02, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000006, USBBUGCODE_BAD_SIGNATURE An Internal data structure (object)
	has been corrupted.
Arg2: fffffa80054fbd28, Object address
Arg3: 00000000ffffff02, Signature that was expected
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF88002F92FB0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8000307ebc0

STACK_TEXT:  
fffff880`02f92df0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


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:  ZEROED_STACK

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

Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier

Simply follow the instructions on tutorial:

Driver Verifier - Enable and Disable

nsfryer · 04 Jan 2015

Sorry this took so long Koolkat77. I wasn't near my PC for the holiday.

Ran Verifier for 48 hours, only one BSOD while trying to play StarMade.

koolkat77 · 04 Jan 2015

Code:


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


Loading Dump File [C:\Users\USER\Downloads\Compressed\nsfryer_04-01-2015\nsfryer_04-01-2015\010415-23088-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
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03003000 PsLoadedModuleList = 0xfffff800`03246890
Debug session time: Mon Jan  5 08:09:15.256 2015 (UTC + 6:00)
System Uptime: 3 days 9:37:01.919
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80003085ca1, fffff880061db398, fffff880061dabf0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80003085ca1, The address that the exception occurred at
Arg3: fffff880061db398, Exception Record Address
Arg4: fffff880061dabf0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MmAccessFault+e81
fffff800`03085ca1 498d442450      lea     rax,[r12+50h]

EXCEPTION_RECORD:  fffff880061db398 -- (.exr 0xfffff880061db398)
ExceptionAddress: fffff80003085ca1 (nt!MmAccessFault+0x0000000000000e81)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000003
Attempt to read from address 0000000000000003

CONTEXT:  fffff880061dabf0 -- (.cxr 0xfffff880061dabf0)
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000003
rdx=fffff8a00afdf000 rsi=0000000000000000 rdi=0000000000000001
rip=fffff80003085ca1 rsp=fffff880061db5d0 rbp=fffff880061db640
 r8=fffff800032b3600  r9=0000000fffffffff r10=0000000000000000
r11=fffff781c0000488 r12=fffffa80077fd8b0 r13=fffff8a00afdf5d8
r14=fffff800032b3600 r15=0000000000000110
iopl=0         nv up ei pl zr ac po cy
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010257
nt!MmAccessFault+0xe81:
fffff800`03085ca1 498d442450      lea     rax,[r12+50h]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000003

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b0100
GetUlongFromAddress: unable to read from fffff800032b01c0
 0000000000000003 Nonpaged pool

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c
fffff880`13023eb0 4939040a        cmp     qword ptr [r10+rcx],rax

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

TRAP_FRAME:  fffff880061db730 -- (.trap 0xfffff880061db730)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000048472 rbx=0000000000000000 rcx=fffff8a00afdf5a8
rdx=0000000000000006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88013023eb0 rsp=fffff880061db8c8 rbp=0000000000000000
 r8=0000000000000006  r9=0000000000000007 r10=0000000000000030
r11=fffffa8007ee33d8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c:
fffff880`13023eb0 4939040a        cmp     qword ptr [r10+rcx],rax ds:fffff8a0`0afdf5d8=707b040000000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003076cee to fffff80003085ca1

STACK_TEXT:  
fffff880`061db5d0 fffff800`03076cee : 00000000`00000000 fffff8a0`0afdf5d8 00000000`00000000 fffff8a0`0cdab7a0 : nt!MmAccessFault+0xe81
fffff880`061db730 fffff880`13023eb0 : fffff880`13021162 fffff8a0`0cdab7a0 fffffa80`08db97b0 fffffa80`07ee2000 : nt!KiPageFault+0x16e
fffff880`061db8c8 fffff880`13021162 : fffff8a0`0cdab7a0 fffffa80`08db97b0 fffffa80`07ee2000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+0x4c
fffff880`061db8d0 fffff880`1301e9d3 : 00000000`00000000 fffffa80`070ed020 00000000`00000016 fffffa80`070f5068 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xda
fffff880`061db910 fffff880`130387d9 : 00000000`00000000 fffff8a0`05426c50 fffffa80`00000000 fffffa80`04e79d70 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`061dbae0 fffff880`13038514 : fffff800`00b94080 fffff880`13037f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`061dbcd0 fffff880`13038012 : 00000000`00000000 fffffa80`06f0f010 00000000`00000080 fffffa80`039b7010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`061dbd00 fffff800`0331473a : 00000000`0640f277 fffffa80`077fd8b0 fffffa80`039f0890 fffffa80`077fd8b0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`061dbd40 fffff800`030698e6 : fffff800`031f3e80 fffffa80`077fd8b0 fffff800`03201cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`061dbd80 00000000`00000000 : fffff880`061dc000 fffff880`061d6000 fffff880`061db2c0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

STACK_COMMAND:  .cxr 0xfffff880061dabf0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+4c

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

Do you have on-board graphics? You could use it.

Unplug and remove your graphics card to test.

nsfryer · 05 Jan 2015

Yeah I have on-board graphics. Will remove my card and test. Am I just looking to see if I don't BSOD again?

koolkat77 · 06 Jan 2015

nsfryer said:

Am I just looking to see if I don't BSOD again?

Kinda

nsfryer · 14 Jan 2015

Ran with on-board graphics for a few days. Wasn't capable of running too much but I didn't BSOD. Cleaned my case since it was open, plugged my card back in, ran fine for a day and got BSOD again last night. :/ Has ran stable so far this evening though.

nsfryer · 24 Jan 2015

After two weeks, these are my new dump logs. Typically a few days in between events, then today (1/23/15) i get 4 bsods in the span of two hours. >.<