|
Member
Iscritto dal: Apr 2008
Città: Trieste
Messaggi: 34
|
Ciao, ragazzi allora il pc di un mio amico si impalla principalmente quando accede alla rete internet, mentre quando guarda film o fa altro il pc sembra funzionare bene. Di seguito il listato del debugger, io non ci ho capito molto, qualcuno può aiutarmi?
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Fabio\Desktop\Minidump\Mini111909-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols;set _NT_SYMBOL_PATH=srv*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Thu Nov 19 18:36:39.046 2009 (GMT+1)
System Uptime: 0 days 0:07:35.609
Loading Kernel Symbols
...............................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {ffffffec, 1, 804d9079, 0}
Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!NtWaitForMultipleObjects+2ec )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 804d9079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffec
FAULTING_IP:
nt!ObfDereferenceObject+2c
804d9079 0fc101 xadd dword ptr [ecx],eax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 805668be to 804d9079
STACK_TEXT:
b55779d8 805668be b5577d64 01f9fbf0 805666c6 nt!ObfDereferenceObject+0x2c
b5577d48 804de7ec 0000001e 031a6678 00000001 nt!NtWaitForMultipleObjects+0x2ec
b5577d48 7c91e514 0000001e 031a6678 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01f9fc70 00000000 00000000 00000000 00000000 0x7c91e514
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+2ec
805668be ebe9 jmp nt!NtWaitForMultipleObjects+0x2ec (805668a9)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!NtWaitForMultipleObjects+2ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a
FAILURE_BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
BUCKET_ID: 0x50_nt!NtWaitForMultipleObjects+2ec
Followup: MachineOwner
|