BSOD playing Steam Games

nsfryer · Dec 27, 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 · Dec 29, 2014

Code:

[FONT="Lucida Console"]
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
---------
[/FONT]

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.

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Warning

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

Keep us posted.

nsfryer · Dec 31, 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 · Dec 31, 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 · Jan 4, 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 · Jan 4, 2015

Code:

[FONT="Lucida Console"]
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
---------

[/FONT]

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

Unplug and remove your graphics card to test.

nsfryer · Jan 5, 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 · Jan 6, 2015

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

Kinda

nsfryer · Jan 14, 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 · Jan 24, 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. >.<

koolkat77 · Jan 24, 2015

Code:

[FONT="Lucida Console"]Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\nsfryer_23-01-2015\nsfryer_23-01-2015\012315-32151-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`0328e890
Debug session time: Sat Jan 24 11:59:17.613 2015 (UTC + 6:00)
System Uptime: 0 days 0:23:50.784
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88001007ab7, fffff8800bc05620, 0}

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

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88001007ab7, Address of the instruction which caused the bugcheck
Arg3: fffff8800bc05620, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
fltmgr!FltpAllocateInitializeNameGenerationContext+d7
fffff880`01007ab7 488b4828        mov     rcx,qword ptr [rax+28h]

CONTEXT:  fffff8800bc05620 -- (.cxr 0xfffff8800bc05620;r)
rax=0000000004a6d010 rbx=fffffa8004a189c0 rcx=fffffa80071b2650
rdx=ffffffffffffffff rsi=fffffa80071b2650 rdi=fffffa8004a189c0
rip=fffff88001007ab7 rsp=fffff8800bc06000 rbp=fffffa80049bf860
 r8=0000000000000000  r9=0000000000000000 r10=fffff8800101e940
r11=0000000000000000 r12=fffff8800bc06198 r13=fffffa80052c6500
r14=fffffa80074cac28 r15=0000000000000000
iopl=0         ov up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010a87
fltmgr!FltpAllocateInitializeNameGenerationContext+0xd7:
fffff880`01007ab7 488b4828        mov     rcx,qword ptr [rax+28h] ds:002b:00000000`04a6d038=????????????????
Last set context:
rax=0000000004a6d010 rbx=fffffa8004a189c0 rcx=fffffa80071b2650
rdx=ffffffffffffffff rsi=fffffa80071b2650 rdi=fffffa8004a189c0
rip=fffff88001007ab7 rsp=fffff8800bc06000 rbp=fffffa80049bf860
 r8=0000000000000000  r9=0000000000000000 r10=fffff8800101e940
r11=0000000000000000 r12=fffff8800bc06198 r13=fffffa80052c6500
r14=fffffa80074cac28 r15=0000000000000000
iopl=0         ov up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010a87
fltmgr!FltpAllocateInitializeNameGenerationContext+0xd7:
fffff880`01007ab7 488b4828        mov     rcx,qword ptr [rax+28h] ds:002b:00000000`04a6d038=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  nmctxth.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from fffff8800102523b to fffff88001007ab7

