Thursday, 23 May 2013

Fault 14

I noticed that the computer is overheating and losing performance. The cause was a dusty fan that does not allow for proper cooling the CPU. It is a very common problem for many users and nobody really knows what cause lees performance of PC. The best way to clean it is to use compressed air or vacuum cleaner. Also make sure the fan is dry and does not contain any liquid which could cause many damage. Once fan is cleaned, it is ready to be run.

Friday, 17 May 2013

Fault 13

This fault occurred while loading the desktop. Fault says “Windows could not connect to printer”. As it comes out printer was not even added and that’s why this printer occurred. To add the printer, I go to Control Panel, Devices and Printers, right mouse click, Add a printer and choose between two. My printer is wireless so I have to search for it, once is founded, click Next and fault should no longer appeared.



Friday, 10 May 2013

Fault 12

When trying to install Windows XP in VirtualBox (Ubuntu 10.04 host) and was getting this exact error. I changed the VM settings from 512MB RAM to 768MB RAM, and now it is working.

Fault 11


This error has occurred while I was trying to run program Steam. This fault says that one or more steam application is currently running. As a remedy I had to open Task Manager I close it by right click and close. Once it has been done program could run without any problems.

Fault 10

This error occurred on my computer while I was trying to play game. To play the game program called “STEAM” needs to be installed to paly trough internet with other players. This fault was keep showing even after restarting PC and network card. The solution was to update the program and I have also set automatic update if any available to prevent any further errors. After update software work correctly and allow playing through network.


Fault 9

This error occured when i was trying to register my WinZip to fix it I had to follow these stepts:

1.Click on the Taskbar Start button. In the text box just above the Start button type: C:\ProgramData and press the Enter key on the keyboard.
2.Delete the WinZip folder
3.Open WinZip and enter your registration information

Fault 8

This fault was detected during startup and it was a fault in the form of sound. From motherdoard mined sounds at various time intervals and lengths, so each of syganol corresponds to some error. To check what fault it is, check what BIOS is installed on computer and base on it find for beep code comes with this particlar type. It was an AMI BIOS so I have faound a website with all beep code meaning, my beep code was 1 long and 2 short.

First thing I did was to check for RAM if they pluged correctly. As it comes out later RAM was not placed in a right place.


Fault 7

When booting the computer I came across this fault. Rundll32.exe error in Windows is usual occurs when a computer has been infected with malware or a virus. As a remedy I have fully scan computer with antivirus software and deleted all infected files and viruses.

Thursday, 2 May 2013

Fault 6

This fault has been found because the computer could not turn on. Cables in the front panel connector were confused and badly plugged. Earlier, someone already tried to connect all the cables correctly, but did not succeed. For a computer to be switched on all the cables must be connected correctly. When the front panel cables are connected and the computer is switched on, I noticed the hardware LED is not flashing so I decided to have a look again and find what May be the problem. As it turned out cable "LED" was connected to the reverse and that is why the LED does not flasing.

Fault 5



The fault appeared while playing on the PlayStation 3. Fault show that the cat5 cable is disconnected from the input. As it turned out clip responsible for holding the cable in right place was broken and thats why cable was keep fall out from cat5 ethernet socket. The solution will be to buy a new cat5 or fix it yourself if you have the proper tools.

Fault 4




This fault is known as the "blue screen error". This is because the system found a problem with the hardware or software that has been installed or connected so in order to avoid further complications or data lost computer restart it self. This is a remady of how to fix it.
  1. From the desktop right-click on My Computer.
  2. Click the Properties option.
  3. In the System Properties window click the Advanced tab.
  4. In Advanced click the Settings button under Startup and Recovery.
  5. In the Startup and Recovery window uncheck the Automatically restart check box.
  6. Click Ok.

Fault 3


This problem was encountered when logging on to the server. It could be because the wrong password or error in the administrative files. The solution will be logging in to the Administration server list, find the user and reset the password for "password". During the next login password will be avalible for change.