Unsolved
This post is more than 5 years old
1 Rookie
•
11 Posts
0
3246
July 3rd, 2019 09:00
XPS 8930, Device Manager errors
I recently received a Dell XPS 8930 computer. Within the Device Manager, there are errors (yellow exclamation points) next to all twelve incidences of the processor (CPU), which is an Intel Core i7-8700. The exact error message is "A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)."
I have tried the Dell automated driver update functions several times, but nothing changes. Do I need a specific driver for the Intel processor to resolve this error? If so, where can I find it and exactly what is the driver file name?
Or, is something else causing this problem? Thanks very much for any assistance you can offer.


RoHe
12 Elder
•
45.2K Posts
•
172.6K Points
0
July 8th, 2019 11:00
I agree, there's still a problem. Something is preventing the IntelPPM.sys driver from loading so you've just substituted a generic driver, but this needs to be fixed.
It sounds like a Registry error, but at the least, did you update or reinstall the chipset drivers and try using IntelPPM.sys again?
You may actually have to reinstall Windows, so back up all your personal files on external media and make sure you have the Product Keys for all your software, eg Microsoft Office, first...
JN50
1 Rookie
•
11 Posts
0
July 17th, 2019 09:00
I did update and reinstall the drivers multiple times. In every case, the Intel PPM driver caused the device manager error 32 problem to recur.
In terms of a registry problem, any ideas where to look? I agree that my use of the generic processor driver may well be a band-aid fix that just removes certain symptoms (such as the error 32 code), but does not address the underlying cause of the problem.
I use this machine on a daily basis and to reload Windows 10 (with its numerous updates), all the applications on the machine and ferret out and restore the data files is a monumental task (in terms of the time required) that I simply can't do at the present time. I wish there a less drastic, more efficient solution than nuke and reinstall everything.
By the way, I did run the Microsoft SFC utility twice and it found no damaged Windows/system files.
RoHe
12 Elder
•
45.2K Posts
•
172.6K Points
0
July 17th, 2019 11:00
Make sure all your files are backed up...
Uninstall the generic processor driver, then install the Intel PPM driver, and click the button to scan for hardware changes at the top of the Device Manager window. Reboot.
Does that help?
Vic384
6 Operator
•
3.2K Posts
0
July 17th, 2019 12:00
"In terms of a registry problem, any ideas where to look"
Check out this article: https://support.microsoft.com/en-us/help/888731/how-to-determine-the-type-of-processor-that-your-windows-server-2003-x
While the article is about Windows Server, I looked in the registry and found for my computer running Windows 10 Pro for PROCESSOR_IDENTIFIER the following: Intel 64 Family 6 Model 94 Stepping 3, GenuineIntel. My processor is an i7-6700.
JN50
1 Rookie
•
11 Posts
0
July 19th, 2019 14:00
JN50
1 Rookie
•
11 Posts
0
July 19th, 2019 15:00
Vic384
6 Operator
•
3.2K Posts
0
July 19th, 2019 16:00
I am glad your problem is solved. It is possible that Processor_Identifier is not what Windows uses to determine which driver to install but that is determined by something else in the registry. We will never know what caused the problem, but hopefully the solution will help someone.
RoHe
12 Elder
•
45.2K Posts
•
172.6K Points
0
July 19th, 2019 16:00
Glad you got it sorted.
Out of curiosity, do you know if the Intel driver Win 10 found is the same version number as the one you kept installing?
Maybe Intel quietly pushed out a new driver to fix problems like the one you were having...??
Just a random thought...