Computer in reboot loop
-
Recently, I bought a new Canon imageCLASS MPC600F multifunction printer. When I installed the drivers, the computer didn’t boot properly. It works as normal until Windows starts, at which stage it automatically reboots and continues in this loop until I press the computer power button. The computer is running Windows XP Professional.
My original thoughts were that the drivers may not support Windows XP. This still may be the case, so your first point of call should be to download the newest drivers from the Canon website at www.canon.com.au/products/multifunctionals/multifunctional_colour_bubble_jet/imageclass%20mpc600f_drivers.html which definitely supports Windows XP. Unless this is contrary to the installation instructions provided with the printer, make sure the printer is not connected to the computer until after you have installed the drivers. But make sure that before you boot up the computer (with the drivers installed) the printer is physically connected, as it may not like having the drivers installed with no device. Another way to approach the driver installation is (with no current drivers on the computer) to turn off the computer, connect the printer and start. With luck, Windows should recognise the new device connected to the computer and ask you to install the drivers. At this stage, install the drivers and see how it goes from there. If this does not help, the problem may be caused by a conflict with another device or device drivers. This can get incredibly tricky to diagnose and fix, especially without knowledge of your computer’s configuration. Although this is not the most desirable solution, at this stage you may wish to consider backing up your valuable data and reinstall Windows. Once you have reinstalled Windows, try installing the Canon as one of your first devices. If it successfully installs and works, continue to install your additional devices until either: all the devices are installed (most likely), or the problem resurfaces. By doing this, you should be able to track down the conflicting application.