To fix the error code 31 on your Bluetooth adapter, you can follow these steps:
- Update the Device Driver: Go to Device Manager, right-click on the "Generic Bluetooth Adapter", and select "Update Driver". Choose the option to search automatically for updated driver software.
- Reinstall the Device Driver: If updating the driver does not work, you can uninstall the device. Right-click on the "Generic Bluetooth Adapter" and select "Uninstall device". After uninstalling, restart your computer, and Windows should attempt to reinstall the driver automatically.
- Use the Generic Bluetooth Driver: If you're unsure which driver to use, you can select the generic driver for testing. In the Update Driver Software Wizard, select Bluetooth Radios and then choose Generic Adapter as the manufacturer and Generic Bluetooth Adapter as the model. This can help in cases where the specific driver is causing issues.
- Check for Windows Updates: Ensure that your Windows is up to date, as updates may include fixes for driver issues.
- Registry Fix: If the problem persists, you may need to add a registry key to ensure successful driver initialization. This is applicable for Windows 10 version 1903 and later. You can add the RetryDeviceInitialize registry key under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais\Readerswith a DWORD value of 1. Restart your computer afterward.
If none of these steps resolve the issue, you may need to check for hardware problems or consider seeking further assistance.
References:
- Code 31 in Device Manager when Microsoft Usbccid Smartcard Reader is in a problem state
- Code 31 - CM_PROB_FAILED_ADD
Asus Strix z790-E, 13700K, 2x16 Trident Z 6800, 3060TI, Win 11, dual monitors
Just got this put together last week, everything appears normal, XMPI profile enabled and seems to be running at 6800.
But after boot to windows, everything normal and seems to be running as expected, the q-code keeps jumping back and forth from 30, 31, and 32. Does this right after boot, without going to sleep. Been watching it for 5+ minutes after normal boot, still doing it.
Is this normal? I thought once the computer was booted up, the q-code should should be stable at A0 or something.
How to fix code 31?
How to fix error code 31 on bluetooth adapter?
Q Code 31 and 98
Has anyone a real idea how to fix Code31 in device manager?
Good Day Macrg01,
My name is Carlo, I'm an Independent Advisor and community member like you.
I am also using Windows 10 pc. Let us work together to sort this out.
First, what is the exact model of your device for me to check the updated display driver from your manufacturers website.
For the meantime here's the steps you can try.
-Click Start, type CMD and run it as administrator
-Copy and paste the command below and hit enter.
Sfc /scannow
Wait until the pc finishes scanning and repairing any corrupted system files then proceed with the next command
DISM /Online /Cleanup-Image /RestoreHealth
Use an old display driver.
-Press Windows key + X
-Go to Device Manager
-Expand the Display Adapters
-Look for Display driver that was installed
-Right click and Update
-Look for "Browse my computer for driver
-Let me pick drivers available drivers
-Choose an old driver and use it.
-Restart and check
If issue persist, we will download and install the display driver from your manufacturers website.
I hope the information above helps. Please let me know how it goes.
Have a wonderful day ahead and stay safe.
With Warm Regards,
Carlo T.
Hi Macrg01, Welcome to Microsoft Community :)
It's my pleasure to help you today.
I’m sorry you’ve had to deal with this.
I know how frustrating this may be for you.
Restart your computer if you haven't done so already. The Code 31 error could source from a temporary memory glitch.
Did you install a device or make a change in Device Manager just before the Code 31 error appeared?
If so, it's possible that the change you made caused the Code 31 error.
Undo the change if you can, restart your PC, and then check again for the Code 31 error.
Roll back the driver to a version prior to your updates.
Use System Restore to undo recent Device Manager related changes.
Delete the UpperFilters and LowerFilters registry values. A common cause of Code 31 errors is the corruption of two registry values in the DVD/CD-ROM Drive Class registry key.
Deleting similar values in the Windows Registry could also be the solution to a Code 31 error that appears on a device other than a DVD or CD drive. The UpperFilters/LowerFilters tutorial linked above will show you exactly what you need to do.
Some people have had luck deleting the entire key that holds the UpperFilters and LowerFilters values. If deleting the specific values doesn't fix the Code 31 error, try backing up the key you identify in that tutorial above, and then delete the key, reboot, import the key from the backup, and reboot again.
Update the drivers for the device. Installing the latest manufacturer supplied drivers for a device with the Code 31 error is a likely fix for this problem.
Reinstall the Microsoft ISATAP network adapter if the Code 31 error is related to the MS ISATAP adapter not working properly.
Open Device Manager and access the Action > Add legacy hardware screen. Start the wizard and select Install the hardware that I manually select from a list (Advanced). Click through the steps and choose Network adapters > Microsoft > Microsoft ISATAP Adapter from the list.
Replace the hardware. As a last resort, you might need to replace the hardware that has the Code 31 error.
It's also possible that the device is not compatible with this version of Windows. Check the Windows HCL to be sure.
If you're convinced that hardware isn't the cause of this particular Code 31 error, you could try a repair install of Windows. If that doesn't work, try a clean install of Windows. We don't recommend doing either of those before you try replacing the hardware, but you may have to give them a shot if you're out of other options.
Source: https://www.lifewire.com/how-to-fix-code-31-err....
I hope it helps :)
Sincerely,
Juliet
Independent Advisor
Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information.
Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products).
Thoroughly research any product advertised on the sites before you decide to download and install it
So, on FB marketplace, someone is selling a 7900 xtx for $400. However, it is for parts, he says the fans spin max speed but he gets no output from it. I think I can lowball it for $300 maybe. Anyways, he also says there is a code 31 error, and that indicates it is something with the drivers/driver installation. I just want to know if I should buy this GPU, and whether it is fixable or not.
Because of the error, the fingerprint scanner doesn't work, and also I can't connect my phone to my laptop via USB cable.
I tried reinstalling the drivers, but it didn't solve the problem.
OS - Windows 10 Home Single Language (Version -22H2) Ram - 8GB Processor - Intel i5 1035G1 OS Build - 19045.5247
I'm trying to get my brand new ASUS ROG Crosshair X870E Apex to POST, and I’m stuck at POST code 31 with CPU Q-LED solid on. There’s no display output at any point.
My Setup:
-
Motherboard: ASUS ROG Crosshair X870E Apex
-
CPU: Ryzen 9 9950X3D (also tested 9800X3D)
-
RAM: Tried multiple DDR5 kits
-
GPU: 4090 Discrete GPU installed
-
PSU: Corsair AX1600i 1600W, known good
-
Cooling: Custom loop
What I’ve Tried:
-
Cleared CMOS multiple times
-
Updated BIOS via Flashback (successfully completed)
-
Tested two CPUs (9950X3D and 9800X3D)
-
Multiple RAM kits, both slots and one stick at a time, all known-good
-
Stripped system down to only CPU, one stick of RAM, PSU, and GPU
-
Checked socket pins carefully – looks clean
-
Tried Retry, Safe Boot, LN2 Mode, and Slow Mode – no change
-
BIOS Flashback LED blinks and completes as expected
-
Q-LED behavior: DRAM LED is on during memory training, then goes off; CPU LED comes on and stays on
-
POST code always gets to 31 and then stops
At this point, I’m thinking it’s a bad board, but hoping someone here might have a fix or see something I missed before I RMA.