; Troubleshooting | The Digital Blog : TECHNICALATHMA - Part 2

Beep Error Codes

Standard Original IBM POST Error Codes

Code Description
1 short beep System is OK
2 short beeps POST Error – error code shown on screen No beep
Power supply or system board problem Continuous beep Power supply, system board,
or keyboard problem Repeating short beeps Power supply or system board problem
1 long, 1 short beep System board problem
1 long, 2 short beeps Display adapter problem (MDA, CGA)
1 long, 3 short beeps Display adapter problem (EGA)
3 long beeps 3270 keyboard card

IBM POST Diagnostic Code Descriptions

Code Description

100 – 199 System Board
200 – 299 Memory
300 – 399 Keyboard
400 – 499 Monochrome Display
500 – 599 Colour/Graphics Display
600 – 699 Floppy-disk drive and/or Adapter
700 – 799 Math Coprocessor
900 – 999 Parallel Printer Port
1000 – 1099 Alternate Printer Adapter
1100 – 1299 Asynchronous Communication Device, Adapter, or Port
1300 – 1399 Game Port
1400 – 1499 Colour/Graphics Printer
1500 – 1599 Synchronous Communication Device, Adapter, or Port
1700 – 1799 Hard Drive and/or Adapter
1800 – 1899 Expansion Unit (XT)
2000 – 2199 Bisynchronous Communication Adapter
2400 – 2599 EGA system-board Video (MCA)
3000 – 3199 LAN Adapter
4800 – 4999 Internal Modem
7000 – 7099 Phoenix BIOS Chips
7300 – 7399 3.5″ Disk Drive
8900 – 8999 MIDI Adapter
11200 – 11299 SCSI Adapter
21000 – 21099 SCSI Fixed Disk and Controller
21500 – 21599 SCSI CD-ROM System

Share

Beep Code Manual

Beep Code Manual, based on Megatrends Int. & Phoenix

BIOS Beep Codes

When a computer is first turned on, or rebooted, its BIOS performs a power-on self test (POST) to test the system’s hardware, checking to make sure that all of the system’s hardware components are working properly. Under normal circumstances, the POST will display an error message; however, if the BIOS detects an error before it can access the video card, or if there is a problem with the video card, it will produce a series of beeps, and the pattern of the beeps indicates what kind of problem the BIOS has detected.
Because there are many brands of BIOS, there are no standard beep codes for every BIOS.

The two most-used brands are AMI (American Megatrends International) and Phoenix.

Below are listed the beep codes for AMI systems, and here are the beep codes for Phoenix systems.

AMI Beep Codes

Beep Code Meaning
1 beep DRAM refresh failure. There is a problem in the system memory or the motherboard.
2 beeps Memory parity error. The parity circuit is not working properly.
3 beeps Base 64K RAM failure. There is a problem with the first 64K of system memory.
4 beeps System timer not operational.
There is problem with the timer(s) that control functions on the motherboard.
5 beeps Processor failure. The system CPU has failed.
6 beeps Gate A20/keyboard controller failure.
The keyboard IC controller has failed, preventing gate A20 from switching
the processor to protect mode.
7 beeps Virtual mode exception error.
8 beeps Video memory error.
The BIOS cannot write to the frame buffer memory on the video card.
9 beeps ROM checksum error. The BIOS ROM chip on the motherboard is likely faulty.
10 beeps CMOS checksum error.
Something on the motherboard is causing an error when trying to interact with the CMOS.
11 beeps Bad cache memory. An error in the level 2 cache memory.
1 long beep, 2 short Failure in the video system.
1 long beep, 3 short A failure has been detected in memory above 64K.
1 long beep, 8 short Display test failure.

Continuous beeping A problem with the memory or video.

Phoenix Beep Codes

Phoenix uses sequences of beeps to indicate problems. The “-” between each number below indicates a pause between each beep sequence. For example, 1-2-3 indicates one beep, followed by a pause and two beeps, followed by a pause and three beeps. Phoenix version before 4.x use 3-beep codes, while Phoenix versions starting with 4.x use 4-beep codes. Click here for AMI BIOS beep codes.

Beep Code Meaning

