D
DMorais
Guest
Hello, I would like to know if anyone can help me. In just one day my computer "crashed" and shut down 3 times, one time i was playing and the other two times i was using it normally.
I opened the dmp file, and that was the result:
*******************************************************************************
* *
* 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: fffff8800fe000df, The address that the exception occurred at
Arg3: fffff88005f63088, Exception Record Address
Arg4: fffff88005f628f0, Context Record Address
Debugging Details:
------------------
fffff800035fb0e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff800036b6300
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on ODINSON-PC
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 2
Key : Analysis.Memory.CommitPeak.Mb
Value: 64
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8800fe000df
BUGCHECK_P3: fffff88005f63088
BUGCHECK_P4: fffff88005f628f0
EXCEPTION_RECORD: fffff88005f63088 -- (.exr 0xfffff88005f63088)
ExceptionAddress: fffff8800fe000df (nvlddmkm+0x00000000001580df)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000001fa0
Attempt to read from address 0000000000001fa0
CONTEXT: fffff88005f628f0 -- (.cxr 0xfffff88005f628f0)
rax=fffffa800e685150 rbx=0000000000000000 rcx=fffffa800fce8b30
rdx=fffffa800e685151 rsi=00000000ffffffff rdi=0000000000001fa0
rip=fffff8800fe000df rsp=fffff88005f632c0 rbp=000000000000000b
r8=fffffa800e685150 r9=0000000000000180 r10=fffff88003b8b2a0
r11=fffffa800c586c80 r12=0000000000000000 r13=fffffa800b32ec20
r14=00000000000020f0 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0x1580df:
fffff880`0fe000df 488b37 mov rsi,qword ptr [rdi] ds:002b:00000000`00001fa0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff800035fb0e8: Unable to get Flags value from nt!KdVersionBlock
fffff800035fb0e8: Unable to get Flags value from nt!KdVersionBlock
fffff800035fb0e8: Unable to get Flags value from nt!KdVersionBlock
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800036b62f0
GetUlongPtrFromAddress: unable to read from fffff800036b64a8
0000000000001fa0
ERROR_CODE: (NTSTATUS) 0xc0000005 - A instru o no 0x
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000001fa0
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`05f632c0 00000000`00e0ac20 : 00000000`00000000 00000000`00000100 fffff880`105cd610 fffff880`10548838 : nvlddmkm+0x1580df
fffff880`05f632c8 00000000`00000000 : 00000000`00000100 fffff880`105cd610 fffff880`10548838 fffff880`0fd73102 : 0xe0ac20
SYMBOL_NAME: nvlddmkm+1580df
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88005f628f0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+1580df
OS_VERSION: 7.1.7601.24520
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {23f1858c-0898-688a-839b-ff89feb86b17}
Followup: MachineOwner
Continue reading...
I opened the dmp file, and that was the result:
*******************************************************************************
* *
* 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: fffff8800fe000df, The address that the exception occurred at
Arg3: fffff88005f63088, Exception Record Address
Arg4: fffff88005f628f0, Context Record Address
Debugging Details:
------------------
fffff800035fb0e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff800036b6300
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on ODINSON-PC
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 2
Key : Analysis.Memory.CommitPeak.Mb
Value: 64
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8800fe000df
BUGCHECK_P3: fffff88005f63088
BUGCHECK_P4: fffff88005f628f0
EXCEPTION_RECORD: fffff88005f63088 -- (.exr 0xfffff88005f63088)
ExceptionAddress: fffff8800fe000df (nvlddmkm+0x00000000001580df)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000001fa0
Attempt to read from address 0000000000001fa0
CONTEXT: fffff88005f628f0 -- (.cxr 0xfffff88005f628f0)
rax=fffffa800e685150 rbx=0000000000000000 rcx=fffffa800fce8b30
rdx=fffffa800e685151 rsi=00000000ffffffff rdi=0000000000001fa0
rip=fffff8800fe000df rsp=fffff88005f632c0 rbp=000000000000000b
r8=fffffa800e685150 r9=0000000000000180 r10=fffff88003b8b2a0
r11=fffffa800c586c80 r12=0000000000000000 r13=fffffa800b32ec20
r14=00000000000020f0 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0x1580df:
fffff880`0fe000df 488b37 mov rsi,qword ptr [rdi] ds:002b:00000000`00001fa0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff800035fb0e8: Unable to get Flags value from nt!KdVersionBlock
fffff800035fb0e8: Unable to get Flags value from nt!KdVersionBlock
fffff800035fb0e8: Unable to get Flags value from nt!KdVersionBlock
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800036b62f0
GetUlongPtrFromAddress: unable to read from fffff800036b64a8
0000000000001fa0
ERROR_CODE: (NTSTATUS) 0xc0000005 - A instru o no 0x
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000001fa0
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`05f632c0 00000000`00e0ac20 : 00000000`00000000 00000000`00000100 fffff880`105cd610 fffff880`10548838 : nvlddmkm+0x1580df
fffff880`05f632c8 00000000`00000000 : 00000000`00000100 fffff880`105cd610 fffff880`10548838 fffff880`0fd73102 : 0xe0ac20
SYMBOL_NAME: nvlddmkm+1580df
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr 0xfffff88005f628f0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+1580df
OS_VERSION: 7.1.7601.24520
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {23f1858c-0898-688a-839b-ff89feb86b17}
Followup: MachineOwner
Continue reading...