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 1e help.

18 Apr 2011   #1

Win 7 64-bit
 
 
BSOD 1e help.

I have been crashing multiple times today and cant figure out why. Can someone take a look and let me know?

My System SpecsSystem Spec
.

18 Apr 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Dgsims View Post
I have been crashing multiple times today and cant figure out why. Can someone take a look and let me know?

Easy your Avast. Remove and replace with Microsoft Security Essentials

AVG - Download tools

http://www.microsoft.com/security_essentials/

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


Loading Dump File [C:\Users\K\Desktop\New folder (2)\041811-16520-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03468000 PsLoadedModuleList = 0xfffff800`036ade90
Debug session time: Mon Apr 18 20:38:33.824 2011 (GMT-4)
System Uptime: 0 days 0:00:35.353
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff880010eecd2, 1, 24}

Unable to load image 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
Probably caused by : aswFsBlk.SYS ( aswFsBlk+5589 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880010eecd2, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000024, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
fltmgr!FltpParseStreamName+32
fffff880`010eecd2 664489442440    mov     word ptr [rsp+40h],r8w

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000024

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800037190e8
 0000000000000024 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  taskeng.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880075b3e80 -- (.trap 0xfffff880075b3e80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80066d1850
rdx=fffffa80066d186e rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010eecd2 rsp=fffff880075b4010 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000037
r11=fffffa80066d1850 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fltmgr!FltpParseStreamName+0x32:
fffff880`010eecd2 664489442440    mov     word ptr [rsp+40h],r8w ss:0018:fffff880`075b4050=0000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003534028 to fffff800034e8640

STACK_TEXT:  
fffff880`075b35f8 fffff800`03534028 : 00000000`0000001e ffffffff`c0000005 fffff880`010eecd2 00000000`00000001 : nt!KeBugCheckEx
fffff880`075b3600 fffff800`034e7cc2 : fffff880`075b3dd8 fffff880`075b4098 fffff880`075b3e80 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`075b3ca0 fffff800`034e683a : 00000000`00000001 00000000`00000024 fffffa80`06802800 fffff880`075b4098 : nt!KiExceptionDispatch+0xc2
fffff880`075b3e80 fffff880`010eecd2 : fffffa80`068028d0 fffff880`011022fe fffff880`075b6000 fffff880`075b000c : nt!KiPageFault+0x23a
fffff880`075b4010 fffff880`010eef68 : 00000000`00000000 00000000`00000000 fffffa80`068028d0 00000000`00000000 : fltmgr!FltpParseStreamName+0x32
fffff880`075b4050 fffff880`010eee1e : fffffa80`068028d0 fffff880`010cf132 00000000`00000000 00000000`00000000 : fltmgr!FltpGetNormalizedFileNameWorker+0xa8
fffff880`075b4090 fffff880`010dab9d : c00000bb`075b4200 00000000`00000000 fffffa80`04ce56b0 fffff880`075b6000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`075b40f0 fffff880`010d4bf6 : fffffa80`0399a080 fffffa80`04ce5310 fffffa80`04978108 fffff880`0111f052 : fltmgr!HandleStreamListNotSupported+0x15d
fffff880`075b4130 fffff880`010dbb44 : fffffa80`068f1b00 00000000`00000000 fffffa80`04ce5310 00000000`00000101 : fltmgr! ?? ::FNODOBFM::`string'+0x30f3
fffff880`075b41b0 fffff880`04ea8589 : fffffa80`068028d0 00000000`00000001 fffffa80`05aa8c01 fffff880`075b42a0 : fltmgr!FltGetFileNameInformation+0x184
fffff880`075b4240 fffffa80`068028d0 : 00000000`00000001 fffffa80`05aa8c01 fffff880`075b42a0 fffffa80`049e5d00 : aswFsBlk+0x5589
fffff880`075b4248 00000000`00000001 : fffffa80`05aa8c01 fffff880`075b42a0 fffffa80`049e5d00 00000000`00000000 : 0xfffffa80`068028d0
fffff880`075b4250 fffffa80`05aa8c01 : fffff880`075b42a0 fffffa80`049e5d00 00000000`00000000 00000000`00120189 : 0x1
fffff880`075b4258 fffff880`075b42a0 : fffffa80`049e5d00 00000000`00000000 00000000`00120189 fffff880`04ea825a : 0xfffffa80`05aa8c01
fffff880`075b4260 fffffa80`049e5d00 : 00000000`00000000 00000000`00120189 fffff880`04ea825a 00000000`00000001 : 0xfffff880`075b42a0
fffff880`075b4268 00000000`00000000 : 00000000`00120189 fffff880`04ea825a 00000000`00000001 fffffa80`0682d8e0 : 0xfffffa80`049e5d00


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswFsBlk+5589
fffff880`04ea8589 ??              ???

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  aswFsBlk+5589

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswFsBlk

IMAGE_NAME:  aswFsBlk.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d651fc0

FAILURE_BUCKET_ID:  X64_0x1E_aswFsBlk+5589

BUCKET_ID:  X64_0x1E_aswFsBlk+5589

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

1: kd> lmvm aswFsBlk
start             end                 module name
fffff880`04ea3000 fffff880`04eac000   aswFsBlk T (no symbols)           
    Loaded symbol image file: aswFsBlk.SYS
    Image path: aswFsBlk.SYS
    Image name: aswFsBlk.SYS
    Timestamp:        Wed Feb 23 09:54:56 2011 (4D651FC0)
    CheckSum:         00007421
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
Reply

 BSOD 1e help.




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 01:28 PM.
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