New
#11
I am glad we are making progress; that is good news. But we want to get you BSOD free.
Error code 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes are Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.
The dump indicates a hardware/driver problem.I still find an obsolete driver on your system. The dumps shows a memory error, c0000005 (Access violation). As I stated previously, that driver may not be the cause of your crash; but it is not helping the stability of your system.Code:Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50 Debug session time: Tue Sep 7 20:28:21.261 2010 (GMT-4) System Uptime: 0 days 0:41:56.712 Loading Kernel Symbols ............................................................... ................................................................ ........ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff8800104391f, 0, 58434ffe} Probably caused by : fltmgr.sys ( fltmgr!FltpPassThrough+f ) Followup: MachineOwner --------- 0: 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: fffff8800104391f, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000058434ffe, 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!FltpPassThrough+f fffff880`0104391f 498bb0b8000000 mov rsi,qword ptr [r8+0B8h] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000058434ffe READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d070e0 0000000058434ffe CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 EXCEPTION_RECORD: fffff88002849d08 -- (.exr 0xfffff88002849d08) ExceptionAddress: fffff8800104391f (fltmgr!FltpPassThrough+0x000000000000000f) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000058434ffe Attempt to read from address 0000000058434ffe TRAP_FRAME: fffff88002849db0 -- (.trap 0xfffff88002849db0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8004dd8010 rbx=0000000000000000 rcx=fffff88002849fe0 rdx=fffffa8004752a40 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800104391f rsp=fffff88002849f40 rbp=0000000000000001 r8=0000000058434f46 r9=000000000000000c r10=fffffa8003d21090 r11=0000000000000006 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc fltmgr!FltpPassThrough+0xf: fffff880`0104391f 498bb0b8000000 mov rsi,qword ptr [r8+0B8h] ds:f000:00000000`58434ffe=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002b09a39 to fffff80002acf740 STACK_TEXT: fffff880`02849538 fffff800`02b09a39 : 00000000`0000001e ffffffff`c0000005 fffff880`0104391f 00000000`00000000 : nt!KeBugCheckEx fffff880`02849540 fffff800`02aced82 : fffff880`02849d08 fffff880`02849fe0 fffff880`02849db0 fffffa80`056ad330 : nt!KiDispatchException+0x1b9 fffff880`02849bd0 fffff800`02acd8fa : 00000000`00000000 fffff880`02849fe0 fffffa80`0510a000 fffff800`02c81300 : nt!KiExceptionDispatch+0xc2 fffff880`02849db0 fffff880`0104391f : fffffa80`00004001 fffffa80`065e80b8 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x23a fffff880`02849f40 fffff880`010426c7 : 00000000`00000001 fffff800`02dd49f0 fffff880`0284a100 00000000`00000801 : fltmgr!FltpPassThrough+0xf fffff880`02849fc0 fffffa80`04590010 : 00000000`00000b60 fffffa80`04dd8108 fffffa80`045ba1d0 fffffa80`065e80e8 : fltmgr!FltpDispatch+0xb7 fffff880`0284a020 00000000`00000b60 : fffffa80`04dd8108 fffffa80`045ba1d0 fffffa80`065e80e8 00000000`000000d6 : 0xfffffa80`04590010 fffff880`0284a028 fffffa80`04dd8108 : fffffa80`045ba1d0 fffffa80`065e80e8 00000000`000000d6 00000000`00000000 : 0xb60 fffff880`0284a030 fffffa80`045ba1d0 : fffffa80`065e80e8 00000000`000000d6 00000000`00000000 00000000`00000001 : 0xfffffa80`04dd8108 fffff880`0284a038 fffffa80`065e80e8 : 00000000`000000d6 00000000`00000000 00000000`00000001 fffffa80`056ad330 : 0xfffffa80`045ba1d0 fffff880`0284a040 00000000`000000d6 : 00000000`00000000 00000000`00000001 fffffa80`056ad330 fffffa80`045ba1d0 : 0xfffffa80`065e80e8 fffff880`0284a048 00000000`00000000 : 00000000`00000001 fffffa80`056ad330 fffffa80`045ba1d0 fffffa80`0434e738 : 0xd6 STACK_COMMAND: kb FOLLOWUP_IP: fltmgr!FltpPassThrough+f fffff880`0104391f 498bb0b8000000 mov rsi,qword ptr [r8+0B8h] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: fltmgr!FltpPassThrough+f FOLLOWUP_NAME: MachineOwner MODULE_NAME: fltmgr IMAGE_NAME: fltmgr.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11f FAILURE_BUCKET_ID: X64_0x1E_fltmgr!FltpPassThrough+f BUCKET_ID: X64_0x1E_fltmgr!FltpPassThrough+f Followup: MachineOwner ---------
Rtnic64.sys Mon Mar 31 01:39:38 2008 - Realtek Ethernet NIC driver Realtek
This driver really needs to be updated; it is a pre-Windows 7 driver.
Quote