Pc-Check Windows Monitor Mesh Test Failure Information

Group Number 350X

Device Monitor

This is a test group for Monitors (LCD and CRT). This test group provides testing of the display monitor connected to the primary video adapter. All of the monitor tests use the Windows® API and do not require additional software libraries such as DirectX®.

Each of the monitor tests display a pattern used to check a particular feature of the monitor. All of the tests require the operator to interactively verify proper operation. The tests may be run using all screen resolutions and colour depths. Each test relies on user input, the actual duration is indeterminate. However, it should normally take no longer than 2-5 seconds for a user to determine whether the display is correct or not.

Before each test starts, a dialogue box is displayed indicating which test will run. It also contains text indicating how to start the test and how to indicate whether the test ran correctly. This box will be displayed once any key is pressed while the test pattern is shown. Once a key has been pressed a dialogue box appears asking whether the test was displayed correctly.

Test Number 304

Mesh

The display is completely filled with an alternating one-zero mesh pattern. Any 'splotches' of black or white indicate a DAC problem, phosphor bleeding, or LCD panel elements that are stuck off or on.

Estimated Test Time 3s

PARAM1: Display Initial Test Message

Specifies whether or not to display a test dialogue box before the test runs.

ERRORCODES & TROUBLESHOOTING

The operator has chosen to fail the device based on the appearance of the test." CODE="0x00/3FF"

TROUBLESHOOTING0: The operator has failed the test. Because this is an interactive only test, the operator should supply additional information to the reasons for the test failure.

A function failed at the Windows® API level." CODE="0x01/001"

TROUBLESHOOTING1: The test failed due to a Windows® API failure. Check that your graphics drivers are up to date.

A resource failure occurred." CODE="0x02/3FF"

TROUBLESHOOTING1: The test failed due to a Windows® API failure. Check that your graphics drivers are up to date.

The operator has not responded in a reasonable time." CODE="0x03/3FF"

TROUBLESHOOTING0: The operator has failed the test. Because this is an interactive only test, the operator should supply additional information to the reasons for the test failure.

An incorrect number of monitors were detected." CODE="0x04/002"

TROUBLESHOOTING2: The expected number of monitors were not detected, or a failure occurred enumerating monitors. Check to ensure all monitors are connected and powered, and that video adapter drivers are up to date.

TROUBLESHOOTING3: Test script or parameter error. Please check your test settings.

No monitors were detected." CODE="0x05/3FF"

TROUBLESHOOTING2: The expected number of monitors were not detected, or a failure occurred enumerating monitors. Check to ensure all monitors are connected and powered, and that video adapter drivers are up to date.

The test can not be run on this device. Count tests must be run on the system device and pixel tests must be run on monitor devices." CODE="0x06/3FF"

TROUBLESHOOTING3: Test script or parameter error. Please check your test settings.

The EDID Checksum was incorrect." CODE="0x07/3FF"

TROUBLESHOOTING4: There was an issue with the monitor hardware or interface. Check the manual or firmware.

The operator was unable to prove that the monitor is working." CODE="0x08/3FF"

TROUBLESHOOTING0: The operator has failed the test. Because this is an interactive only test, the operator should supply additional information to the reasons for the test failure.

Unable to find monitor source due to mirrored monitor or other error." CODE="0x09/3FF"

TROUBLESHOOTING2: The expected number of monitors were not detected, or a failure occurred enumerating monitors. Check to ensure all monitors are connected and powered, and that video adapter drivers are up to date.

Failed to set monitor brightness" CODE="0x0A/3FF"

TROUBLESHOOTING4: There was an issue with the monitor hardware or interface. Check the manual or firmware.