When you think the Blue Screen of Death (BSOD) is no longer happening in the latest Windows versions, think again. A Windows 11 BSOD is caused by certain versions of the Intel Smart Sound Technology (SST) driver. The IntcAudioBus.sys driver causes the crash.
More details directly from Microsoft explain the details of the versions of the driver that cause the problem.
In case you are experiencing the BSOD, you can install a newer driver version (if available from Intel or your computer manufacturer). If not, a driver rollback might also work. Boot into safe mode in case you cannot access the Windows 11 interface in the normal way.
But even if you are not seeing any Windows BSOD errors, it is wise to check if your system is using the Intel SST driver and update the driver for it. Use the Device Manager to check for the audio device.
Richt-click the Start menu, and then select the Run otpion.
Type “devmgmt.msc” and press Enter to start the Device Manager.
Right click the devices listed, and click Properties to see the driver version details (Driver tab).
From the Device Manager it is also possible to Update the driver or Roll Back the driver. If you do choose to update the driver using the Update Driver button, make sure you do not use the automatic but use the search on disk option. That allows for the manual selection of the driver, rather than updating from the Microsoft Update Catalog, which could still give you the incorrect version.
To make sure your Windows PC always has the latest drivers, we recommend using a program like DriverFinder. It automatically checks your PC hardware devices and finds the lates device drivers for them.
The Windows Device Manager uses error codes to indicate the status and problems with devices in a Windows system. This has been the case since Windows XP and is still the same in Windows 11. Code 22 is one such error code indicating that a device has been disabled.
To fix the code 22 error for the device, follow these simple steps to re-enable the device.
Open the Device Manager. Press the Windows + R keys and type devmgmt.msc in the Run dialog box to start the program.
In the Device Manager, navigate to the device with the Code 22 error status.
Right-click the device and in the popup menu, select Enable device.
Wait for the device to be enabled and then close the Device Manager.
Your device is now enabled again and should function as expected and intended.
In most cases, this should work without problems, since the error clearly indicates the cause of the problem. But in some cases, enabling the device might not work, or result in a different error code for the device. Always try rebooting the system first before any further steps.
If a reboot and enabling the device do not solve the code 22 error, a problem will be preventing the device from being enabled. In older systems, this could be a resource problem. Things like changing the hardware device to a different slot, resetting the CMOS, and loading default BIOS settings would be required.
But with the latest PCs, the UEFI BIOS, and automatic hardware configuration options, such steps are no longer required. Check for recent hardware changes and reverse them to solve the error for the code 22 device. For USB devices, unplug other USB devices to see if that solves the error.
A final step to ensure the device can be enabled is installing the latest drives for the device. In Windows 10 and Windows 11, drivers for the most common devices are updated automatically. For non-standard devices or older Windows version, you may need to manually update the drivers.
Since the code 22 error has been happening for graphics devices as well, it is important to check the compatibility of the driver with the hardware. Incompatible hardware or a driver for the wrong Windows version can result in device errors, including code 22.
Find the right drivers for you hardware and Windows version easily using the DriverFinder software.
You would think the big companies get it right, but even Dell seems to have gotten it wrong with their DBUtil driver bug. Dell’s firmware update driver appears to have been a security problem going as far back as 2009!
The current version 2.3 of the Dell BIOS driver (dbutil_2_3.sys) allows the OS and system apps to interact with the computer’s BIOS and hardware. A vulnerability in the driver could be abused to allow access to driver functions which would enable execution of malicious code with administrator level and kernel-level privileges.
Any time you would have executed a firmware update on a Windows Dell system, you could have this driver present on your computer. Note that this is independent of the Windows version. The issue affects the DBUtil driver only, not the firmware updates installed using this driver.
The best thing to do is to remove the driver immediately, until an update can be installed.
Check these file locations for the driver file:
C:\Users\<username>\AppData\Local\Temp
C:\Windows\Temp
A solution from Dell for Windows 10 is already available.
The full details on the issue and the work in progress from Dell regarding the solution can be found here.
Another confirmation that security remains a sensitive issue, particularly with drivers. We recommend to always keep your drivers up-to-date as much as possible.
And since we are talking security… if you are using Windows Defender for your PC security, make sure you check for updates as well. A recent bug in Microsoft Defender can fill up the system driver of Windows 10 with thousands of files of varying sizes. A patch is available,m so check your Windows Defender version and update it if required. More details on the bug can be found here.
By default Windows 10 automatically installs devices and download updated drivers when available. In some cases you do not want this, in which case you need to disable automatic driver updates. In Windows 10, the easiest method is to use the Control Panel.
Here are the steps:
1) Open the Control Panel by typing “control panel” in the Search box next to the Start button and press Enter.
2) In the search results, click the Control Panel App to open it.
3) In the Control Panel window, click the System and Security option, and then click the System option.
4) In the new Settings window that opens, scroll down until you see the Advanced system settings option and click it.
5) This will open the System Properties dialog box. Here you need to select the Hardware tab, and then click the Device Installation Settings button.
6) Now change the radio button from Yes to No, and click Save Changes.
Close all windows that were opened in the above steps and you’re done. You can now manually decide which driver you want to install for each hardware device.
In Windows 10 Pro you also can use the group policy editor
In a corporate environment you might want to use the Windows 10 group policy editor to change system settings rather than using the control panel. Note that this is not possible on the Windows 10 Home version.
The steps are as following:
1) In the Search box next to the Start button type “gpedit” and press Enter. In the search results, click the Edit group policy Control Panel option
2) In the Group Policy Editor window, open the Computer Configuration and then open the Administrative Templates.
3) Next, open the Windows components, scroll down to the Windows Update entry and click it.
4) In the right-hand panel, scroll down until you see the option Do not include drivers with Windows Updates. Right-click it, and in the popup menu, select Edit.
5) In the right-hand panel, scroll down until you see the option Do not include drivers with Windows Updates. Right-click it, and in the popup menu, select Edit.
6) In the dialog box that opens up, select the Enabled radio button and click OK.
7) Close the Group Policy Editor window and you’re done.
In general, you want to keep your computer up to date, including device drivers. But if you have a driver-related problem, installing an older version can sometimes solve the issue. And in that case, you do not want Windows Update to automatically update the driver again. It could also be that there is no driver for your hardware in Windows 7, but a Vista driver works. In those cases you want to manually install it and not rely on the Windows driver update service, so just disable automatic driver updates in Windows.
Steps to disable automatic driver updates
In Vista and Windows 7 you can easily disable the automatic driver updates. Just follow these steps:
Open the Control Panel
Select System and Maintenance
Select System
Now click Advanced system settings in the left-hand panel (if the UAC is turned on, click Continue to proceed)
Next, click the Hardware tab
Click the Windows Update Driver Settings button
Now you need to select the driver update option you want to use. The default option will automatically check for drivers and update them. To disable automatic driver updates in Vista, select either the second or third option and click OK.
Use the Group Policy Editor
In some cases, this appears not to work, and then there is another method to disable automatic driver updates in Vista and Windows 7. This involves the local group policy editor, which can be started from the Start menu by typing gpedit.msc followed by Enter.
Once started, in the Local Group Policy Editor, navigate to the following: Computer Configuration -> Administrative Templates -> System -> Driver Installation.
Next, change the setting for Turn Off Windows Update Device Driver Search Prompt to Enabled. After clicking OK and closing the Local Group Policy Editor, just restart Windows and that’s it.
Since the Local Group Policy Editor is used, this second option is limited to the Professional and Ultimate editions of Windows Vista and Windows 7. The Home versions do not have this option.
For Windows 10 and Windows 11, you can also disable automatic updates using the instructions in here.
Most printer manufacturers provide extensive software packages to support their printers on Windows, including Vista. Apart from the actual printer driver, which ensures Vista can communicate with the printer device, the software will generally include a control panel, a print manager, and often additional programs. All-in-one printers for example have software to support the scanning and faxing functions.
Due to the size and complexity of the printer software, the installation will normally include a setup or install program. Running this and following the installation instructions (to the letter) will install the printer on your Windows Vista computer.
Update Printer Drivers in Vista
The large printer manufacturing companies, like HP, use in-place update software these days, so you will automatically be notified of updates. Installing the printer driver update is then also done for you. But not all manufacturers have such sophisticated processes in place, and you also should consider if you want to run all these automatic schedulers on your PC.
If you want to manually update your printer driver in Vista, is is possible to use the same installation procedure as used for the initial installation. That is, download the printer driver update for Vista and run the setup or install program.
It can be possible to first uninstall the existing printer software though. What is important is if the printer driver update software is a full install, or an update. When you download a printer driver update for Vista, the website of the manufacturer will mention this type of information in the release notes. If it is a full installer, you can first try running it. But if it fails, simply uninstall the printer software in the Control Panel first. Then reboot and try it again.
If the installer does not work, or there is no setup or install program, it is possible to manually update the printer driver in Vista. This process is outlined below.
Manual Printer Driver Update Steps
First open the Control Panel from the Vista Start menu.
Next, click the Printer link under the Hardware and Sound category.
Now select and right-click the Printer for which you want to update the driver.
In the popup menu, select Run as administrator, and in the submenu, select Properties.
If the UAC comes up, click Continue.
Next, click the Advanced tab, and then click the New Driver button.
In the Add Printer Driver Wizard, click Next, then Have Disk and finally Browse.
Now navigate to the location of the Vista printer driver update, and then click Open and OK.
This process will use the driver information file (.inf) to find the printer driver update and install the required driver files onto your computer.
Don’t forget to turn on your printer when you update the printer driver. It is easy to forget since the printer will show in the list, but it will be grayed out rather than show in black. But the printer should be turned on to allow communication between Vista and the printer. Otherwise the driver update installation might fail.
Programs that automatically update device drives on your system need to match the hardware in your system with the devices in their database. Once a match is found, they check the driver version to see if it is newer, so the update can be recommended.
That sounds pretty simple, doesn’t it?
Well, in a way it is, but it is still possible that a driver update program recommends a program that should not be installed on your system. We call this a false positive. There are two possible reasons for a false positive in driver updates, a device mismatch, and a driver version mismatch.
Device Matching Logic
To understand this, we need to look at how a device is identified in Windows. If we open the Device Manager, select a device, and then right-click it to see the Properties, we can select the Details tab. In the list of properties, we select the Hardware Ids:
The screenshot will vary depending on the Windows version, but the concept and logic are the same throughout all Windows versions.
As you can see in the screenshot, a device can have multiple hardware ids. The top one in the list is an exact match of the device, where the brand, model, type, and even revision number would match. Going down the list, the device match is broader, but still specific, that is why all these identifiers are present in the list of hardware ids.
But Windows allows for the use of compatible drivers, so that, if an exact match on the driver is not available, the device can still be used with a compatible driver. This may result in reduced support for the device, not all functionality may be available, but at least the device works.
If we select the Compatible Ids in the property list for the same device, we see:
Again, we see a list of identifiers, where the top one would be the preferred match, and the lower ones are broader matches.
When a driver is needed for a device, Windows will always first try to find a driver for the device based on a hardware id match. If none can be found, a driver match based on the compatible ids can be used.
So if an existing driver has a match on a hardware id, while an update is recommended that matches on a compatible id for the device, we consider that a false positive.
Driver Version Comparison
Apart from a list of devices that are supported by a driver, a driver also has a date and version. The date and version are combined in a single identifier, like this:
“03/22/2010,6.236.0322.2010”
The first part is the date, and the second part is the version number. Windows checks for new drivers based on the driver date, the version is optional. So if a driver program recommends a driver update based on a newer version, while the date is older than the currently installed driver, this is again a false positive.
In the Device Manager, you can select the Driver tab to see the date and version of the currently installed driver:
Drivers do not always have the complete date and version information, and even the date format is not always consistent. Driver programs of course need to factor in these aspects when recommending driver updates.
Windows Version Matching
Not only should a driver match a device by supporting the hardware ID, but it also needs to be suitable for the Windows version.
Drivers that are suitable for Windows 10 will in most cases be compatible with Windows 11. The same is true for using XP drivers in Vista and Vista drivers in Windows 7 (and in some cases even in Windows 8.1).
But it is not guaranteed that older drivers are compatible with newer Windows versions. Simply trying it will tell you if they work. And even if not directly compatible, older drivers can sometimes be installed by running the installer in Compatibility Mode for the older Windows version.
For this reason it is also recommended to always make a driver backup or creae a system restore point before updating device drivers. That way, you can revert back to the previous version in case of any problems. Another option is to have an installer for a previous version of a driver on your system so that can be reinstalled in case of problems.
And as a last resort, manually installing the driver using the INF files can work.
In addition to the Windows version, the system architecture is important. Drivers for Windows 32-bit will in most cases not work in 64-bit systems and vice versa.
Programs that recommend or update drivers for your computer need to consider these aspects. False positives can happen when a program recommends drivers that are for an older Windows version but don’t work on your Windows version.
In our tests, we found DriverFinder to have the best device driver matching logic.
All hardware equipment inside and connected to personal computers uses an identifier to uniquely identify itself. This allows operating systems to recognize the device and install the necessary software for it. In Windows, this generally means that a device driver for the hardware is installed. The hardware ID for a device can be checked to locate a driver for it.
The hardware identifier is a combination of the bus type, the hardware manufacturer (or vendor), and the device identifier. In some cases, additional sub-system identifiers and revision information is included to distinguish between variations of a device.
So when you are looking for a device driver for a piece of hardware, it is useful to know the hardware id of the device. This can tell you which manufacturer made the device and help you find a device driver. Read on to find out how to check the hardware ID for a device in Microsoft Windows. The steps are valid for Windows XP all the way up to Windows 11.
Check the Hardware ID using the Windows Device Manager
The hardware id for a device in Windows can be found in the Windows Device Manager. To check the hardware id for a device, follow these steps:
Open the Device Manager from the Control Panel. You can also type “devmgmt.msc” at the Run option in the Start menu (or menu Search option for Windows 7 and newer).
In the Device Manager, right-click the device, and select Properties in the popup menu.
Next, select the Details tab.
Now select the entry called Hardware Ids in the Property dropdown list.
As you can see in the screenshot, there can be multiple hardware ids for a device. The top one is the most specific identifier, and going down, the identifiers are more generic. The reason this is done is to allow a device driver to be selected based on a match to any of these hardware identifiers. This allows drivers to be used that are applicable to variations of devices.
The hardware manufacturer in this example is NVidia, which is identified by VEN_10DE.
Obviously, this is a device for which a driver is already installed, and the manufacturer and model for the device are shown. But the hardware id is also available for unknown devices and not recognized devices. This way, the hardware id, or Windows device ID, can be used to find the correct driver for the device. If no exact match for the driver is available, you can also check out the Compatible Ids by selecting that as the Property selector.
Note: Depending on the hardware device, the number of tabs in the device properties dialog will vary. But there will always be a Details tab as used in the steps in this guide.
Programs like DriverFinder use the hardware id and the compatible id to find a matching driver for a device as well. This way these programs can find a driver for a device to match the hardware and Windows version.
FAQs
What is a hardware ID?
The hardware ID for a device is an identifier for a piece of computer hardware. Think of a sound card, or a webcam, for example. The hardware ID is vendor-specific. A hardware ID consists of a device class, vendor identifier, device identifier, subsystem identifier (different versions of the device), and a revision number. An example of a hardware ID is: PCI\VEN_8086&DEV_9A49&SUBSYS_14321043&REV_01
Revisions can be used for updates of firmware on the same device for example.
Is hardware ID the same as Device ID?
Yes, the hardware ID is often referred to as the device ID.
Is the hardware ID the same for all Windows versions?
A hardware ID is specific to a device. So, it is linked to the equipment, not the operating system. The hardware ID will not change for different Windows versions.
How do I find the hardware ID?
The hardware ID for a device can be found in the Windows Device Manager. In each version of Windows, the steps are the same. Open the Device Manager, right-click the device, select Properties, select the Details tab, and under Property select Hardware Ids. The Value shown contains the hardware ID(s) for the device.
What is the hardware ID used for?
The hardware ID is used by Windows to identify the device and find a device driver for it. Microsoft finds a driver in the repository or the Windows Update catalog. If no driver is available with Microsoft, a driver from the manufacturer needs to be installed to allow communication between Windows and the device.
What is a compatible ID?
The compatible IDs for a device are also hardware IDs. The difference is that a hardware ID is unique to a single device, while compatible IDs can apply to multiple devices. The compatible IDs identify the device as a piece of equipment of a certain category that can be used for certain functions. This is important if no unique device driver is available for a device. A driver for a compatible ID of the device can enable Windows to still communicate with the device.
Do Virtual Devices also have a hardware ID?
Yes, virtual devices in Windows also have a hardware ID. These devices also need software to function, and need to be identified as a device within Windows. Examples are:
Whenever using hardware devices in Microsoft Windows, Windows will install a device driver for each hardware device. Many devices are supported by Windows itself, especially in the latest Windows versions. But in some cases, you will need to install additional drivers. During driver installation Windows can search on the Internet for a device driver, or you will be prompted for a location where Windows can find the driver for the new hardware device.
But in some cases even supported devices are not recognized by Windows. That could be because the driver is missing or corrupt. Another option is that Windows does not look in the right place for the driver. The location where Windows looks for device drivers by default is C:\Windows\Inf (since the inf files are used to match a device with a driver).
Since the installation path for Windows can vary, this path for Windows device drivers is actually configured as %SystemRoot%\Inf. In this, the %SystemRoot% refers to an environment variable that always points to the right path for the Windows installation.
The path for Windows device drivers in the registry
The driver location is stored in the Windows registry. And the registry key that is used to store the driver path is: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\DevicePath
So if you are getting unexpected errors indicating that the device is not recognized, check the device path in the Windows registry. If the %SystemRoot%\Inf value is not present in the DevicePath, then change it to that, or add it to the path.
The DevicePath variable can also be extended with additional locations for drivers. If for example, you have a network location where you store device drivers for all PCs and hardware devices, you can add that to the variable. Just separate the path with a semicolon. E.g.: %SystemRoot%\Inf;\Drivers
OEM manufacturers also use this option to include additional drivers in the default Windows setup.
To start the Registry Editor, use the search option in the Taskbar, or press the Windows + R key to bring up the Run window and then type “regedit.exe” and press Enter.
Since Windows 7 is relatively new, not all hardware is compatible with Windows 7 yet. Microsoft always recommends people use the hardware compatibility check feature to find out if the computer hardware is compatible with Windows 7. Some hardware devices, however, might never become compatible since manufacturers do not create new drivers for older devices anymore.
Windows 7 Code 10 Error
As a result, you can experience a variety of device errors in Windows 7, one of which is device driver error code 10. In itself, error code 10 in Windows 7 means that the device cannot start, but there can be different causes for the error.
Microsoft’s recommendation is to first update the drivers using the Device Manager. This should help solve problems that are related to outdated, incompatible, and even corrupt drivers. But also make sure you install the latest Windows 7 updates, as software improvements in the operating system can also help fix device-related issues.
Ok, an error code 10 can happen for all kinds of devices, and one of the more common devices is the audio device. Apart from driver issues, also make sure you check the status of the Windows Audio service. If the Windows Audio service is not running, you can have the right drivers installed, but the device will not work.
For USB devices the error code 10 will result in the device not being accessible. In that case, uninstalling USB devices in the Device Manager is a common solution. You can try uninstalling the USB device that has the problem, but very often it is necessary to uninstall all USB devices, reboot, and then wait for the USB devices to be reinstalled. Make sure to unplug the external USB devices before you reboot, so you can add them one by one again.
For older hardware, the code 10 error can also be the result of hardware conflicts. In most cases, you will see that the hardware device will not appear on the hardware compatibility list, but it is useful to check the resource usage on the device in the Device Manager. On desktop computers, this kind of problem can be solved by changing the BIOS settings (IRQ assignments, memory ranges), or even unplugging conflicting hardware. Obviously, that is only feasible if you do not need that specific device.
Windows 7 Device Drivers
Because the most common cause of error code 10 in Windows 7 is incorrect device drivers, you should always try to get the right drivers for the device. Checking on a regular basis can pay off, as drivers are updated frequently. Using the Microsoft Update feature is one way to check, but there are a number of limitations with that.
The first limitation is that you will only get real Windows 7 drivers, which are signed drivers that have Microsoft approval. You will not get unsigned drivers or drivers that are not for Windows 7. So if there is a Vista driver for your device, which might work in Windows 7, you will not get it. Even Windows XP drivers sometimes work in Windows 7, possibly in compatibility mode.
The second limitation is that Windows Update will automatically install new drivers. This assumes that the update will succeed without problems, replacing or overwriting the old driver. In quite a few instances, however, it is better to first uninstall the existing driver before installing the new driver. Quite a few audio manufacturer’s recommend this practice to prevent driver update problems.
So make sure you use a variety of methods to update the driver for your device and fix error code 10 in Windows 7.
