Solved BSOD - can only enter safe mode

[Enigma3542002]

I have an ASUS ET2400INT all-in-one running Win 7 Home Premium 64 bit. The problem is below the divider lines in this post, and right below is my history, which may or may not be related:

Previous occurrences:

A) Screen blank-outs after 6 months. Screen would flicker, then return to normal after 1 sec. Taskbar popup says "NVIDIA display driver stopped responding and has successfully recovered."

B) Started getting BSODs randomly. Then came a point where either a) boot into Windows but freeze on any graphics intensive operation, or b) boot into a blank screen, or c) fail to boot into Windows at all.

C) Problem traced to the video driver/display adapter. Uninstalling the video driver and uninstalling the display adapter stopped the failures to boot, and the BSODs.

D) Ultimately, uninstalling the video driver, PLUS using Phyxion's Driver Sweeper to completely remove it, then reinstalling, stopped the BSODs, login problems, etc.

E) However, in recent months, the screen blank-outs and "NVIDIA display driver stopped responding and has successfully recovered" returned. Being busy, I learned to ignore that occasional issue.

===========================================

Current issue:

Largely normal operations today, except I choose to open a Windows Media Center recording. It does not open. Instead, a message comes up something like "Windows Media Center not responding or unavailable." I decide to restart the whole PC. After "Starting Windows", BSOD; BCCode: 1000007e.

- It initially wants to do a "Startup Repair," which I cancel after 20 minutes.
- Every time, after "Starting Windows," BSOD; BCCode: 1000007e.

I'm writing this in Safe Mode. I've tried:

A) Uninstalling graphics driver and display adapter, try to restart normally: BSOD.
B) Use System Restore point back to one that was set this morning: BSOD.

The logs are attached---any help would be appreciated!!!!

 

[richc46]

Your problem is caused by Avast. Uninstall and replace with Microsoft Security Essentials. It is built for Windows and has never caused a BSOD
Before doing anything create a system restore point so you will always have the option to go back
I have bolded the driver that is causing your problem.

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

Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_My-PC-Wed_01_14_2015_210005_90.zip\011415-18829-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17118.amd64fre.win7_gdr.120830-0334
Machine Name:
Kernel base = 0xfffff800`04265000 PsLoadedModuleList = 0xfffff800`044a1e70
Debug session time: Wed Jan 14 23:56:08.946 2015 (UTC - 5:00)
System Uptime: 0 days 0:00:05.818
Loading Kernel Symbols
...............................................................
.................
Loading User Symbols
Unable to load image \SystemRoot\System32\Drivers\[B]aswSP.SYS[/B], Win32 error 0n2
*** 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, fffff88003b46b73, fffff880009a8fa8, fffff880009a8810}
Probably caused by : aswSP.SYS ( aswSP+40b73 )
Followup: MachineOwner
---------
3: 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: fffff88003b46b73, The address that the exception occurred at
Arg3: fffff880009a8fa8, Exception Record Address
Arg4: fffff880009a8810, 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+40b73
fffff880`03b46b73 48897008        mov     qword ptr [rax+8],rsi
EXCEPTION_RECORD:  fffff880009a8fa8 -- (.exr 0xfffff880009a8fa8)
Cannot read Exception record @ fffff880009a8fa8
CONTEXT:  fffff880009a8810 -- (.cxr 0xfffff880009a8810)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80064b7a40
rdx=0000000000000002 rsi=fffff8a0002e21d0 rdi=fffffa80068e57c0
rip=fffff88003b46b73 rsp=fffff880009a91e0 rbp=0000000000000000
 r8=0000000000008e08  r9=0000000000000030 r10=fffff80004265000
r11=000000000000038d r12=fffffa80068d8000 r13=fffff88003b06000
r14=0000000000000001 r15=fffff880009a9420
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+0x40b73:
fffff880`03b46b73 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 fffff8000450c0e0
 0000000000000008 
FOLLOWUP_IP: 
aswSP+40b73
fffff880`03b46b73 48897008        mov     qword ptr [rax+8],rsi
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER:  from fffffa80068d8000 to fffff88003b46b73
STACK_TEXT:  
fffff880`009a91e0 fffffa80`068d8000 : 00000000`00000000 00000000`49777361 00000000`000007ff fffff880`009a92f0 : aswSP+0x40b73
fffff880`009a91e8 00000000`00000000 : 00000000`49777361 00000000`000007ff fffff880`009a92f0 fffff800`00000008 : 0xfffffa80`068d8000

SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  aswSP+40b73
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: aswSP
IMAGE_NAME:  aswSP.SYS
DEBUG_FLR_IMAGE_TIMESTAMP:  50905836
STACK_COMMAND:  .cxr 0xfffff880009a8810 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_aswSP+40b73
BUCKET_ID:  X64_0x7E_aswSP+40b73
Followup: MachineOwner
---------

 

[Enigma3542002]

Thanks for the quick reply! I am surprised given that AVAST has been used by my system for years.

In safe mode I cannot create a restore point but there is one from earlier today and earlier this month.

Will be uninstalling avast now, try to see if I can enter regular Windows...fingers crossed!!!!!!

 

[richc46]

I can tell you that I was given 2 .dmp reports they were both identical and indicate Avast. If you have BSODs again, it is due to an additional problem

 

[Enigma3542002]

WOW! As soon as Avast was gone---the computer was back to normal. THANK YOU!!!!!

I have reinstalled my graphics driver and display adapter (a red herring, apparently)--and installed Microsoft Security Essentials.

The reason I used Avast is this: years ago I had GIANT antispyware, then it began Microsoft Antispyware, and that seemed to be ineffective. That was Win XP days.

Anyways, my work uses Microsoft Security Essentials, and now so does this computer...

Avast was updated for the new year---wonder if that was why it conflicted?

I will keep monitoring to see if the crashes occur again...but right now it's working! Can't believe that this whole saga was so quick to reach this level of restored functionality.

A BIG THANK YOU!

 

[richc46]

That's great news. I do not think that you will be getting any more BSOD's. We found the problem.
For the best protection, MSE in conjunction with Malwarebytes.
Actually, an antivirus that is more effective than MSE is Panda. Since you cannot use Avast, you may want to give it a try. It too can cause BSODs, but a simple adjustment would put an end to that. Its up to you.

 

[Enigma3542002]

Thanks again! I will try Malwarebytes....already using MSE now.