Common Test Error Messages |

When BurnInTest encounters an error during a test run a short description of the error is displayed in the main window. What follows is an explanation of the common errors that may be encountered. No errors No errors have been detected. Incorrect mathematical addition / subtraction / division / multiply

The execution of a mathematical operation came up with the wrong result (e.g. 1 + 1 = 3). This is a very serious error for a computer as it means the computer is incapable of execution the same sequence of instructions to get the same result. Possible reasons are faulty RAM, System bus, CPU or overheating. There is a strong chance that your computer will crash or lock up just after an error like this because if the computer can’t add two numbers correctly, there is a good chance that it can’t continue to run a program either.

Incorrect MMX addition / subtraction / multiplication
Incorrect 128bit (SIMD-SSE) floating point addition
Incorrect 128bit (SIMD-SSE) floating point multiply
Incorrect 64bit 3DNow! floating point result

Similar to the above, mathematical faults except that the error occurred while using the extended CPU instructions. (Rather than the standard 32bit Maths)

Failed Windows call - Line Drawing / Bitmaps / Shapes

The Windows operating system has failed to correctly complete the graphical operation that was requested by BurnInTest. This could indicate that Windows is running low on internal resources or that there is a problem with the software drivers for the video card.

No free memory for buffer

Windows does not have enough free memory to allow the allocation of a buffer.

If the test that displays this error has not started, then this may not be a system error, but rather a warning that there was not enough memory to run the test. For example, the memory test may report this error if there is insufficient available memory to start the memory test, rather than a physical memory error. This may be due to (i) Another BurnInTest test using a lot of memory, e.g. the 2D video memory test with the test all available memory option can use a significant amount of system RAM (depending on the system), or (ii) Another process is using a lot of memory. It is suggested that other applications are closed whilst BurnInTest tests are running, or (iii) there is not enough memory for some other reason.

Not enough free disk space

There is not enough free space on the disk to create a test file for the Disk tests.

Test file could not be created

BurnInTest was unable to create a file on the disk in order for it to be able to run the disk tests. Check that you have access to the disk with Windows explorer, Check file write and create permissions in the root directory of the disk under test.

Error while writing to the disk

The test file could not be completely written to the disk. This could indicate a hardware error or a sudden lack of free disk space

Error writing to disk - Disk is full

The test file could not be completely written to disk because the selected hard drive is full.

Test file could not be re-opened

The test file was created successfully, but could not be reopened for verification. This could indicate a hardware error or a resource problem within Windows.

Error while reading from the disk

The test file created on the disk can no longer be read. This could indicate a hardware error or a problem within windows.

Data Verify failure

This is a serious error that indicates that the data read from the disk is NOT the same as the data that was written to the disk. This could indicate a hardware error.

Disk is full or FAT root file system limit reached

A test file could not be created on the disk being tested because the disk is full or the capacity of the file system has been exhausted. Normally this error only happens when the disk is formatted using the old FAT files system. Floppy disks still use the old FAT file system and there is a limited number of files that can be created in the root directory of a floppy disk. The number of files depends on the length of each file name. (and does NOT depend on available disk space). Thus this not really an error, but a limitation of the FAT file system. (Which has now been replaced by FAT32 and NTFS).

Warning - Disk low speed threshold crossed

The disk speed has fallen below the low speed threshold as specified in the Disk test preferences window.

Could not set CD Time format
Could not get number of audio tracks
Could not play the audio track
CD-ROM failed to return status information
Can not detect audio information on CD
No audio media in CD-ROM

These errors relate to one of the following problems.
There is not a CD in the first CD-ROM connected to the computer.
The CD in the CD-ROM is not a Music CD.
The CD is already in use by another application.
The CD has an error on it and is unreadable.
The CD is dirty, dusty or scratched and can not be read
The CD Software drivers are not correctly installed.
The CD-ROM has a hardware error.

Checksum failure for optical disk file

This indicates that the file read from the optical data disk being tested failed the checksum verification. This means that the optical drive is unable to accurately read data from the optical disk being tested.

Could not open file on optical disk for reading

The disk in the optical drive selected could not be opened for reading as a data disk.

Error while reading file from optical disk

A full block of data could not be read from the optical data disk.

Error while searching for files on optical data disk

An error occurred while searching for files on a optical data disk. This can be the result of a corrupted (Error code 1117) or blank optical disk (Error code 21).

Data read from the optical disk was incorrect

A block read from a specialized PassMark Test CD or DVD was incorrect. There was at least one byte in the block that was not the value expected. In the detailed error log there is additional information that give the number of bytes in error and displays the expected value and the value actual read from the disc. It may be that the drive is faulty but you should check that the disc is not scratched, dusty or damaged before assuming a hardware fault.

Could not determine type of PassMark Test CD/DVD

