Chronic BSOD STOP 0xD1

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am running windows 2000 SP4 on a Compaq/HP ML350G2. I have a pair of
servers with tme same hardware but differnet software (one is a citrix
server, the other is an Exchange server). One of the 2 has been experiencinc
chronic STOP 0xD1 BSOD's. The issue occurs sometimes 3 or 4 times in an hour
but then does not occur for weeks.

Anyone have any suggestions?

The following is the bugcheck analysis, they all look the same:
*******************************************************************************
*
*
* 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: 0000000d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 0000000d, address which referenced memory

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


READ_ADDRESS: 0000000d

CURRENT_IRQL: 2

FAULTING_IP:
+d
0000000d ?? ???

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 083aed90 to 0000000d

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8047184c 083aed90 0000000f 083a5650 0000001b 0xd
88e4054c 00000000 00000000 00000002 00000000 0x83aed90


FAILED_INSTRUCTION_ADDRESS:
+d
0000000d ?? ???

FOLLOWUP_IP:
nt!KiTrap0E+20b
80467df7 f7457000000200 test dword ptr [ebp+0x70],0x20000

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap0E+20b

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4344ec59

STACK_COMMAND: .trap ffffffff804717dc ; kb

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+20b

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+20b

Followup: MachineOwner
---------
 
Have you check out the following KB articles?

http://support.microsoft.com?kbid=900345 "Fixes that are included in the Update Rollup 1 for Microsoft Windows 2000 Service Pack 4 that is dated June 28 2005 "
http://support.microsoft.com?kbid=247421 "STOP 0x000000D1 in Ino_fltr.sys with Inoculan "
http://support.microsoft.com?kbid=260956 "'Stop 0x000000D1' Error Message in Tcpip.sys "
http://support.microsoft.com?kbid=269279 "The BLACKDRV.SYS file Causes the Stop Error Message: 0X000000D1{0XBE70D600 0X000000000X000000000XBE92F13C} "
http://support.microsoft.com?kbid=278945 "'STOP 0xA' or 'STOP 0xD1' Error Messages Occur When You Attempt to Synchronize Exchange Server Mail "
http://support.microsoft.com?kbid=293077 "Error Message: STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL "
http://support.microsoft.com?kbid=302400 "STOP 0x000000D1 Error Message When You Run Compaq Teaming "
http://support.microsoft.com?kbid=309660 "FtDisk May Cause a 'STOP Error 0x000000D1' Error Message When You Shut Down Your Computer "
http://support.microsoft.com?kbid=311975 "Stop 0x000000D1 Error When You Dial a 9 for an Outside Telephone Line to Connect to ISP "
http://support.microsoft.com?kbid=318988 "Stop 0x000000B8 Error Occurs in a Windows 2000 Cluster "
http://support.microsoft.com?kbid=329703 "'STOP' Error Messages in Qafilter.sys or Qsfilter.sys with Third-Party Quota Management Tool "
http://support.microsoft.com?kbid=331053 "'DRIVER_IRQL_NOT_LESS_OR_EQUAL' Error Message when You Dismount a Volume "
http://support.microsoft.com?kbid=812484 "'DRIVER_IRQL_NOT_LESS_OR_EQUAL 3cisati.sys' Error Message When You Run Windows 2000 Setup "
http://support.microsoft.com?kbid=816990 "FTDisk May Cause a 'STOP Error 0x000000D1' Error Message When You Shut Down Your Computer "
http://support.microsoft.com?kbid=817864 "Network Monitor Protocol Causes Stop Code 0xD1 When Closing Adapter "
http://support.microsoft.com?kbid=839516 "You may receive stop error messages when you try to run Adaptec Easy CD Creator or Adaptec DirectCD on a Windows 2000-based computer "
http://support.microsoft.com?kbid=840890 "You receive a 'Stop 0x000000D1' error message on your Windows 2000-based computer "
http://support.microsoft.com?kbid=841194 "You receive a 'Stop 0x000000D1' error message in the Netbt.sys driver on your Windows 2000-based computer "
http://support.microsoft.com?kbid=892137 "You receive a 'STOP 0x000000D1' error message when an invalid cache entry is read or written on a Windows 2000 Server-based computer "



I am running windows 2000 SP4 on a Compaq/HP ML350G2. I have a pair of
servers with tme same hardware but differnet software (one is a citrix
server, the other is an Exchange server). One of the 2 has been experiencinc
chronic STOP 0xD1 BSOD's. The issue occurs sometimes 3 or 4 times in an hour
but then does not occur for weeks.

Anyone have any suggestions?

The following is the bugcheck analysis, they all look the same:
*******************************************************************************
*
*
* 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: 0000000d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 0000000d, address which referenced memory

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


READ_ADDRESS: 0000000d

CURRENT_IRQL: 2

FAULTING_IP:
+d
0000000d ?? ???

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 083aed90 to 0000000d

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8047184c 083aed90 0000000f 083a5650 0000001b 0xd
88e4054c 00000000 00000000 00000002 00000000 0x83aed90


FAILED_INSTRUCTION_ADDRESS:
+d
0000000d ?? ???

FOLLOWUP_IP:
nt!KiTrap0E+20b
80467df7 f7457000000200 test dword ptr [ebp+0x70],0x20000

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap0E+20b

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4344ec59

STACK_COMMAND: .trap ffffffff804717dc ; kb

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+20b

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+20b

Followup: MachineOwner
---------
Click to expand...

Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com
http://www.jsifaq.com
 
Thank you for your reply. Yest I ran a search at support.microsoft.com and
eliminated each of the availalbe atricles as a solution. It appears that
your list is the same / similar. Many of the items can be discounted
instantly since they call a specific driver where in my case the crash is in
ntoskrnl.exe.

Again thank you for the reply and pointers!

Jason
 
Back
Top