So I am randomly having a problem that manifested itself today....it is painfully annoying.
All of my USB devices and my card reader all show the code 52 in device manager.
Code 52: Windows cannot verify the digital signature for the drivers required for this device
I can currently get around this by hitting f8 and telling windows to not verify digital signatures when the system boots up but this is not a solution.
Has anyone else had this issue and is there anyway to fix it?
Any help is greatly appreciated!
-
cookinwitdiesel Retired Bencher
-
Have you tried reinstalling the driver for all USB ports? Also, Nvidia chipset driver comes to mind
-
cookinwitdiesel Retired Bencher
I first thought they would be nvidia drivers, but they are all MS ones in device manager...
I can give that a try though -
Uninstall, driver sweep, reinstall? I know when I had my R1 (and it started to happen with my R2) that when playing certain games I would get a device disconnect/reconnect noise, presumably from my MX518 since that was the only USB device connected. Could never pinpoint what exactly was disconnecting/reconnecting, and I just never got around to calling up support to identify the problem.
-
-
cookinwitdiesel Retired Bencher
Been out of it a few days, will try the new chipset driver now. And for what it is worth, this happened AFTER loading up setpoint for my new G9x (bada$$ mouse!) so I will remove that too and see if it helps
I also experienced my blu ray playback stuttering ALOT around the same time this problem came up -
cookinwitdiesel Retired Bencher
Reinstalling the chipset driver did nothing (15.49 from nvidia - worked fine on multiple other installs)
Removing setpoint 5.20 did nothing
Importing registries from known working install did nothing
This is getting VERY frustrating
I do not want to have to completely reformat this drive again (would be like 7th time.....this SSD is fast but a nightmare so far) -
I found this guide (by Gokul T, Microsoft Support Moderator):
Give it a try:
Boot into Advanced Boot Options and disable driver signing checking.
The Advanced Boot Options screen lets you start Windows in advanced troubleshooting modes.
You can access the menu by turning on your computer and pressing the F8 key before Windows starts.
Disabling driver signature enforcement has helped a lot of users in fixing the issue.
You may also delete the USB "Upper Filter" & "Lower Filter" Entry and check if that helps.
Before we go any further, please first backup the Registry.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
1. Click “Start”, type “regedit” (without quotation marks) in the “Search” bar and press Enter.
Note: If UAC (User Account Control) pops up, please accept it.
2. Right click “Computer” (the root node) in the left pane, click “Export” under the “File” menu, choose “All” under “Export range”, and select “Desktop” in the “Save” in box and type backup in “File Name”. Click “Save”.
Note: The backup file is on the Desktop and named backup.reg. We can simply restore the registry by double-clicking the backup.reg file.
3. Click “Start”, type “regedit” (without quotation marks) in the “Search” bar and press Enter again.
4. Locate the “UpperFilters” value under the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}
5. On the “Edit” menu, click “Delete”, and then click “OK”.
6. Locate the “LowerFilters” value under the same key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}
7. On the “Edit” menu, click “Delete”, and then click “OK”.
8. Quit Registry Editor and restart the computer.
Hope this helps. -
cookinwitdiesel Retired Bencher
Already seen that, those values don't exist in my registry at all. I took the entire HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}
branch from a working install and loaded them in the not working one and it did not fix the problem at all -
Have you replaced anything recently ( CPU/GPU/RAM/HDD)? Or even re-seated? This could be a memory issue as well.
If you have another RAM stick (not HyperX), try using it and see what happens.
Some even suggest re-seating a CPU every time after re-seating/replacing RAM, lol. -
cookinwitdiesel Retired Bencher
I am 100% certain it is not hardware related....I have 3 different hard drives with me, each with a different image of windows 7
only the one with this problem is having the problem, the other 2 are
I would just clone one of the others onto the ssd but this intel ssd is useless with acronis true image
Maybe I can make a system image of one of the others through windows and then restore that.....I would really prefer to just fix the clean install I have on this ssd though....the other 2 are heavily used "dirty" installs -
I know it would be best to just find the culprit, but for a couple of possible workarounds: Look here
-
cookinwitdiesel Retired Bencher
I am tired of dealing with this crap....guess I will just reformat again and waste further time....
-
I've run into the same exact issue with my Aurora Desktop.
I tried system restore and that managed to fix it for a few hours (I would reboot the pc and not need to disable driver signature enforcement).
However, I have no clue what caused this, and in addition to having to press F8 and disable driver signature enforcement everytime i boot up, my audio is not working at all (it seems to detect my speakers, but no sound comes through no matter what I try).
This PC is becoming a real nuisance -
-
cookinwitdiesel Retired Bencher
I need to be able to actually do things with my computer....like game and play blu ray....
-
Oh, you actually do things on your system, lol.
In that case - low level format :wink: -
cookinwitdiesel Retired Bencher
Well, have windows mostly reloaded now. This time I am making a system image before loading all my crap on it (just the main utilities and drivers loaded at the moment) in case problems arise again
-
I used to see this sort of problem with Windows XP all the time, back in the days of rampant spyware. It usually ended up being a problem in general with the machine's cryptography.. the give away was usually that websites and programs that required SSL and such wouldn't work either. If you loaded up Msinfo32.exe, then looked at the Software Environment section, then Signed Drivers, the entire "Signed" column would be "No", all the way down.
Most of the time, you could fix it by running Regsvr32 initpki.dll, which would reinitialize the public key infrastructure (I think?), then everything would be fine after a reboot. I never really was able to find any solid documentation on what exactly it was that Windows did during the re-initialization process, but it usually took at least a few minutes on most machines. Unfortunately, I don't think initpki.dll exists on Windows 7, so you can't just invoke the procedure like you used to be able to.. but I'd be shocked if there wasn't some sort of equivalent, maybe just a differently named library that does the same thing.
Digitally Signed Driver problem
Discussion in 'Alienware 17 and M17x' started by cookinwitdiesel, Jun 6, 2010.