Boot Error– "Unexpected Interrupt In Protected Mode"
If you turn on your computer and Windows fails to load to your Desktop, but instead displays the following error message, Unexpected Interrupt In Protected Mode, there are a couple of things that might be happening. Here are some troubleshooting steps which you can try to get your machine up and running again.
First, try rebooting your machine. If that doesn’t “cure” it, keep reading.
Causes: causes for this particular error message may be hardware-related: a failed or failing motherboard, or failing (or over-heating) CPU, or it may be related to a corrupted BIOS. Since the hardware issues most likely will require replacement parts and/or a trip to the shop, lets first tackle the BIOS possibility.
What is a “BIOS”? Your computer’s BIOS is a very basic set of instructions that tells your machine where to look for a keyboard and mouse and an operating system. It runs when your machine is first powered on. To make changes in the BIOS, you’re going to interrupt the boot process before Windows loads, so you need to use a keyboard that is plugged into the PS/2 port on the back of the machine, and not a wireless one.
1) Reboot your machine, and get ready to act quickly. Very early you will see a little bit of text that says, “hit F2* to enter setup.” (*Different manufacturers use different keys– F2 is the most common, but it may be the Esc key, Del, or F10. Refer to your computer builder’s website if you cannot determine which key to press.) Rapidly hit the suggested key several times, and enter “Setup” — this is your BIOS control panel.
2) Look to the bottom of the screen for Setup’s menu choices. Now look for the Function Key choice that will reset the BIOS to its default configuration. This is frequently the F5 key, but it may be F6.. In the screenshot above, look to the lower right: for this BIOS, it is F5 we want. “Setup Defaults”.
3) Save and Exit the Setup utility, and reboot. (In the sample BIOS, that’s the F10 key. But you may have to hit Esc, an then answer “Yes” to the Save? question. It varies.)
If resetting the BIOS to its defaults does not restore Windows functionality, I recommend you take your machine in to a qualified tech who can determine the hardware issues.
If it did restore it, you want to ask yourself what caused the BIOS corruption? Usually the answer is a recently installed program, or malware– be sure to run an antivirus scan.
Today’s free link: DriverScanner from Uniblue. Scan, backup, and Update your PC’s drivers. Folks– I have only just now used this new tool. I learned of it from Bill Mullins, who is as reliable a source as I have ever run across. To read his review, click here. This is a 30-day free trial, which normally would disqualify it from being posted here, but I am impressed enough to make this one-time exception.
Copyright 2007-8 © Tech Paul. All rights reserved. post to jaanix
Share this post : | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Troubleshooting the Blue Screen Of Death
BSOD’s, spontaneous reboots, freezing, and “incorrect password” lockouts. Bad computer. Bad.
Ah yes, the Blue Screen of Death. I sincerely hope you never see this rascal. The BSOD, or more properly, the Windows Stop Message, occurs when Windows detects a problem from which it cannot recover. The operating system halts and ‘diagnostic information’ is displayed on a blue screen as a series of hexadecimal numbers (there actually are a few humans capable of understanding, and using this information to effect repairs…but as far as I know, they all live in Seattle) which, frankly, will be of little use to the average user. Usually, a simple reboot resolves the issue. But sometimes it doesn’t–you reboot, Windows loads, you get the Welcome screen, and bingo! BSOD. Wash/rinse/repeat. Aargh!!!
If this happens to you, the odds are pretty good that you have (quite recently) added a new device (or card) or memory module to your machine, or installed a program that your machine just doesn’t like.
If it was a module, device, or card, try removing it and restoring your machine to the way it was before the install. If you run for a day or so with no BSOD’s, then you can be fairly sure you’ve found the culprit. It may be that the device is defective. It may be that you didn’t install it exactly correctly [maybe it didn’t “seat” all the way into its slot?], or maybe your machine was being fussy the day you installed? Don’t give up on your new card/device/module just yet. Go to the manufacturer’s Website and download the latest device driver for your version of Windows, and “unzip” and install it (by double-clicking on the downloaded file). Then reinstall your card/device/module–taking extra care to fully seat it, and double check your wires and cables–and reboot. If it is a defective unit, it will not be long before our friend the BSOD revisits…return the unit to the seller (or manufacturer) for exchange or refund.
If you suspect a recently installed application (or…Microsoft Update) is the cause, then use the Add/Remove Programs tool to uninstall it. (XP+older: Start> Control Panel> Add/Remove Programs, Vista: Start> Control Panel> Uninstall a program.) [Note: in Vista, uninstalling Updates is done through Windows Update itself, not Add/Remove.]
If you are unable to get into Windows, reboot and start hitting the F8 key to get into Safe Mode. [For more info, click here] Again, run for a day or two, and if you do not experience any BSOD’s, you’ve (most likely) found the perp. Again, you need not despair and abandon the program. It may have simply been an incomplete or corrupted install that was causing the stop errors. Try reinstalling it, but first make sure that there are no other applications running–turn off your AV, your IM, and close IE. You will soon know whether it is simply an incompatible or poorly written application.
I am going to stop here, but I want to acknowledge that this is far from a complete discussion on all the possible causes (nor cures) for BSOD’s and the other woes mentioned at the top of this post. I will return to this topic again, and I invite your comments and critiques, and suggestions. I close by suggesting you also read my article on the Windows System Restore tool (click here) and reminding you that — should all your efforts fail, my services are available at http://aplusca.com.
Today’s free link: Sandra Lite from SiSoft. This is a benchmarking and system analysis tool that shows you a wealth of information about the workings of your computer, and detects areas that aren’t working as well as they should.
Copyright 2007-8 © Tech Paul. All rights reserved. post to jaanix
Share this post : | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |