Windows 7: BSOD at frequent intervals, various error codes

onionjoe76 · 20 Feb 2012

Hi there hope someone can help before I am tempted to throw my computer out of the window.. yes, i am that frustrated.

Got a new PC couple of weeks ago and have been having problems from day 1. I am getting increasingly regular blue screens. It's not just when trying to load software, or actually do anything. It can be sitting idling and suddenly it dies on me.

Spec

Windows 7 Home Premium 64bit
First OS installed (new build system)
System age 3 weeks
OS age 3 weeks

Ive attached all the dump files I could find. Really hope someone can help me.

onionjoe76 · 20 Feb 2012

PS..

I've tried memtest86, ran it for a long long time and there is no problem with my RAM.

writhziden · 22 Feb 2012

Code:


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


Loading Dump File [D:\Kingston\BSODDmpFiles\onionjoe76\022012-12511-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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0320e000 PsLoadedModuleList = 0xfffff800`03453670
Debug session time: Mon Feb 20 11:42:35.715 2012 (GMT-7)
System Uptime: 0 days 0:00:47.322
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffba8009e0bdf8, 2, 1, fffff800032974b0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffba8009e0bdf8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032974b0, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bd100
 ffffba8009e0bdf8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ObfReferenceObject+20
fffff800`032974b0 f0480fc11f      lock xadd qword ptr [rdi],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  avast.setup

TRAP_FRAME:  fffff88007a206b0 -- (.trap 0xfffff88007a206b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffba8009e0bf00 rbx=0000000000000000 rcx=ffffba8009e0be28
rdx=fffffa8009e0bb60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032974b0 rsp=fffff88007a20840 rbp=fffff88007a20c00
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8008d0c8a0
r11=fffff8a0017847a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ObfReferenceObject+0x20:
fffff800`032974b0 f0480fc11f      lock xadd qword ptr [rdi],rbx ds:c8d0:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000328a1e9 to fffff8000328ac40

STACK_TEXT:  
fffff880`07a20568 fffff800`0328a1e9 : 00000000`0000000a ffffba80`09e0bdf8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`07a20570 fffff800`03288e60 : 00000000`00000000 00000000`00000000 00000000`00f80008 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`07a206b0 fffff800`032974b0 : fffff880`07a20c20 00000000`00000000 fffff8a0`00000002 fffff800`00b96080 : nt!KiPageFault+0x260
fffff880`07a20840 fffff800`032ecb5a : fffffa80`09e0bef8 00000006`00300008 00000000`000006d4 00000000`00000b68 : nt!ObfReferenceObject+0x20
fffff880`07a20870 fffff800`0356085e : 00000000`00000000 00000000`00000000 fffff880`07a20c20 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1a8d0
fffff880`07a20930 fffff800`0354409d : 00000000`20000001 00000000`20000000 00000000`78457300 00000000`00000000 : nt!PspExitThread+0x2ae
fffff880`07a20a30 fffff800`0327e3fa : 00000000`00000100 fffffa80`09e0bc20 00000000`00000001 fffff800`0329013d : nt!PsExitSpecialApc+0x1d
fffff880`07a20a60 fffff800`0327e740 : 00000000`00000246 fffff880`07a20ae0 fffff800`03544010 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`07a20ae0 fffff800`03289f77 : fffffa80`09e0bb60 00000000`0000037c fffff880`07a20bf8 fffffa80`0952cab0 : nt!KiInitiateUserApc+0x70
fffff880`07a20c20 00000000`74b62e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0199ee58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74b62e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`03288e60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

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

Loading Dump File [D:\Kingston\BSODDmpFiles\onionjoe76\022012-13072-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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e57670
Debug session time: Mon Feb 20 11:41:09.360 2012 (GMT-7)
System Uptime: 0 days 0:07:07.594
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffba8009d8dbb0, 2, 1, fffff80002c966ec}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiAdjustWorkerThreadPriority+95 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffba8009d8dbb0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c966ec, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec1100
 ffffba8009d8dbb0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForSingleObject+13c
fffff800`02c966ec f00fba2e07      lock bts dword ptr [rsi],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880021ff9b0 -- (.trap 0xfffff880021ff9b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=d77dd5ae2d8e64c0 rbx=0000000000000000 rcx=0000000000000011
rdx=0000000000000031 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c966ec rsp=fffff880021ffb40 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff88002fd5180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe cy
nt!KeWaitForSingleObject+0x13c:
fffff800`02c966ec f00fba2e07      lock bts dword ptr [rsi],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8e1e9 to fffff80002c8ec40

STACK_TEXT:  
fffff880`021ff868 fffff800`02c8e1e9 : 00000000`0000000a ffffba80`09d8dbb0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`021ff870 fffff800`02c8ce60 : fffffa80`08f3b5e0 00000000`00000001 fffffa80`0919d9c0 00000000`ff29f5e0 : nt!KiBugCheckDispatch+0x69
fffff880`021ff9b0 fffff800`02c966ec : 00000000`00000002 fffffa80`08e44560 fffffa80`09107410 fffff880`04da4376 : nt!KiPageFault+0x260
fffff880`021ffb40 fffff800`02c6f872 : fffffa80`09107700 00000000`0000001b fffffa80`08e44500 fffff880`02fd5100 : nt!KeWaitForSingleObject+0x13c
fffff880`021ffbe0 fffff800`02c94b6c : ffffffff`ffb3b4c0 ffffba80`09d8dbb0 fffffa80`091077d8 00000000`00000000 : nt!ExpWaitForResource+0xae
fffff880`021ffc50 fffff880`04dd4dd9 : fffff880`04dd1dc0 fffffa80`08e44560 00000000`00000080 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`021ffcc0 fffff880`04dd1e9e : fffffa80`08e44560 00000000`00000080 00000000`00000000 fffffa80`09107410 : dxgmms1!VidSchiAdjustWorkerThreadPriority+0x95
fffff880`021ffd00 fffff800`02f29fee : 00000000`02a58067 fffffa80`08d8db60 fffffa80`069a4b30 fffffa80`08d8db60 : dxgmms1!VidSchiWorkerThread+0xde
fffff880`021ffd40 fffff800`02c805e6 : fffff800`02e04e80 fffffa80`08d8db60 fffff800`02e12cc0 fffff880`01233384 : nt!PspSystemThreadStartup+0x5a
fffff880`021ffd80 00000000`00000000 : fffff880`02200000 fffff880`021fa000 fffff880`021ff680 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiAdjustWorkerThreadPriority+95
fffff880`04dd4dd9 418bef          mov     ebp,r15d

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  dxgmms1!VidSchiAdjustWorkerThreadPriority+95

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidSchiAdjustWorkerThreadPriority+95

BUCKET_ID:  X64_0xA_dxgmms1!VidSchiAdjustWorkerThreadPriority+95

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

Loading Dump File [D:\Kingston\BSODDmpFiles\onionjoe76\022012-24476-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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e58670
Debug session time: Mon Feb 20 11:17:17.323 2012 (GMT-7)
System Uptime: 0 days 0:00:42.931
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800738af81, fffff880078865e0, 0}

Unable to load image \SystemRoot\system32\drivers\spsys.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
Probably caused by : spsys.sys ( spsys+21f81 )

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

1: 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: fffff8800738af81, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880078865e0, 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: 
spsys+21f81
fffff880`0738af81 ff1501c1feff    call    qword ptr [spsys+0xe088 (fffff880`07377088)]

CONTEXT:  fffff880078865e0 -- (.cxr 0xfffff880078865e0)
rax=fffff88007887b85 rbx=0000000000000000 rcx=0000000000000ab5
rdx=fffff8800788703c rsi=fffff8a007d0b000 rdi=fffff88007888088
rip=fffff8800738af81 rsp=fffff88007886fc0 rbp=0000000000000020
 r8=0000000000000004  r9=fffff88007887038 r10=0000000000000000
r11=0000000000000750 r12=fffff8a007d0c690 r13=fffff8a001070415
r14=fffff8a007d0c610 r15=fffff7804000002c
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
spsys+0x21f81:
fffff880`0738af81 ff1501c1feff    call    qword ptr [spsys+0xe088 (fffff880`07377088)] ds:002b:fffff880`07377088=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  sppsvc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000087fc0000004 to fffff8800738af81

STACK_TEXT:  
fffff880`07886fc0 0000087f`c0000004 : 00000000`000c44b7 fffff8a0`07d0b000 fffff880`00000188 fffff8a0`07d0b000 : spsys+0x21f81
fffff880`07886fc8 00000000`000c44b7 : fffff8a0`07d0b000 fffff880`00000188 fffff8a0`07d0b000 fffff8a0`07d0e000 : 0x87f`c0000004
fffff880`07886fd0 fffff8a0`07d0b000 : fffff880`00000188 fffff8a0`07d0b000 fffff8a0`07d0e000 00000000`00000000 : 0xc44b7
fffff880`07886fd8 fffff880`00000188 : fffff8a0`07d0b000 fffff8a0`07d0e000 00000000`00000000 00001f80`00000000 : 0xfffff8a0`07d0b000
fffff880`07886fe0 fffff8a0`07d0b000 : fffff8a0`07d0e000 00000000`00000000 00001f80`00000000 00000000`00000000 : 0xfffff880`00000188
fffff880`07886fe8 fffff8a0`07d0e000 : 00000000`00000000 00001f80`00000000 00000000`00000000 00000000`00000000 : 0xfffff8a0`07d0b000
fffff880`07886ff0 00000000`00000000 : 00001f80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff8a0`07d0e000


