|Why were you re-installing the operating system?|
Did your client have any specific symptoms other than Windows wasn't working as it should?
can be caused by a hardware problem but it can also be caused by a software problem, usually related to the bios.
One thing it's extremely unlikely to be caused by is a wonky power supply.
It's also unlikely to be caused by a hard drive "logic board" or physical problem.
I searched the Asus forums in general about this error, and about this error for this mboard.
Nothing stuck out as especially likely to cause Stop: 0x0000007B for this mboard.
Apparently, it can be caused by ram errors, sometimes caused by ram that is compatible but the default ram voltage in the bios is not correct for the particular modules being used, but you say you've tested the ram and it's fine
Apparently, a problem with the graphics card can cause this error.
This mboard does not have onboard video.
You have not mentioned the graphics card.
Did you try removing the graphics card, cleaning it's contacts, re-installing the graphics card, or try another graphics card?
I looked at the Asus forums regarding this mboard.
There was at least one mention of bad capacitors on the mboard (I didn't look at all the posts about this mboard).
Open up your case and examine the mboard to see if you have bad capacitors, and/or other findable signs of mboard damage .
This was the original bad capacitor problem - has some example pictures.
History of why the exploding capacitors and which mboard makers were affected:
What to look for, mboard symptoms, example pictures:
Home page that site
- what the problem is caused by
- he says there are STILL bad capacitors on more recent mboards.
Pictures of blown capacitors, other components - power supplies, Athlon cpu's, etc.:
If you don't see anything obvious or suspicious regarding that.....
I looked at this model's manual.
If you are using a SATA hard drive
- Apparently, you can get this Stop: 0x0000007B error if you have a drive you intend on booting from connected to the wrong SATA socket.
- on this mboard, you can only boot from a partition on a hard drive (or boot a bootable disk in a SATA optical drive) if the drive is connected to SATA1 and SATA2 - the two SATA sockets closer to the COM header on the mboard (they're seen by the bios as master).
SATA3 and SATA4 are only for drives storing data (they're seen by the bios as slave).
Apparently, you can get this Stop: 0x0000007B error if you have a data cable connection problem.
Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and on the mboard, or on the drive controller card - it should not move when you merely brush your hand against it near the socket - if it does, mere vibration can cause a poor connection of it - use another SATA data cable that does "latch", or tape the connector in place.
(There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged)
The same thing applies for the SATA power connection.
- the bios defaults have the SATA controller(s) in Standard IDE mode (IDE compatible mode).
(bios Setup - Main menu - IDE Configuration - Configure SATA as: Standard IDE)
If you have the SATA controller(s) in another mode, apparently, in some cases, you get the Stop: 0x0000007B error some time affter you press F6 to provide a floppy disk in a floppy drive with the SATA controller drivers on it.
In that case this MAY work - if you set the bios to Main menu - IDE Configuration - Configure SATA as: Standard IDE, you don't need to press F6, and Setup will work normally (you can load the SATA controller drivers later after Setup has finished, then change the SATA mode to something else in the bios, if you wish).
NOTE that (2000's and XP's) Setup will only find SATA drivers that are on floppy disk in a regular floppy drive in almost all cases - a USB connected floppy drive is not recognized as a valid drive unless it is one of a very small number of models, most of which have not been made for many years. Setup cannot find SATA drivers on a CD, a hard drive, or a USB connected drive of any type other than a USB floppy drive it recognizes.
Apparently, a USB connected optical drive can cause this error.
In theory, having a USB connected printer or multifunction device connected while Setup is running could cause this error.
You haven't mentioned cards in slots. Are there any installed other than a video card? If so, try removing it/them while running Setup.
I've had odd resource conflicts with one particular USB mouse model. If you're using a USB mouse you could try another model or a PS/2 mouse.
You could try unplugging everything that's not necessary for running Setup, if you haven't already done so.
if you're using an IDE hard drive.....
Don't mix CS and master/slave settings for two drives on the same data cable.
Some hard drives, e.g. some Western Digital models, have two different ways master can be set - one, e.g.Master (single) for when it is by itself on a data cable, the other e.g. Master with slave, for when there is another drive on the same cable. Make sure that's correct.
For 80 wire data cables, one specific end connector MUST connect to the mboard - usually it's blue, but in any case it's the one farther from the middle connector on a three connector data cable.
On older mboards, it may not detect a drive correctly or at all if it's jumpered slave and is by itself on a data cable, or if it's jumpered CS and connected to the middle connector on a three connector data cable by itself. On newer mboards, often the drive is detected even if that's the case, BUT in some circumstances it won't be detected correctly.
(this also applies to IDE optical drivesand floppy drives)
It is common to un-intentionally damage IDE data cables, especially while removing them - the 80 wire ones are more likely to be damaged. What usually happens is the cable is ripped at either edge and the wires there are either damaged or severed, often right at a connector or under it's cable clamp there, where it's hard to see - if a wire is severed but it's ends are touching, the connection is intermittant, rather than being reliable.
Another common thing is for the data cable to be separated from the connector contacts a bit after you have removed a cable - there should be no gap between the data cable and the connector - if there is press the cable against the connector to eliminate the gap.
80 wire data cables are also easily damaged at either edge if the cable is sharply creased at a fold in the cable.
Try another data cable if in doubt.
- the bios defaults have the RAID IDE (second) header controller(s) in Standard IDE mode (or similar). You may have problems if the hard drive is connected to that if it's not in that mode.
If you have the hard drive connected to the other (first, main chipset) IDE header, it could be it will be less likely you would get the error.