Windows

Question

PNP Detected Fatal Error - Windows Update Intel - System - 8.3.10209.6897

By nauthement ·
Tags: Windows
Hello,

Still new to the forum so please tell me if this post is in the wrong place.

I work in the IT department of my company and starting yesterday (10/22/20), we're had three users to date get BSODs with the error code PNP Detected Fatal Error. I've been able to get each one back up by System Restoring to a point before their latest Windows Update, and this seems to have stabilized the machines for now.

While troubleshooting I noticed applying a particular Intel update would cause it to BSOD again and we'd have to System Restore again. I've screenshot the update and attached to this post. Has anyone else come across this issue?

I've disabled Windows Updates for the time being; nervous about re-enabling updates or manually downloading the Intel - System - 8.3.10209.6897 update off Microsoft's Catalog. Any suggestions or similar problems from anyone?
Thread display: Collapse - | Expand +

All Answers

Collapse -

Driver Updates

by jsanders1603414860 In reply to PNP Detected Fatal Error ...

I have had the same issue on three laptops. They are all Dells that are a few years old. I have found that installing all the latest drivers including BIOS update resolves the update issue. I disabled updates until all drivers were updated. Then re-enabled Windows Updates and it did not blue screen any more.

Collapse -

Disable Drivers

by StefanCardnell In reply to Driver Updates

Agree with this. After a painstaking day of dealing with the same issue, I found the "Intel - System - 8.3.10209.6897" driver update was the cause of the issue. A little research shows this updated is responsible for the "Intel Dynamic Platform and Thermal Framework" driver.

If you are in Safe Mode and can't boot, go to Device Manager and disable this "Intel Dynamic Platform and Thermal Framework" driver. Then you can reboot and get back to the Windows OS. Afterwards, install the Windows updates - they should be successful.

After I installed the Windows updates, I saw that "Intel Dynamic Platform and Thermal Framework" was no longer listed in Device Manager. Could it be the Windows update removes this driver, but the driver is giving a BSOD when it's being removed?

Collapse -

Disable Drivers

by jsanders1603414860 In reply to Disable Drivers

Another option is to boot into safe mode, go to c:\windows\system32\drivers and see if you have any of these files dated from 2018 (listed below). One or multiple of them is the culprit. I renamed my SoftwareDistribution folder to *.old and renamed these three files to *.old. Then was able to boot. I have this on four Dell laptops now, all of which were a few years old.

dptf_acpi.sys
dptf_cpu.sys
esif_lf.sys

Collapse -

Disable Drivers

by nauthement In reply to Disable Drivers

Thank you both for the input, it's truly been a lifesaver.

We had another one BSOD with the same error today, marking 4 in total. I System Restored to before the Windows Updates like the others, so I've got it stable for now.

I see the files for:
dptf_acpi.sys
dptf_cpu.sys
esif_lf.sys
They date back to 2014. Should I follow the same guidelines and rename them as .old along with the SoftwareDistribution folder? If so, once I rename the to .old do you think I'd be able to re-start Windows Updates successfully without getting the BSOD? Or is that method just icing on the cake to installing driver updates?

Speaking of installing driver updates, I don't see an option to disable the Intel Dynamic Platform and Thermal Framework driver. I could go one-by-one and update drivers by having it search for the updates on the web automatically, should I take that route?

Collapse -

Disable Drivers

by jsanders1603414860 In reply to Disable Drivers

If you are stable then you shouldn't have to mess with renaming SoftwareDistribution or the other files. I was doing that as a means of getting it fixed. I had a few laptops that would immediately BSOD again because the update causing teh issue was downloaded and ready to intall. So within a few couple minutes of getting the PC to boot up it would BSOD again because the update started trying to install again. So, renaming the SoftwareDistribution folder bought me some time to get the wuauserv service disabled before it would BSOD again. The 2014 version of those files are the good ones. So no need to rename those files now.

Collapse -

Disable Drivers

by nauthement In reply to Disable Drivers

Ah, gotcha. I've the Windows Updates disabled via Services and Group Policy (Configure Automatic Updates = Disabled). Will Windows attempt to start updates again after a certain amount of time even though the service is currently stopped and disabled on startup and the GP is set to disabled for auto-updating?

Collapse -

So, how long to hide this update??

by JamesMurdock In reply to Disable Drivers

I am trying this https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-window advice to "hide" this particular update.
Renaming the three files and the SoftwareDistribution folder allowed me to reboot, (actually rebooting three times telling me that my system was "Working on updates" first, but luckily those renamed files did not reappear!
I immediately froze updates in Settings, then used the troubleshooter tool linked above to list all updates, and select the OP's named update (listed twice identically) to be hidden.

Is this a good way to avoid this update?
When should I allow this update? Is it OK to block it forever?

Collapse -

Hiding the update working?

by josh1525872500 In reply to So, how long to hide this ...

I've tried disabling the Windows Update service and also tried hiding the update (and actually tried hiding all updates that showed as available to install). But, after a few days, I inevitably end up back in the blue screen/system restore/try something else loop.

Definintely curious if the Show/Hide Updates utility is working for anyone. Or if anyone has found another permenant solution?

And I know this is wishful thinking, but has anyone seen any news from Intel or Microsoft on this?

Collapse -

Same problem

by fourlane In reply to PNP Detected Fatal Error ...
Collapse -

Bad Intel Dynamic Platform and Thermal Framework Device Driver

by ronaldroth In reply to PNP Detected Fatal Error ...

I had this same issue happen to me on 2020.11.24 to my Dell E7450. Based on the feedback from this forum - I booted to Safe Mode and went into System The driver dates on Intel Dynamic Platform and Thermal Framework were all mucked up (2014). I force the driver to update to the latest available (2018), rebooted, and everything was good (so far...)

Related Discussions

Related Forums