Conference irocz::terminal_servers

3481.0. "crash codes 200, then 100 on nas1.5bl95d" by KERNEL::FREKES (Like a thief in the night) Tue Mar 25 1997 14:09

Folks

I had an interesting problem this morning, while out on customer site. 
A DECserver700-16 running NAS V1.5bl95D-34. While I was using the server it
did a fatal bugcheck with the following registers:
PC=078D4E30 SP=07974E5C SR=2000 C=0200
The server appeared to have hung at this point. I then power cycled the server, 
and durring the boot, it crashed again, this time with the following:
PC=0001C7D4 SP=07802020 SR=2700 C=0100. The 7seg. display was showing a P, and
the server did not recover itself from this. I was forced to power cycle it a 
2nd time and this time it booted up ok. 

Each time the software/selftest status was normal. Was this because I power 
cycled the server, or some other reason. I don't think the server would have 
ever recovered if I had not power cycled it.

Any hints as to what these crash codes mean, would be greatful. In the end I 
replaced the hardware, and used the existing Flash Card, and memory simm. While
I was on site, it remained operational.

Regards
	Steven Freke
	UK CSC 
    

RE: .0

Code 200 is software checksum error (the code continually checksums itself 
in the background, looking for unexpected corruptions of the image).  Code
100 is a DRAM parity error.

Regards,

Dave

    >100 is a DRAM parity error.
    
    Does this mean I should swap the memory sim?
    
    Steven

RE: .2
    
>    Does this mean I should swap the memory sim?
 
Only if the Code 100 crash is repetitive.

Regards,

Dave