"DPTF" Errors

I've been noticing many copies of the following error in my
Application Log (Event Viewer\Windows Logs\Application) lately
(Windows 10 on a circa-2012 Asus notebook computer running
an intel core i5 CPU):

Intel(R) Dynamic Platform and Thermal Framework: ESIF(8.2.11003.3588)
TYPE: ERROR MODULE: DPTF TIME 43646 ms
DPTF Build Version: 8.2.11003.3588
DPTF Build Date: Jan 10 2017 09:52:34
Source File: ..\..\..\..\Sources\Policies\
ConfigTdpPolicy\ConfigTdpPolicy.cpp @ line 191
Executing Function:
ConfigTdpPolicy:nDomainPowerControlCapabilityCha nged
Message: Expected binary data size mismatch. (PPSS)
Participant: TCPU [0]
Domain: PKG [0]
Policy: ConfigTDP Policy [0]

I have no clue what that gibberish means. Is this something important,
or something I can safely ignore?


somewhat_off_topic_rant

Also, why is Microsoft taunting me with tidbits from their own damn
C++ source code??? I thought Microsoft Windows (all versions) has
always been "closed source"? Since I can't access MS's source, why
is MS throwing pieces of it in my face? It's not like I can look it
up or debug/repair/rebuild their OS for them. They'll have to do that
themselves if/when Windows 11 comes out. (Unless they decide to
release Windows 9 first. That would figure. It's Microsoft; they
count weird: 3, NT, 98, ME, 2000, XP, Vista, 7, 8, 10, 9, 37...)

And besides, I thought Windows was written in C, not C++? MS's hacks
got tired of implementing vectors and linked lists from scratch,
over and over, and harangued MS for access to the STL and classes
until they finally relented?

For that matter, why isn't MS writing Windows in C#? Their own damn
language not good enough for them? Throw C# to the plebes, but do all
the REAL programming behind the scenes with a REAL programming language?
So it would seem.

/somewhat_off_topic_rant


--
Cheers,
Robbie Hatley
Midway City, CA, USA
perl -E 'say "\154o\156e\167o\154f\100w\145ll\56c\157m";'
http://www.well.com/user/lonewolf/
https://www.facebook.com/robbie.hatley

"Robbie Hatley" wrote in message
...


I've been noticing many copies of the following error in my
Application Log (Event Viewer\Windows Logs\Application) lately
(Windows 10 on a circa-2012 Asus notebook computer running
an intel core i5 CPU):

Intel(R) Dynamic Platform and Thermal Framework: ESIF(8.2.11003.3588)
TYPE: ERROR MODULE: DPTF TIME 43646 ms
DPTF Build Version: 8.2.11003.3588
DPTF Build Date: Jan 10 2017 09:52:34
Source File: ..\..\..\..\Sources\Policies\
ConfigTdpPolicy\ConfigTdpPolicy.cpp @ line 191
Executing Function:
ConfigTdpPolicy:nDomainPowerControlCapabilityCh anged
Message: Expected binary data size mismatch. (PPSS)
Participant: TCPU [0]
Domain: PKG [0]
Policy: ConfigTDP Policy [0]

I have no clue what that gibberish means. Is this something important,
or something I can safely ignore?


somewhat_off_topic_rant

Also, why is Microsoft taunting me with tidbits from their own damn
C++ source code??? I thought Microsoft Windows (all versions) has
always been "closed source"? Since I can't access MS's source, why
is MS throwing pieces of it in my face? It's not like I can look it
up or debug/repair/rebuild their OS for them. They'll have to do that
themselves if/when Windows 11 comes out. (Unless they decide to
release Windows 9 first. That would figure. It's Microsoft; they
count weird: 3, NT, 98, ME, 2000, XP, Vista, 7, 8, 10, 9, 37...)

And besides, I thought Windows was written in C, not C++? MS's hacks
got tired of implementing vectors and linked lists from scratch,
over and over, and harangued MS for access to the STL and classes
until they finally relented?

For that matter, why isn't MS writing Windows in C#? Their own damn
language not good enough for them? Throw C# to the plebes, but do all
the REAL programming behind the scenes with a REAL programming language?
So it would seem.

/somewhat_off_topic_rant



This may help:

https://social.technet.microsoft.com...10itprogeneral
--


Bob S.

Robbie Hatley wrote:

I've been noticing many copies of the following error in my
Application Log (Event Viewer\Windows Logs\Application) lately
(Windows 10 on a circa-2012 Asus notebook computer running
an intel core i5 CPU):

Intel(R) Dynamic Platform and Thermal Framework: ESIF(8.2.11003.3588)
TYPE: ERROR MODULE: DPTF TIME 43646 ms
DPTF Build Version: 8.2.11003.3588
DPTF Build Date: Jan 10 2017 09:52:34
Source File: ..\..\..\..\Sources\Policies\
ConfigTdpPolicy\ConfigTdpPolicy.cpp @ line 191
Executing Function:
ConfigTdpPolicy:nDomainPowerControlCapabilityCha nged
Message: Expected binary data size mismatch. (PPSS)
Participant: TCPU [0]
Domain: PKG [0]
Policy: ConfigTDP Policy [0]

I have no clue what that gibberish means. Is this something important,
or something I can safely ignore?


somewhat_off_topic_rant

Also, why is Microsoft taunting me with tidbits from their own damn
C++ source code??? I thought Microsoft Windows (all versions) has
always been "closed source"? Since I can't access MS's source, why
is MS throwing pieces of it in my face? It's not like I can look it
up or debug/repair/rebuild their OS for them. They'll have to do that
themselves if/when Windows 11 comes out. (Unless they decide to
release Windows 9 first. That would figure. It's Microsoft; they
count weird: 3, NT, 98, ME, 2000, XP, Vista, 7, 8, 10, 9, 37...)

