Just put together this pc today and it randomly bsod'd twice. No idea why hoping you guys could help me out. Thanks in advance.
Is Windows 7 . . .
- x64
- windows 7
- full retail version
- Full Retail = you purchased it from retailer
- 1 day old
- os 1 day old
Simple
Your Avast. Remove and replace with Microsoft Security Essentials
http://files.avast.com/files/eng/aswclear5.exe
Virus, Spyware & Malware Protection | Microsoft Security Essentials
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\Windows_NT6_BSOD_jcgriff2\061511-12090-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 (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16792.amd64fre.win7_gdr.110408-1633 Machine Name: Kernel base = 0xfffff800`02c1e000 PsLoadedModuleList = 0xfffff800`02e5be50 Debug session time: Wed Jun 15 21:47:10.396 2011 (GMT-4) System Uptime: 0 days 0:49:40.503 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffa8007ea51d8, 0, fffff8800680c2af, 0} Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSP.SYS *** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS Could not read faulting driver name Probably caused by : aswSP.SYS ( aswSP+c2af ) Followup: MachineOwner --------- 3: 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: fffffa8007ea51d8, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff8800680c2af, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec60e0 fffffa8007ea51d8 FAULTING_IP: aswSP+c2af fffff880`0680c2af 488b4048 mov rax,qword ptr [rax+48h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: Blizzard Updat CURRENT_IRQL: 0 TRAP_FRAME: fffff880088cd420 -- (.trap 0xfffff880088cd420) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8007ea5190 rbx=0000000000000000 rcx=fffffa800422c13a rdx=000000000207391c rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800680c2af rsp=fffff880088cd5b0 rbp=fffffa8008e69e50 r8=0000000000000000 r9=0000000000000000 r10=00740073006e0049 r11=00000000000000d8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc aswSP+0xc2af: fffff880`0680c2af 488b4048 mov rax,qword ptr [rax+48h] ds:fffffa80`07ea51d8=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002d0f024 to fffff80002c8e700 STACK_TEXT: fffff880`088cd2b8 fffff800`02d0f024 : 00000000`00000050 fffffa80`07ea51d8 00000000`00000000 fffff880`088cd420 : nt!KeBugCheckEx fffff880`088cd2c0 fffff800`02c8c7ee : 00000000`00000000 fffff880`088cd640 00000000`00000000 fffffa80`08e69e50 : nt! ?? ::FNODOBFM::`string'+0x427f7 fffff880`088cd420 fffff880`0680c2af : fffff880`088cd640 fffffa80`08e69e50 fffff880`088cd530 fffffa80`08e69e50 : nt!KiPageFault+0x16e fffff880`088cd5b0 fffff880`088cd640 : fffffa80`08e69e50 fffff880`088cd530 fffffa80`08e69e50 00000000`00000000 : aswSP+0xc2af fffff880`088cd5b8 fffffa80`08e69e50 : fffff880`088cd530 fffffa80`08e69e50 00000000`00000000 fffff880`078253b1 : 0xfffff880`088cd640 fffff880`088cd5c0 fffff880`088cd530 : fffffa80`08e69e50 00000000`00000000 fffff880`078253b1 fffffa80`08e69e50 : 0xfffffa80`08e69e50 fffff880`088cd5c8 fffffa80`08e69e50 : 00000000`00000000 fffff880`078253b1 fffffa80`08e69e50 fffffa80`0422c064 : 0xfffff880`088cd530 fffff880`088cd5d0 00000000`00000000 : fffff880`078253b1 fffffa80`08e69e50 fffffa80`0422c064 fffffa80`068b1ce0 : 0xfffffa80`08e69e50 STACK_COMMAND: kb FOLLOWUP_IP: aswSP+c2af fffff880`0680c2af 488b4048 mov rax,qword ptr [rax+48h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: aswSP+c2af FOLLOWUP_NAME: MachineOwner MODULE_NAME: aswSP IMAGE_NAME: aswSP.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4dc929b6 FAILURE_BUCKET_ID: X64_0x50_aswSP+c2af BUCKET_ID: X64_0x50_aswSP+c2af Followup: MachineOwner ---------
Quote