kamacio1
29-08-2008, 10:08
Ciao a tutti,ho letto tutto il thread "Windows dump" perchè mi interessa da vicino, ho un problema di riavvio del PC da ormai qualche mese e ora ho deciso
di capire esattamente a cosa imputarlo.
Ho visto che tra voi c'è gente in grado di interpretare il log del programma Windbg, io purtroppo non ne sono capace.Se foste così gentili da dargli
un'occhiata mi fareste un grande favore:grazie!
Il log è il seguente:
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS_SYMBOL_REPOSITORY\Mini082908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\WINDOWS_SYMBOL_REPOSITORY*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81808000 PsLoadedModuleList = 0x81915930
Debug session time: Fri Aug 29 09:19:41.094 2008 (GMT+2)
System Uptime: 0 days 0:00:51.704
Loading Kernel Symbols
......................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {8d, 16128, 510001, c00001c1}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+2bd )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000008d,
Arg2: 00016128
Arg3: 00510001
Arg4: c00001c1
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_8d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 81845058 to 818c36d9
STACK_TEXT:
80699d24 81845058 0000004e 0000008d 00016128 nt!KeBugCheckEx+0x1e
80699d74 8195a039 80699dc0 819b06d5 80810b98 nt!MmZeroPageThread+0x2bd
80699d7c 819b06d5 80810b98 f96ffe76 00000000 nt!Phase1Initialization+0x12
80699dc0 81897686 8195a027 80810b98 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmZeroPageThread+2bd
81845058 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MmZeroPageThread+2bd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4812bd66
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_8d_nt!MmZeroPageThread+2bd
BUCKET_ID: 0x4E_8d_nt!MmZeroPageThread+2bd
Followup: MachineOwner
---------
di capire esattamente a cosa imputarlo.
Ho visto che tra voi c'è gente in grado di interpretare il log del programma Windbg, io purtroppo non ne sono capace.Se foste così gentili da dargli
un'occhiata mi fareste un grande favore:grazie!
Il log è il seguente:
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS_SYMBOL_REPOSITORY\Mini082908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\WINDOWS_SYMBOL_REPOSITORY*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81808000 PsLoadedModuleList = 0x81915930
Debug session time: Fri Aug 29 09:19:41.094 2008 (GMT+2)
System Uptime: 0 days 0:00:51.704
Loading Kernel Symbols
......................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {8d, 16128, 510001, c00001c1}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+2bd )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000008d,
Arg2: 00016128
Arg3: 00510001
Arg4: c00001c1
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_8d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 81845058 to 818c36d9
STACK_TEXT:
80699d24 81845058 0000004e 0000008d 00016128 nt!KeBugCheckEx+0x1e
80699d74 8195a039 80699dc0 819b06d5 80810b98 nt!MmZeroPageThread+0x2bd
80699d7c 819b06d5 80810b98 f96ffe76 00000000 nt!Phase1Initialization+0x12
80699dc0 81897686 8195a027 80810b98 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmZeroPageThread+2bd
81845058 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MmZeroPageThread+2bd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4812bd66
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_8d_nt!MmZeroPageThread+2bd
BUCKET_ID: 0x4E_8d_nt!MmZeroPageThread+2bd
Followup: MachineOwner
---------