Hej, Jag har ett litet problem med min dator (Som vanligt
)
Det senaste när jag har spelat WoW så har datorn startat om sig själv. Utan blue screen eller nåt.
Jag uppskattar all hjälp jag kan få.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini090109-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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Sep 1 22:29:54.656 2009 (GMT+2)
System Uptime: 0 days 0:11:50.238
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, 2601b3, 7, 0}
Probably caused by : ntoskrnl.exe ( nt!_woutput+414 )
Followup: MachineOwner
---------
0: 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: 002601b3, page frame number
Arg3: 00000007, current page state
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: Wow.exe
LAST_CONTROL_TRANSFER: from 00000000 to 804f9f43
STACK_TEXT:
a8c06bc4 00000000 0000004e 00000099 002601b3 nt!_woutput+0x414
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!_woutput+414
804f9f43 5d pop ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!_woutput+414
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3
FAILURE_BUCKET_ID: 0x4E_99_nt!_woutput+414
BUCKET_ID: 0x4E_99_nt!_woutput+414
Followup: MachineOwner
) Det senaste när jag har spelat WoW så har datorn startat om sig själv. Utan blue screen eller nåt.
Jag uppskattar all hjälp jag kan få.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini090109-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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Sep 1 22:29:54.656 2009 (GMT+2)
System Uptime: 0 days 0:11:50.238
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, 2601b3, 7, 0}
Probably caused by : ntoskrnl.exe ( nt!_woutput+414 )
Followup: MachineOwner
---------
0: 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: 002601b3, page frame number
Arg3: 00000007, current page state
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: Wow.exe
LAST_CONTROL_TRANSFER: from 00000000 to 804f9f43
STACK_TEXT:
a8c06bc4 00000000 0000004e 00000099 002601b3 nt!_woutput+0x414
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!_woutput+414
804f9f43 5d pop ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!_woutput+414
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3
FAILURE_BUCKET_ID: 0x4E_99_nt!_woutput+414
BUCKET_ID: 0x4E_99_nt!_woutput+414
Followup: MachineOwner