BurnInTest was expecting to find a specialized test CD/DVD in the drive selected. A specialized test CD/DVD has a specific set of files, which all have a specific file size. These disc are normally purchased from PassMark Software or made using the PassMark CD-Maker utility. BurnInTest was not able to find the correct files or the files appear to have the wrong file size. If you don’t have a specialized test CD/DVD available, select one of the other two test options in the preferences window.

Error loading DirectX .dll

DirectX (version specified in the System Requirements section) is not installed correctly.

Error initializing DirectX
Error initializing DirectX device

These errors relate to one of the following problems.
DirectX (version specified in the System Requirements section) or above is not installed correctly.
You need to install the most recent driver for your graphics card.
You’ve selected an incompatible screen resolution and/or color depth for your desktop.

Error creating DirectX textures
Out of video memory

This error means that you have exhausted all of your graphic adapters onboard memory.

Warning: Switching to reference rasterizer

BurnInTest was unable to initialize a hardware accelerated device and is using software emulation to render the 3D graphics test. This will result in a much lower frame rate.

Video memory corruption

One of the pixel values read from video memory is not the same as that which was written to video memory. This may indicate that your video memory is damaged.

Error initializing DirectDraw

DirectDraw could not be initialized. Check that DirectX (version specified in the System Requirements section) is installed. Check that the most recent version of your video adapter driver is present.

Frame could not be displayed and was skipped

DirectDraw reported an error when displaying one of the test patterns to the test window. If you receive many of these errors, reboot and check that the most recent version of your video adapter is present. There are several instances when this message is expected. One example is when the video display mode is changed or power control settings are altered.

Not enough video memory available for test

The minimum video memory required for the test (usually 100KB) could not be allocated. Check your display adapter is not carrying out any other resource hungry processes, such as games. Attempt a reboot and ensure that the most recent version of your video adapter is present.

Minimum color depth of 16 bits required.

Your screen mode is set to a color depth of less than 16 bits. Set the screen mode to 16 bit or 32 bit color and run the test again.

Could not find the default printer
Could not open the default printer
Could not send page to printer
Could not open printer spooler
Error writing data to spooler

These errors relate to one of the following problems.
There is no printer defined in the Windows setup.
There is no default printer selected.
The default printer is not connected to the printer.
There is no paper / ink / toner in the printer.
There was a communications problem to the printer. e.g. The parallel port may not be functioning correctly.

Could not open printer command file

The printer command file specified by the user was not found on the hard disk. Check the path name and file name are correct in the preferences window.

Error verifying data in RAM

The data written to memory is not the same as the information read from memory. This is a very serious error, much like the “Incorrect mathematical…”, error above. It’s highly likely that your computer is about to crash or lock up.

Error allocating RAM from Windows

The Windows operating system was not able to allocate the amount of RAM requested by BurnInTest for the memory test. As the RAM must be allocated in a continuous block, this error can sometimes be seen as a result of free memory fragmentation.

Error connecting to network
Could not create a network socket
Could not set socket timeouts

During the establishment of a network connection an error was encountered. The Network address selected has no effect on if these errors occur. They can be the result of the following problems.
– There is no network connection configured for the computer
– The computer is physically disconnected from the network
– The Internet TCP/IP protocol is not installed on this computer

Networking functions aren't available (ws2_32.dll)

During the establishment of a network connection an error was encountered. This error indicates that the Windows Network Socket functions supplied by the library ws2_32.dll are not available on this system. This main mean that
- The Internet TCP/IP protocol is not correctly installed on this computer

Could not allocate memory for packets

Windows is low on resources and cannot allocate any more memory.

Could not resolve host name, check settings

The Network address selected does not seem to be correct. Try another address, or using a TCP/IP address directly. The address 127.0.0.1 is good for testing as it is an internal loop back.

No permission to open RAW network socket

If you are a non-administrator logged you will get this error with the Network test. In Windows 2000, there is no way to disable this security check. Access to Raw Sockets is granted on a per-transport basis. For the address family AF_INET, only administrators have the access necessary to create Raw Sockets. The test should be run while logged in as the ‘administrator’.

Timeout sending packet
Timeout waiting for packet
Error sending packet
Error receiving packet
Bad packet

These errors relate to one of the following problems.
The Host using the network address selected doesn’t reply to ‘ping’ messages. Try a different host.
There is a configuration problem in your network connection.
Your network card may be faulty.
The network itself is not reliable. The information send was not the same as the information echoed by the remote host.
The network is congested or faulty and the packets are not being echoed within the timeout period specified in the preferences window.

Network test alarm. Error ratio exceeded

The Bad Packet ratio specified in the Network test preferences has been exceeded.

Got someone else’s packet

This is not really an error. It’s more of an information message. Don’t worry about this message.

Bad packet. Checksum incorrect

The checksum in the echoed, incoming data packet is not correct. This indicates data corruption or a fault on the remote machine. Note that this checksum is calculated by the remote machine.

Bad packet. Corrupt data

The contents of the incoming data packet are not correct. Normally this error would not been seen as the checksum should detect the incorrect data before this error occurs.

