Windows 10: DPTF ERROR EVENT ID 17

how could I stop this error which is causing a blue screen?ESIF8.7.10200.12510 TYPE: ERROR MODULE: DPTF TIME 1133601 msDPTF Build Version: 8.7.10200.12510DPTF Build Date: Nov 5 2019 18:36:19Source File: c:\jenkins\workspace\dptf\src\dptf\sources\manager\domainworkitem.cpp @ line 79Executing Function: DomainWorkItem::writeDomainWorkItemErrorMessagePolicyMessage: Unhandled exception caught during execution of work itemFramework Event: DomainCreate [17]Participant: STR0 [0]Domain: DFL [0]Policy: Adaptive Performance Policy [0]Exception Function: Policy::bindDomainException Text:

:)

 

Windows 10 Event ID 17, DPTF Application Error

Hello,

I need some information on the subject error. Can anyone tell me what it is and what it might do to the system? MS Support site is LESS than helpful...

Machine Details: Dell Precision 7510 running Windows 10 (all system updates performed). Connected to Dell Docking station with wired Gigabit ethernet connected to ISP Router directly, using IPv4 and static IP setup. Extra Dell 24" HD monitor connected to
docking station to provide 2 screens for viewing.

Symptoms: Main notebook screen goes black. If I react fast enough I am able to quickly go to the windows icon on the attached monitor and shut the system down. If not, the 2nd monitor will start to lose taskbar functionality and I am not able to shut down
(ctrl-alt-del does not function), screen eventually goes black as well then the mouse stops and then disappears... Once I lose ctrl-alt-del and the taskbar, I have to do a hard shutdown of the system and reboot. This is the most likely culprit I can tell
from the event logs... Event log details are as follows:

Log Name: Application

Source: DPTF Logged: 02/05/2019 10:31:10 AM

Event ID: 17 Task Category: None

Level: Error Keywords:

User: LOCAL SERVICE Computer: MyComputer01

OpCode: Info

ESIF(8.4.11000.6436) TYPE: ERROR MODULE: DPTF TIME 228060118 ms

DPTF Build Version: 8.4.11000.6436

DPTF Build Date: Apr 27 2018 16:54:10

Source File: ..\..\..\..\Sources\Policies\PassivePolicy\PassivePolicy.cpp @ line 305

Executing Function: PassivePolicy:nDomainPerformanceControlCapabilityChanged

Message:

DPTF Build Version: 8.4.11000.6436

DPTF Build Date: Apr 27 2018 16:54:10

Source File: ..\..\..\Sources\Manager\EsifServices.cpp @ line 228

Executing Function: EsifServices:rimitiveExecuteSetAsUInt32

Message: Error returned from ESIF services interface function call

Participant: TCPU [0]

Domain: CPU [1]

ESIF Primitive: SET_PERF_PRESENT_CAPABILITY [82]

ESIF Instance: 255

ESIF Return Code: ESIF_E_ACPI_EVAL_FAILURE [1105]

Policy: Passive Policy [3]

 

Windows 10 Event ID 17, DPTF Application Error

Hello, I need some information on the subject error. Can anyone tell me what it is how to fix it?

Nome do Log: Application

Fonte: DPTF

Data: 26/06/2020 23:59:52

Identificação do Evento:17

Categoria da Tarefa:Nenhum

Nível: Erro

Palavras-chave:

Usuário: SERVIÇO LOCAL

Computador: DESKTOP-

Descrição:

ESIF(8.4.11000.6436) TYPE: ERROR MODULE: DPTF TIME 1349713 ms

DPTF Build Version: 8.4.11000.6436

DPTF Build Date: Apr 27 2018 16:54:10

Source File: ..\..\..\..\Sources\Policies\ConfigTdpPolicy\ConfigTdpPolicy.cpp @ line 206

Executing Function: ConfigTdpPolicy:nDomainPowerControlCapabilityChanged

Message:

DPTF Build Version: 8.4.11000.6436

DPTF Build Date: Apr 27 2018 16:54:10

Source File: ..\..\..\Sources\Manager\EsifServices.cpp @ line 539

Executing Function: EsifServices:rimitiveExecuteSetAsTimeInMilliseconds

Message: Error returned from ESIF services interface function call

Participant: TCPU [1]

Domain: PKG [0]

ESIF Primitive: SET_RAPL_POWER_LIMIT_TIME_WINDOW [340]

ESIF Instance: 0

ESIF Return Code: ESIF_E_PRIMITIVE_NOT_FOUND_IN_DSP [2404]

Participant: TCPU [1]

Domain: PKG [0]

Policy: ConfigTDP Policy [1]

 

Event id 17

Hi Joao,

Conflicts with the wireless adapter is one of the possible reasons why you are encountering this issue. We suggest that you follow the troubleshooting steps on this

link that was provided by AndreiV. on October 6, 2016 to resolve the issue.

Should you need further assistance, don't hesitate to get back to us.