0x00000002 DEVICE_QUEUE_NOT_BUSY fix error

DEVICE_QUEUE_NOT_BUSY blue screen of death with code 0x00000002 is a rare error that indicates that the device queue was not busy due to software failures or a device malfunction. Often error 0x00000002 appears when the printer driver is damaged or if the key is not signed.

DEVICE \ _QUEUE \ _NOT \ _BUSY blue screen of death with code 0x00000002 is a rare error that indicates that the device queue was not busy due to software failures or a device malfunction. Often error 0x00000002 appears when the printer driver is damaged or if the key is not signed.

If a STOP 0x2 error occurs, the computer may enter a cyclic reboot. If, after the blue screen of death, Windows boots up, the user may see a message stating that "Windows was restored after an unexpected shutdown." In this case, you need to check the functionality of the connected printers and other devices, as well as update the driver.

Connecting a network printer through an IP or TCP port, as well as a print server, is a simple procedure that all office workers or users of multiple personal computers. However, in some cases, a blue screen of death appears with the message DEVICE \ _QUEUE \ _NOT \ _BUSY or error 0x00000002, indicating that the printer driver is not installed, not found or damaged.

Methods to resolve error 0x00000002 on Windows 7

On Windows 7, error 0x00000002, a printer driver is not installed rarely occurs, but its solution requires some effort. Therefore, if you cannot install the printer driver and error 0x00000002 occurs, you should use the following tips.

Method 1. Removing the printer and its drivers

  • Click "Start", "Control Panel" and select "Devices and Printers."

  • Now restart the print manager. To do this, open "Services", "Print Manager". Stop the service, and then restart it. Or, better yet, just restart.

Now you need to remove the printer driver. To do this, do the following:

  • Click "Start" and select "Run." Or immediately click “Win ​​+ R” and enter “printui / s / t2”.

  • A new window will open. Go to the tab “Driver”. We select the wrong driver and click "Delete".

  • Next, in the search bar, enter “printmanagement.msc” (without quotes).

  • The "Print Management" window appears. Find "Custom Filters", and then go to "All Drivers."

  • Remove the driver package that causes the crash.

  • Restart the computer and try to connect the network printer again.

Method 2. Installing a new driver

If you cannot install the printer driver and error 0x00000002 constantly interferes with causing BSoD, you should install the official driver from the device’s developer or download the “Universal Print Driver”. However, it is important to note that installing the universal driver from Microsoft may not solve the problem.

Methods 3. Cleaning the system and registry from old drivers

If error 0x00000002 occurs on an old build of Windows 7 and you previously uninstalled the failed driver, you should clean the registry and the system from older software. This can be done in the following way.

First, clear the Spool folder. However, given that it is constantly used by the Print Manager, it can only be deleted in safe mode.

Let the following be to the folder: C: \ Windows \ System32 \ Spool. In this folder we are interested in the following contents:

  • C: \ Windows \ System32 \ spool \ prtprocs \ w32x86 - delete everything, chrome e file winprint.dll .
  • C: \ Windows \ System32 \ Spool \ Printers - delete all data about installed printers
  • C: \ Windows \ System32 \ Spool \ Drivers \ w32x86 - we clean the directory from all the files that were previously installed (on x64 systems, the path is Drivers \ x64).

After cleaning the Spool folder, we reboot in normal mode and reinstall the drivers for the connected printer.

Now you need to clean the registry from old files that were created by the printer and its software. To do this, do the following:

  • Click “Win ​​+ R” and enter “regedit”.

  • We check the status of the components on which the Spooler service depends. To do this, go to the branch "HKEY \ _LOCAL \ _MACHINE \ SYSTEM \ CurrentControlSet \ Services \ Spooler". Here we look at the “DependOnService” parameter. The RPCSS value must be specified. Also, other values ​​may be indicated, they do not need to be deleted. The main thing is RPCSS.

  • Now we remove all printing devices that were installed in the system. Go to the branch "HKEY \ _LOCAL \ _MACHINE \ System \ CurrentControlSet \ Control \ Print \ Printers", where expanding it, the entire list of printers will appear. To delete them, we can use the “Delete” key.

  • We clean the registry from entries of old drivers. Expand the branch "HKEY \ _LOCAL \ _MACHINE \ System \ CurrentControlSet \ Control \ Print \ Environments \ WindowsNTx86 \ Drivers \ Version-3" (in x64 bit operating systems you need to open ... \ Environments \ Windows NTx64 \ Drivers \ Version-3). We remove the entire list of drivers installed in the system.

  • In the branch "HKEY \ _LOCAL \ _MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Print \ Monitors", the list of parameters should look like this.

  • BJ Language Monitor

  • Local Port

  • PJL Language Monitor

  • Standard TCP / IP Port

  • USB Monitor