COM port is already in use by another program

The serial port selected for the test is already is use by Windows. This may be for the mouse, a modem or another serial device.

The requested COM port could not be found

The serial port selected for the test does not exist in this computer. This could happen if COM4 is selected but the computer has only 2 serial ports, COM1 and COM2.

Error while opening COM port

Windows has reported an error while trying to open the serial port selected for the test. This could be a configuration problem in Windows. This error should not normally been seen.

Error getting current COM port configuration
Error while setting new COM port configuration

Windows has reported an error while trying to configure the selected serial port. The most common cause for this error would be the selection of a speed that is not supported by the serial port chips installed in the computer (the UART). Most chips only support speeds up to 115Kbit/s.

Corruption. Data received didn't match data sent

BurnInTest has detected that the data received from the serial port doesn’t match the data sent. This could indicate that there is a hardware problem. This type of data corruption would however be a fairly rare type of event. The more common result of a hardware failure would be the total inability to send or receive data. (see below).

Error while setting current COM port timeouts

Windows has reported an error while trying to set the timeout periods for the data transmission and reception. This could be a configuration problem in Windows. This error should not normally been seen.

Error while sending data to the COM port

Error while receiving from the COM port

Windows has reported an error while trying to send / receive data through the serial port. If a device (such as a loop back plug) is not connected to the serial port then no data can be sent. If the loop back plug is connected and is not faulty, then this error may indicate a hardware fault.

COM port Clear To Send (CTS) line stuck high

COM port Clear To Send (CTS) line stuck low

COM port Data Set Ready (DSR) line stuck high

COM port Data Set Ready (DSR) line stuck low

The signal pin test phase of the serial test has failed. This might be because of an incorrectly wired up loop back plug, a cabling problem between the serial socket and the motherboard, a non standard COM port or a problem with the Windows configuration for the COM port. A failure of the CTS pin may be caused by the associated RTS pin, to which it is looped. A failure of the DSR pin may be caused by the associated DTR pin, to which it is looped. If you have made your own serial port loop back plug - check it carefully.

Parallel device driver not initialized

To access the Parallel port under Windows 2000, XP and 2003 Server BurnInTest needs to load a special device driver that allows direct access to the parallel port. If this driver, “DIRECTIO.sys”, can not be found or loaded then this is the error message. You need to be logged in as the administrator in order to load this driver. In Windows Vista (and later) you need to be running with elevated administrator privileges or turn Windows UAC off. This error may also occur if the file is missing.

Parallel device driver could not detect port

This error usually occurs if the parallel port test attempts to access a parallel port, which doesn’t exist (such as perhaps LPT3 or LPT4). It can also happen if the BIOS settings for the port are not correct. Note that the old ‘bi-directional’ BIOS mode is not supported. ECP or EPP mode is required.

Could not open parallel device driver

This error usually occurs if the parallel port test fails to access a parallel port, which does exist.

Warning: Could not lock parallel port

When the parallel port test initializes, it attempts to lock the port for exclusive access. This is essentially to prevent Windows XP and above “warm polling” the port, which can produce invalid test results. This error results in a failure to lock the port and does not represent a failure in testing the parallel port.

Corruption. Data received didn't match data sent

The data sent to the Parallel port was not the same as the data received. This may indicate a hardware problem or a missing or faulty loop back connector.

Error while sending data to the parallel port
Error while receiving data to the parallel port

Windows has reported an error while trying send or receive data. This could be a configuration problem in Windows. This error should not normally been seen.

Could not detect the parallel port selected

BurnInTest was unable to find a parallel port at the location selected. Try picking another port and see the Parallel port test description for more details about port selection

Could not access the tape drive selected

The tape drive selected from the preferences window (e.g. TAPE1) could not be found connected to the computer.

Error while formatting tape partition

The tape drive reported an error while trying to format the tape in the tape drive.

Error while loading (rewinding) tape

The tape drive reported an error as a result of a request to load and position the tape for writing.

Error while locking tape in drive

The tape drive reported that it was unable to lock the tape in the drive. Some tape drives may not support this option and this art of the test can be turned off in the tape preferences window.

Tape device is not ready to start test

The tape drive is not in a state where it can accept a new command (but it should be).

No media in tape drive

The tape drive reported that there is no media in the drive.

No free memory for write buffer

There is not enough free RAM to allocate a write buffer.

Error while seeking to new position on tape

The tape drive reported an error while seeking to a new position on the tape.

Error while writing to tape

The tape drive failed to fully write the current data block to the tape.

Error while writing file marker between files

The tape drive failed to write a file marker. (A flag to indicate a new file)

Error while reading data block from tape

The tape drive failed to fully read the current data block from the tape.

Corruption. Data read didn't match data written

The data read from the tape didn’t match the data written to the tape.

Unable to get/set tape drive parameters

A request to get/set the tape drive capabilities resulted in an error.

Unable to get/set tape media parameters

A request to get/set the capabilities of the media current in the tape drive resulted in an error.

