BSOD Acer Apsire One

pstables · 06 Mar 2010

Ok, bit of history - had an Acer Aspire One 150 for a few months now. It came with Ubuntu (or some other Linux flavour) and I'm a Windows man so I put the Beta of W7 on, followed by the RC. Both of these were "Ultimate". System was pretty rock solid. I tried to update the BIOS and the thing died horribly so had to go back to Acer for repair. I thought they would just force a reflash as it's a common problem but it had a motherboard replacement and was sent back.

In the meantime, W7 was released to the Development community and I used my MDSN subscription to install the real W7 ultimate on the newly returned AAO. That was when the problems began and I was getting BSOD several times a day. I had friends with the same kit running W7 happily so I thought "hardware error", phoned Acer and they said unless it was returned with the original OS they would charge for any repair. I stuck the Linux distro back on and it seemed more stable (although I didn't use in anger TBH). I then gave XP a try and again, rock solid so that's where I left it for several months, no problems at all.

Saw a colleague again recently with W7 Home Premium running solid as a rock on the AAO so I gave it another try (instead of Ultimate) and lo and behold BSOD after BSOD. I'm still suspecting H/W problem but don't know where to go from here seeing as it doesn't manifest under XP (or Linux).

Anyway, crash dumps attached, any assistance appreciatd.

Paul

usasma · 06 Mar 2010

5 memory dumps - dated between 25 Feb 10 and 05 Mar 10
2 STOP 0xA - more info on this error here: BSOD Index
2 STOP 0x8E - more info on this error here: BSOD Index
1 STOP 0x1A - more info on this error here: BSOD Index
1 is blamed on ntkrnlmp.exe (a core Windows component), 1 blamed on MpFilter.sys, 3 blamed on ntoskrnl.exe

Check this link to see if it pertains to your issue: A hotfix is available to resolve some problems with the Forefront Client Security client
If not, please remove you Microsoft antimalware software and replace it with a free antivirus for testing purposes (you can reinstall the Microsoft stuff, if you like, when we're done troubleshooting this issue).

Additionally, there is a problem with the Operating System. Sometime between 25 Feb 10 and 01 Mar 10 there was a change to the system that involved the kernel of the Operating System.

25 Feb 10: Built by: 7600.16385.x86fre.win7_rtm.090713-1255
01 Mar 10: Built by: 7600.16481.x86fre.win7_gdr.091207-1941

The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Also, please replace or update this driver:

sncduvc.SYS Mon Dec 29 04:13:29 2008

It belongs to your HP/Suyin Webcam driver and can be downloaded from the support website of your system's manufacturer.

Summary of the BSOD's:

Code:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Thu Feb 25 14:18:38.145 2010 (GMT-5)
System Uptime: 0 days 5:47:38.754
BugCheck 1000008E, {c0000005, 818bf529, 903b7bb0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExfReleasePushLock+3d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  lsass.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Mon Mar  1 18:44:20.249 2010 (GMT-5)
System Uptime: 0 days 2:41:45.967
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1000008E, {c0000005, 81a22001, a50db1dc, 0}
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : MpFilter.sys ( MpFilter+132b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Tue Mar  2 03:16:40.298 2010 (GMT-5)
System Uptime: 0 days 8:31:31.001
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck A, {c0178598, 0, 0, 818a2b90}
Probably caused by : ntoskrnl.exe ( nt+68b90 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Tue Mar  2 05:27:53.281 2010 (GMT-5)
System Uptime: 0 days 2:10:21.999
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Fri Mar  5 16:21:12.667 2010 (GMT-5)
System Uptime: 0 days 0:45:08.401
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck A, {835967d7, 0, 0, 818a4d25}
Probably caused by : ntoskrnl.exe ( nt+68d25 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

pstables · 06 Mar 2010

Many thanks, will give those a go. Like I said, this is a genuine MSDN subscriber version and the problems were the same on previous Ultimate edition (rather than home premium).

pstables · 08 Mar 2010

Ok, Microsoft Security Essentials removed, Windows Defender disabled.
Windows Genuine Advantage tool run.
sfc /scannow run

I couldn't find an updated driver for the camera so disabled it.

2 more BSOD since then (attached).

This is a pretty clean build, installed around 2 weeks ago and I got the BSOD within an hour of the installation.