Has my New Computer really Died?

Dr-DirtyDumpDr-DirtyDump
edited May 2004 in Hardware
Please tell me this is not true

I have just fried my AMD64 3200 KT8, had the same problems i.e. no Random Restarts, Freezes, CD-ROM opening would lock the PC? I Tried installing updated BIOS drivers from MSI utility, and now its fooked. I have heard speak that it is the CPU. My Comp boots up still but it can not read from the A dirve or CD DVD drives. Monitor does not work either. I have used a Jumper to see what the 4 Lights of doom would spell and all 4 stay solid RED.... guess its fried eh? So I have no way to reboot and the Jumper is telling me bad news. Well I have contacted the nice people at where I brought it from and hope the warrantry holds on. Thing is what happens if this occurs on the replacement PC?

I can add PC info if needed. I was so looking forward to the UK Bank Holiday 3 days of gaming thumbs instead I have to look at my dead PC

Comments

  • teflemingtefleming
    edited May 2004
    Have you tried reseating the CPU? Have you tried booting it up without RAM (it should beep at you?) Have you tried a different video card?

    I don't think you could have fried anything by updating BIOS...

    Just for clarity: You were having problems, so you updated bios, then it stopped working all together?

    Also, your full system specs (mainly RAM, video) couldn't hurt
  • Dr-DirtyDumpDr-DirtyDump
    edited May 2004
    Hi,

    I have not tried "reseating" as it was built before delivery. I am a little nervous about jigging with it, as the compnay is coming to collect and I dont want them thinking it was me adjusting things. I will be brave and have a little prod though.

    Your clarity is right. The darn PC had loads of problems I checked event viewer and saw NFTS problems, the HDD was corrupt when I ran CHKNFTS C: in DOS so I cleaned it up at reboot, this happened several times. (I only got the PC 3 days ago!). Also the freezes seemd to occur primarily when I opened the CD ROM. I also had a couple of Virus attacks wormblaster I think.

    1GB RAM DDR3200
    Radeon 9800XT
    KT8 Neo
    Barracuda 120gB
    AMD64 3400

    I am just concerned that the Jumper that plugs into the MOBO had those 4 RED LEDS displayed I will try without the RAM now.

    I have resolved myself to this being a dodgy PC but my mind keeps niggling to investigate further

    Cheers
  • teflemingtefleming
    edited May 2004
    Does the company you bought it from offer a "burn-in" service? Most builders will burn-in before shipping. (Burning a system in will usually prevent flaky issues like what you were having.) Asking for a burnin might delay your receive date, but its probably worth it if you're not comfortable performing a re-seat.
  • Dr-DirtyDumpDr-DirtyDump
    edited May 2004
    I just removed the RAM and started the PC. No beeps. There seems to be a strange clicking sound which I believe is coming from a CD unit, I tried disconnecting and restarting and no difference. Still no monitor start nor reboot.

    Oh well I guess I will have to await a replacement.

    Thanks fo your help I will ask about the Burn In from the company. I am pretty sure they did this though as all drivers etc seemed to be in place.
  • ShortyShorty Manchester, UK Icrontian
    edited May 2004
    Did you run liveupdate? and it stopped working after you did it... or before??
  • Dr-DirtyDumpDr-DirtyDump
    edited May 2004
    I had problems before running MSI liveupdate. I ran the Liveupdate thinking it would help resolve some of the problems discovered by the SANDRA tool. i.e. Corrupt HDD and BIOS out of date

    I have just tried clearing the CMOS but still no joy?
  • ShortyShorty Manchester, UK Icrontian
    edited May 2004
    What is very important to understand is that Athlon 64 motherboards are very sensititve to memory. Corrupt HDD is definitely a by product of poor memory performance.

    BIOS out of date is normal. Just because there is a new BIOS out for your motherboard doesn't mean that you need to update it ;)

    This sounds like poor memory coupled with a failed BIOS update. Clearing the CMOS won't fix the problem.

    Sorry mate, but it sounds like your board is hosed.
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited May 2004
    Sounds like it got dropped from a high ramp during shipping or something - I mean, really, all those problems in a brand new computer? I suspect physical trauma.
  • Dr-DirtyDumpDr-DirtyDump
    edited May 2004
    I though so :(

    Do you have any suggestions as to good memory? Its just if and when I get the replacement I really dont want the same thing happening again.

    If I replaced the RAM now is it too late? Is my MOBO board Dead?

    Thanks for your help
  • ThraxThrax 🐌 Austin, TX Icrontian
    edited May 2004
    Corsair or Kingston registered PC3200 memory is awesome.
  • qparadoxqparadox Vancouver, BC
    edited May 2004
    If the bios flash failed the bios is certainly dead, you could buy a new bios chip or try some fancy reflashing methods ... but you don't want to do that on a new computer you just paid a lot for. I definitely think this is the result of poor memory. With the recent RAM price increases I've noticed several local companies using absolute crap memory (some even dug up some PC2100) in their new machines to maintain price points. Realistically the company should replace your machine with one that has RAM that works. If you want top quality RAM something like Kingston Hyperx, Cosair or Muskin would be in order.

    Thrax, does that board have registered memory support?
  • ShortyShorty Manchester, UK Icrontian
    edited May 2004
    You can try a reflash.. if you have form of access to the BIOS.. if it shows up at all...but you don't want to really do much more.. as Im sure the supplier of said kit is going to ask you how much futzing around you did ;)

    Thrax hit the memory on the head. Don't scrape on A64 memory. You will pay for it later on.
  • ShortyShorty Manchester, UK Icrontian
    edited May 2004
    qparadox wrote:
    Thrax, does that board have registered memory support?
    No. Athlon 64 does not required registered memory. It's single channel socket 754.

    Registered is required by the FXxx and Opteron Socket 940 family.
  • Dr-DirtyDumpDr-DirtyDump
    edited May 2004
    Thanks Guys fo this info....
    .....I will get a replacement and install good RAM
  • ShortyShorty Manchester, UK Icrontian
    edited May 2004
    Dr.DirtyDump wrote:
    Thanks Guys fo this info....
    .....I will get a replacement and install good RAM
    That's what we are here for ;)

    Get any more problems.. say here first :cool:
  • Dr-DirtyDumpDr-DirtyDump
    edited May 2004
    what do you think of Corsair XMS3200 TWINX1024-3200LL??

    Would this be good?
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited May 2004
    MSBlaster will eat system files. When it is done, 2-3 days later as far as system running time in days, the PC will not be able to load Windows or will run like the HD has corrupt system files. AND, NTFS file system handlers can be trashed by Blaster, AND, the journals will be all out of whack so the NTFS checker will have to treat drive as corrupt. Blaster force renames .exe files and can relocate them also, and infect them so they are useless. It also can disable some AV, and destroy some AV version executables beyond use. Unfortunately, if your MSI Liveupdate also got blastered, it would produce a bad flash when flashed from Windows. Only way to recover from that is to reflash manually from DOS, clear CMOS table, and redo from scratch the BIOS settings.

    One little thing, my MSI board did NOT beep unless it was BIOS beep and BIOS error (did not like a USB mouse on a PS\2 adapter, ANY adapted mouse of three I tried, THEN it would stop and beep after POST was mostly complete, but early POST errors were LED given, not audible series at all.). Instead, it had an 4 LED set in a 2X2 matrix on a slot riser (aka slotket) that gave POST diagnostics. The manual had a set of LED color codes in a table, and what was probably wrong from those.

    So, if it could not post, the only thing that showed up was LEDS in a pattern that indicated where in POST seuence the hang was. Since the slotket was on back of box, most folks would not think to look for this, but see if your computer motherboard manual has an LED POST ERROR Diagnostics table in it, OK??? And tell us what LEDs are what color-- if your board has such things???

    NO LEDS means board is dead or RAM and video card and CPU are ALL unseated, or any two of those are unseated. SOME LEDS can tell us where post hung, and it will hang at fatal (to POST) error point, but that does not mean necessarily fatal to motherboard itself.

    John D.
  • muddocktormuddocktor
    edited May 2004
    Dr.DirtyDump wrote:
    what do you think of Corsair XMS3200 TWINX1024-3200LL??

    Would this be good?


    That's some great memory there.:)
  • ThraxThrax 🐌 Austin, TX Icrontian
    edited May 2004
    Dan wrote:
    No. Athlon 64 does not required registered memory. It's single channel socket 754.

    Registered is required by the FXxx and Opteron Socket 940 family.

    Oh god. I made such a noob mistake. I'm usually the one telling people they DON'T need registered for an S754 rig.

    Cripes. :zombie:
  • Dr-DirtyDumpDr-DirtyDump
    edited May 2004
    the 4 leds on the Jumper D Bracket prior to POST stay RED according to the Manual this is

    "the D-LED will hang here is the processor is damaged or not installed properly."


    The LEDS look something like this

    O O
    O O

    But are red.

    If this has been caused by wormblaster and faulty RAM how can I protect my "replacement comp" from it? I will try NAV 2004 and a good Firewall prior top getting on the WEB. I mean I am going to rpelace the RAM but protection from Wormblaster prior to getting updates protection etc.
  • EyesOnlyEyesOnly Sweden New
    edited May 2004
    The nav cd might let you scan the comp before you install. As for viruses screwing up the hardware that's impossible as far as i know. They will corrupt files though.

    Have you checked that the cpu is installed correctly. Wait you didn't install that? Well as dan said if you've flashed the bios with a faulty virused app then that could have caused this. Viruses wont get into your rig unless you download something unknown so when you get everything set up, install virus app of choice and update the definitions. Then you shouldn't get any viruses.

    Hope you get this fixed.
Sign In or Register to comment.