New
#21
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M. Usual caused by Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.
This one points to memory corruption.Code:Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50 Debug session time: Mon Aug 30 19:13:28.617 2010 (GMT-4) System Uptime: 0 days 7:40:23.006 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80002b45a86, fffff880033e78a8, fffff880033e7110} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49705 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002b45a86, The address that the exception occurred at Arg3: fffff880033e78a8, Exception Record Address Arg4: fffff880033e7110, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt! ?? ::FNODOBFM::`string'+49705 fffff800`02b45a86 488b00 mov rax,qword ptr [rax] EXCEPTION_RECORD: fffff880033e78a8 -- (.exr 0xfffff880033e78a8) ExceptionAddress: fffff80002b45a86 (nt! ?? ::FNODOBFM::`string'+0x0000000000049705) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880033e7110 -- (.cxr 0xfffff880033e7110) rax=6d3d6362b5379cf8 rbx=0000000000000000 rcx=6d3d6362b5379cf8 rdx=fffffa80079a7000 rsi=fffff880033e7ba0 rdi=fffffa800438ab48 rip=fffff80002b45a86 rsp=fffff880033e7ae0 rbp=0000000000000002 r8=0000000000000001 r9=fffffa800438ab48 r10=0000000000000005 r11=0000000000000000 r12=0000000000000001 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt! ?? ::FNODOBFM::`string'+0x49705: fffff800`02b45a86 488b00 mov rax,qword ptr [rax] ds:002b:6d3d6362`b5379cf8=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: LogonUI.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfb0e0 ffffffffffffffff FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+49705 fffff800`02b45a86 488b00 mov rax,qword ptr [rax] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff80002ad7ee2 to fffff80002b45a86 STACK_TEXT: fffff880`033e7ae0 fffff800`02ad7ee2 : 00000000`00006be7 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x49705 fffff880`033e7b80 fffff800`02ad8173 : 00000000`00000008 fffff880`033e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`033e7bd0 fffff800`02d67c06 : fffffa80`03b7c680 00000000`00000080 fffffa80`03b50990 00000000`00000001 : nt!KeBalanceSetManager+0x1c3 fffff880`033e7d40 fffff800`02aa1c26 : fffff880`009b1180 fffffa80`03b7c680 fffff880`009bc0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033e7d80 00000000`00000000 : fffff880`033e8000 fffff880`033e2000 fffff880`033e7710 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+49705 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880033e7110 ; kb FAILURE_BUCKET_ID: X64_0x7E_nt!_??_::FNODOBFM::_string_+49705 BUCKET_ID: X64_0x7E_nt!_??_::FNODOBFM::_string_+49705 Followup: MachineOwner ---------
Let's test your RAM
RAM - Test with Memtest86+
Post back with the results.