FOLLOWUP_IP: 
spsys+21f81
fffff880`0738af81 ff1501c1feff    call    qword ptr [spsys+0xe088 (fffff880`07377088)]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  spsys+21f81

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: spsys

IMAGE_NAME:  spsys.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a085e7a

STACK_COMMAND:  .cxr 0xfffff880078865e0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_spsys+21f81

BUCKET_ID:  X64_0x3B_spsys+21f81

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

Loading Dump File [D:\Kingston\BSODDmpFiles\onionjoe76\022012-23212-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 Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea3e90
Debug session time: Mon Feb 20 11:00:34.229 2012 (GMT-7)
System Uptime: 0 days 0:01:03.462
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffba8008e4e480, 1, fffff80002fcaf95, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PspInsertThread+1a5 )

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

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

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0f0e8
 ffffba8008e4e480 

FAULTING_IP: 
nt!PspInsertThread+1a5
fffff800`02fcaf95 488910          mov     qword ptr [rax],rdx

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800557eed0 -- (.trap 0xfffff8800557eed0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffba8008e4e480 rbx=0000000000000000 rcx=fffffa800960aa38
rdx=fffffa8007f2a8e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fcaf95 rsp=fffff8800557f060 rbp=fffffa800960a730
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!PspInsertThread+0x1a5:
fffff800`02fcaf95 488910          mov     qword ptr [rax],rdx ds:000f:ffffba80`08e4e480=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c88bf7 to fffff80002cde640

STACK_TEXT:  
fffff880`0557ed68 fffff800`02c88bf7 : 00000000`00000050 ffffba80`08e4e480 00000000`00000001 fffff880`0557eed0 : nt!KeBugCheckEx
fffff880`0557ed70 fffff800`02cdc76e : 00000000`00000001 ffffba80`08e4e480 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44811
fffff880`0557eed0 fffff800`02fcaf95 : 00000000`00000000 fffffa80`07f2ad20 00000000`00000000 fffffa80`07f2a4c0 : nt!KiPageFault+0x16e
fffff880`0557f060 fffff800`02fca4f2 : fffffa80`07f2a4c0 fffffa80`0960a730 fffff880`0557f500 fffff880`0557f240 : nt!PspInsertThread+0x1a5
fffff880`0557f1e0 fffff800`02fce385 : fffff880`0557f580 00000000`00000000 00000000`00000001 fffff880`0557fa10 : nt!PspCreateThread+0x246
fffff880`0557f460 fffff800`02cdd8d3 : fffff880`0557fca0 fffffa80`0939e380 fffff880`0557fbf8 00000000`0019db00 : nt!NtCreateThreadEx+0x25d
fffff880`0557fbb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PspInsertThread+1a5
fffff800`02fcaf95 488910          mov     qword ptr [rax],rdx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PspInsertThread+1a5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x50_nt!PspInsertThread+1a5

BUCKET_ID:  X64_0x50_nt!PspInsertThread+1a5

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

Caused by avast. Other possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
DirectX/display card/display card driver. Same possible causes as 1.
Caused by the Microsoft software protections service. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

Thanks to Dave76 for help understanding possible causes.

Run through the following steps. Test after each whether it improves stability. If your computer still crashes, proceed to the next step.

If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Follow the steps to do HD Diagnostic for your hard drive.
Remove avast antivirus with the avast uninstall utility and replace with the good and free system security combination.

onionjoe76 · 13 Mar 2012

Thank you for your help.

writhziden · 13 Mar 2012

You're welcome. Did you complete all steps, or did you just notice the thread had a response? Let us know how the system is currently responding and whether the steps help.

onionjoe76 · 13 Mar 2012

Hi... Just saw the reply. Will start going through the steps tomorrow. Thanks for you help.

writhziden · 13 Mar 2012

You're welcome. Let us know how the process goes and how the system responds or if you need any help. Best of luck!

Windows 7: BSOD at frequent intervals, various error codes

BSOD at frequent intervals, various error codes problems?