Welcome to WebmasterWorld Guest from 188.8.131.52
Once had a AMD Via chipset board running a sonic storm sound card and a diamond stealth AGP graphics card. Only to find out that the sonic storm was not fully compatible with the via chipset booting up at a different current to the motherboard and subsequently screwed the initialisation of the agp graphics card due to iregularities in the frequency, thus creating blue screens about 10 times a day for a total of 1 week until I had figured out what had happened, sold the parts on to mates of mine and got myself a more compatible Intel system.
Before switching to Win2K though, countless hours were spent trying to pinpoint the problem. The HDD was wiped and the OS replaced at least 10 times. The power supply was replaced. The HDD was replaced.
After 2 weeks of installing Win2K, the OS was so badly corrupted that nothing would respond. The HDD was wiped again and the system crashed during install. At that point, I replaced all the generic memory and replaced it with Crucial memory. It has been running fine since then, without any crashes. When the system gets a little sluggish, the computer gets a reboot (about once a week).
The bottom line is spend the extra $$ on top quality memory. Otherwise, you will be spending time troubleshooting. Besides, memory is dirt cheap. It has dropped about 70-80% since the beginning of the year.
Every once in a while I log out to let the display server free up memory. It tends to eat a lot, because I view a lot of digital photographs. There might be a memory leak somewhere, but I think it is just the amount of images I shuffle around that causes it to grow.
I have seen it hang sometimes, due to a faulty graphics driver that has since been updated. When it happened the display just froze. I have usually just telnetted into it and killed the display server and logged in again. No need to reboot for a graphics driver error.
It runs Debian Linux, the 'sarge/testing' version. Last reboot was due to a kernel upgrade.
My server runs Debian woody/stable. It has been up for 96 days today. It was rebooted because the university where it is located, shut down the electricity completely for a weekend for some repairs and security checks.
In ten years of using Linux I cannot remember seeing one single panic (which is the Unix BSOD - a simple text message saying "Kernel panic: some incomprehensible explanation here") that I didn't cause myself by being mean to the poor computer.
Since Windows appears to garbagate itself in time I built my fresh system with all the important apps (but no work done yet) and ghosted it to a separate partition.
When bluescreens become more frequent, I just restore that and Bingo.
Yeah, and an additional box with linux, too.
The problem? The processor was too COOL. I had to change the low value on the operating temperature of the processor. The temp would drop below the allowed temperature range value and the system would power down.
I cursed XP Pro for two weeks while I was trying to find the problem. ;)