XPS 8930, Device Manager errors

windows 10? 64bit? and does SFC pass, (no windows corruption and HDD passes smart test causes same if fails )

let me guess you bought  used PC with that error ?

and didn't just happen one day  …. like magic, THE CPU Is wrong.

off hand Id say upgrade the BIOS using only the F12 key way.

this will add newer CPU support (may) dell does not do a publish  CPU supported list beyond an newer CPU not sold with the PC new. (I call it the first blush spec) what it really supports is not documented, but in fact vast posts exist of others trying them all  if you search)

oK,   There are 2 limits,  the chip set limit say Gen 8 CPU rule then BIOS rules(means dells limits)

the 3rd limit can be if PC VRM only do 85 watts going higher say in I7 more powerful CPU will not work.

z370 chip set 2017 wow that nice. I have z270 .

The spec by dell shows 8th generation Intel Core i3/i5/i7/i7k (in generic form)

Core i7-9700KF (95 watt is the  big dog)

then this great post at dell. searches DO WORK

https://www.dell.com/community/XPS-Desktops/XPS-8930-supported-CPU/td-p/6218024

off and wrong bios version I guess. The above last  link is very good;. the special edition !

Thanks for your reply.  I will attempt to answer your questions:

OS is Windows 10 Pro, 64 bit, version 1903.  The Dell computer was refurbished and came directly from Dell.  BIOS version is 1.1.6 - the latest available.

I did run SFC with the VerifyOnly switch and it came back with no errors with the Windows system files.

The standard processor for the XPS 8930 is and has been the Intel Core i7-8700.  Given that, I assume that it is a Dell supported processor for that XPS model.

Reinstall or update the chipset drivers...?

Try to update the drivers in Device Manager by right clicking the CPU device and selecting Update driver.

Also check in the BIOS to see if it is reporting the correct Processor Type, Processor ID, etc.

Is this PC running Intel Rapid Storage Technology (IRST)?

Check out this link (but do a little more research before you proceed). The solution for this person is in the last message in the thread.

Intel Core i7-*7820x CPU Yellow Exclamation Marks - Help please?

https://www.windows10forums.com/threads/intel-core-i7-7820x-cpu-yellow-exclamation-marks-help-please.18608/

http://support.microsoft.com/kb/982116

https://support.microsoft.com/en-us/help/314060/

Your CD or DVD drive is not recognized by Windows or other programs

Version: 17.2.0.1009 (Latest) Date: 3/15/2019

https://downloadcenter.intel.com/download/28650/Intel-Rapid-Storage-Technology-Intel-RST-User-Interface-and-Driver?product=55005

This issue may have occurred after one of the following situations:

• You upgrade the Windows operating system or do WIN10 feature update.
• You install or uninstall CD or DVD recording programs.
• You uninstall Microsoft Digital Image.

Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

The device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)

Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)

---

@ggeinec wrote:

Is this PC running Intel Rapid Storage Technology (IRST)?

Check out this link (but do a little more research before you proceed). The solution for this person is in the last message in the thread.

Intel Core i7-*7820x CPU Yellow Exclamation Marks - Help please?

https://www.windows10forums.com/threads/intel-core-i7-7820x-cpu-yellow-exclamation-marks-help-please.18608/

---

I should have been more clear about IRST. I believe the IRST drivers take over from the native drivers. So if I am correct, and your system has IRST drivers, you may want to check to see if there are updated IRST drivers for your system. But be careful because you can't just install any IRST drivers.

The link to the other person's solution for your problem has nothing to do with IRST drivers themselves.

If machine passes ePSA ...

then update BIOS.

If it survives that, Nuke and Pave system (clean install Windows).

First of all, thanks very much to everyone who posted suggested solutions to my problem.  I tried everything other than a complete reinstallation of the Windows 10 OS.

I wanted to let you know that I was able to solve the i7-8700/Device Manager Error Code 32 problem.  What I had to do was to uninstall all twelve of the i7-8700 processor incidences in Device Manager.  Then I had to manually select the generic “processor” option for the driver, rather than the “Intel Processor” driver option.  Once that was done, the driver for the Core i7-8700 was “Processr.Sys,” rather than “IntelPPM.Sys.”

You will notice in looking at the attached screenshots that the yellow exclamation marks and Error Code 32 warnings are now completely absent from the Device Manager/Processor.  This only worked with I selected the *generic* processor driver.  When I selected the Intel option, the same errors returned in the device manager.

I find it odd that a generic processor driver seems to work better than the Intel-specific driver, but I could find no other way to eliminate the Code 32 Device Manager errors.

Thank you for posting your solution. Hopefully it can help someone else with a similar problem. It is strange that IntelPPM.sys did not work; that is what my driver is but my CPU is not an i7-8700.

Still sounds like an issue with chipset drivers - at least to me. So selecting 'generic' allows the chipsets to work correctly because -otherwise- the chipset doesn't recognize the CPU correctly.

What does BIOS say about what CPU is installed? And if you run msinfo32.exe from Start>Run, what does it say about the CPU?

Have you put the PC through any benchmarking tests to see if the "generic" CPU lives up to what you'd expect from the one you actually have installed?

Hi JN50,

Thanks for posting.  Apologies that your system is not performing as expected.

Has this issue been resolved?  If you still require assistance and the system is under warranty, you may contact me privately. Be sure to include your personal information (name, address, telephone, email) and your computer's service tag number in your message. Thanks.

If there is no warranty, then you could contact our Out of Warranty team to get a quote for a paid service request. 

Hello Robert,

Thanks for following up on my problem.  As specified in my previous "XPS 8930 Device Errors" post above, I was able to eliminate the Code 32 Processor errors in the Device Manager by uninstalling all twelve of the logical processor cores in the Device Manager, then manually installing the generic "Processor" driver instead of the Intel-specific Processor driver.  Even though I'm glad this worked in terms of removing the errors, I find it puzzling that a generic processor driver worked better in this regard than the Intel driver.

Thanks for your follow-up, Ron.  Here are the answers to  your questions:

BIOS - processor identified as Intel Core i7-8700.

MSINFO -  same as above

I also ran the Intel Processor Diagnostic Tool.  Again, the processor was determined to be the Intel Core i7-8700,  All tests run by this program were passed.

BENCHMARKING TESTS - I did not run any benchmark tests.  However, I would very much like to do so.  Could you please recommend some processor benchmark tests and I will download and run then.  Thanks.

---

@JN50 wrote:

Hello Robert,

Thanks for following up on my problem.  As specified in my previous "XPS 8930 Device Errors" post above, I was able to eliminate the Code 32 Processor errors in the Device Manager by uninstalling all twelve of the logical processor cores in the Device Manager, then manually installing the generic "Processor" driver instead of the Intel-specific Processor driver.  Even though I'm glad this worked in terms of removing the errors, I find it puzzling that a generic processor driver worked better in this regard than the Intel driver.

---

While it removed the error, the machine is not fixed.

Sounds like you still have a hardware or core Windows problem.