spacer spacer spacer
  arrow Description
  arrow Sample Screen
  arrow Key Facts
  arrow Solutions
  arrow Forum Help
  arrow Technical Details
  arrow Vendor Summary
  arrow Research this Issue
  help Solutions Help
  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!
Ensures you have the latest drivers and software updates to make your PC run better and safer.
  Partition Commander
Now it's easy for anyone to safely partition their hard drive! You can reclaim waste disk space, organize files, even add new OSes.
Fatal Error Solutions


STOP: 0x00000103


A network card has a problem or device driver has a bug.

This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.

  Sample Screen  

A problem has been detected and Windows has been shut down to prevent damage to your computer.


If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

Technical Information:

*** STOP: 0x00000103

Beginning dump of physical memory
Physical memory dump complete.

Contact your system administrator or technical support group for further

Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown.
  Key Facts  
Full Title

Stop Code


occurance meter
  Vista, 2008, 7, 8

  Microsoft Corporation
  Solutions and Fixes  
  Date Votes ratings
Replace Network Card
    Add    Flag
solution icon
Try replacing the network card as some card defects can cause the fault.
solves it indicator
risk indicator
effort indicator
  FaultWire Staff
Posted: 2-Sep-2009
Get the Latest Updates
    Add    Flag
solution icon

Install the latest Windows software updates. Don't forget to check for non-critical updates too!

To manually get updates, open Internet Explorer (you can't use a non-Microsoft browser for updates).

For IE 8 and later: Click on Safety, then Windows Update. Follow the instructions.


For IE 7 and older: Click on Tools, then Windows Update. Follow the instructions.

solves it indicator
risk indicator
effort indicator
  FaultWire Staff
Posted: 5-Oct-2008
Get the Latest Drivers
    Add    Flag
solution icon

Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSoD issues.

You can use a product like Driver Genius or Radar Sync to verify you have the latest drivers and help keep all your drivers up-to-date. If you're comfortable with driver installations, you can individually find and install current drivers.

A some of the most popular driver download sites:

solves it indicator
risk indicator
effort indicator
  FaultWire Staff
Posted: 5-Oct-2008

Also see our list of common Fatal Error Solutions.

  Forum Help  
Forums on topic

Check out what others say about this issue and review or add your own comments and solutions!

Go to Forums on topic.
  Technical Details  
  technical details

The multiple UNC provider (MUP) has encountered invalid or unexpected data. The MUP cannot channel a remote file system request to a network redirector, the Universal Naming Convention (UNC) provider.

After the Stop code will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.

Parameter 1 specifies the cause of the issue.

0x00000001 The MUP could not locate the file context that corresponds to a file object. This typically indicates that the MUP is seeing an I/O request for a file object for which MUP did not see a corresponding IRP_MJ_CREATE request. The likely cause of this bug check is a filter driver error.
0x00000002 A file context is known to exist for the file object, but was not what was expected (for example, it might be NULL).
0x00000003 The IRP completion status was unexpected or invalid. This bug check should only be caused by file system filter drivers that are attached to legacy network redirectors. Legacy redirectors used to register with MUP. This bug check detects filter drivers that return an NTSTATUS that is not STATUS_SUCCESS in IRP_MJ_CLEANUP or IRP_MJ_CLOSE requests.

Parameter 2 depends on the value of Parameter 1.

Parameter 3 depends on the value of Parameter 1.

Parameter 4 depends on the value of Parameter 1.

  Vendor Summary  
  Microsoft Corporation (more info...)

Microsoft Corporation Logo



    While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by non-Microsoft applications, drivers and hardware issues.  
  Research this Issue  
Getting search results...
  While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at so we can correct it.