STACK_TEXT:  
fffff880`0bc06000 fffff880`0102523b : fffffa80`052c6500 fffffa80`04a03a58 fffffa80`074cab70 fffffa80`074cac50 : fltmgr!FltpAllocateInitializeNameGenerationContext+0xd7
fffff880`0bc06070 fffff880`01024be9 : fffffa80`04a03a58 fffffa80`04a189c0 00000000`00000017 00000000`000007ff : fltmgr!FltpNormalizeNameFromCache+0x24b
fffff880`0bc06190 fffff880`01025f81 : 00000000`00000032 00000000`00000043 00000000`0000002d 00000000`00000000 : fltmgr!FltpExpandShortNames+0x239
fffff880`0bc061f0 fffff880`01025e1e : fffffa80`074cab70 fffff800`030a0000 00000000`00000000 fffff880`01014a00 : fltmgr!FltpGetNormalizedFileNameWorker+0xc1
fffff880`0bc06230 fffff880`01011b9d : c00000bb`08684000 00000000`00000000 fffffa80`070b7fb0 fffff880`0bc07000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`0bc06290 fffff880`0100bbf6 : fffffa80`04449100 fffffa80`070b74c0 fffffa80`04a6d108 fffffa80`07b1e630 : fltmgr!HandleStreamListNotSupported+0x15d
fffff880`0bc062d0 fffff880`01012b44 : 00000000`00000000 00000000`00000000 fffffa80`070b74c0 00000000`00000101 : fltmgr! ?? ::FNODOBFM::`string'+0x30f3
fffff880`0bc06350 fffff880`01089caf : fffffa80`074cab70 fffffa80`086840c0 fffff880`0bc06519 fffffa80`086840c0 : fltmgr!FltGetFileNameInformation+0x184
fffff880`0bc063e0 fffffa80`074cab70 : fffffa80`086840c0 fffff880`0bc06519 fffffa80`086840c0 fffff880`0bc065f8 : MpFilter+0x28caf
fffff880`0bc063e8 fffffa80`086840c0 : fffff880`0bc06519 fffffa80`086840c0 fffff880`0bc065f8 00000000`00000000 : 0xfffffa80`074cab70
fffff880`0bc063f0 fffff880`0bc06519 : fffffa80`086840c0 fffff880`0bc065f8 00000000`00000000 fffff880`0106c000 : 0xfffffa80`086840c0
fffff880`0bc063f8 fffffa80`086840c0 : fffff880`0bc065f8 00000000`00000000 fffff880`0106c000 fffffa80`078bfb30 : 0xfffff880`0bc06519
fffff880`0bc06400 fffff880`0bc065f8 : 00000000`00000000 fffff880`0106c000 fffffa80`078bfb30 fffff880`0bc065f8 : 0xfffffa80`086840c0
fffff880`0bc06408 00000000`00000000 : fffff880`0106c000 fffffa80`078bfb30 fffff880`0bc065f8 fffff880`01089b77 : 0xfffff880`0bc065f8


FOLLOWUP_IP: 
MpFilter+28caf
fffff880`01089caf ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  MpFilter+28caf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MpFilter

IMAGE_NAME:  MpFilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53bdfdba

STACK_COMMAND:  .cxr 0xfffff8800bc05620 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_MpFilter+28caf

BUCKET_ID:  X64_0x3B_MpFilter+28caf

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_mpfilter+28caf

FAILURE_ID_HASH:  {f0199ed5-4684-7f95-860a-ef19e92ee6a2}

Followup: MachineOwner
---------
[/FONT]

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Memtest should be done overnight.

nsfryer · Jan 24, 2015

Will run memtest while i'm at work today. It seems like I've gotten every error under the sun (antivirus, dx11, gfx drivers, memory) could this all be caused by one thing or do I have a whole host of issues here?

nsfryer · Jan 25, 2015

8 Passes, no errors. Any other ideas?

Arc · Jan 25, 2015

Hi.

Can you uninstall Microsoft Security Essentials and install a fresh downloaded copy of it?

Let us know the result.

nsfryer · Jan 25, 2015

Arc said:
Hi.

Can you uninstall Microsoft Security Essentials and install a fresh downloaded copy of it?

Let us know the result.

MSE install is less than a month old. I uninstalled Avast! per KoolKat77's recommendation and installed MSE when this BSOD debacle started. Should I still reinstall MSE?

Arc · Jan 26, 2015

Yes, do it.

nsfryer · Jan 27, 2015

Due to my own stupidity I had to purchase a new processor (bent the pins on the old one). It will be a few days still before it gets delivered. First task after that is to install MSE. I will keep you informed. Thank you folks for all your help so far.

Arc · Jan 28, 2015

nsfryer said:
Due to my own stupidity I had to purchase a new processor (bent the pins on the old one).

Been there, done that!

BSOD playing Steam Games

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer