Power rails should be withing 5% of specified voltage. For 12 volts that would be 11.4 - 12.6. A calculator will give you the others.
There is no accurate way to measure voltages except with a digital multimeter ($20 at Radio Shack). Onboard voltage monitoring is notoriously unreliable.
If you suspect power issues, play safe and swap the PSU. You could have bad capacitors in the PSU (a lot of that lately). Voltage may not indicate a problem if you have bad caps.
I'd prune your startups. WHY are you running Daemon Tools on a Server 2003 box? Are you actually using this as a server or as a workstation. If the latter, WHY? Server 03 is NOT a workstation OS and is not going to be compatible with some apps you'd use on a workstation. Some incompatible background application like that could be causing your problem. I have no idea if Daemon Tools is compatible with Server 2003 or not, but I wouldn't have it running on a server. You don't run ANYTHING on a server OS that you don't need to. Daemon is a possible culprit since it emulates a hardware SCSI controller and drive and the Machine Check Exception is generally a hardware error.
If you've hacked the OS to enable XP features in it like System Restore so you can use it as a workstation OS, then I don't even want to talk to you. You're running a hacked and inherently unstable OS and you shouldn't be suprised if you have problems. Install WinXP.
Machine Check Exceptions are usually hardware or driver related. A failing drive, for instance, can cause it. Download the drive manufacturer's diagnostic and run a full (advanced) diagnostic test on the drive.
Bad memory can also cause that error and so can incorrect memory timing. Run MEMTEST86+ for 12 hours to check memory stability. If you've fiddled with your memory timing make a note of the settings and then reset them to BIOS safe defaults and see if that helps.
Overheating can also, indirectly, cause hardware faults that will generate this error.
Lots of other hardware related issues can cause this error as well. Get the exact error code and consult this page:
http://aumha.org/win5/kbestop.php
SYMPTOMS
A computer running Windows NT Server or Workstation shows the following Stop error code:
STOP: 0x0000009C (0x00000030, 0x00000002, 0x00000001, 0x80003CBA)
NOTE: The parameters for the Stop message may vary from the parameters shown.
CAUSE
The computer processor detected a hardware error and reported it to Windows NT using the Machine Check Exception (MCE) feature of Pentium processors or the Machine Check Architecture (MCA) feature of some Pentium Pro processors.
MORE INFORMATION
Windows NT Server and Workstation version 4.0 now have the ability to report exceptions generated by the MCE or MCA features.
The Pentium and Pentium Pro processors provide a mechanism to detect and to report hardware-related problems such as memory parity errors and cache errors. To signal a hardware error, the processor signals the detection of a machine check error by generating a machine check exception (Interrupt 18). Windows NT simply reports the fact that the error occurred and displays parameters that you can use to decode the exception. Contact your hardware vendor or processor manufacturer for information regarding the Machine Check Architecture or consult the Intel Pentium Pro Family Developer's Manual - Volume 3: Operating System Writer's Manual.
Hope this helps...
