Šark Šream.prog
03-01-2009, 10:20
Salve ragazzi, ho da poco montato il mio nuovo pc...
Ho installato vista e ieri mentre navigavo in internet si č presentata una schermata blu...
ho usato windbg per leggere il dump del crash ma non riesco a capire cosa ha provocato l'errore..
posto il contenuto del file:
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: fffff9800d277652, The address that the exception occurred at
Arg3: fffff9800d2e0a58, Exception Record Address
Arg4: fffff9800d2e0430, Context Record Address
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
MODULE_NAME: HTTP
FAULTING_MODULE: fffff80001c00000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4549be6a
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.
FAULTING_IP:
HTTP!UlPrepareAuthCacheKeyHash+2
fffff980`0d277652 4d8b2424 mov r12,qword ptr [r12]
EXCEPTION_RECORD: fffff9800d2e0a58 -- (.exr 0xfffff9800d2e0a58)
ExceptionAddress: fffff9800d277652 (HTTP!UlPrepareAuthCacheKeyHash+0x0000000000000002)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: fffff9800d2e0430 -- (.cxr 0xfffff9800d2e0430)
rax=fffffa8004ca6700 rbx=01c96d252a185aed rcx=fffffa8004ca6700
rdx=fffffa8004cdd010 rsi=00000000000000b4 rdi=fffffa8004cdfd70
rip=fffff9800d277652 rsp=fffff9800d2e0c90 rbp=fffffa8004cdfd78
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffffa8001cd61e8 r12=0000000000000000 r13=fffffa8004cdfd78
r14=fffffa8004cdd000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
HTTP!UlPrepareAuthCacheKeyHash+0x2:
fffff980`0d277652 4d8b2424 mov r12,qword ptr [r12] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff9800d277652
STACK_TEXT:
fffff980`0d2e0c90 00000000`00000000 : fffffa80`04cdc010 ffff0000`000aa4bb 00000000`00000004 00000000`00000004 : HTTP!UlPrepareAuthCacheKeyHash+0x2
FOLLOWUP_IP:
HTTP!UlPrepareAuthCacheKeyHash+2
fffff980`0d277652 4d8b2424 mov r12,qword ptr [r12]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: HTTP!UlPrepareAuthCacheKeyHash+2
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: HTTP.sys
STACK_COMMAND: .cxr 0xfffff9800d2e0430 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Ho installato vista e ieri mentre navigavo in internet si č presentata una schermata blu...
ho usato windbg per leggere il dump del crash ma non riesco a capire cosa ha provocato l'errore..
posto il contenuto del file:
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: fffff9800d277652, The address that the exception occurred at
Arg3: fffff9800d2e0a58, Exception Record Address
Arg4: fffff9800d2e0430, Context Record Address
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
MODULE_NAME: HTTP
FAULTING_MODULE: fffff80001c00000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4549be6a
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.
FAULTING_IP:
HTTP!UlPrepareAuthCacheKeyHash+2
fffff980`0d277652 4d8b2424 mov r12,qword ptr [r12]
EXCEPTION_RECORD: fffff9800d2e0a58 -- (.exr 0xfffff9800d2e0a58)
ExceptionAddress: fffff9800d277652 (HTTP!UlPrepareAuthCacheKeyHash+0x0000000000000002)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
CONTEXT: fffff9800d2e0430 -- (.cxr 0xfffff9800d2e0430)
rax=fffffa8004ca6700 rbx=01c96d252a185aed rcx=fffffa8004ca6700
rdx=fffffa8004cdd010 rsi=00000000000000b4 rdi=fffffa8004cdfd70
rip=fffff9800d277652 rsp=fffff9800d2e0c90 rbp=fffffa8004cdfd78
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffffa8001cd61e8 r12=0000000000000000 r13=fffffa8004cdfd78
r14=fffffa8004cdd000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
HTTP!UlPrepareAuthCacheKeyHash+0x2:
fffff980`0d277652 4d8b2424 mov r12,qword ptr [r12] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff9800d277652
STACK_TEXT:
fffff980`0d2e0c90 00000000`00000000 : fffffa80`04cdc010 ffff0000`000aa4bb 00000000`00000004 00000000`00000004 : HTTP!UlPrepareAuthCacheKeyHash+0x2
FOLLOWUP_IP:
HTTP!UlPrepareAuthCacheKeyHash+2
fffff980`0d277652 4d8b2424 mov r12,qword ptr [r12]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: HTTP!UlPrepareAuthCacheKeyHash+2
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: HTTP.sys
STACK_COMMAND: .cxr 0xfffff9800d2e0430 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------