Windows 2003 Server Bluescreens

I have a Windows 2003 server that almost every night bluescreens

I´m wondering if anyone out there might have any ideas about how to fix the problem

Server is not running SP1

Loading Dump File [D:\Mini082505-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 MP (2 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_gdr.050225-1827
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Thu Aug 25 02:15:42.187 2005 (GMT+2)
System Uptime: 0 days 12:19:56.968
Loading Kernel Symbols
.................................................................................................
Loading unloaded module list
..
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {14, 2, 1, 8050e61e}

Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+2d )

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

1: 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: 00000014, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8050e61e, address which referenced memory

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


WRITE_ADDRESS: 00000014

CURRENT_IRQL: 2

FAULTING_IP:
nt!IoCancelIrp+2d
8050e61e c6462401 mov byte ptr [esi+0x24],0x1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 805d885f to 8050e61e

TRAP_FRAME: f3ad8bc0 -- (.trap fffffffff3ad8bc0)
ErrCode = 00000002
eax=00000000 ebx=00000000 ecx=f3ad8c38 edx=00000000 esi=fffffff0 edi=00000000
eip=8050e61e esp=f3ad8c34 ebp=f3ad8c3c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!IoCancelIrp+0x2d:
8050e61e c6462401 mov byte ptr [esi+0x24],0x1 ds:0023:00000014=??
Resetting default scope

STACK_TEXT:
f3ad8c3c 805d885f fffffff0 860af518 f3ad8cf0 nt!IoCancelIrp+0x2d
f3ad8c5c 80595778 85be7da0 85be7da0 00000001 nt!IoCancelThreadIo+0x30
f3ad8cf0 805d2f2a 00000001 86103668 804f3221 nt!PspExitThread+0x459
f3ad8cfc 804f3221 86103668 f3ad8d48 f3ad8d3c nt!PsExitSpecialApc+0x1b
f3ad8d4c 804dfda8 00000001 00000000 f3ad8d64 nt!KiDeliverApc+0x1c6
f3ad8d4c 7ffe0304 00000001 00000000 f3ad8d64 nt!KiServiceExit+0x56
010cfcd0 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


FOLLOWUP_IP:
nt!IoCancelIrp+2d
8050e61e c6462401 mov byte ptr [esi+0x24],0x1

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!IoCancelIrp+2d

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42226ccd

STACK_COMMAND: .trap fffffffff3ad8bc0 ; kb

FAILURE_BUCKET_ID: 0xA_W_nt!IoCancelIrp+2d

BUCKET_ID: 0xA_W_nt!IoCancelIrp+2d

Followup: MachineOwner

 

ntkrnlmp.exe -

Are you running a single or multi processor box?

Do you have the latest BIOS update from the vendor installed?

 

It´s a multiprocessor box

But I might have an answer to the problem. I got a tip from a friend to update all drivers and Bios from Dell´s site.

The server is a Dell PowerEdge 2650

 

The tip is a good one. Hopefully it will cure your problem.