Unknown Stop Error


Honorable Member
Microsoft MVP

This one appears to have been caused by you Avast antivirus. AV apps are often the source of BSOD's. I would remove it and replace with Microsoft Security Essentials. It doesnt seem to cause nearly as many.

I would also run a system file check to verify and repair your system files

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then

read here for more information SFC /SCANNOW Command - System File Checker - Windows 7 Forums

Let us know the results from the report at the end.


Ken J

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\K\Desktop\091710-26254-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a1c000 PsLoadedModuleList = 0xfffff800`02c59e50
Debug session time: Thu Sep 16 21:52:21.687 2010 (GMT-4)
System Uptime: 0 days 0:06:41.482
Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffb8a0071f6618, 0, fffff88001056fa9, 7}

Unable to load image \SystemRoot\System32\Drivers\aswFsBlk.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswFsBlk.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.SYS

Could not read faulting driver name
Probably caused by : luafv.sys ( luafv!LuafvPreClose+56 )

Followup: MachineOwner

1: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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

Debugging Details:

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc40e0

fffff880`01056fa9 488b4820        mov     rcx,qword ptr [rax+20h]





PROCESS_NAME:  mscorsvw.exe


TRAP_FRAME:  fffff88006c66a10 -- (.trap 0xfffff88006c66a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb8a0071f65f8 rbx=0000000000000000 rcx=ffffb8a0071f65f8
rdx=fffffa800442e620 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001056fa9 rsp=fffff88006c66ba0 rbp=fffffa800442e620
 r8=fffffa800607a4c0  r9=fffff88006c66d48 r10=fffffa8004e38718
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff880`01056fa9 488b4820        mov     rcx,qword ptr [rax+20h] ds:ffffb8a0`071f6618=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b0b849 to fffff80002a8c740

fffff880`06c668a8 fffff800`02b0b849 : 00000000`00000050 ffffb8a0`071f6618 00000000`00000000 fffff880`06c66a10 : nt!KeBugCheckEx
fffff880`06c668b0 fffff800`02a8a82e : 00000000`00000000 00000000`00000000 fffffa80`00000000 fffff880`06c66b88 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`06c66a10 fffff880`01056fa9 : fffffa80`049ed440 00000000`00000000 fffff880`06c66c50 fffff880`0105632e : nt!KiPageFault+0x16e
fffff880`06c66ba0 fffff880`01056533 : fffffa80`04e38710 fffffa80`04e38710 fffffa80`05677180 fffffa80`0607a4c0 : fltmgr!GetContextFromStreamList+0x99
fffff880`06c66c20 fffff880`01f558a2 : fffffa80`04e38710 00000000`00000000 fffff8a0`001cc640 00000000`00000000 : fltmgr!FltGetStreamHandleContext+0x43
fffff880`06c66c50 fffff880`01054027 : 00000000`00000000 fffffa80`04e38710 fffffa80`0607aaa0 fffff880`06c66ca8 : luafv!LuafvPreClose+0x56
fffff880`06c66d40 fffff880`01054be9 : fffff880`06c66e00 00000000`00000302 fffffa80`049ed400 fffffa80`0607b200 : fltmgr!FltpPerformPreCallbacks+0x2f7
fffff880`06c66e40 fffff880`010536c7 : fffffa80`0477b750 fffffa80`049ed440 fffffa80`04759ac0 00000000`00000000 : fltmgr!FltpPassThrough+0x2d9
fffff880`06c66ec0 fffff800`02da278e : fffffa80`0442e620 fffffa80`0493f710 fffffa80`03c699e0 fffffa80`049ed440 : fltmgr!FltpDispatch+0xb7
fffff880`06c66f20 fffff800`02a918b4 : 00000000`00000000 fffffa80`06b1a060 fffffa80`03cdc080 fffff880`06c67030 : nt!IopDeleteFile+0x11e
fffff880`06c66fb0 fffff800`02da2514 : fffffa80`06b1a060 00000000`00000000 fffffa80`06b52b60 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`06c67010 fffff800`02da2414 : 00000000`00003b44 fffffa80`06b1a060 fffff8a0`00001a70 00000000`00003b44 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`06c670a0 fffff800`02a8b993 : fffffa80`06b52b60 fffff880`06c67170 fffffa80`04188430 fffffa80`06ea61a8 : nt!ObpCloseHandle+0x94
fffff880`06c670f0 fffff800`02a87f30 : fffff880`01076153 00000000`00000017 00000000`0000001f fffffa80`04188430 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06c67288 fffff880`01076153 : 00000000`00000017 00000000`0000001f fffffa80`04188430 00000000`000007ff : nt!KiServiceLinkage
fffff880`06c67290 fffff880`01077361 : 00000000`0000002d 00000000`00000056 00000000`00000020 00000000`00000000 : fltmgr!FltpExpandShortNames+0x283
fffff880`06c672f0 fffff880`0107713e : fffffa80`04188430 fffff880`06c60000 00000000`00000000 00000000`00000000 : fltmgr!FltpGetNormalizedFileNameWorker+0xc1
fffff880`06c67330 fffff880`01062b2d : c00000bb`06c67400 00000000`00000000 fffffa80`0607afb0 fffff880`06c68000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`06c67390 fffff880`0105cbd6 : fffffa80`04766080 fffffa80`0607a4c0 fffffa80`04d5d8f8 fffff880`06c676b8 : fltmgr!HandleStreamListNotSupported+0x15d
fffff880`06c673d0 fffff880`01063ad4 : fffffa80`04732d00 00000000`00000000 fffffa80`0607a4c0 00000000`00000101 : fltmgr! ?? ::FNODOBFM::`string'+0x3143
fffff880`06c67450 fffff880`01fa5529 : fffffa80`04188430 00000000`00000001 fffffa80`0608af00 fffff880`06c67540 : fltmgr!FltGetFileNameInformation+0x184
fffff880`06c674e0 fffffa80`04188430 : 00000000`00000001 fffffa80`0608af00 fffff880`06c67540 00000000`00000000 : aswFsBlk+0x5529
fffff880`06c674e8 00000000`00000001 : fffffa80`0608af00 fffff880`06c67540 00000000`00000000 00000000`00000000 : 0xfffffa80`04188430
fffff880`06c674f0 fffffa80`0608af00 : fffff880`06c67540 00000000`00000000 00000000`00000000 00000000`00130196 : 0x1
fffff880`06c674f8 fffff880`06c67540 : 00000000`00000000 00000000`00000000 00000000`00130196 fffff880`01fa5271 : 0xfffffa80`0608af00
fffff880`06c67500 00000000`00000000 : 00000000`00000000 00000000`00130196 fffff880`01fa5271 00000000`00000001 : 0xfffff880`06c67540


fffff880`01f558a2 85c0            test    eax,eax


SYMBOL_NAME:  luafv!LuafvPreClose+56

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  luafv.sys


FAILURE_BUCKET_ID:  X64_0x50_luafv!LuafvPreClose+56

BUCKET_ID:  X64_0x50_luafv!LuafvPreClose+56

Followup: MachineOwner

There are still remnants (all the drivers) of Avast, so you should use the uninstall utility found here, in safe mode:

AV Uninstallers - Windows 7 Forums


Update your Microsft keyboard driver:

NuidFltr NuidFltr.sys Fri May 08 04:53:31 2009

Software Download


Update your Microsoft LifeCam drivers:

VX6KCamd VX6KCamd.sys Mon Apr 27 21:46:40 2009
VX6000Xp VX6000Xp.sys Mon Apr 27 21:48:54 2009

Software Download

The LifeCam drivers are still the same. The crashes are either being caused by them or faulty RAM.

To be sure, you could disconnect the camera from the system and reboot. See if any stop errors happen like this. Or double check on updating the drivers again.

There's nothing to add, disconnect the cam and if bsod's continue then run memtest overnight:

Memtest86+ - Advanced Memory Diagnostic Tool


Invalid system memory was referenced. Typically the address is just plain bad or it is pointing at freed memory.
GetPointerFromAddress: unable to read from fffff80002cfa0e0

VX6KCamd.sys Tue Apr 28 04:46:40 2009
VX6000Xp.sys Tue Apr 28 04:48:54 2009


Honorable Member
Microsoft MVP
Cybercore is correct. If memtest doesnt reveal any memory errors you should run a system file check to verify (and repair) your system files
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then

read here for more information SFC /SCANNOW Command - System File Checker -

And if that turns out ok run driver verifier.

Beyond that, please run Verifier with these settings:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.