Jump to content


  • Content Count

  • Joined

  • Last visited

About Glaucus

  • Rank
    New Member
  1. I have. I've also tried booting with just the DVD-RW in there with a boot cd. No go.
  2. I did it for 8 hours. I'm trying it again as we speak, for 24 hours.
  3. I'm using different drives on different cables on different controllers. It doesn't make a difference. It still loses each drive randomly and doesn't detect them correctly.
  4. Nothing. I tried both suggestions, and there is no change. It is still playing "Now I see it, now I don't" with the hard drives. It is still taking hours to try to boot off each disk and failing. I can't find anything about DFI RMA or warranties...
  5. I've had my LanParty NF4 Ultra-D for about a year and a half now. Sometime last week, the system running it just dropped. I say "dropped" because I only had network access to it (1700 miles away), and it just disappeared off the network. When I finally got home and rebooted it, it froze right after it showed the "PCI Devices" screen (when it starts looking for the boot devices). I discovered that if I disabled EVERYTHING (including IDE controllers) it would move on and try to netboot (failing of course). If I enable the SATA drives* (onboard), it freezes. If I just enable the PATA drive/controller, then it takes a while, and then fails to boot off them, telling me "MISSING SYSTEM DISK" or some such. I'm at my wits end here, and can't remember how long the warranty on the board is . Pretty much guaranteed that the controller died for some reason. I have no idea what happened since I had to reboot it when it froze the first time. If need be I might be able to get the kernel logs from the system disk to see exactly what happened before it froze. But that wouldn't be easy, especially since I can't boot a CD off the box... BTW, I pulled the power off of every drive in the system to be sure it wasn't the PSU, and I really doubt it is the PSU. *It doesn't detect the SATA disks correctly (160 GB instead of 250GB). It also doesn't always detect the PATA drives across reboots, even if the controller is enabled.
  6. Thanks for the advice everyone. It seems that my problem was that my PSU was failing. I replaced it, and haven't had the problem again. Now it seems as though my CD-RW drive is failing... When it rains, it pours. Good thing I just got a butt load of graduation money
  7. I just placed an OverNight order w/ NewEgg for the SeaSonic S12-600. It seemed to be the popular pick over at Ars Technica, and it more than meets the requirements.
  8. I have an Antec TruePower 300 Watt. I noticed the note on PSU's when I joined the forum, so I am ordering a new one from NewEgg. Unfortunately, I am completely locked out of Windows, and it happened with Linux, so it isn't a driver problem. Plus, I have never overclocked. Since it locked up first with the DVD drive, I think it might be my secondary IDE controller. I hope it is just my PSU.
  9. Sorry, I assumed that since when I created my account it asked me about all the stuff it added it automaically. I didn't check. It should be there now.
  10. Windows XP x64 has nothing to do with it. I am having some sort of hardware failure. I can't even install Windows XP or Linux without it locking up on me.
  11. I just installed WinXP x64 on my Lanparty NF4 Ultra motherboard w/ 3000+ AMD64 proc. I am running 2x 512MB Ram (Corsair I think). I installed a new DVD burner, and, without installing any drivers, tried to read a CD off it. The machine instantly BSODed w/ MACHINE_CHECK_EXCEPTION ( KB 329284). I restarted and everything was peachy. Then, a few hours later, I returned to my computer and it was BSODed again (same error). When I restarted, it BSOD'ed a few seconds after the Windows Logo came up and instantly restarted itself. It has done this every time. I tried to boot into safe mode, but it froze on apcitab1.dat every time. Figuring Windows had just messed itself up, I tried installing gentoo, but it dropped w/ a kernel panic as I was unpacking a portage snapshot. Clearly, I have a hardware failure somewhere in my system, but I have no idea how to figure out what it is. I have run memtest86 for a couple of hours, with no errors. I am currently running it again and will do so till tomorrow just to rule memory out completely. I tried booting with only one cdrom, to make sure I wasn't taxing my powersupply, but it failed the same way. Help please!
  • Create New...