General Troubleshooting

The Run.exe file on the driver disk is a necessary file for auto installation of all drivers. With the enhanced security system in Windows Vista and Win 7, every time the user tries to install a software or application, Windows will prompt the user to confirm the action. The purpose of the run.exe file is to obtain admin rights first so that all drivers can be installed automatically without users having to click many confirmation boxes. Since the goal of the run.exe file is to obtain admin rights, it is easy to be identified as a Trojan since most Trojan files show the same behaviour. However, we already confirmed that the Trojan detection is a false positive. If you are using Microsoft Security Essentials, Norton Antivirus, or Avira Antivirus software, they will not report this file as a threat, if you have your code updated. Otherwise please disable your Antivirus software before installing drivers to avoid this kind of confusion.

Most such cases are caused by defective or incompatible memory chips. As a result, you should verify whether it is compatible with the installed chipset. Some memory makers publish their own memory compatibility lists.

Compatibility lists are also available on our website In the event that your memory is not listed, we suggest that you replace it. Individual memory modules may also be defective.

The problem is not with the motherboard in 90 per cent of such cases. Please follow these steps to isolate the problem:

1. Please remove all non-essential components (hard drives, disk drives, card reader, etc…) The CPU and memory, along with the video card, if required, can be left in place at this stage.
2. Please erase the CMOS by following this procedure:
   1. Remove the electrical cord
   2. Remove the CMOS battery
   3. Press the CMOS button / Place the jumper in the reset position (10-20 seconds)
   4. Reinstall the battery, electrical cord and try again.
3. Inspect the motherboard as much as possible for signs of damage.
4. Test the CPU in another system or another CPU in the current PC.
5. Test the memory in another system, or different memory in the current XPC. We recommend the use of brand name memory for testing purposes.
6. Test the video card in a new system or another video card in the current PC.

Sometimes it is difficult to know why a computer does not POST. A number of things could be wrong with the system including the motherboard, power supply or components.

If the issue is being caused by a component, be it defective or incorrectly seated, you can use these steps to narrow the problem down:

• Power down the system.
• Disconnect the cable from the back of your computer.
• Remove power from all external components, hard drive, optical drive (DVD and/or CD drive), external video card, if one is present, and use internal video, again if present.
• Remove all memory modules.
• Disconnect CMOS Battery.
• Hold front power button with power cable DISCONNECTED for 30 seconds.
• Reconnect CMOS Battery.
• Replace one memory module.
• Replace video card, if one was originally in the system.
• Reconnect power cord and reboot the system.
• System will halt at POST and ask, if you wish to enter BIOS or load Windows.
• Choose BIOS option by pressing the DEL Key.
• Navigate to the Load Optimized Defaults entry on the main screen.
• Choose and accept this setting to optimise the BIOS settings.
• Exit screen and return to main BIOS screen.
• Navigate to Standard CMOS Features and make sure the date and time are accurate.
• Save and Exit the BIOS by pressing the F10 key.
• The computer will reboot. Let it reboot and hang.
• Power it down, disconnect power cable and reconnect hard drive.
• Reboot system and see what happens.

If your system does not POST, please try the above procedure with one memory module at a time by itself until you get a video screen. If you do not get a video screen, then something else might be wrong with your unit.

If the system POSTs, continue attaching devices and testing each until the system is back up.

The above procedure should help you narrow down the issue, if it is being caused by a component.