Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD...need help!!!

08 Jul 2011   #11
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

The driver verified dump blames l160x64.sys, which is the NDIS Miniport Driver for Atheros L1 Gigabit Ethernet Controller, you should update it ATHEROS drivers for Microsoft Windows

Other dumps blame a component of Avast(aswSP.SYS), remove Avast and use MSE
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800028d705c, fffff88002e63428, fffff88002e62c90}

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
Probably caused by : aswSP.SYS ( aswSP+101da )


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: fffff800028d705c, The address that the exception occurred at
Arg3: fffff88002e63428, Exception Record Address
Arg4: fffff88002e62c90, 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!ExQueueWorkItem+cc
fffff800`028d705c 48894108        mov     qword ptr [rcx+8],rax

EXCEPTION_RECORD:  fffff88002e63428 -- (.exr 0xfffff88002e63428)
ExceptionAddress: fffff800028d705c (nt!ExQueueWorkItem+0x00000000000000cc)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002e62c90 -- (.cxr 0xfffff88002e62c90)
rax=fffffa80039e2148 rbx=fffff80002a745a0 rcx=dffff80002a745a8
rdx=0000000000000000 rsi=fffff8800127a050 rdi=fffffa8004e53040
rip=fffff800028d705c rsp=fffff88002e63660 rbp=fffff88002e63800
 r8=0000000000000000  r9=fffff880012a0230 r10=fffffa80047b9680
r11=fffffa8004d16010 r12=fffff80002a49e80 r13=fffffa80039e52a8
r14=fffff80002a745a8 r15=fffffa80039e2148
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ExQueueWorkItem+0xcc:
fffff800`028d705c 48894108        mov     qword ptr [rcx+8],rax ds:002b:dffff800`02a745b0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b070e0
 ffffffffffffffff 

FOLLOWUP_IP: 
aswSP+101da
fffff880`03b581da ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880012217cd to fffff800028d705c

STACK_TEXT:  
fffff880`02e63660 fffff880`012217cd : fffffa80`03f61640 fffffa80`03f61688 00000000`00000000 fffffa80`03f61640 : nt!ExQueueWorkItem+0xcc
fffff880`02e636d0 fffff880`012cef74 : fffffa80`054873a0 fffff8a0`00122140 fffffa80`054873a0 00000000`00000000 : Ntfs!NtfsQueueClose+0x111
fffff880`02e63700 fffff880`0101123f : fffff880`02e63801 fffffa80`06020c10 fffff880`02e68000 00000000`00000002 : Ntfs!NtfsFsdClose+0x774
fffff880`02e63800 fffff880`0100f6df : fffffa80`04f90040 fffffa80`06020c10 fffffa80`047b9600 fffffa80`06020c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`02e63890 fffff800`02be44de : fffffa80`054873a0 fffffa80`04912590 fffffa80`039cd040 fffffa80`04f90040 : fltmgr!FltpDispatch+0xcf
fffff880`02e638f0 fffff800`028d48b4 : fffff880`02e63b50 fffffa80`039cd040 fffffa80`039dd9f0 fffff880`02e63a48 : nt!IopDeleteFile+0x11e
fffff880`02e63980 fffff800`02be4264 : fffffa80`039cd040 00000000`00000000 fffffa80`04e53040 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`02e639e0 fffff800`02be4164 : 00000000`00003a78 fffffa80`039cd040 fffff8a0`00001a70 00000000`00003a78 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`02e63a70 fffff800`028ce953 : fffffa80`04e53040 fffff880`02e63b40 00000000`00000000 00000000`000007ff : nt!ObpCloseHandle+0x94
fffff880`02e63ac0 fffff800`028caef0 : fffff880`03b581da fffff880`02e63d48 00000000`00000001 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02e63c58 fffff880`03b581da : fffff880`02e63d48 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff880`02e63c60 fffff880`02e63d48 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`02e63d00 : aswSP+0x101da
fffff880`02e63c68 00000000`00000001 : 00000000`00000000 00000000`00000000 fffff880`02e63d00 00000000`00000000 : 0xfffff880`02e63d48
fffff880`02e63c70 00000000`00000000 : 00000000`00000000 fffff880`02e63d00 00000000`00000000 ffffffff`80003a78 : 0x1


SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  aswSP+101da

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4e11a5d4

STACK_COMMAND:  .cxr 0xfffff88002e62c90 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_aswSP+101da

BUCKET_ID:  X64_0x7E_aswSP+101da

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



My System SpecsSystem Spec
.
22 Jul 2011   #12
Gin520

Windows 7 ultimate x64
 
 

i got new problem
hope u can help.
My System SpecsSystem Spec
23 Jul 2011   #13
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

We need the full report, not just the minidumps
https://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
.

Reply

 BSOD...need help!!!




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 13:31.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App