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
  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
Fatal Error Solutions

The Windows Driver Framework has detected...

STOP: 0x0000010D


A device driver may have a bug.

Some older versions of Windows may show the description as "FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION".

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.

The Windows Driver Framework has detected that a violation has occurred.

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: 0x0000010D

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
  The Windows Driver Framework has detected that a violation has occurred. 

Stop Code


occurance meter
  Vista, 2008, 7, 8

  Microsoft Corporation
  Solutions and Fixes  
  Date Votes ratings
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

A violation was detected in the File system Run-time library (FsRtl) Extra Create Parameter (ECP) package.

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

Parameter 1, and in some cases Parameter 2 specify the cause of the issue.

Parameter 1 Parameter 2 Cause
0x00000001 Pointer A framework-based driver has timed out during a power operation. This typically means that the device stack did not set the DO_POWER_PAGABLE bit and a driver attempted a pageable operation after the paging device stack was powered down.
0x00000002 undefined An attempt is being made to acquire a lock that is currently being held.
0x00000003 handle Windows Driver Framework Verifier has encountered a fatal error. In particular, an I/O request was completed, but a framework request object cannot be deleted because there are outstanding references to the input buffer, the output buffer, or both.
0x00000004 undefined A NULL Parameter was passed to a function that required a non-NULL value.
0x00000005 handle A framework object handle of the incorrect type was passed to a framework object method.
0x00000006 0x00000001 No more I/O stack locations are available to format the underlying IRP.
0x00000006 0x00000002 An attempt was made to format a framework request object that did not contain an IRP.
0x00000006 0x00000003 The driver attempted to send a framework request that has already been sent to an I/O target.
0x00000006 0x00000004 The driver has completed a framework request, but has written more bytes to the output buffer than are specified in the IRP.
0x00000007 handle A driver attempted to delete a framework object incorrectly by calling WdfObjectDereference to delete a handle instead of calling WdfObjectDelete.
0x00000008 handle An operation occurred on a DMA transaction object while it was not in the correct state.
0x0000000A pointer A fatal error has occurred while processing a request that is currently in the queue.

0x0000000B 0x00000000 A handle passed to WdfObjectAcquireLock or WdfObjectReleaseLock represents an object that does not support synchronization locks.
0x0000000B 0x00000001 The spin lock is being released by a thread that did not acquire it.

Parameter 3 depends on the value of Parameter 1, and in some cases, Parameter2.

Parameter 4 is not defined.

  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.