NetServer LC 2000r BugCheckCode 0x0000009c

[Joe Courtney]

We have a netserver that keeps rebooting itself periodically throughout the day and night. There is no information in the event logs. The reboots donâ t seem to coincide with any backup or other operation software or hardware. The only info I have comes from:

***********************************************
**
** Windows 2000 Crash Dump Analysis
**
***********************************************

Filename . . . . . . .memory.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x00030000
PfnDataBase. . . . . .0x8204f000
PsLoadedModuleList . .0x80484b40
PsActiveProcessHead. .0x804862a8
MachineImageType . . .i386
NumberProcessors . . .2
BugCheckCode . . . . .0x0000009c
BugCheckParameter1 . .0x00000002
BugCheckParameter2 . .0x003446ff
BugCheckParameter3 . .0xb6000000
BugCheckParameter4 . .0x00140001

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x80062c0c

All research points to a hardware problem. We have replaced all memory in the machine with no luck. Can anyone tell me how I might further research the problem? A few newsgroups suggest the manufacturer could tell us more information from the BugCheckParameters, but we have had no luck to this point.

Thanks for any he

[Tony Maimer]

Hello Joe,

The best thing to do at his point is to install Instant Top Tools b(ITT), if you don't already have Top Tools agents installed.

You can get ITT at http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?locale=en_US&taskId=135&prodSeriesId=50440&prodTypeId=15351&pnameOID=19399&swEnvOID=226#1124

To see if there is a hardware event, go to the Status tab and look in the event log. Anything in yellow or red should be noted as an actual condition.

Tony

[kris rombauts]

Hello Joe,

after doing what Tony suggested first and if that does not result in a clear indication which component is faulty, it might be because the H/W issue is related to the CPU or related component on the systemboard (PCI chipset/BUS controller) itself and as such it's possible that the management agents are not capable of reporting this kind of issue.
The System eventlog (SEL) would be the best place to look at after you installed the agents.

Reason why i think this way is that if you look into the meaning of a stop 9c i.e. here on those couple of articles (see url below) you might want to suspect the CPU itself.

http://support.microsoft.com/search/default.aspx?InCC_hdn=True&Catalog=LCID%3D1033%26CDID%3DEN-US-KB%26PRODLISTSRC%3DON&Product=&KeywordType=ALL&Titles=false&numDays=&maxResults=25&Queryl=stop+0x0000009c&Query=stop+0x0000009c&QuerySource=gsfxSearch_Query&srchExtraQry=

or go to http://support.microsoft.com and search on stop 0x0000009c

HTH

Kris

[Rhonda Stewart]

had the same 9c error. i changed memory power supply and everything and it was down to the processor itself. So its either a overheating problem or the processor is gone.