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 unable to start up my computer normally


14 Jul 2013   #1
Matiree

Windows 7 Ultimate x64
 
 
BSOD unable to start up my computer normally

I had this custom built computer made over 2 years ago by my little brother. I never had any problems with it, no BSOD or anything. I left the city a couple of days ago and usually when I'm not home, my dad uses my computer. He doesn't know how to use one properly so I have no idea what he did. I came back and every time I try to start my computer, it blue screens right after it displays the windows logo.

I am currently in safe mode. Help?

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF880040FDE93
BCP3: FFFFF880009A8E58
BCP4: FFFFF880009A86B0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\071413-23212-01.dmp
C:\Users\Lisa\AppData\Local\Temp\WER-34928-0.sysdata.xml


My System SpecsSystem Spec
.

14 Jul 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Try Advanced Boot Options and the Safe Mode with Networking. Then post it following the Blue Screen of Death (BSOD) Posting Instructions.
My System SpecsSystem Spec
14 Jul 2013   #3
Matiree

Windows 7 Ultimate x64
 
 

Here.
My System SpecsSystem Spec
.


14 Jul 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Both the BSODs are caused by Avast, and avast predominantly through the entire all stack.

avast! Self Protection Driver
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff88003e70e93, fffff880009a8e58, fffff880009a86b0}

Probably caused by : aswSP.SYS ( aswSP+41e93 )

Followup: MachineOwner
---------
Description here: Driver Reference Table - aswSP.SYS

avast! Virtualization Driver
Code:
fffff880`009a8218  fffff880`02db433cUnable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
 aswSnx+0xf133c
Description here: Driver Reference Table - aswSnx.SYS

First try .... Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Is still cannot boot in normal mode, second try: Scan the system for possible virus infection with the following programs.
If still the same, third and final try .... Follow it:
Troubleshooting Windows 7 Failure to Start

Let us know the results.
______________________________________________________________________________
BSOD ANALYSIS:
Code:
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88003e70e93, fffff880009a8e58, fffff880009a86b0}

Probably caused by : aswSP.SYS ( aswSP+41e93 )

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

0: 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: fffff88003e70e93, The address that the exception occurred at
Arg3: fffff880009a8e58, Exception Record Address
Arg4: fffff880009a86b0, 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: 
aswSP+41e93
fffff880`03e70e93 48897008        mov     qword ptr [rax+8],rsi

EXCEPTION_RECORD:  fffff880009a8e58 -- (.exr 0xfffff880009a8e58)
ExceptionAddress: fffff88003e70e93 (aswSP+0x0000000000041e93)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000008
Attempt to write to address 0000000000000008

CONTEXT:  fffff880009a86b0 -- (.cxr 0xfffff880009a86b0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80076b7910
rdx=0000000000000002 rsi=fffff8a0003f93e0 rdi=fffffa8007b3b6f0
rip=fffff88003e70e93 rsp=fffff880009a9090 rbp=fffffa8007b28850
 r8=0000000000008e08  r9=0000000000000030 r10=fffff80003600000
r11=000000000000038d r12=fffffa8007ab7000 r13=fffff88003e2f000
r14=0000000000000001 r15=fffff880009a92d0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
aswSP+0x41e93:
fffff880`03e70e93 48897008        mov     qword ptr [rax+8],rsi ds:002b:00000000`00000008=????????????????
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:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000008

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800038ad100
GetUlongFromAddress: unable to read from fffff800038ad1c0
 0000000000000008 Nonpaged pool

FOLLOWUP_IP: 
aswSP+41e93
fffff880`03e70e93 48897008        mov     qword ptr [rax+8],rsi

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffffa8007ab7000 to fffff88003e70e93

STACK_TEXT:  
fffff880`009a9090 fffffa80`07ab7000 : 00000000`00000000 00000000`49777361 00000000`000007ff fffff880`009a91a0 : aswSP+0x41e93
fffff880`009a9098 00000000`00000000 : 00000000`49777361 00000000`000007ff fffff880`009a91a0 fffff800`00000008 : 0xfffffa80`07ab7000


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aswSP+41e93

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  518b62d9

STACK_COMMAND:  .cxr 0xfffff880009a86b0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_aswSP+41e93

BUCKET_ID:  X64_0x7E_aswSP+41e93

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

0: kd> lmvm aswSP
start             end                 module name
fffff880`03e2f000 fffff880`03e91000   aswSP    T (no symbols)           
    Loaded symbol image file: aswSP.SYS
    Image path: \SystemRoot\System32\Drivers\aswSP.SYS
    Image name: aswSP.SYS
    Timestamp:        Thu May 09 14:18:25 2013 (518B62D9)
    CheckSum:         000608C9
    ImageSize:        00062000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !thread
My System SpecsSystem Spec
14 Jul 2013   #5
Matiree

Windows 7 Ultimate x64
 
 

Thanks! All I had to do was uninstall avast and so far, so good!
My System SpecsSystem Spec
14 Jul 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

So the first try worked. Very good to know
For any other further issue, let us know
My System SpecsSystem Spec
Reply

 BSOD unable to start up my computer normally




Thread Tools



Similar help and support threads for2: BSOD unable to start up my computer normally
Thread Forum
Your computer was unable to start BSOD Help and Support
BSOD appears every time, computer lags, unable to copy files. BSOD Help and Support
Your computer was unable to start, Startup Repair. General Discussion
Your computer was unable to start General Discussion
Solved Unable to Remove Pinned "Computer" From Start Menu General Discussion
"Your computer was unable to start" help! General Discussion
Update to Adobe Caused "Your computer was unable to start"? General Discussion

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 11:06 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App