Member Avatar for CIsForCookie

Hey guys, sorry I’m new here but I seem to be having a problem with a new computer I just inherited from a friend. It came in an Alienware case and it’s got one of these Asus p4t533-c mobos in it that you can find a lot of problems about on Google, thing is I couldn’t find MY problem, and I was wondering if anyone could possibly give me a hand.

Basically I snatched this thing from a friend last night and when I try to turn it on, fans spin, lights come on, ps/2 keyboard and USB works (computer beeps when I push keys), it gives me ONE SHORT beep (no error during POST), everything seems fine but nothing comes up on the screen. It (the screen) doesn’t stay in standby, and is reading a signal at 1280x1024 @ 30HZ, but it stays black despite being taken out of standby. The last thing is that if I hit the power button, it (the computer) shuts off immediately; I don’t have to hold it.

Now, if I remove a stick of RAM (it has 4), the symptoms change. Fans still spin, drives turn on, however I now get no signal to my screen, it DOES NOT beep regardless of what I do to it and the keyboard will not work. Also, I now have to HOLD DOWN the power button to shut the computer off. This happens regardless of which stick of ram I take out, or how many.

I've tried... Removing the CMOS battery, changing PSUs, unplugging d*** near everything in the case, unplugging the HD, pulling ram, and changing the graphics card. I even tried taking the graphics card out completely at which point it will give me the proper error that the card is missing (1 long beep followed by 3 short beeps), but only as long as all 4 sticks of ram are seated.

I'm at a loss and I just want something to come up on the screen. I was wondering if anyone could give me a hand, or if it seems the thing is just shot and not worth fixing... Thanks for any advice!!!

  • 2 Contributors
  • 1 Reply
  • 185 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by jobforce

Dani AI

Generated

Brief, ordered troubleshooting addendum based on 's description and 's POST-card suggestion. Work top-to-bottom; do each step cleanly and test between steps. If unsure about any step, stop and get help to avoid damage.

  • Do a minimal out-of-case (breadboard) boot: place the board on cardboard, connect only PSU (24-pin + CPU 4/8-pin), CPU + cooler, one known-good RAM stick, and the system speaker or front-panel power switch short. Try both onboard video (if available) and the discrete GPU only when needed. This rules out case shorts and peripheral interactions. (techyorker.com)

  • Single-stick, slot-by-slot RAM test: use one known-good DIMM and try every memory slot in turn; then repeat with each stick you have. Faulty slots or mismatched population order often cause the exact intermittent POST behavior described. Consult the board manual for the recommended primary slot. (asus.com)

  • Confirm audible/vocal POST and speaker wiring: some Asus boards use a vocal POST reporter or a speaker-select jumper; make sure a speaker is connected to the correct header and the board is set to use it so you get diagnostic beeps/messages. Look up the board's POST code/beep table in the manual when you hear codes. (asus.com)

  • Use a POST/diagnostic card if you still get no video but power: a cheap PCI/PCIe/USB POST card will capture the BIOS POST code sequence and point to the failing stage when the display never appears. This is especially useful when the video subsystem never initializes. (passmark.com)

  • Inspect for physical failures: check for bulging/leaking caps, bent pins or damaged connectors, and try a different, known-good PSU and GPU if available. If the board refuses to POST in a minimal out-of-case test (and the POST card shows an early/stuck code), the motherboard or its VRM circuitry is likely the fault and replacing the board or using professional bench diagnostics is the practical next step. (lifewire.com)

Take ESD precautions, document any changes, and note exact POST codes or behaviors when you report back — those details make the next diagnostic steps much faster.

Member Avatar for jobforce

I would try using a P.O.S.T. diagnostic card and plug it in the USB port if you haven't already. It will return a POST error code which you can look up. Then, you would save a lot of time. These cards are very inexpensive (usually $5-10 bucks). Did your friend tell you anything about the problems experienced just before you got the machine?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.