And besides, I thought Windows was written in C, not C++? MS's hacks
got tired of implementing vectors and linked lists from scratch,
over and over, and harangued MS for access to the STL and classes
until they finally relented?

For that matter, why isn't MS writing Windows in C#? Their own damn
language not good enough for them? Throw C# to the plebes, but do all
the REAL programming behind the scenes with a REAL programming language?
So it would seem.

/somewhat_off_topic_rant

Those messages are coming from Intel driver code.

Check Device manager ("devmgmt.msc" or right-click Start and
it's in the menu).

Probably down in System Devices, you might find
something like this.

Intel Dynamic Platform and Thermal Framework

I don't think my desktop would have one of those, because
my desktop only has "TDP" not "TDP and SDP" like mobile
designs. SDP is "Scenario Design Power" and is a power
limit selected for the device, so the chassis doesn't
overheat.

You can see here, that at least some information and programming,
is coming across from a BIOS ACPI table of some sort.

https://software.intel.com/en-us/art...ramework-intel

That article doesn't really tell you a lot. You might
have to look for a Linux article, to get some tech info.

Here is my search string, to see what the Linux folks know:

Dynamic Platform and Thermal Framework coreboot

I used the word CoreBoot, because that's the open source
attempt to build a BIOS design for computers. A number of
people have replaced their OEM BIOS with a CoreBoot BIOS,
but it requires a rocket scientist skill set.

https://github.com/intel/dptf

There are two contributors to this. The work the OEM
did in designing the BIOS table with the values in it.
And the Intel driver, that responds to sensor feedback,
and adjusts how long the processor can stay boosted.

One comment I could find, suggested the problems started
showing in Windows 10, after a certain OS Upgrade. Which might
be because they started shipping a different Intel driver.

1) You could change the BIOS version. Make sure the
BIOS tools offered allow "revert" to a previous version!
While normally OEM BIOS are pretty good (no need to revert),
this DPTF stuff has caused grief (instability) on a few
different platforms. And it could be that a newer BIOS
might "overfix" things.

2) You could look for a newer Intel driver. Typically, because
this sucker is an ACPI object based driver, you start with the
OEM making the laptop or tablet (Dell) and see if they have
a driver package on their site. Once you know what kind of
package it is, it will make a trip to downloadcenter.intel.com
a bit easier. I don't really know if Intel considers this driver
to be a CPU driver or a PCH driver. I doubt typing DPTF into
the downloadcenter Search will find it, and you might need some
other sort of identifier out of the Dell driver, to help you
track down a later (Intel site provided) driver.

3) I doubt an OS patch is going to help. About the only
contribution Microsoft would be making, is "gluing"
the two subsystems together (ACPI communications to Intel driver).
Maybe at one time, an older version of Windows 10 didn't pass the
info, or maybe DPTF was nullified.

In any event, yes, computers are fun sometimes. There's nothing
like exposing the customer to "how thermals work" on their machine :-/
And making them chase down all sorts of obscure details. I wonder if any
of their tech support people ever got a handle on this stuff ?

Patching the Intel driver won't help, if an ACPI table has
malformed data that the Intel driver isn't parsing properly.
But how do you prove the BIOS is at fault ?

And if this is robbing your machine of compute power, you
definitely want to fix this. If the machine seems to be working
OK, then fixing it right away might not be as important.

In Linux, you can dump ACPI tables, but I don't know if DPTF
is a standard table or not.

Paul

On 3/25/2018 9:40 PM, Bob_S wrote:

This may help:

https://social.technet.microsoft.com/Forums/en-US/
f3964e2b-84e6-4456-8963-4b30fb75407a/intel-dynamic-platform-and-
thermal-framework-error-computer-shutting-down?forum=win10itprogeneral


Ah, yes, that sounds familiar, especially the part about
"sudden shutdown". Just last night, I'd forgotten to plug-in
my power supply, and a couple hours later, the system suddenly
jumped to cold shutdown. The OS didn't shut down, mind you,
the screen just suddenly went black, the HD made a "shhh-clink"
sound of the heads parking, and the fan & HD spun down to 0RPM.
Probably an out-of-date driver.


--
Cheers,
Robbie Hatley
Midway City, CA, USA
perl -E 'say "\154o\156e\167o\154f\100w\145ll\56c\157m";'
http://www.well.com/user/lonewolf/
https://www.facebook.com/robbie.hatley

On 3/25/2018 7:59 PM, KenW wrote:

Doubt if you will have any luck with Asus, but look for updated Intel
drivers on their site.

Thanks. I was able to download some driver zips from Asus for this
model. I'm not sure if one of them is the "thermal" thing, but
I'll find out.


--
Cheers,
Robbie Hatley
Midway City, CA, USA
perl -E 'say "\154o\156e\167o\154f\100w\145ll\56c\157m";'
http://www.well.com/user/lonewolf/
https://www.facebook.com/robbie.hatley

Paul wrote:
And besides, I thought Windows was written in C, not C++? MS's hacks
got tired of implementing vectors and linked lists from scratch,
over and over, and harangued MS for access to the STL and classes
until they finally relented?

For that matter, why isn't MS writing Windows in C#? Their own damn
language not good enough for them? Throw C# to the plebes, but do all
the REAL programming behind the scenes with a REAL programming language?
So it would seem.


Some of the code for the Windows Live Platform programs, backend online
cloud services, mobile, Store, Windows apps, and cloud integration to
Windows is in C++.

--
....w¡ñ§±¤ñ
msft mvp 2007-2016, insider mvp 2016-2018