spacer spacer spacer
 
 
application solutions
Applications
 
exception solutions
Exceptions & Crashes
  fatal BSoD errors Fatal BSoD Errors
  fatal startup Fatal Startup
 
internet solutions
Internet
 
Windows 8 solutions
Windows 8
 
Windows 7 solutions
Windows 7
 
vista solutions
Windows Vista
 
xp solutions
Windows XP
spacer
  annoyances Annoyances
 
index to publishers
Index to Publishers
 
file lookup
File lookup
  entertainment Entertainment
 
 
box_image
PC Mover
Move applications, files and settings from one PC to another. Handles Windows upgrades too, even XP 32-bit to Windows 7 64-bit!
 
  RadarSync
Ensures you have the latest drivers and software updates to make your PC run better and safer.
box_image  
Exception Solutions
     
 

View information and solutions for exceptions where Windows contineus to run. If Windows crashes with a BSoD message, see our Fatal BSoD solutions. There are four types of exceptions you may encounter:

hang
Hang - If a program locks up, typically in a loop it can't get out of it's considered a hang. The program must be terminated, and any unsaved work will be lost. Other running applications are not normally affected.
   
fatal
Fatal - The program performed some action it is not allowed to do, such as dividing by zero or accessing an area of memory it does not have permission to access. Usually these are fatal and the program must be closed, but other running programs are not normally affected.
   
error
Error - The program encountered a serious error, but it might be possible to continue depending on what the issue is. Some programs will handle issues from this category, but those that fail to handle the error will normally cause Windows to terminate the program.
   
warning
Warning - Some functions return a warning, such as a printer is out of paper. Programs should handle these exceptions, usually with a warning message. When the issue is corrected, the program can continue. Many warnings are handled invisibly to the user and will not produce any message.

There is a wide range of methods Windows and applications communicate exceptions. If the message includes an Exception Code, use that number to look up the issue. Often you will have to select a button or hotlink within the message to get the exception code. For example, in some Windows Vista/7 messages you have the option "View problem details" to expand the dialog and show the Exception code.

Use our Exception Decoder to understand what the various parts of any exception code means.

 
     
  Our Top Exception Issues  
     
  0xC0000005 - Access violation
Exception: Hang - Program has stopped working
0xC000000D - Invalid parameter
0x80000002 - Alignment fault exception
0xC00000DE - Invalid domain role
 
     
  (Based on frequency of occurrence, no warnings)  
   
  Lookup an Exception Code  
     
 
 
Enter a hex exception value in the style: C1234567 or 0xC1234567.
 
     
  List Exceptions by Type  
     
 

Select the type of exceptions to list.

 
     
  type buttons 000-03F 040-07F 080-0BF 0C0-0FF 100+  
     
 
Sort by: sort by (Currently sorted by name)
 
 

 
 
Selection 3
Page:  previous   1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16    next 

0xC0000150 - Serial no device initialized
0xC0000080 - Server disabled
0xC0000081 - Server not disabled
0xC00002A0 - Server Security Identifier mismatch
0xC00002FF - Server shutdown in progress
0xC0150025 - Settings Management Infrastructure primitive installer...
0xC000016C - Shared Interrupt Request busy
0xC0000299 - Shared policy
0xC00000CF - Sharing paused
0xC0000043 - Sharing violation
0xC00002FE - Shutdown in progress
0xC0150007 - Side-by-Side activation context disabled
0xC015001E - Side-by-Side assembly is not a deployment
0xC015000C - Side-by-Side assembly missing
0xC0150004 - Side-by-Side assembly not found
0xC0150002 - Side-by-Side can't generate activation context
0xC015001A - Side-by-Side component store corrupt
0xC0150014 - Side-by-Side corrupt activation stack
0xC0150015 - Side-by-Side corruption
0xC015000F - Side-by-Side early deactivation
0xC015001B - Side-by-Side file hash mismatch
0xC0150027 - Side-by-Side file hash missing
0xC015001F - Side-by-Side file not part of assembly
0xC015001D - Side-by-Side identities different
0xC0150018 - Side-by-Side identity duplicate attribute
0xC0150019 - Side-by-Side identity parse error
0xC0150003 - Side-by-Side invalid activation context data format
0xC0150010 - Side-by-Side invalid deactivation
0xC0150017 - Side-by-Side invalid identity attribute name
0xC0150016 - Side-by-Side invalid identity attribute value
0xC0150008 - Side-by-Side key not found
0xC0150005 - Side-by-Side manifest format error
0xC015001C - Side-by-Side manifest identity same but contents...
0xC0150006 - Side-by-Side manifest parse error
0xC0150022 - Side-by-Side manifest too big
0xC0150011 - Side-by-Side multiple deactivation
0xC015000E - Side-by-Side process default already set
0xC0150013 - Side-by-Side process termination requested
0xC0150001 - Side-by-Side section not found
0xC0150023 - Side-by-Side setting not registered
0xC0150012 - Side-by-Side system default activation context empty
0xC015000B - Side-by-Side thread queries disabled
0xC0150024 - Side-by-Side transaction closure incomplete
0xC0150009 - Side-by-Side version conflict
0xC015000A - Side-by-Side wrong section type
0xC0000381 - Smart card card blocked
0xC0000382 - Smart card card not authenticated
0xC000038D - Smart card certificate expired
0xC0000389 - Smart card certificate revoked
0xC0000387 - Smart card I/O error
0xC00002FA - Smart card logon required
0xC0000383 - Smart card no card
0xC0000385 - Smart card no certificate
0xC0000384 - Smart card no key container
0xC0000386 - Smart card no keyset
0xC000038F - Smart card silent context
0xC0000321 - Smart card subsystem failure
0xC0000380 - Smart card wrong personal identification number
0xC0000283 - Source element empty
0xC0190049 - Sparse not allowed in transaction
0xC0000124 - Special account
0xC0000125 - Special group
0xC0000126 - Special user
0xC0000409 - Stack buffer overrun
0xC00000FD - Stack overflow
0xC0000228 - Stack overflow read
0xC0000016 - Still busy
0xC0190022 - Stream miniversion not found
0xC0190023 - Stream miniversion not valid
0xC00002F6 - Strong cryptography not supported
0xC000004A - Suspend count exceeded
0xC0000715 - Symbolic link class disabled
0xC0000134 - Synchronization required
0xC0000452 - System device not found
0xC000036E - System hive too large
0xC00002EB - System shutdown
0xC00002C2 - System standby failed
0xC00A0039 - Target session incompatible sessions
0xC000014C - The registry is corrupt
0xC0000502 - Thread already in task
0xC000004B - Thread is terminating
0xC000012A - Thread not in process
0xC000070E - Thread pool free library on completion failed
0xC000070A - Thread pool handle exception
0xC000070D - Thread pool release mutex on completion failed
0xC000070C - Thread pool release semaphore on completion failed
0xC000070F - Thread pool released during operation
0xC000070B - Thread pool set event on completion failed
0xC0000133 - Time difference at domain controller
0xC000000C - Timer not canceled
0xC0000245 - Timer resolution not set
0xC000012B - Token already in use
0xC0000189 - Too late
0xC0000209 - Too many addresses
0xC00000C1 - Too many commands
0xC000015A - Too many context IDs
0xC0000082 - Too many Globally Unique Identifiers requested
0xC0000265 - Too many links
0xC0000074 - Too many local user identifiers requested
0xC00000CD - Too many names