Ayuda

21/08/2005 - 11:17 por quejio | Informe spam
Hola, resulta que ultimamente estoy teniendo una serie de pantallazos azules,
y me he aventurado en usar el windbg, pero soy incapaz de saber exactamente
cual es el error. Por lo que me dice el problema es de un controlador,
incluso puede ser del antivirus, pero no soy capaz de averiguar analizandolo,
por lo que pido ayuda. Si eso a ver si os podreis poner en contacto en
quejio@gmail.com y asi poder enviaros el MEMORY.DMP para saber si vosotros
sabeis contestar eso. Gracias
 

Leer las respuestas

#1 quejio
21/08/2005 - 11:58 | Informe spam
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Aug 21 10:56:25.843 2005 (GMT+2)
System Uptime: 0 days 0:24:45.544
Loading Kernel Symbols
...
Loading unloaded module list
.
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 13dbe, 3, 0}

Probably caused by : memory_corruption ( nt!MiEliminateWorkingSetEntry+250 )

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: 00013dbe, page frame number
Arg3: 00000003, current page state
Arg4: 00000000, 0

Debugging Details:



DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x4E

LAST_CONTROL_TRANSFER: from 805228ad to 805371aa

STACK_TEXT:
f89aac68 805228ad 0000004e 00000099 00013dbe nt!KeBugCheckEx+0x1b
f89aac98 80507094 01006433 c036f4a4 00000000
nt!MiEliminateWorkingSetEntry+0x250
f89aacc0 80539143 00006433 c0c0003c c036f4a4 nt!MiFreeWsle+0x45
f89aacec 80527911 0000018a c0c0003c 00000002 nt!MiTrimWorkingSet+0x6e
f89aad38 804e6630 00000000 81fbeda8 00000000 nt!MmWorkingSetManager+0x160
f89aadac 80574128 00000000 00000000 00000000 nt!KeBalanceSetManager+0x97
f89aaddc 804efc81 804e659f 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
nt!MiEliminateWorkingSetEntry+250
805228ad 008b461cc1e0 add [ebx+0xe0c11c46],cl

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiEliminateWorkingSetEntry+250

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

STACK_COMMAND: kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_nt!MiEliminateWorkingSetEntry+250

BUCKET_ID: 0x4E_nt!MiEliminateWorkingSetEntry+250

Followup: MachineOwner


ahi teneis lo que me sale en el windbg, espero alguna instruccion, gracias

Preguntas similares