Tape is write protected

The tape media is write protected and the test cannot continue.

Tape drive has reported that it requires cleaning

The tape drive and/or the media in the drive are dirty. Clean the tape drive before reattempting the test.

Tape partition is too small for test files

The media is too small or the tape drive does not have the capability to fit the requested files on the tape. Select fewer files or smaller files or use a bigger tape.

Could not open MIDI Sequencer or MIDI file

The sound test was not able to open the sound card device or the midi sound file on the disk for playback. This can be because the test file has been moved or deleted from the disk or because the sound card has not been installed correctly.

Failed to play back MIDI via sequencer

The MIDI sequencer was not able to play back the file. This error is normally accompanied with a 2nd error message in the detailed log that gives additional information.

Could not play back wave file

The sound test was not able to open the sound card device or the wave sound file on the disk for playback. This can be because the test file has been moved or deleted from the disk or because the sound card has not been installed correctly.

Audio Input doesn't match Audio Output

The data received through the audio line in is in a wave type form, but differs from the output waveform by a greater degree than the Max Distortion value set in the Sound test preferences. It is not rare for occasional high distortion values to occur on certain sound cards, especially if the system load is particularly high.

If you are testing the video playback at the same time as the Sound loopback test, ensure the video test file does not include an audio track.

Corrupt Audio input

This is a more serious error than the previous one. The audio line in data is corrupt and in no way resembles the output wave. Check that the audio loopback cable is connected to the correct ports and the Windows mixer settings are properly configured (see section 3.11 Sound card test).

If a system is under high load, the audio device driver may not be able to output a continuous Sine waveform. If this occurs, you may see the "Corrupt Audio input" warning. To determine if this is load related, reduce system load and re-test.

If you are testing the video playback at the same time as the Sound loopback test, ensure the video test file does not include an audio track.

Could not detect USB loopback plug

The USB enumeration process failed to find a USB loopback plug device. This might be because, (1) The USB plug is not physically connected. (2) The USB loopback device driver was not successfully installed. (3) The USB plug was connected while a test was already in progress and thus was not recognized. (4) The Windows O/S is not installed correctly. (5) The USB socket on the PC is faulty. (6) The USB cable being used is faulty or is prone to errors. (7) The plug itself has become faulty. (8) The USB cable is too long or of poor quality (shielded cables under 5m are recommended). As there are many possible causes for this error it can take some investigation to find the origin of the fault. The first step however should always be to remove the plug, wait a few seconds then reconnect the plug.

USB loopback plug identified itself incorrectly

The USB enumeration process succeeded, but the unique identification information stored in the USB plugs EEPROM memory is incorrect. Under normal conditions this should never happen. The plug can not be used unless it is programmed correctly. Contact PassMark Software for assistance.

Could not allocate RAM for USB I/O buffers

The system is low on memory

USB device open failed

The initial attempt to connect to the device failed. The device might already be open and locked by another process. With all the tests stopped, try removing the plug, waiting a few seconds then reconnecting the plug.

USB device reset failed

Setting USB data rate failed

Setting USB data characteristics failed

Setting USB flow control failed

Setting USB I/O timeouts failed

Purging of USB I/O data buffers failed

Set USB loopback DTR failed

Set USB loopback RTS failed

These errors are all very rare. Normally errors will occur earlier in the initialization process and not at these steps. In addition to the possible causes for errors mentioned above, it is also possible that there is a software configuration problem. If one of theses errors persists, contact PassMark Software for assistance.

Data packet transmission failed

USB driver reported send error

Data could not be sent to the USB device. It may be that the device has an intermittent connection to the host and has disconnected itself. (i.e. a faulty cable). It may also indicate that there is a problem with the device drivers or USB hardware.

Data packet reception failed

USB driver reported receive error

Data could not received from the USB device. It may also indicate that there is a problem with the device drivers or USB hardware.

USB data packet verify failed

A block of data was sent to, and received from, the USB plug but the data was corrupted. What was received did not match what was sent. This could indicate a poor quality cable that is subject to external electromagnetic interference or faulty USB hardware.

Warning: Too many USB errors attempted reset

After 10 errors BurnInTest automatically attempts clear the error condition start by provoking a reset on the device and device drivers. If the error condition does clear after this action the problem was almost definitely a software problem.

Insufficient rights to lock pages

Either you are not running Windows 2000 or XP or the administrator user rights to lock pages in memory is not set. See the page in the help file called, Setting the Lock Pages in Memory right for more information. This right is required for the advanced memory test and is turned off be default. If you have set this right, make sure you are logged on as the administrator and have rebooted the machine so that the change takes effect.

Could not get extended RAM info. W2000 or XP Req.

The user has selected the advanced RAM test but there was a problem detecting while trying to obtain information about extended RAM. This maybe because the system is not running Windows 2000 or later.

SMART Threshold exceeding condition detected.

