View Single Post
14 Mar 2010  
jcgriff2

Windows 7 - Vista
 
 

The bugcheck on the lone dump = 0x1e (0xc0000005,,,) = kernel mode exception; exception = 0xc0000005 = memory access violation. NT Kernel named as probable cause (default).

Run the driver verifier --> Tech Support Forum - View Single Post - Windows Has Recovered From Unexpected Shutdown - Blue Screen of Death - BSOD

Attach the zipped msinfo32 NFO file to next post.

Regards. . .

jcgriff2

.

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

Loading Dump File [C:\Users\PalmDesert7\AppData\Local\Temp\Temp1_031310-20264-01[1].zip\031310-20264-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

Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03258e50
Debug session time: Sat Mar 13 07:26:42.911 2010 (GMT-5)
System Uptime: 1 days 3:24:03.160
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8800c1ebf70, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KipFatalFilter+1b )
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: fffff8800c1ebf70, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, 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: 
+0
fffff880`0c1ebf70 98              cwde
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c30e0
 0000000000000000 
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
CURRENT_IRQL:  2
EXCEPTION_RECORD:  fffff8800c1ece98 -- (.exr 0xfffff8800c1ece98)
ExceptionAddress: fffff8000308ef16 (nt!RtlCopyMemoryNonTemporal+0x0000000000000016)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME:  fffff8800c1ecf40 -- (.trap 0xfffff8800c1ecf40)
Unable to read trap frame at fffff880`0c1ecf40
LAST_CONTROL_TRANSFER:  from fffff8000311db2b to fffff8000308cf00
STACK_TEXT:  
fffff880`0c1ebeb8 fffff800`0311db2b : 00000000`0000001e ffffffff`c0000005 fffff880`0c1ebf70 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c1ebec0 fffff800`030e0390 : fffffa80`0805b1f0 00000000`00000000 00000000`043a088e 00000000`00000001 : nt!KipFatalFilter+0x1b
fffff880`0c1ebf00 fffff800`030bb4dc : 00000000`00000000 00000000`00000000 fffffa80`0805b1f0 fffffa80`06f17e20 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`0c1ebf40 fffff800`030b2bed : fffff800`031d3470 fffff880`0c1ee5d0 00000000`00000000 fffff800`0301b000 : nt!_C_specific_handler+0x8c
fffff880`0c1ebfb0 fffff800`030ba250 : fffff800`031d3470 fffff880`0c1ec028 fffff880`0c1ece98 fffff800`0301b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0c1ebfe0 fffff800`030c71b5 : fffff880`0c1ece98 fffff880`0c1ec6f0 fffff880`00000000 00000000`00000007 : nt!RtlDispatchException+0x410
fffff880`0c1ec6c0 fffff800`0308c542 : fffff880`0c1ece98 005c0033`0065006d fffff880`0c1ecf40 00000000`000000cd : nt!KiDispatchException+0x135
fffff880`0c1ecd60 fffff800`0308ae4a : fffffa80`0805bf30 fffff880`04a1a71d 00000000`00000000 fffffa80`0805b1f0 : nt!KiExceptionDispatch+0xc2
fffff880`0c1ecf40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KipFatalFilter+1b
fffff800`0311db2b cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!KipFatalFilter+1b
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_0x1E_nt!KipFatalFilter+1b
BUCKET_ID:  X64_0x1E_nt!KipFatalFilter+1b
Followup: MachineOwner
---------
1: kd> .exr 0xfffff8800c1ece98
ExceptionAddress: fffff8000308ef16 (nt!RtlCopyMemoryNonTemporal+0x0000000000000016)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
My System SpecsSystem Spec