JSI Tip 5782. Stop 0x000000B8 or 0x000000D1 in your Windows 2000 cluster?

A cluster node BSODs with one of the following errors and stack trace:

STOP 0x00000b8
ATTEMPTED_SWITCH_FROM_DPC (b8) A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending code and original DPC routine.

f2027320 8042a43b 00000003 f2027368 00000000 nt!RtlpBreakWithStatusInstructionf2027350 8042aa2e 00000003 85e7e588 85e7e588 nt!KiBugCheckDebugBreak+0x31f20276dc 8042a2bd 000000b8 00000000 00000000 nt!KeBugCheckEx+0x390f20276f4 8046a076 000000b8 ffffffff 00000202 nt!KeBugCheck+0xff2027704 80469dc9 f2027740 85e7e5f4 85e7e588 nt!ScPatchFxe+0x34f2027718 8042bd4d 00000000 85b603f8 00000000 nt!KiSwapThread+0x1b1f2027740 8041516b 855a22e8 00000000 00000000 nt!KeWaitForSingleObject+0x1a3f202777c 804146df 85b603f8 85b603f8 f20277a0 nt!ExpWaitForResource+0x2df202778c 80414733 80065410 85b603f8 85cece00 nt!ExpAcquireResourceExclusiveLite+0x7bf20277a0 bff569fd 85b6042c 00000001 e204f3c8 nt!ExAcquireResourceExclusiveLite+0x45f20277b8 bff587fe 85b603e8 e204f3c8 f20277e7 KSecDD!KSecDereferenceListEntryPaged+0x21f20277e8 bff59cde e204f3c8 bf237874 00000001 KSecDD!KSecDereferenceListEntry+0x1cf202780c bff585fd e204f3c8 f202785c 00000000 KSecDD!NtLmVerifySignature+0x75f2027874 bf233f61 857272c8 00000001 00000010 KSecDD!VerifySignature+0x33f2027890 bf235e22 857272c8 00000001 00000001 clusnet!CcmpReceivePacketHandler+0x25f20278cc bf28cfb6 857272c8 00000016 f2027934 clusnet!CnpTdiReceiveDatagramHandler+0x17af2027958 bf28d41e 8568ee48 2e01010a f2020f0d tcpip!UDPDeliver+0x256f20279b4 bf28d89b 85ca2488 2f01010a 2e01010a tcpip!UDPRcv+0x27bf2027a00 bf28d757 bf28d32d 85ca2488 85cece1e tcpip!DeliverToUser+0xf9f2027ab8 bf28c805 85ca2488 85cece32 00000030 tcpip!IPRcvPacket+0x581f2027af8 bf28c866 00000000 85cea858 85cece10 tcpip!ARPRcvIndicationNew+0x17bf2027b34 bfec179a 85c39dc8 00000000 85d12510 tcpip!ARPRcvPacket+0x5cf2027b8c bfe1f3bb 85d4ba00 f2027bac 00000002 NDIS!ethFilterDprIndicateReceivePacket+0x2ea

OR

STOP 0x000000D1DRIVER_IRQL_NOT_LESS_OR_EQUALChildEBP RetAddr Args to Childf6823de4 bfeca768 e2b52008 4d4c544e 00000000 KSecDD!KSecReferenceListEntry+0x10f6823e10 bfec90ff e2b52008 00000000 f6823e60 KSecDD!NtLmMakeSignature+0x16f6823e24 bf8b6434 bf8ba87c 00000000 f6823e60 KSecDD!MakeSignature+0x33f6823e7c bf8b4df2 00000001 00004bb7 00004bb7 clusnet!CxSendHeartBeatMessage+0xc4f6823eb0 80431d00 bf8baae0 00000000 7057917a clusnet!CnpHeartBeatDpc+0x348f6823fb0 80431be6 fb658c1c ffdff848 ffdff000 nt!KiTimerListExpire+0x112f6823fdc 80464a18 80482e60 00000000 00177b05 nt!KiTimerExpiration+0xb6f6823ff4 80469e3b be87bd44 020f7c78 0026def8 nt!KiRetireDpcList+0x47

If someone caused the Clusnet.sys driver to be loaded when the computer starts, you will experience this problem.To fix this problems:

1. Use the Registry Editor to navigate to:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesClusnetStart.

2. Double-click the ClusnetDriverServiceLoad Value Name, a REG_DWORD data type, and change the data value from 1 to 3.