1-1-1-3 Faulty CPU/motherboard. Verify real mode.
1-1-2-1 Faulty CPU/motherboard.
1-1-2-3 Faulty motherboard or one of its components.
1-1-3-1 Faulty motherboard or one of its components. Initialize chipset registers
with initial POST values.
1-1-3-2 Faulty motherboard or one of its components.
1-1-3-3 Faulty motherboard or one of its components. Initialize CPU registers.
1-1-3-2
1-1-3-3
1-1-3-4 Failure in the first 64K of memory.
1-1-4-1 Level 2 cache error.
1-1-4-3 I/O port error.
1-2-1-1 Power management error.
1-2-1-2
1-2-1-3 Faulty motherboard or one of its components.
1-2-2-1 Keyboard controller failure.
1-2-2-3 BIOS ROM error.
1-2-3-1 System timer error.
1-2-3-3 DMA error.
1-2-4-1 IRQ controller error.
1-3-1-1 DRAM refresh error.
1-3-1-3 A20 gate failure.
1-3-2-1 Faulty motherboard or one of its components.
1-3-3-1 Extended memory error.
1-3-3-3
1-3-4-1
1-3-4-3 Error in first 1MB of system memory.
1-4-1-3
1-4-2-4 CPU error.
1-4-3-1
2-1-4-1 BIOS ROM shadow error.
1-4-3-2
1-4-3-3 Level 2 cache error.
1-4-4-1
1-4-4-2
2-1-1-1 Faulty motherboard or one of its components.
2-1-1-3
2-1-2-1 IRQ failure.
2-1-2-3 BIOS ROM error.
2-1-2-4
2-1-3-2 I/O port failure.
2-1-3-1
2-1-3-3 Video system failure.
2-1-1-3
2-1-2-1 IRQ failure.
2-1-2-3 BIOS ROM error.
2-1-2-4 I/O port failure.
2-1-4-3
2-2-1-1 Video card failure.
2-2-1-3
2-2-2-1
2-2-2-3 Keyboard controller failure.
2-2-3-1 IRQ error.
2-2-4-1 Error in first 1MB of system memory.
2-3-1-1
2-3-3-3 Extended memory failure.
2-3-2-1 Faulty motherboard or one of its components.
2-3-2-3

Share

Steps To Speed Up Windows Xp in 23 Ways

Since defragging the disk won’t do much to improve Windows XP performance, here are 23 suggestions will. Each can enhance the performance and reliability of your customers’ PCs. Best of all, most of them will cost you nothing.

  • To decrease a system’s boot time and increase system performance, use the money you save by not buying defragmentation software — the built-in Windows defragmenter works just fine — and instead equip the computer with an Ultra-133 or Serial ATA hard drive with 8-MB cache buffer.
  • If a PC has less than 512 MB of RAM, add more memory. This is a relatively inexpensive and easy upgrade that can dramatically improve system performance.
  • Ensure that Windows XP is utilizing the NTFS file system. If you’re not sure, here’s how to check: First, double-click the My Computer icon, right-click on the C: Drive, then select Properties. Next, examine the File System type; if it says FAT32, then back-up any important data. Next, click Start, click Run, type CMD, and then click OK. At the prompt, type CONVERT C: /FS:NTFS and press the Enter key. This process may take a while; it’s important that the computer be uninterrupted and virus-free. The file system used by the bootable drive will be either FAT32 or NTFS. I highly recommend NTFS for its superior security, reliability, and efficiency with larger disk drives.
  • Disable file indexing. The indexing service extracts information from documents and other files on the hard drive and creates a “searchable keyword index.” As you can imagine, this process can be quite taxing on any system.
  • Update the PC’s video and motherboard chipset drivers. Also, update and configure the BIOS.
  • Empty the Windows Prefetch folder every three months or so. Windows XP can “prefetch” portions of data and applications that are used frequently. This makes processes appear to load faster when called upon by the user. That’s fine. But over time, the prefetch folder may become overloaded with references to files and applications no longer in use. When that happens, Windows XP is wasting time, and slowing system performance, by pre-loading them. Nothing critical is in this folder, and the entire contents are safe to delete.
  • Once a month, run a disk cleanup. Here’s how: Double-click the My Computer icon. Then right-click on the C: drive and select Properties. Click the Disk Cleanup button — it’s just to the right of the Capacity pie graph — and delete all temporary files.
  • In your Device Manager, double-click on the IDE ATA/ATAPI Controllers device, and ensure that DMA is enabled for each drive you have connected to the Primary and Secondary controller. Do this by double-clicking on Primary IDE Channel. Then click the Advanced Settings tab. Ensure the Transfer Mode is set to “DMA if available” for both Device 0 and Device 1. Then repeat this process with the Secondary IDE Channel.
  • Upgrade the cabling. As hard-drive technology improves, the cabling requirements to achieve these performance boosts have become more stringent. Be sure to use 80-wire Ultra-133 cables on all of your IDE devices with the connectors properly assigned to the matching Master/Slave/Motherboard sockets. A single device must be at the end of the cable; connecting a single drive to the middle connector on a ribbon cable will cause signaling problems. With Ultra DMA hard drives, these signaling problems will prevent the drive from performing at its maximum potential. Also, because these cables inherently support “cable select,” the location of each drive on the cable is important. For these reasons, the cable is designed so drive positioning is explicitly clear.
  • Remove all spyware from the computer. Use free programs such as Ad Aware by Lavasoft or SpyBot Search & Destroy. Once these programs are installed, be sure to check for and download any updates before starting your search. Anything either program finds can be safely removed. Any free software that requires spyware to run will no longer function once the spyware portion has been removed; if your customer really wants the program even though it contains spyware, simply reinstall it. For more information on removing Spyware visit this Web Pro News page.
  • Remove any unnecessary or unused programs from the Add/Remove Programs section of the Control Panel.
  • Turn off any and all unnecessary animations, and disable active desktop. In fact, for optimal performance, turn off all animations. Windows XP offers many different settings in this area. Here’s how to do it: First click on the System icon in the Control Panel. Next, click on the Advanced tab. Select the Settings button located under Performance. Feel free to play around with the options offered here, as nothing you can change will alter the reliability of the computer — only its responsiveness.
  • If your customer is an advanced user who is comfortable editing their registry, try some of the performance registry tweaks offered at Tweak XP.
  • Visit Microsoft’s Windows update site regularly, and download all updates labeled Critical. Download any optional updates at your discretion.
  • Update the customer’s anti-virus software on a weekly, even daily, basis. Make sure they have only one anti-virus software package installed. Mixing anti-virus software is a sure way to spell disaster for performance and reliability.
  • Make sure the customer has fewer than 500 type fonts installed on their computer. The more fonts they have, the slower the system will become. While Windows XP handles fonts much more efficiently than did the previous versions of Windows, too many fonts — that is, anything over 500 — will noticeably tax the system.
  • Do not partition the hard drive. Windows XP’s NTFS file system runs more efficiently on one large partition. The data is no safer on a separate partition, and a reformat is never necessary to reinstall an operating system. The same excuses people offer for using partitions apply to using a folder instead. For example, instead of putting all your data on the D: drive, put it in a folder called “D drive.” You’ll achieve the same organizational benefits that a separate partition offers, but without the degradation in system performance. Also, your free space won’t be limited by the size of the partition; instead, it will be limited by the size of the entire hard drive. This means you won’t need to resize any partitions, ever. That task can be time-consuming and also can result in lost data.
  • Check the system’s RAM to ensure it is operating properly. I recommend using a free program called MemTest86. The download will make a bootable CD or diskette (your choice), which will run 10 extensive tests on the PC’s memory automatically after you boot to the disk you created. Allow all tests to run until at least three passes of the 10 tests are completed. If the program encounters any errors, turn off and unplug the computer, remove a stick of memory (assuming you have more than one), and run the test again. Remember, bad memory cannot be repaired, but only replaced.
  • Disable unnecessary services. Windows XP loads a lot of services that your customer most likely does not need.
  • If you’re sick of a single Windows Explorer window crashing and then taking the rest of your OS down with it, then follow this tip: open My Computer, click on Tools, then Folder Options. Now click on the View tab. Scroll down to “Launch folder windows in a separate process,” and enable this option. You’ll have to reboot your machine for this option to take effect.
  • At least once a year, open the computer’s cases and blow out all the dust and debris. While you’re in there, check that all the fans are turning properly. Also inspect the motherboard capacitors for bulging or leaks.

