Re: Bug check: 0x000000d1 (0x77f68b33, 0x000000ff, 0x00000000, 0x77f68b33)
From: George Valkov (null_at_somewhere.com)
Date: 05/29/04
- Next message: Gerald: "Re: USB Ports"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: Cannot start WindowsServer 2003"
- Maybe in reply to: Kristofer Gafvert: "Re: Bug check: 0x000000d1 (0x77f68b33, 0x000000ff, 0x00000000, 0x77f68b33)"
- Next in thread: Jonathan Maltz [MS-MVP]: "Re: Bug check: 0x000000d1 (0x77f68b33, 0x000000ff, 0x00000000, 0x77f68b33)"
- Reply: Jonathan Maltz [MS-MVP]: "Re: Bug check: 0x000000d1 (0x77f68b33, 0x000000ff, 0x00000000, 0x77f68b33)"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 29 May 2004 23:22:53 +0300
Microsoft (R) Windows Debugger Version 6.3.0011.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\Documents and Settings\gfc\Desktop\Mini052704-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*F:\Documents and Settings\gfc\My
Documents\Debug\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 UP Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_rtm.030324-2048
Kernel base = 0x804de000 PsLoadedModuleList = 0x80568c08
Debug session time: Thu May 27 19:47:05 2004
System Uptime: 1 days 15:15:39.269
Loading Kernel Symbols
............................................................................
................................................
Loading unloaded module list
.......................
Loading User Symbols
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: 77f68b33, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 77f68b33, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 77f68b33
CURRENT_IRQL: 0
FAULTING_IP:
+77f68b33
77f68b33 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 804eaa00 to 8053eec8
TRAP_FRAME: ed360d64 -- (.trap ffffffffed360d64)
ErrCode = 00000004
eax=014400ab ebx=01e4fc00 ecx=01e4fc1c edx=7ffe0304 esi=000001d4
edi=01aa7894
eip=77f68b33 esp=01e4fbec ebp=01e4fef8 iopl=0 nv up di pl nz ac pe
cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
efl=00010013
001b:77f68b33 ?? ???
Resetting default scope
STACK_TEXT:
ed360d48 804eaa00 0000000a 77f68b33 000000ff nt!KeBugCheckEx+0x19
ed360d48 77f68b33 0000000a 77f68b33 000000ff nt!KiTrap0E+0x21f
WARNING: Frame IP not in any known module. Following frames may be wrong.
01e4fbe8 00000000 00000000 00000000 00000000 0x77f68b33
FAILED_INSTRUCTION_ADDRESS:
+77f68b33
77f68b33 ?? ???
FOLLOWUP_IP:
nt!KiTrap0E+21f
804eaa00 833da078568000 cmp dword ptr [nt!KiFreezeFlag (805678a0)],0x0
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiTrap0E+21f
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3e800a79
STACK_COMMAND: kb
BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+21f
Followup: MachineOwner
---------
- Next message: Gerald: "Re: USB Ports"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: Cannot start WindowsServer 2003"
- Maybe in reply to: Kristofer Gafvert: "Re: Bug check: 0x000000d1 (0x77f68b33, 0x000000ff, 0x00000000, 0x77f68b33)"
- Next in thread: Jonathan Maltz [MS-MVP]: "Re: Bug check: 0x000000d1 (0x77f68b33, 0x000000ff, 0x00000000, 0x77f68b33)"
- Reply: Jonathan Maltz [MS-MVP]: "Re: Bug check: 0x000000d1 (0x77f68b33, 0x000000ff, 0x00000000, 0x77f68b33)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|