Windows XP - Error 0x00000d1 XP

 
Vista:

Error 0x00000d1 XP

Publicado por Pepe (3 intervenciones) el 18/12/2005 16:21:57
Sufro constantes reinicios causados por un driver que hace una llamada a una posición de memoria que no existe. Mi problema viene al intentar localizar al driver causante de esto. He hecho un volcado de memoria completa y al analizarlo con windbg me sale lo siguiente:

Loading Dump File [C:\WINDOWS\MEMORY2.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 Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Dec 18 16:18:59.515 2005 (GMT+1)
System Uptime: 0 days 15:54:12.206
Loading Kernel Symbols
.....................................................................................................................................................................................
Loading unloaded module list
..................................
Loading User Symbols
......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {c90018, 2, 1, 7c921713}

Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+238 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00c90018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c921713, address which referenced memory

Debugging Details:
------------------

WRITE_ADDRESS: 00c90018

CURRENT_IRQL: 2

FAULTING_IP:
ntdll!RtlAllocateHeap+c5a
7c921713 66894118 mov [ecx+0x18],ax

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 7c921713 to 804e0aac

STACK_TEXT:
b8ac5d64 7c921713 badb0d00 7c91eb94 b8ac5d98 nt!KiTrap0E+0x238
00c8ef80 7c809a0f 00090000 00140000 0035c024 ntdll!RtlAllocateHeap+0xc5a
00c8efcc 76d2283c 00000000 0035c024 00c8f010 kernel32!LocalAlloc+0x58
00c8efdc 76d2299a 0035c024 000aec98 000a08e8 iphlpapi!GrabMemory+0x10
00c8f010 76d230d1 00000000 00c8f378 00000023 iphlpapi!GetAdapterOrderMap+0xcc
00c8f264 76d2366c 00c8f30c 000b1a98 00c8f378 iphlpapi!GetAdapterList+0x46
00c8f29c 76d261af 00000000 000b1a98 00c8f378 iphlpapi!GetAdapterInfo+0x29
00c8f2f0 76ee7c72 000b1a98 00c8f30c 00000000 iphlpapi!GetAdapterInfoEx+0x1c
00c8f310 76ee899e 00000000 00000029 7673a0c0 DNSAPI!IpHelp_GetAdaptersInfo+0x32
00c8f394 767345a3 00000001 00c8f8bc 000caa14 DNSAPI!NetInfo_Build+0x2c
00c8f3bc 767336f7 00c8f8bc 000caa14 00c8f8c0 dnsrslvr!GrabNetworkInfo+0xae
00c8f3cc 7673303f 00c8f3f0 00c8f8c4 00c8f8f8 dnsrslvr!ResolverQuery+0x2e
00c8f8c0 77e59dc9 00000000 000caa14 00000001 dnsrslvr!R_ResolverQuery+0x111
00c8f8e8 77ed321a 76732f48 00c8f8fc 00000005 RPCRT4!Invoke+0x30
00c8fcf8 77ed36ee 00000000 00000000 000c26f4 RPCRT4!NdrStubCall2+0x297
00c8fd14 77e5988c 000c26f4 0009da30 000c26f4 RPCRT4!NdrServerCall2+0x19
00c8fd48 77e597f1 767317c9 000c26f4 00c8fdf0 RPCRT4!DispatchToStubInC+0x38
00c8fd9c 77e5971d 00000009 00000000 7673a068 RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x113
00c8fdc0 77e5bd0d 000c26f4 00000000 7673a068 RPCRT4!RPC_INTERFACE::DispatchToStub+0x84
00c8fdfc 77e5bb6a 000ca9c8 0009d848 000ae930 RPCRT4!LRPC_SCALL::DealWithRequestMessage+0x2db
00c8fe20 77e56784 0009d884 00c8fe38 000ae930 RPCRT4!LRPC_ADDRESS::DealWithLRPCRequest+0x16d
00c8ff80 77e56c22 00c8ffa8 77e56a3b 0009d848 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x28f
00c8ff88 77e56a3b 0009d848 00000048 76731700 RPCRT4!RecvLotsaCallsWrapper+0xd
00c8ffa8 77e56c0a 0009afc0 00c8ffec 7c80b50b RPCRT4!BaseCachedThreadRoutine+0x79
00c8ffb4 7c80b50b 000ced60 00000048 76731700 RPCRT4!ThreadStartRoutine+0x1a
00c8ffec 00000000 77e56bf0 000ced60 00000000 kernel32!BaseThreadStart+0x37

FOLLOWUP_IP:
nt!KiTrap0E+238
804e0aac f7457000000200 test dword ptr [ebp+0x70],0x20000

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap0E+238

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xD1_W_nt!KiTrap0E+238

BUCKET_ID: 0xD1_W_nt!KiTrap0E+238

Followup: MachineOwner
---------

0: kd> !IRP 7c921713
IRP signature does not match, probably not an IRP

Ojalá me pudiérais ayudar.

Saludos.
Valora esta pregunta
Me gusta: Está pregunta es útil y esta claraNo me gusta: Está pregunta no esta clara o no es útil
0
Responder