Share

Steps To Repair Winsock

Run Regedit
Delete the following two registry keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

Restart the computer
Go to Network Connections
Right click and select Properties
Click on the Install button
Select Protocol
Click on the Add button
Click on the Have Disk button
Browse to the \Windows\inf directory
Click on the Open button
Click on the OK button
Highlight Internet Protocol (TCP/IP)
Click on the OK button
Reboot

Share

Steps to Test Winsock 2

The symptoms when Winsock2 is damaged show when you try to release and renew the IP address using IPCONFIG…

And you get the following error message:

An error occurred while renewing interface ‘Internet’: An operation was attempted on something that is not a socket.

Also Internet Explorer may give the following error message:
The page cannot be displayed Additionally, you may have no IP address or no Automatic Private IP Addressing (APIPA) address, and you may be receiving IP packets but not sending them.

There are two easy ways to determine if Winsock2 is damaged:

From the XP source files, go to the Support / Tools directory

Winsock Test Method 1:

Run netdiag /test:winsock

The end should say Winsock test ….. passed

Winsock Test Method 2:

Run Msinfo32
Click on the + by Components
Click on the by Network
Click on Protocol
There should be 10 sections if the Winsock2 key is ok
MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
RSVP UDP Service Provider
RSVP TCP Service Provider
MSAFD NetBIOS [\Device\NetBT_Tcpip…
MSAFD NetBIOS [\Device\NetBT_Tcpip…
MSAFD NetBIOS [\Device\NetBT_Tcpip…
MSAFD NetBIOS [\Device\NetBT_Tcpip…
MSAFD NetBIOS [\Device\NetBT_Tcpip…
MSAFD NetBIOS [\Device\NetBT_Tcpip…

If the names are anything different from those in this list, then likely Winsock2 is corrupted and needs to be repaired.
If you have any 3rd party software installed, the name MSAFD may be changed.
There should be no fewer than 10 sections.

Share




These contents are copyrighted to Y5MEDIA and cannot be reproduced without Permission of the admin