One of the drives S.M.A.R.T Attributes has exceeded its threshold. This signals imminent drive failure and indicates the tests should be stopped and the drive replaced. To learn more about S.M.A.R.T, see What is S.M.A.R.T?

Could not get extended RAM info. W2000 or XP Req.

The user has selected the advanced RAM test but there was a problem detecting while trying to obtain information about extended RAM. This maybe because the system is not running Windows 2000 or later.

Recoverable Video playback error.

Unrecoverable video playback error.

Video format not supported or invalid.

Unable to play the video file.

Failed to play the video file specified in Preferences. The Video codec may not be supported. Check the installed video codecs. A level 2 trace log may also provide additional information.

Video Codec not supported or audio only.

The Video file specified in Preferences is either Audio only or the Video Codec is not supported. Check that the Video contains video. Considering using the Video samples available from the PassMark Software website.

Configured Parallel port does not exist

The Parallel port configured does not exist on the current system. Check that the Parallel port specified in preferences exists on this system.

Could not set USB2Test mode

The USB test failed as there was insufficient memory for BurnInTest to communicate with the USB 2.0 Loopback plug device driver.

Unable to get disk Volume extent information

BurnInTest has been unable to determine the physical disks that are used to form the disk drive volume (letter). A level 2 trace log may also provide additional information.

Butterfly seeking test not supported for this disk

BurnInTest has been unable to determine the physical disk drive geometry from the disk drive device driver (like number of cylinders etc) required to perform the Butterfly seek test. This may be for devices that do not support drive geometry, like some USB drives. It may also be an access privileges issue. This error can be ignored by changing the BITErrorClassification.txt file in the BurnInTest directory, e.g. for skipping the Butterfly seek test for non-cylinder based disks (eg. USB drives). A level 2 trace log may also provide additional information.

Unable to open Physical disk drive for seeking

The physical disk drive (rather than disk volume letter) could not be opened for the Disk Butterfly seek test.

Seek size requested not equal to actual

During the seeking part of Disk or CD test, the requested seek size did not match the actual seek size. A level 2 trace log may also provide additional information.

Not enough memory for the test

The test (e.g. Sound) was not able to be run as there was not sufficient memory.

Unable to load DirectDraw functions

Software emulation is not available

No hardware support for operation

Hardware-only DirectDraw object creation not possible

DirectDraw problem prevents the test from running. Check DirectDraw hardware acceleration is enabled on the test system. By default, most servers (eg. all Windows 2003 servers) have DirectDraw hardware acceleration disabled. DirectDraw hardware acceleration can typically be enabled from: Control panel -> Display -> Settings -> Advanced -> Troubleshoot, and move the Hardware acceleration slider to the right (ie. to increase the level of graphics hardware acceleration). In some cases you will need to use the Graphics card manufacturers tool to enable Direct3D hardware acceleration.

Invalid video file specified

No test video playback files entered in preferences.

Unsupported waveform audio format for output device

Sound output device unable to be opened

Could not create the sound output object

Unsupported waveform audio format for input device

Sound input device unable to be opened

There was an error during the audio test. A level 2 trace log may also provide additional information.

Unable to allocate memory for audio clip buffer

The audio test was not able to be run as there was not sufficient memory for the test data to be created.

Insufficient system resources to complete test

The test (e.g. CD, Disk or USB) was not able to be run as there was not sufficient memory for the test data to be created.

Unable to create CD test data

Error creating a test image (that is to be written to the CD). This may be caused by insufficient space on the Hard disk drive or insufficient privileges to the location specified in Preferences.

Unable to initialize for CD burning

Error retrieving information about the CD drive to test.

Unable to open CD test data

Error opening test data image (that is to be written to the CD). This may be an access violation issue.

Unable to select CD recorder for test CD drive

Error preparing for CD burn test. Typically the test CD drive was not found.

Unable to Burn CD

There has been an error starting the CD burn test. The most common reasons are hardware faults, unsupported media (e.g. CD-R, DVD-R, DVD-RW), the CD drive is not a burner. Additional information should be displayed in the log file. A level 1 trace log may also provide additional information.

Video Playback is dropping samples

The video playback test has dropped video frames. This is typically caused by the system load being too high for the video playback test to be able to handle the display of all video frames. This error can be ignored by changing the BITErrorClassification.txt file in the BurnInTest directory.

External Plug-in reported error

The Plugin reported an error, but did not specify an error message. If possible, it may be useful to change your Plugin test to define specific error messages.

External Plug-in file does not exist

BurnInTest has not been able to find the Plugin test file specified in preferences. Check the path and file names.

Unable to communicate with the External Plug-in

BurnInTest has been unable to communicate with the plugin in order to start the Plugin test. Check the command line parameters and the Plugin software code to ensure the BurnInTest interface is properly handles, as per the sample applications on the PassMark website.

Data failed to validate, checksum error

Test data packet payload sent or received during the Advanced network test was corrupt.

Unable to initialize advanced network test

General Advanced network test startup error. A level 2 trace log may provide additional information.

