| |
|
 |
| |
|
|
| |
|
| |
Description |
|
| |
|
|
| |
The Plug and Play manager failed, likely due to a bug in the Plug and Play driver.
Some older versions of Windows may show the description as "PNP_DETECTED_FATAL_ERROR". 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.
Plug and Play detected an error most likely caused by a faulty driver. 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: 0x000000CA
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance. |
|
|
| |
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 |
|
Plug and Play detected an error most likely caused by a faulty driver.
|
Stop Code |
|
0x000000CA
|
Type |
|
Fatal
|
|
Windows |
|
2000, XP, Vista, 2008, 7, 8
|
Vendor |
|
Microsoft Corporation |
|
|
| |
|
|
| |
Solutions and Fixes |
|
| |
|
|
| |
|
Update Plug and Play Driver |
|
|
Update the Plug and Play driver with a version suitable for this version of Windows. |
| |
|
|
FaultWire Staff
Posted: 2-Sep-2009 |
|
|
|
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.
|
| |
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
Also see our list of common Fatal Error Solutions. |
|
| |
|
|
| |
Forum Help |
|
| |
|
|
| |
 |
Check out what others say about this issue and review or add your own comments and solutions!
Go to Forums on topic. |
|
|
| |
|
|
| |
Technical Details |
|
| |
|
|
| |
| |
 The Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver.
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 |
Duplicate PDO: A specific instance of a driver has enumerated multiple PDOs with identical device ID and unique IDs. |
| 0x00000002 |
Invalid PDO: An API which requires a PDO has been called with random memory, or with an FDO, or with a PDO which hasn't been initialized
(An uninitialized PDO is one that has not been returned to Plug and Play by QueryDeviceRelation or QueryBusRelations.)
|
| 0x00000003 |
Invalid ID: An enumerator has returned an ID which contains illegal characters or isn't properly terminated. (IDs must contain only characters in the ranges 0x20 - 0x2B and 0x2D - 0x7F.) |
| 0x00000004 |
Invalid enumeration of deleted PDO: An enumerator has returned a PDO which it had previously deleted using IoDeleteDevice. |
| 0x00000005 |
PDO freed while linked in devnode tree: The object manager reference count on a PDO dropped to zero while the devnode was still linked in the tree. (This usually indicates that the driver is not adding a reference when returning the PDO in a query IRP.) |
| 0x00000008 |
Null pointer returned as a bus relation: One or more of the devices present on the bus is a NULL PDO. |
| 0x00000009 |
Invalid connection type passed to IoDisconnectInterruptEx: A driver has passed an invalid connection type to IoDisconnectInterruptEx. The connection type passed to this routine must match the one returned by a corresponding successful call to IoConnectInterruptEx. |
| 0x0000000A |
Incorrect notify callback behavior: A driver failed to preserve IRQL or combined APC disable count across a Plug 'n' Play notification. |
| 0x0000000B |
Deleted PDO reported as relation: One of the removal relations for the device being removed has already been deleted. |
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 |
|
| |
|
|
| |
|
|
| |
|
|
| |
|
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...
|
|
| |
|
|
| |
Notes |
|
| |
|
|
| |
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. |
|
| |
|
|
|
|
 |
 |
 |
| | |
|
|
