Fun Stuff > CLIKC
The PC-building/hardware knowledge thread
pwhodges:
I've seen a faulty disk hang the motherboard up like that.
In other news, I'm building myself a new desktop. It has a server-class motherboard holding a low-end Xeon and 16GB of RAM, with space to go to 32GB (hence the Xeon, though the 8GB DIMMs with the right DRAM type required to do that are real hard to get at present), and enough PCI slots for my various high-end audio interfaces. My first motherboard with no IDE or floppy connectors.
The machine is used for (a) audio editing, in surround (well Ambisonics, but you need to know what that is :wink: ), and (b) running Hauptwerk, which uses huge sample sets fully loaded into RAM. My present 8GB machine is too small for the latest sample set I got, and some sample sets (that I can't afford right now) require 24GB or more.
The 8GB machine (which has a Q6600 cpu) will become my server machine, running HyperV (like I'm about to do at work, replacing VMware ESX) so that I can have virtual servers for the main functions I need.
The old server (a 7-year-old twin Xeon workstation) will become an experimental machine for running audio programs in Linux.
imagist42:
Might try disconnecting various devices one at a time?
clockworkjames:
Take it apart, put it back together with only the bare essentials hooked up (cpu, memory, optical drive with a bootable CD in it, graphics card, psu & some luck should be all you need), listen for any unnusual sounds when it is running.
If your mobo has a clear cmos button, push it. If not take the little CR2032 watch battery out for like 10 minutes then ut it in and try again.
I would agree it sounds most like a HDD failure (mechanical parts are generally the first to fail for obvious reasons) but it is worth checking all your options first.
LTK:
--- Quote from: imagist42 on 16 Dec 2010, 14:10 ---Might try disconnecting various devices one at a time?
--- End quote ---
I was trying different combinations of hard disk and disk drives to see if the fault was in any of those, but that didn't do anything. Moved on to the RAM cards, and one of the two turned out to be faulty. Luckily that was the one I first ejected, so it's all good now.
I did try to replace the little button battery, so the BIOS chip has been reverted to factory settings, but that's not a problem. Thanks for the tips, anyway.
imagist42:
I've had issues with faulty RAM locking down a system before too. But at least it wasn't a HDD. I fucking hate the recovery process when one of those dies on you.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version