Corrupt header data

The header of an Advanced network received test packet is corrupt (wrong values or size).

Unable to start winsock, advanced network test can not continue

Unable to start Windows sockets which is required for the Network tests. Version 2.2 or higher of Winsock is required.

COM port detected a Receive Overrun Error

A COM port hardware input buffer has overflowed.

It is often related to load on the COM port and the CPUs ability to service the COM port interrupts (ie. CPU load and interrupt priorities). The COM port typically has two 16 byte buffers (on a UART/Super IO chip). One for transmit and one for receive. The "COM port detected a Receive Overrun Error" occurs if data is received by the receive buffer when the receive FIFO buffer is full. That is, before a COM port interrupt is serviced by the CPU to copy the receive buffer to RAM. The COM port interrupt trigger level is a Windows setting, this is typically defaulted to 14 - ie. generate a CPU interrupt when 14 of the 16 bytes in the UART buffer are full. In this case the last byte in the UART receive FIFO is overwritten and that data is lost.

To investigate further you could try changing:

(1) the COM port speed (reduce)

(2) the COM port duty cycle (reduce)

(3) the UART settings (please see: http://support.Microsoft.com/kb/131016/EN-US/ ). For example reduce both buffers to 8 (ensure that the transmit FIFO is not larger than the receive FIFO).

(4) If you are running the optical drive test at the same time, then you should check that the optical drive is on a controller that is set to DMA rather than PIO (as PIO will lead to a large number of CPU interrupts, which will impact the servicing of the COM port interrupt). I understand that the controller can automatically drop from DMA to PIO mode based on the number errors (such as a badly scratched disks).

COM port detected a Receive Parity Error

The serial port hardware detected a parity error during the serial port test.

COM port detected a Receive Framing error

The serial port hardware detected a framing error during the serial port test.

COM port detected a Transmit Queue is full

BurnIntest tried to transmit test data character over the configured serial port, however the output buffer (on the serial port handling chip) was full.

Automatic data transmission recovery attempted

Automatic data reception recovery attempted

The USB test using the USB 2.0 Loopback plug has failed on a write or read to the USB plug.

USB errors can be corrected at different layers, including hardware, operating system/device driver and application layers. Errors that are not recovered at a hardware layer are often recovered at a device driver layer (but not always). With BurnInTest and the USB 2.0 Loopback plug, PassMark have intentionally not attempted error recovery at the device driver level as this may mask real hardware problems. This error is a hardware error (such as poor quality USB cabling or other electrical interference) that is not recovered at the USB hardware layer. BurnInTest will try to recover from the error at the application layer to determine if the error is recoverable (i.e. the data has not been removed from or corrupted in the appropriate buffer)

These errors can be ignored by changing the BITErrorClassification.txt file in the BurnInTest directory. In this case BurnInTest will attempt recovery, and only report the error if recovery fails. Note: BurnInTest will not re-send data in order to achieve recovery.

Could not play back MP3 file

The playback of an MP3 test file has failed. This can be due to the Audio device driver being out of date.

Advanced Network test error

General Advanced network test error. A level 1 trace log may provide additional information.

No media detected in drive

No floppy disk has been detected in the floppy disk drive.

No operations reported in timeout period

There where no operations during the last watchdog time period (2 minutes) or the test did not start. This error is a warning that investigation is required.

Advanced Network Send error

Advanced Network Receive error

There has been an error when trying to send or receive test data during the Advanced Network test. This is a network error. A level 2 trace log may provide additional information.

Unable to open test window

BurnInTest has not been able to open a test window. This may be due to lack of system resources.

Failed to create texture for 3D test

This is a graphics card or DirectX error. With version 5.2 (not V5.3 or later) this error could have occurred if the user had insufficient privileges to create temporary files in the root directory of the drive (such as a standard user on Windows Vista)

DirectX Direct3D version required is unavailable

DirectX 9.0c is not installed on the test system. Install DirectX 9.0c.

Direct3D hardware accelerator function Unavailable

Direct3D hardware acceleration is not enabled on the test system. By default, most servers (eg. all Windows 2003 servers) have Direct3D hardware acceleration disabled. Direct3D hardware acceleration can typically be enabled from: Control panel -> Display -> Settings -> Advanced -> Troubleshoot, and move the Hardware acceleration slider to the right (ie. to increase the level of graphics hardware acceleration). In some cases you will need to use the Graphics card manufacturers tool to enable Direct3D hardware acceleration.

Unable to create dialog for GUI test

Unable to create image list for GUI test

Failed Windows call - GUI treeview

Failed Windows call - GUI listbox

Failed Windows call - GUI listview

Failed Windows call - GUI progress bar

Failed Windows call - GUI sliders

Failed Windows call - GUI checkboxes

Failed Windows call - GUI shake test

There have been an error performing the standard 2D tests of performing common Window drawing functions. This could be a Windows operating system or graphics card problem.

Not enough packets sent to verify error ratio

During the Standard network test, if an error is detected, but there has been insufficient testing to reach a level of confidence as to whether the set packet sent:error ratio has been reached, then this error is raised instead of the ratio error.

Test control message error

There has been an error handling Advanced Network control messages, such as setting up new connections or the reporting of statistics from the Endpoint to BurnInTest.

No Endpoints. Check endpoint.exe & firewalls.

BurnInTest has been unable to find any instances of the Endpoint software that must be run on a remote system for the Advanced network test. This is commonly caused by either Endpoint.exe not being run on a remote system or a Firewall blocking UDP) access to the Endpoint on the remote system. Please check (at least) one Endpoint.exe is running on a remote system and that Firewalls are configured to allow (TCP and UDP) access to it.

