Server crash 1

[frl]

Hello,

I installed Win2000 Server on a new IBM x345 machine 3 months ago. Since then this server crashed 3 or 4 times and I got the following message in Event viewer:
DATE: 8.11.04
TIME: 1:04 am

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 11/8/2004
Time: 1:04:10 AM
User: N/A
Computer: W2KSERVER
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x00000008, 0x00000002, 0x00000001, 0xf6728730). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.

I checked the microsoft knoweledge base arricles but couldnt find anything usefull.
Any ideas?
Thanks!

 

[mayfran]

You may have bad RAM.

 

[venkateshshah]

it looks hardware problem.. may be RAM or HDD .. or check if you installed any new hardware.

 

[patrichek]

i have the same message. I installed windows debugging tools to read the memory.dmp file that was created during the bug check. I think my problem is the raid controller.
go to microsofts website

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

for more info
good luck!

 

[frl]

Thanks for replies! I tried the debugging tools on my memory.dmp and got the following info:

Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.


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

************************************************************
WARNING: Dump file has been truncated. Data may be missing.
************************************************************
Symbol search path is: SRV*c:\websymbols*

http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Product: LanManNt
Kernel base = 0x80400000 PsLoadedModuleList = 0x80484980
Debug session time: Sun Nov 28 22:16:42 2004
System Uptime: 8 days 0:09:18.000
Loading Kernel Symbols
..............................................................................................
Loading unloaded module list
........................
Loading User Symbols
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 1, f6728730}

*** WARNING: Unable to verify checksum for CILUSB.EXE
*** ERROR: Module load completed but symbols could not be loaded for CILUSB.EXE
Probably caused by : openhci.sys ( openhci!OpenHCI_Alloc_HcdTD+16 )

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

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


WRITE_ADDRESS: 00000008

CURRENT_IRQL: 2

FAULTING_IP:
openhci!OpenHCI_Alloc_HcdTD+16
f6728730 c74008ad2bad2b mov dword ptr [eax+0x8],0x2bad2bad

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f672bfe0 to f6728730

TRAP_FRAME: be383868 -- (.trap ffffffffbe383868)
ErrCode = 00000002
eax=00000000 ebx=87609de8 ecx=88fecaac edx=88fecf28 esi=88ec4d40 edi=87609e20
eip=f6728730 esp=be3838dc ebp=be383920 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
openhci!OpenHCI_Alloc_HcdTD+0x16:
f6728730 c74008ad2bad2b mov dword ptr [eax+0x8],0x2bad2bad ds:0023:00000008=????????
Resetting default scope

STACK_TEXT:
be3838d8 f672bfe0 88fec928 87cee128 87609de8 openhci!OpenHCI_Alloc_HcdTD+0x16
be383920 f672c5df 88fec928 888c3848 87609de8 openhci!OpenHCI_ControlTransfer+0x19a
be383940 8006627b 88fec870 00000000 00000000 openhci!OpenHCI_QueueGeneralRequest+0x49
be38396c 8041d442 88ec5c60 88fec8a4 00000001 hal!HalAllocateAdapterChannel+0x11b
be383984 f672baf9 88ec5c60 88fec870 00000001 nt!IoAllocateAdapterChannel+0x28
be3839b8 f672b9ae 888c3801 00000000 888c3848 openhci!OpenHCI_EndpointWorker+0x12d
be3839cc f672bcc5 88fec900 888c3848 88fec928 openhci!OpenHCI_ProcessEndpoint+0x68
be3839f0 f672833d 88fec802 87cee100 88fec928 openhci!OpenHCI_QueueTransfer+0x189
be383a1c f67292c9 88fec870 87cee128 88fec870 openhci!OpenHCI_URB_Dispatch+0x61
be383a40 8041dfe5 88fec870 88fec870 0000001b openhci!OpenHCI_Dispatch+0xfb
be383a54 f64e0539 f64e1fd2 87cee128 88fec870 nt!IopfCallDriver+0x35
be383a58 f64e1fd2 87cee128 88fec870 87cee128 usbhub!USBH_PassIrp+0x15
be383a74 f64e228a 88ec5168 87cee128 888c3930 usbhub!USBH_PdoUrbFilter+0x64
be383a90 f64e069a 00020a18 87cee128 be383ad8 usbhub!USBH_PdoDispatch+0xd8
be383aa0 8041dfe5 888c3930 87cee128 00000000 usbhub!USBH_HubDispatch+0x46
be383ab4 bfe2e9da 87cee204 87609de8 c0000001 nt!IopfCallDriver+0x35
be383ad8 bfe2c818 888c2c10 87cee128 be383afc hidusb!HumGetFeature+0x20a
be383b00 f6758872 888c2c10 87cee128 87cee128 hidusb!HumInternalIoctl+0x188
be383b10 f675b80a 888c2c10 87cee128 87cee24c HIDCLASS!DerefDriverExt+0x29b
be383b3c f6758585 888c2c10 87cee128 87cee24c HIDCLASS!InitDriverExtData+0x48
be383b64 f6758e6a 888c1307 87cee128 000b0192 HIDCLASS!RefDriverExt+0x124
be383bf4 f67588de 888c13e8 87cee128 8041dfe5 HIDCLASS!HidpGetSetFeature+0x149
be383c00 8041dfe5 888c1330 87cee128 87cee128 HIDCLASS!DerefDriverExt+0x307
be383c14 804b1152 87cee24c 00000000 87cee128 nt!IopfCallDriver+0x35
be383c28 804b1fa6 888c1330 87cee128 8736a688 nt!IopSynchronousServiceTail+0x60
be383d00 804a9c16 00000124 00000000 00000000 nt!IopXxxControlFile+0x5d6
be383d34 80466ef9 00000124 00000000 00000000 nt!NtDeviceIoControlFile+0x28
be383d34 77f82ca0 00000124 00000000 00000000 nt!KiSystemService+0xc9
00a7fd18 7c5794e7 00000124 00000000 00000000 ntdll!NtDeviceIoControlFile+0xb
00a7fd7c 6f9a1441 00000124 000b0192 00000000 KERNEL32!DeviceIoControl+0xf8
00a7fda4 0040152e 00000124 007c3520 00000008 HID!HidD_GetFeature+0x20
WARNING: Stack unwind information not available. Following frames may be wrong.
00000001 00000000 00000000 00000000 00000000 CILUSB+0x152e


FOLLOWUP_IP:
openhci!OpenHCI_Alloc_HcdTD+16
f6728730 c74008ad2bad2b mov dword ptr [eax+0x8],0x2bad2bad

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: openhci!OpenHCI_Alloc_HcdTD+16

MODULE_NAME: openhci

IMAGE_NAME: openhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3e5ffecb

STACK_COMMAND: .trap ffffffffbe383868 ; kb

BUCKET_ID: 0xD1_W_openhci!OpenHCI_Alloc_HcdTD+16

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


The only thing I can see from here is that some driver is using improper memory address. If somebody can see which driver (or hardware) is causing problems, it would realy help. Thank you and sorry for long post!