System mechanic, dashboard displays unknown error

First you need to check to see if there is any information on the dashboard display. Are you getting any messages on the display? Are you getting any number sequences on the display? Are there any lights on the dashboard that don't go out when you start the engine?
Next you need to get access to a diagnostic system or a good quality OBD2 scanner. This will find any error codes to find what the problem could be. A Good Auto electrician will be able to help you with this.

31: DPD offset adjustment error .
Contact any service technician. You can't repair this. The error code list to this set:
The meaning of error code is as below:
01: Communication error (No reply from syscon)
02: Syscon hung up
03: Power OFF request when syscon hung up
19: Thermal shutdown
24: MoveSledHome error
25: Mechanical move error (5 Changer)
26: Mechanical move stack error
30: DC motor adjustment error
31: DPD offset adjustment error
32: TE balance adjustment error
33: TE sensor adjustment error
34: TE loop gain adjustment error
35: FE loop gain adjustment error
36: Bad jitter after adjustment
40: Focus NG
42: Focus layer jump NG
51: Spindle stop error
52: Open kick spindle error
60: Focus on error
61: Seek fail error
62: Read Q data/ID error
70: Lead in data read fail
71: TOC read time out (CD)
80: Can't buffering
81: Unknown media type
Are you confident to do anything with these error displays.
If you wish to get some details; check the site linked here. Pull up older posts.
http://electronicshelponline.blogspot.com/

This indicates that a problem exists in the control system of the 4WD system. This can be mechanical like a sticking clutch in the transfer case or electrical in nature. You need to have the dealer do special testing to determine what is the actual cause. If you have never changed the fluid in the transfer case do that and see if the light is mechanical in nature from dirty fluid and a sticky cone clutch

The first physically documented computer bug was documented by Dr. Grace Murray Hopper when she was programming the Mark II Calculator (computer). When the system was not functioning correctly after troubleshooting the system, she found a moth between contacts of a relay. After removing the moth the system functioned and the moth was taped in her notes documenting the bug.
A computer error is displayed when a known problem in the computer code (program) expects a result from the hardware (electronic circuit) or software, and it does not fall within the code parameters. In most cases the error can return information about why the computer had a problem.
Conclusion:
A bug is an unknown failure of the system which usually is intermittent and causes the system to crash or results in some type of failure. An error returns information about the system failure which is displayed or documented on the display or in log file.

You may receive one of the following stop error messages while working on your Windows XP computer.
STOP: C0000221 unknown hard error
Path\File_nameSTOP: 0xC0000221 unknown hard error
C:\Winnt\System32\Ntdll.dll (or another specific file or driver)
STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
Path\File_name
Note: The error message may be discussed in many different formats-blue screen or message box. It depends on when the corrupt file was detected.
Similarly, you may receive the following STOP messages when a critical system file fails to load on your Windows NT and Windows 2000 computer.
STOP: C0000221 unknown hard error
<path>\<file_name>STOP: 0xC0000221 unknown hard error
c:\winnt\system32\ntdll.dll
Note: Some other drive may also be given in the message.
On Windows 2000 the following error message may display:
STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
<path>\<file_name>
You usually face this problem when an incorrect driver for one or more hardware is installed on your system. For instance, the error messages described above are displayed when you install a millions of instructions per second (MIPS) driver on a x86 system.
Cause of the Error
This error occurs if the file given in the error message is damaged.
Your Windows XP operating system checks the following files for integrity during system startup:

• All driver files, excluding the files that loaded using the system loader to start your system .
• All DLL (Dynamic Link Libraries) on the system. These include, Graphics Driver Interface (GDI), User, Ntdll, Crtdll, Shell, Kernel and several other DLL files on the system.
• On Windows NT and 2000 computers, all DLLs loaded in the Window server address space are also checked.

The problem may also occur if an Iomega Zip drive is connected to the same cable as your hard disk drive.
Resolution Method
You can resolve this issue by removing the corrupt driver from your computer and then reinstalling a fresh and healthy copy of the driver. You may need to use the Device Manager utility to remove the driver. It is recommended that you clean your registry with the help of a reliable tool, such as RegGenie to ensure that all entries related to the uninstalled driver are removed from the system. After you have completely removed the corrupt driver, restart your system and install a fresh copy of the driver on the system.
If this step does not resolve the problem, you may have to reinstall Windows XP.
It is recommended that you regularly clean your registry with the help of a registry cleaner tool and perform antivirus and antispyware scan using tools, such as Antivirus Plus and StopZilla to prevent such errors from occurring on your system.

GOOD LUCK :-)

Do these errors appear at system start up?
Did you recently install any programs?
If you did, uninstall the program, that should solve the problem.
If you didn't install any program before the error messages, perform a system restore.

have someone stand behind ur car and check ur brake lights when u hit the brake and not ur tail lights when u turn all ur lights on. that warning light came on for me and i discovered a brake light out

low coolant

could be a virus/spyware/malware, also empty you temp and history files, then restart ur pc.