Site and content now available for sale - $1950 Contact Us
Includes 80,000+ pages content, Windows app, database, admin, graphics, and more.
spacer spacer spacer
application solutions
exception solutions
Exceptions & Crashes
  fatal BSoD errors Fatal BSoD Errors
  fatal startup Fatal Startup
internet solutions
Windows 8 solutions
Windows 8
Windows 7 solutions
Windows 7
vista solutions
Windows Vista
xp solutions
Windows XP
  annoyances Annoyances
index to publishers
Index to Publishers
file lookup
File lookup
  entertainment Entertainment
Solutions Help

Exception Solutions Help

This guide will help you understand and find solutions for Windows exception problems. While directly covering Windows 7, Vista, XP and Server 2008, these also often apply to Server 2003, Home Server and other "NT" type platforms.

Key topic include:

  What Key Sections Mean  

Description - The first line is the standard Windows description. We've also added acronyms expansions - just hover over any acronym text that appears in medium blue. We use italics to show fields that will be filled in by Windows such as filenames or values.

We often add an additional text to help explain the issue.

Sample Screen - We show a typical screen shot for this specific error. Your error may look slightly different depending on your system, but it should be quite similar.

Key Facts - The basics of the error appear here. In addition, our occurrence meter (on the left) gives a rough idea of how frequent this issue occurs relative to other Fatal startup issues. Keep in mind that Fatal startup issues are rare, with some users never seeing one.

Solutions and Fixes - Here we explain how you can correct the issue. Most solutions include the Solution Analyzer to show how we rate each solution. You can also see how others rate this issue and you can include your rating.

Forum Help
- Look here to view or add your own comments and solutions. The link goes directly to a thread on this issue, so you don't have to hunt around.

Technical Details - For some messages we've added technical details for developers. While sometimes helpful to anyone, keep in mind these often reference terminology for a knowledgeable software developer.

Vendor Summary- When available, it includes basic contact information for the vendor. Click on the "More Info..." link for expanded information on this vendor. Often the vendor is Microsoft as the reporting vendor, but the issue cited may be from another vendor.

Research This Issue - We've built an immediate search for this specific issue. For this section, you can select different tabs to check results for the entire web, or narrow your search to just Microsoft's site. You can also search Blogs, which may have a different view on the issue.

  Solving the Issue  

Some Issues may require additional research to help find the right solution. Here are a few tips to getting your successful solution:

  1. Forums - Check our forum (via the link on the solutions page) to see if others have left comments or solutions for this specific issue.

  2. Search the web - The web is often an excellent source of ideas and solutions. We've built a quick list using the text from the error message. You can further refine the search if you're not getting the answers you seek. Also try the different search tabs, as the answer may be in a different area of the web.

  3. Visit the Vendor - Use our vendor links to see if the vendor has something on this issue. They may have forums, FAQs and other information. You can also check if you are using the current version of the software, as the current version may already fix the issue.

  4. Vendor Support - The Vendor may offer phone, email or web support. We put this last as you can often find the solution faster using one of the first 3 solutions. Most vendors try to respond quickly, but you might not have an answer for a few days. Also you may find you get better results from the vendor, once you've done a small amount of research ahead of time. You may be able to better explain the issue and/or indicate items you have ruled out.

  5. Third Party Support - If you are working at a company, perhaps they have a help desk or designated individual who can help. You may also have a knowledgeable friend who can assist you. Lastly, there are companies that specialize (for a fee) in providing support on a number of issues. Use the web to locate a company that provides these services.
  Problem Event Name types  

There are several types of Problem Events: Application Crashes, Hangs, Brach Execution issues and CLR20r3.

APP CRASH - These exceptions occur when Windows detects a serious fatal issue that the application does not handle. It covers a wide array of issues except for hangs, and brach execution issues. The wording will vary as APPCRASH or APP CRASH.

HANG - This indicates the program is unresponsive or very slow. Some seemingly hang events are not hangs at all, but the program performing some time-consuming task that does not check input until completed. Common wording includes AppHangB1, AppHangB2 and AppHangXProcB1.

BEX - The program execution attempted to jump into nonexistent or protected memory. For example, if a program is running and attempted to jump directly into the operating system kernel (which is not allowed for security reasons), Window would issue a fatal BEX exception. It can be caused by a bug or memory corruption. A 64-bit program will show BEX64.

CLR20r3 - This code indicates a program hung because of incompatibility with the currently installed .net system and/or a serious bug within the program itself.  The .net system is required for a .net program to run. The .net system currently requires a number of versions overlayed on top of older versions, that can causes a program that relies on an older version of .net to crash when newer .net versions have been installed. Since .net is used with a number of other programs, it is unwise to uninstall the newer .net versions. You will need an updated version of the failed program.

  How We Developed Solutions  

Our team of IT professionals and software developers have many years of real-world experience in volume corporate and academic situations as well as personal installations. Our team used this experience and our analysis of computers to explain the best solutions for each fatal issue, rate solution risks and efforts, and to then order solutions that make the most sense by using a combination of likeliness to solve an issue with the least risk.