Unable to connect to Endpoint. Check endpoint.exe.

BurnInTest has been unable to connect to the Endpoint software that must be run on a remote system for the Advanced network test. This is commonly caused by a Firewall blocking TCP access to the Endpoint on the remote system. Please check (at least) one Endpoint.exe is running on a remote system and that Firewalls are configured to allow (TCP and UDP) access to it.

Unable to load performance counters (check admin privileges)

The advanced network test uses system performance counters. This error is displayed if on test startup, the required performance counters can not be loaded. This can occur if running the Advanced network test without elevated administrator privileges on Windows Vista (and later).

Connection error

General Advanced network test error. This error is reporting through Windows Management Instrumentation. Further information will be displayed in the log, such as "Hardware disabled" and "Hardware not present".

Media disconnected

A network connection has been disconnected during the Advanced network test. This is the equivalent to the system seeing a network cable being unplugged.

Unable to bind to local NIC

During the startup of the Advanced Network test, BurnInTest has failed to allocate a port number on the IP address specified for test. This is typically a Network test error, but also may be caused by other software using (all) ports for that IP address.

Not ready to send data (timeout)

Not ready to receive data(timeout)

There has been a timeout when trying to send or receive test data during the Advanced Network test. This is a network error, but may be caused if the system is greatly overloaded.

The 3D test was interrupted

Typically this occurs if the user interrupts the 3D test by pressing escape when running the full screen 3D test. It is not a 3D error as such.

No operations in a memory test process

In the Multi-Process Torture Test, the number of memory test processes started was less than that configured in Preferences. This is normally due to insufficient system resources and is not specifically a RAM error. Check and possibly reduce the "Torture test settings" in Preferences->RAM.

Memory test failure. Faulty RAM likely.

There has been a low level software fault during the Advanced memory test. This normally occurs due to an attempt to write to faulty RAM.

Standard memory test failure. Faulty RAM likely.

There has been a low level software fault during the standard memory test. This normally occurs due to an attempt to write to faulty RAM.

Failed to start a memory test process

In the Multi-Process Torture Test, one of the test processes failed to start. This is normally due to insufficient system resources and is not specifically a RAM error. Check and possibly reduce the "Torture test settings" in Preferences->RAM.

A test process failed to allocate memory

In the Multi-Process Torture Test, one of the test processes specified failed to allocate RAM. This is normally due to insufficient system resources and is not specifically a RAM error. Check and possibly reduce the "Torture test settings" in Preferences->RAM.

No NIC detected

In the Standard Network test, when "Test all available Network Adapters" is selected, there were more Network Addresses specified for testing (in Preferences->Network) than BurnInTest could detect. Check that the number of Network address specified for testing matches the number of NIC's installed on the system. If this matches, then check your NICs all have IP addresses assigned to them, e.g. that the cable is plugged in and the device driver is loaded.

Unable to create CD/DVD test data

There has been a problem creating the test data files that are required for the CD or DVD burn test. Check disk space and access privileges.

Unable to initialize for CD/DVD burning

There has been a problem starting the CD or DVD burn test. This is typically due to a problem with the IMAPI2 functionality in Windows. The error log may provide additional information.

Unable to Burn CD/DVD

There has been a problem burning data to the CD or DVD burn test. The error log may provide additional information.

Unable to Erase CD/DVD

There has been a problem erasing data from the CD or DVD burn test. The error log may provide additional information.

IMAPI v2 not available

The CD and DVD burn tests require IMAPI2 to be installed on Windows. On Windows XP and Windows 2003 Server, this is available from Microsoft as a patch. Please see the test description for the CD / DVD test.

No media in drive

BurnInTest has attempted to erase the CD or DVD and has found that there is no CD or DVD in the drive under test. Please check that you have a re-writeable CD or DVD in the drive under test and that the test mode matches the media type (i.e. CD or DVD burn test).

Incorrect media in drive for test

BurnInTest has attempted to erase the CD or DVD and has found that the media is not re-writeable CD or DVD in the drive under test. Please check that you have a re-writeable CD or DVD in the drive under test and that the test mode matches the media type (i.e. CD or DVD burn test).

General instruction operation verification failed

