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: New PC BSOD. Help Please.

03 Jun 2011   #1

Windows 7 Home Premium 64bit
New PC BSOD. Help Please.

Hey guys, I got this PC about 2 weeks ago and it has already BSOD twice. Once a few days ago and then again yesterday.

Windows 7 Home Premium 64 bit
PC came preinstalled with Windows 7
No OS changes have been made

Any help will be very much appreciated. Thank you.

My System SpecsSystem Spec

03 Jun 2011   #2

Microsoft Community Contributor Award Recipient

Windows 7 x64

According to the minidump the avast! protection system is causing your problem.
I suggest removing avast! (which has been known to develop issues on some win 7 systems)
and replacing it with MSE
Virus, Spyware & Malware Protection | Microsoft Security Essentials

Which does not suffer from those issues.
Fault info:
aswSP.SYS Wed Feb 04 21:41:01 2009 (498A51BD) avast! Self Protection Driver

crash summary:
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.
Arg1: fffffa8004c41d10, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88002d6cfaf, If non-zero, the instruction address which referenced the bad memory
Arg4: 0000000000000000, (reserved)

Debugging Details:

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc100

fffff880`02d6cfaf 41f644241008    test    byte ptr [r12+10h],8





PROCESS_NAME:  AvastSvc.exe


TRAP_FRAME:  fffff88003a4a720 -- (.trap 0xfffff88003a4a720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80071e4840
rdx=fffffa8006fde671 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002d6cfaf rsp=fffff88003a4a8b0 rbp=fffff88003a4aac8
 r8=fffffa8006fde670  r9=0000000000000150 r10=fffff88002da6000
r11=fffffa8006b15900 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff880`02d6cfaf 41f644241008    test    byte ptr [r12+10h],8 ds:00000000`00000010=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a78a0c to fffff80002accd00

fffff880`03a4a5b8 fffff800`02a78a0c : 00000000`00000050 fffffa80`04c41d10 00000000`00000000 fffff880`03a4a720 : nt!KeBugCheckEx
fffff880`03a4a5c0 fffff800`02acae2e : 00000000`00000000 fffffa80`04c41d10 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`03a4a720 fffff880`02d6cfaf : fffff880`03a4a928 fffff800`00000001 fffff8a0`00000003 fffff800`00000000 : nt!KiPageFault+0x16e
fffff880`03a4a8b0 fffff880`03a4a928 : fffff800`00000001 fffff8a0`00000003 fffff800`00000000 fa8005b4`9b180400 : aswSP+0xafaf
fffff880`03a4a8b8 fffff800`00000001 : fffff8a0`00000003 fffff800`00000000 fa8005b4`9b180400 00000000`00000801 : 0xfffff880`03a4a928
fffff880`03a4a8c0 fffff8a0`00000003 : fffff800`00000000 fa8005b4`9b180400 00000000`00000801 00000000`00000000 : 0xfffff800`00000001
fffff880`03a4a8c8 fffff800`00000000 : fa8005b4`9b180400 00000000`00000801 00000000`00000000 fffff880`0104a19a : 0xfffff8a0`00000003
fffff880`03a4a8d0 fa8005b4`9b180400 : 00000000`00000801 00000000`00000000 fffff880`0104a19a fffffa80`04c41d00 : 0xfffff800`00000000
fffff880`03a4a8d8 00000000`00000801 : 00000000`00000000 fffff880`0104a19a fffffa80`04c41d00 00000000`00000000 : 0xfa8005b4`9b180400
fffff880`03a4a8e0 00000000`00000000 : fffff880`0104a19a fffffa80`04c41d00 00000000`00000000 fffff880`03a4ab30 : 0x801


fffff880`02d6cfaf 41f644241008    test    byte ptr [r12+10h],8


SYMBOL_NAME:  aswSP+afaf

FOLLOWUP_NAME:  MachineOwner




FAILURE_BUCKET_ID:  X64_0x50_aswSP+afaf

BUCKET_ID:  X64_0x50_aswSP+afaf

Followup: MachineOwner
My System SpecsSystem Spec
03 Jun 2011   #3

Windows 7 Home Premium 64bit

Thank you for the quick reply! I did end up noticing that one of the minidump files pointed at avast being the problem. The only thing is that I think my first minidump, from a few days ago, didn't say it was avast so I wasn't sure if there was something there that I wasn't seeing.

Either way I have uninstalled avast and now using a different antivirus. Again thank you for the response, hopefully everything turns out ok for me.
My System SpecsSystem Spec

03 Jun 2011   #4

Microsoft Community Contributor Award Recipient

Windows 7 x64

yeah there were only two minidumps in what you attached for me to view, they both pointed to the same trouble maker.

If you get another one down the road upload the newest minidump and we'll have a look at what is causing it in that instance.
AVAST was definitely the cause here though.
My System SpecsSystem Spec
03 Jun 2011   #5

Windows 7 Home Premium 64bit

Thanks alot I really appreciate it. HUGE help!
My System SpecsSystem Spec

 New PC BSOD. Help Please.

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 05:45 AM.
Twitter Facebook Google+

Windows 7 Forums

Seven Forums Android App Seven Forums IOS App

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33