We leave this list, and delete everything else.

We reboot the system, install new drivers and connect the printer.

If it was not possible to solve the problem, you should roll back the system to an earlier state, check Windows 7 for viruses and test the connected device on another PC. The printer may not be compatible with the OS or system assembly components.

Windows 10 is a fairly young operating system, and therefore many manufacturers of old equipment did not bother release compatible software for their products, including printers. Therefore, when trying to connect a network printer via a TCP / IP port or a print server, the error 0x00000002 may appear on the screen, indicating damage to the drivers or their absence.

Methods to fix error 0x00000002 on Windows 10

On Windows 10, an error connecting a printer with the code 0x00000002 occurs due to damage to the drivers, their incompatibility with the operating system, the complete absence or damage of the virus. However, there are ways to fix it.

First you need to try reinstalling the drivers, after removing the old ones. To do this, do the following:

  • Run the command line with Administrator rights and enter "printui.exe / s / t2".

  • A new window will open. Go to the "Drivers" tab. Select the failed software and click “Remove driver” and “driver package”.

  • Now we reboot the system.

Next, we recommend restarting the Print Manager. To do this, on the command line with Administrator privileges, enter “net stop spooler” (stopping the Manager), and then “net start spooler” (launching the Manager).

Now reconnect the printer. The driver may automatically install or you will have to use the installation disk with the official drivers or download them from the site.

If reinstalling the drivers does not solve the problem, you should clean the registry from old software. To do this, do the following:

  • Click “Win ​​+ R” and enter “regedit”.

  • Now delete the registry branch "HKEY \ _LOCAL \ _MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ PendingFileRenameOperations".

  • Reboot the system.

Now you need to clear the Spool folder. To do this, check if there are subdirectories with names from 1 to 499 in the c: \ Windows \ System32 \ spool \ prtprocs \ x64 folder, delete all these subdirectories and files except winprint.dll.

Now all printers and drivers from the branch "HKLM \ SYSTEM \ CurrentControlSet \ Control \ Print \ Environments" also need to be removed.

Reboot the computer.

We connect the printer and install the driver. The error should disappear. If the problem continues to appear, it is worth checking the PC for viruses, the relevance and compatibility of the installed equipment.

4 Recommendations for the Elimination of BSoD:

1. 0x00000002 DEVICE_QUEUE_NOT_BUSY may appear due to errors in the code of the operating system itself. Microsoft is constantly working to correct such errors, releasing patches and service packs. Installed the latest update package (Service pack) and the constant updating of the system will save a lot of errors.
2. If 0x00000002 DEVICE_QUEUE_NOT_BUSY appeared after the newly installed device driver or program. It is necessary to roll back the driver to an earlier version. With programs, things are easier, removing them will eliminate the cause of the failure. The “Run Last Known Good Configuration” option may be useful.
3. If 0x00000002 DEVICE_QUEUE_NOT_BUSY began to appear after you have connected a new device to the system, then you need to check it for compatibility with your operating system. If the device is compatible, then you need to download the latest drivers from the official website of the manufacturer and install them. If the latest drivers are installed, you need to install an earlier version of the drivers. If the device is incompatible with the operating system, then it is necessary either to change this device or to change the operating system that supports this device.
4. Very often the cause of the appearance of 0x00000002 DEVICE_QUEUE_NOT_BUSY is a malfunction of the RAM. To test it, you can use testing programs, such as memtest86+.