• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

SCO OpenServer Crashing

D

DarkArchon

n00b
Joined
Feb 12, 2003
Messages
34
I am currently having a problem with my SCO OpenServer 5.0.5 / 3.2v5.0.5 system.

Running smoothly for the past 3 years, at random on March 16, 2010 the system crashes. I reboot it. Everything is normal again. 9 hours later it crashes again. This cycle has repeated itself ever since then. System is crashing every 9 hours and I have to reboot it.

This is the following error message that I get on the screen after it crashes:

Unexpected trap in kernel mode
Panic: k trap - kernel mode trap type0x000000E
tying to dump 32671 pages hd (1/41)
409 pages per '.'

This system is critical to my business and I cannot have it crashing all the time.

This is what I have done so far.

1. Replaced Motherboard
2. Replaced CPU
3. Replaced Power Supply
4. Replaced Ram
5. Replaced Network Card
6. Rebooted all network equipment (3 Switches and 1 Cisco Pix Firewall)
7. Replaced hard drive and copied old data from a tape from the night before (3/15)

The strange thing is, which makes me think it is a network or software issue, is that when I disconnect the system from the network, it does not crash.

I cannot see or think of any devices on my network that would randomly every 9 hours cause my system to crash when it was running 3 years no problem.

I have exhausted all of my resources, I refuse to pay $600 to SCO for a help session that may or may not fix my problem.

If anyone could help me, I would greatly appreciate it.
 
The obvious first question is whether or not you had any sort of OS/driver updates. Had you replaced any hardware prior to the crashes starting?

Unless you're dealing with particularly buggy drivers, this sort of thing seems to indicate a memory problem. Google concurs.

When you replaced the memory, did you test it (ie - run memtest86+ for a few hours)? Another possibility is that there's some corruption in your OS on disk - restoring from the previous night's back-ups isn't going to help if corruption occurred a month ago - how hard would it be to do a fresh install & only restore the data you need, rather than doing a full system restore?

You might consider writing/finding a program that will exercise large quantities of memory & test them - if there's bad memory, you might be able to get to it faster with different patterns of system usage. Similarly, you might want to find/write some code to create massive amounts of network traffic to different hosts & see if that can trigger your problem faster.

Worst case scenario - if the machine is crashing hard every 9 hours, you could set up a cron job to make it
 
What does the SCO box run that makes it so critical?

Does SCO say specifically that if they can't solve the issue, that you still have to pay the $600?
 
You must log in or register to reply here.
Back
Top