Computer won't even post anymore...

pseudonympseudonym Michigan Icrontian
edited December 2003 in Hardware
Ok, just got my RMAed Shuttle FN45 back from Newegg. The RMA says it was a repair, but it appears to be a brand new system. I put it together, boot it up, and it won't boot into Windows (Blue screens with the error normally given to a mem problem). So I go back into the bios, mess with the mem timings, and then it locks up at post. Now I'm getting a bit worried, so I clear the CMOS then do it again, mess with the mem speeds and timings, and it won't even boot, just keeps locking up at the first screen where it runs the mem check. So now I figure it HAS to be a mem problem, but I try one more time with the settings, it boots, and then it gives me a screen at post saying that it is "reprogramming MAC address" (thats odd) and then it locks up at boot. Now I'm really peeved, do a reboot and then NOTHING. No post, no screen telling me my mem freq, can't get into the bios etc etc, just nothing, not even a signal to the monitor. I try switching the mem around (only 1 stick, different sticks in each slot, etc etc) and that does nothing, then I worry that the vid card is toast, but thats not it (works in other system). I pulled ram from the other system and thats a no go also.

Now I'm stumped. Only thing I can think of is a Mobo short on the case or something, but it did boot for a time, and it just stopped, and the system comes fuly assembled from the factory (I'd like to avoid yanking the mobo out of that little case.).

Any ideas on why this thing won't even post now?? I'm seriously frustrated because this is the second one that has not worked right. Next steps are to test the mem in the other system with memtest, but I doubt that will pick anything up..... If nothing, I'm telling them to send me an Abit and a case......

Specs-
Shuttle FN45
Radeon 9800 Pro (Flashed)
2x 256 Mushkin Lvl 1 PC3200
AMD 3000+
:shakehead

Comments

  • pseudonympseudonym Michigan Icrontian
    edited November 2003
    Ran Memtest on my memory, thats not the problem (I'm running the memory right now at settings it never liked to run at in the shuttle). It appears there is a compatibility problem with the shuttle and the Mushkin, but I can't be sure. Gonna try stripping down the shuttle to nothing and trying to get it to boot with my good ol samsung that cost 50 bucks...
  • pseudonympseudonym Michigan Icrontian
    edited November 2003
    Stripped it down to nothing (Only HD hookup, no CD/DVD, FDD, front USBs etc) and put in my generic sammy memory (first 256 then 512) and still nothing. Turns on, but still no post. I've ran out of options here. Last thing to do is check to see if the CPU is toasted, but I doubt that highly.
  • muddocktormuddocktor
    edited November 2003
    Sounds to me like you might have another fubarred shuttle mobo. Sounds like some component on the mobo was very weak to start with and completely failed shortly afterwards.:(
  • pseudonympseudonym Michigan Icrontian
    edited November 2003
    Yeah. bit worried about the CPU now though too. I put the cpu (3000+ 400FSb) in my epox (Figured that it would run underclocked fine) and it did the SAME THING to my epox. Luckily, throwing my 2100 back in and clearing the cmos did the trick and I got it back up, but something very funny is going on.

    My 2100 also didn't get the Shuttle running, so I think you are right mudd. time to send it back, but this time its for store credit. Screw this SFF crap.....
  • ketoketo Occupied. Or is it preoccupied? Icrontian
    edited November 2003
    Last ditch effort, might wanna try powering up the Shuttle with a different PSU but I'm guessing that's not gonna do it. Sorry to hear the problems :(
  • pseudonympseudonym Michigan Icrontian
    edited November 2003
    Yeah, I'm done with it I think. I'm just gonna get a refund on the darn thing and put together a new system. It sucks, I really like the small form factor, and I even cut a hole in my desk where it fit nicely and out of the way :( All this because the analog sound didn't work right..... Stupid LAN parties :)

    New system purchase-
    Allied 450W
    Raidmax case (Black, $50 shipped)
    Thermalright something or other....

    add in what I already have and it should be nice.... Long as that CPU isn't the problem.
  • muddocktormuddocktor
    edited November 2003
    Which Epox board did you throw it in? It might be a barton compatibility problem with the bios you are presently running, if that 2100 is a pally and not a Tbred.
  • pseudonympseudonym Michigan Icrontian
    edited November 2003
    I threw the 3000+ in my 8RDA+ just to see if it would run, it didn't, prolly incompatibility as you say. The 2100 is a TBred.
  • muddocktormuddocktor
    edited December 2003
    If it's an 8RDA+, then I doubt that the problem is incapoatibility as that's a fairly new board which should handle bartons just fine. I hope you don't have a borked proc.

    When you get the replacement for the Shuttle in, install that 2100 first and make sure it boots OK, then try that 3000 out in the new mobo. That should tell you right away if the proc is borked.
  • pseudonympseudonym Michigan Icrontian
    edited December 2003
    It won't be a shuttle, I'm rather sick of it (too many problems related to RAM compatibility, ocing, sound. don't wanna deal with it anymore). It'll be an AN7.
Sign In or Register to comment.