STOP ERROR x 0A on 2k3 standard.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

I have a Win 2k3 file server. It crashes every now and then. Event Viewer
reveal following error:

Error code 0000000a, parameter1 18b43200, parameter2 000000ff, parameter3
00000000, parameter4 8074867e.

Which is not of a great help.

So, I had run WinDbg on MEMORY.DMP. Here is the output.

Any ideas on this behaviour?

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 18b43200, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8074867e, address which referenced memory

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


READ_ADDRESS: 18b43200

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalpIpiHandler+16
8074867e f744247000000200 test dword ptr [esp+0x70],0x20000

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from f7130676 to 8074867e

TRAP_FRAME: 8056f4dc -- (.trap ffffffff8056f4dc)
ErrCode = 00000000
eax=85674abd ebx=ffdffdf0 ecx=ffdffdf0 edx=00005c38 esi=ffdffdd0 edi=86350cf8
eip=8074867e esp=8056f550 ebp=8056f550 iopl=0 nv up di ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010086
hal!HalpIpiHandler+0x16:
8074867e f744247000000200 test dword ptr [esp+0x70],0x20000
ss:0010:8056f5c0=00000202
Resetting default scope

STACK_TEXT:
8056f550 f7130676 00000000 00000000 00000000 hal!HalpIpiHandler+0x16
WARNING: Stack unwind information not available. Following frames may be
wrong.
8056f5c0 ffdffdf0 8050365e 865aa3c8 80579d00 processr+0x2676
8056f5e0 804e61ca 00000000 0000000e 00000000 0xffdffdf0


FOLLOWUP_IP:
processr+2676
f7130676 ?? ???

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: processr+2676

MODULE_NAME: processr

IMAGE_NAME: processr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: fffffffe

STACK_COMMAND: .trap ffffffff8056f4dc ; kb

BUCKET_ID: 0xA_processr+2676

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

Tx,
Jay
.

Relevant Pages

  • Re: NDIS IM driver crashes
    ... If kernel debugger is available get stack backtrace. ... Arg2: 00000002, IRQL ... Stack unwind information not available. ... FOLLOWUP_NAME: MachineOwner ...
    (microsoft.public.development.device.drivers)
  • DEVICE_IRQL_NOT_LESS_OR_EQUAL atapi.sys
    ... I captured this memory dump... ... If kernel debugger is available get stack backtrace. ... Stack unwind information not available. ... FOLLOWUP_NAME: MachineOwner ...
    (microsoft.public.windowsxp.help_and_support)
  • WinHex optical drive edit, IRQL_NOT_LESS_OR_EQUAL
    ... Tools --> Open Disk ... Arg2: 000000ff, IRQL ... Stack unwind information not available. ... FOLLOWUP_NAME: MachineOwner ...
    (microsoft.public.windowsxp.general)
  • Re: question for AllocateCommonBuffer and How to send user mode memory data to kernel
    ... I got two bugcheck code when I run the code that I list above,Can ... Arg2: 00000002, IRQL ... FOLLOWUP_NAME: MachineOwner ... If a kernel debugger is available get the stack backtrace. ...
    (microsoft.public.development.device.drivers)
  • Re: EHCI driver causes blue csreen
    ... I use 4 buffers with 64kbytes of size, ... If kernel debugger is available get stack backtrace. ... Arg2: 00000002, IRQL ... FOLLOWUP_NAME: MachineOwner ...
    (microsoft.public.development.device.drivers)