Cephalxn wrote:Some fucking bios screen comes up with shit like "Please enter file name for new bios" and "enter password" (what fucking password?).
That almost sounds like a corrupted BIOS but quite possibly not.
Cephalxn wrote:CPU1* Intel Pentium 4 3066
CPU2 Intel Pentium 4 3066
Probably the same CPU unless you have one of the dual-core jobs.
Cephalxn wrote:then under that is a bunch of numbers climbing to 1040000 (or something), which i'm guessing is my ram... but once it gets to 104000 it goes back to zero and starts again.. repeat x infinity.
Some BIOSes will run the memory test about four times if something goes wrong during boot just in case there is a faulty stick of RAM in the board.
Cephalxn wrote:It says i can hit del to enter setup, but if i do, it goes to a blank screen with a blinking cursor top left and resets after a minute or so.
That's not normal.
Without getting a better idea of what's going on, there's only a couple of things that come to mind:
1) It might be something to do with the BIOS. AFAIK, modern viruses generally can't overwrite the EEPROM and very few would try anyway. They are usually written exclusively to spread. On the other hand, if you recently ran any updates from the motherboard manufacturer (or other vendor, if you bought the unit as a whole), it's possible something Very Bad(tm) has happened to the BIOS. I doubt it, though, because you would not normally be able to boot into Windows.
2) It might be a bad stick of RAM. This is a bit harder to diagnose, though and all solutions require you to pop the case. If you choose to take a look, try to find out how many sticks you've got. If you have about a gig of RAM, you probably have two (it is sometimes a bit more cost effective this way). Modern DDR boards usually have two channels with two slots a piece. If you pop a stick out, make sure it's the one in the SECOND bank (usually labelled bank 1 or bank B--the board will normally be numbered starting from ZERO). Then try booting and see what happens. Maybe even enter BIOS and have a look around.
The reason I say faulty RAM is a real PITA is because of the symptoms. Usually you won't notice anything's amiss until you load up an application that consumes a lot of memory (like WoW) or allocates memory like there's no tomorrow (compiling will usually find this problem--other times only benchmarking apps will uncover it). If it's only freezing up when you're playing WoW, it's probably the RAM. IIRC, Turus ran into a similar problem with his 64-bit rig when it had some new high performance memory. You might want to let it boot up and sit idle for about 15-20 minutes, even overnight, and see what happens.