lello89
25-04-2008, 16:30
Salve a tutti, è da un po di tempo che si verifica un errore...il mio pc si riavvia di continuo(soprattutto quando è sotto sforzo) e nella schermata blu mi esce il seguente errore: PFN_LIST_CORRUPT.
Cercando di capirci un pò di più ho aperto il minidump...e in pratica ho capito che l'errore deriva dal file NTOSKRNL.EXE...
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini042508-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Fri Apr 25 16:09:53.171 2008 (GMT+2)
System Uptime: 0 days 1:11:20.759
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, ff16, 1, 0}
Probably caused by : memory_corruption ( nt!MiCaptureWriteWatchDirtyBit+45 )
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: 00000099, A PTE or PFN is corrupt
Arg2: 0000ff16, page frame number
Arg3: 00000001, current page state
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: WindowsXP-KB835
LAST_CONTROL_TRANSFER: from 80524a2a to 8053354e
STACK_TEXT:
b5f36bbc 80524a2a 0000004e 00000099 0000ff16 nt!KeBugCheck2+0x704
b5f36be8 804ff585 c0506cd0 00000d8d 89462810 nt!MiCaptureWriteWatchDirtyBit+0x45
b5f36c08 805846bf 01848201 89462618 003ffffc nt!RtlpStatusTable+0x31d
b5f36c28 804ff36f 89462618 89462750 89462618 nt!NtAcceptConnectPort+0x6a0
b5f36c60 805849a3 00462618 88ef1da8 88ef1ff0 nt!RtlpStatusTable+0x107
b5f36d08 8057b746 00000000 88ef1da8 00000000 nt!CmpQueryKeyDataFromCache+0x77
b5f36d28 80584828 88ef1da8 00000000 b5f36d64 nt!MiSetProtectionOnSection+0x270
b5f36d54 804de7ec 00000000 00000000 0006ff58 nt!NtSetInformationThread+0x3bc
b5f36d64 7c91eb94 badb0d00 0006fe64 88ef1da8 nt!KiUnexpectedInterrupt65+0x2
WARNING: Frame IP not in any known module. Following frames may be wrong.
b5f36d68 badb0d00 0006fe64 88ef1da8 00000000 0x7c91eb94
b5f36d6c 0006fe64 88ef1da8 00000000 00000000 0xbadb0d00
b5f36d70 88ef1da8 00000000 00000000 00000000 0x6fe64
b5f36d74 00000000 00000000 00000000 00000000 0x88ef1da8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiCaptureWriteWatchDirtyBit+45
80524a2a ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiCaptureWriteWatchDirtyBit+45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 45e54711
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_99_nt!MiCaptureWriteWatchDirtyBit+45
BUCKET_ID: 0x4E_99_nt!MiCaptureWriteWatchDirtyBit+45
Followup: MachineOwner
qualcuno sa spiegarmi cosè e come risolvere? GRAZIE!!!
Cercando di capirci un pò di più ho aperto il minidump...e in pratica ho capito che l'errore deriva dal file NTOSKRNL.EXE...
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini042508-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Fri Apr 25 16:09:53.171 2008 (GMT+2)
System Uptime: 0 days 1:11:20.759
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, ff16, 1, 0}
Probably caused by : memory_corruption ( nt!MiCaptureWriteWatchDirtyBit+45 )
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: 00000099, A PTE or PFN is corrupt
Arg2: 0000ff16, page frame number
Arg3: 00000001, current page state
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: WindowsXP-KB835
LAST_CONTROL_TRANSFER: from 80524a2a to 8053354e
STACK_TEXT:
b5f36bbc 80524a2a 0000004e 00000099 0000ff16 nt!KeBugCheck2+0x704
b5f36be8 804ff585 c0506cd0 00000d8d 89462810 nt!MiCaptureWriteWatchDirtyBit+0x45
b5f36c08 805846bf 01848201 89462618 003ffffc nt!RtlpStatusTable+0x31d
b5f36c28 804ff36f 89462618 89462750 89462618 nt!NtAcceptConnectPort+0x6a0
b5f36c60 805849a3 00462618 88ef1da8 88ef1ff0 nt!RtlpStatusTable+0x107
b5f36d08 8057b746 00000000 88ef1da8 00000000 nt!CmpQueryKeyDataFromCache+0x77
b5f36d28 80584828 88ef1da8 00000000 b5f36d64 nt!MiSetProtectionOnSection+0x270
b5f36d54 804de7ec 00000000 00000000 0006ff58 nt!NtSetInformationThread+0x3bc
b5f36d64 7c91eb94 badb0d00 0006fe64 88ef1da8 nt!KiUnexpectedInterrupt65+0x2
WARNING: Frame IP not in any known module. Following frames may be wrong.
b5f36d68 badb0d00 0006fe64 88ef1da8 00000000 0x7c91eb94
b5f36d6c 0006fe64 88ef1da8 00000000 00000000 0xbadb0d00
b5f36d70 88ef1da8 00000000 00000000 00000000 0x6fe64
b5f36d74 00000000 00000000 00000000 00000000 0x88ef1da8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiCaptureWriteWatchDirtyBit+45
80524a2a ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiCaptureWriteWatchDirtyBit+45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 45e54711
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_99_nt!MiCaptureWriteWatchDirtyBit+45
BUCKET_ID: 0x4E_99_nt!MiCaptureWriteWatchDirtyBit+45
Followup: MachineOwner
qualcuno sa spiegarmi cosè e come risolvere? GRAZIE!!!