The execution of a general instruction operation came up with the wrong result (e.g. 1 + 1 = 3). General instruction include: Integer mathematics (e.g. add, subtract, multiply and divide), Data transfer instructions (e.g. pushing/poping data to/from the stack), Bitwise logical instructions (e.g. bitwise and/or/xor), Shift and rotate instructions (e.g. shift data left x number of bits), Logical instructions (e.g. equals), Control transfer instructions (e.g. jump on x greater than y) and String instructions (eg. copy a text string).

This is a very serious error for a computer as it means the computer is incapable of execution the same sequence of instructions to get the same result. Possible reasons are faulty RAM, System bus, CPU or overheating. There is a strong chance that your computer will crash or lock up just after an error like this because if the computer can’t add two numbers correctly, there is a good chance that it can’t continue to run a program either.

FPU operation verification failed

The execution of a Floating Point Unit instruction operation came up with the wrong result (e.g. 1.1 + 1.1 = 3.3). FPU instructions include: Floating Point math (e.g. add, subtract, multiply and divide), Transcendentals (e.g. sin, cos) and Load constants (e.g. load Pi).

This is a very serious error for a computer as it means the computer is incapable of execution the same sequence of instructions to get the same result. Possible reasons are faulty RAM, System bus, CPU or overheating. There is a strong chance that your computer will crash or lock up just after an error like this because if the computer can’t add two numbers correctly, there is a good chance that it can’t continue to run a program either.

MMX operation verification failed

The execution of a MMX instruction operation came up with the wrong result. MMX (Multimedia Extensions) instructions include a sample of moving MMX registers, adding, subtracting, and multiplying MMX data.

This is a very serious error for a computer as it means the computer is incapable of execution the same sequence of instructions to get the same result. Possible reasons are faulty RAM, System bus, CPU or overheating.

SSE operation verification failed

The execution of a SSE(1) instruction operation came up with the wrong result. SSE (Streaming SIMD extensions) instructions include a sample of moving SSE(1) registers, adding, subtracting, and multiplying SSE data.

This is a very serious error for a computer as it means the computer is incapable of execution the same sequence of instructions to get the same result. Possible reasons are faulty RAM, System bus, CPU or overheating.

SSE2 operation verification failed

The execution of a SSE2 instruction operation came up with the wrong result. SSE2 (Streaming SIMD extensions) instructions include a sample of moving SSE2 registers, adding, subtracting, and multiplying SSE data.

This is a very serious error for a computer as it means the computer is incapable of execution the same sequence of instructions to get the same result. Possible reasons are faulty RAM, System bus, CPU or overheating.

SSE3 operation verification failed

The execution of a SSE3 instruction operation came up with the wrong result. SSE3 (Streaming SIMD extensions) instructions include a sample of moving SSE3 registers, adding, subtracting, and multiplying SSE data.

This is a very serious error for a computer as it means the computer is incapable of execution the same sequence of instructions to get the same result. Possible reasons are faulty RAM, System bus, CPU or overheating.

SSE4.1 operation verification failed

Not used. Reserved for future use.

SSE4.2 operation verification failed

Not used. Reserved for future use.

SSE4a operation verification failed

Not used. Reserved for future use.

Prime number operation verification failed

The execution of a prime number algorithm came up with the wrong result. This is a very serious error for a computer as it means the computer is incapable of execution the same sequence of instructions to get the same result. Possible reasons are faulty RAM, System bus, CPU or overheating.

No operations during test period

No operations have occurred for a particular test during the test period. This typically means that there has been some problem starting the test. Check that the test period is more than a few seconds to allow all the tests to start. Check the test configuration.

Parallel port test requires 64-bit version of BurnInTest

Testing Parallel ports on 64-bit Windows requires the 64-bit version of BurnInTest. Re-test using 64-bit BurnInTest.

The 2D memory test is incompatible with the 3D full screen test

The 2D memory test is not compatible with the 3D full screen test. Either select a windowed 3D test, or select the Lines and Bitmaps 2D test, or run the tests one after the other.

Drive contains partitions. The raw disk test will not run.

A physical disk (e.g. disk number 2) has been selected for testing with the raw disk test. The disk has been found to have partitions on it and hence the test will not run. This is a precaution to avoid destroying data on a disk with the raw disk test. Either, remove the partitions on the disk (only if you understand the implications of doing so) and re-test, or change the test configuration to remove this physcial disk from the test configuration. This error is not related to testing disk volumes, e.g. "C:" - testing a disk volume will not destroy disk data.

The physical drive does not exist on this system. Check settings.

A physical disk (e.g. disk number 2) has been selected for testing with the raw disk test. The disk has either not been found on the system, or the partition information could not be determined. This is a precaution to avoid destroying data on a disk with the raw disk test. Either, remove the partitions on the disk (only if you understand the implications of doing so) and re-test, or change the test configuration to remove this physical disk from the test configuration. This error is not related to testing disk volumes, e.g. "C:" - testing a disk volume will not destroy disk data.