ANAVEM
Languagefr
Server cooling system with thermal management components in a professional data center environment
Event ID 98WarningSystemWindows

Windows Event ID 98 – System: Processor Thermal Throttling Event

Event ID 98 indicates processor thermal throttling has occurred due to high CPU temperatures. This system-level event fires when Windows reduces CPU performance to prevent overheating damage.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
18 March 20269 min read 0
Event ID 98System 5 methods 9 min
Event Reference

What This Event Means

Windows Event ID 98 represents a critical thermal management event that occurs when the operating system's thermal management subsystem detects excessive processor temperatures. This event is generated by the Windows kernel's power management framework, specifically the thermal zone management component that continuously monitors CPU die temperatures through built-in thermal sensors.

When processors approach their thermal design power (TDP) limits, Windows implements dynamic frequency scaling and voltage reduction to prevent thermal damage. The thermal throttling mechanism operates at the hardware level but is coordinated by Windows power management policies. Event ID 98 captures these thermal protection activations, providing system administrators with visibility into potential cooling system failures or excessive computational loads.

The event data typically includes processor identification, thermal zone information, throttling duration, and the specific thermal threshold that was exceeded. In enterprise environments, these events often correlate with high-performance computing workloads, inadequate data center cooling, or aging thermal interface materials. Modern processors in 2026 feature more sophisticated thermal management with multiple thermal zones and graduated throttling responses, making Event ID 98 data more detailed than in previous Windows versions.

Understanding this event is crucial for maintaining system reliability, as repeated thermal throttling can indicate impending hardware failures, reduced system lifespan, and performance degradation that affects user productivity and server workloads.

Applies to

Windows 10Windows 11Windows Server 2019/2022/2025
Analysis

Possible Causes

  • CPU cooler failure or inadequate cooling capacity for the processor
  • Thermal paste degradation between CPU and heat sink
  • Blocked or failed case fans reducing airflow
  • High ambient temperatures in server rooms or workstations
  • Dust accumulation on heat sinks and cooling components
  • Overclocking beyond thermal design limits
  • High-intensity computational workloads exceeding cooling capacity
  • Failing thermal sensors providing incorrect temperature readings
  • Power supply issues causing voltage irregularities
  • Malware or runaway processes consuming excessive CPU resources
Resolution Methods

Troubleshooting Steps

01

Check Event Details and System Temperatures

Start by examining the specific Event ID 98 details to understand the thermal throttling context:

  1. Open Event ViewerWindows LogsSystem
  2. Filter for Event ID 98 using the filter option
  3. Double-click the most recent Event ID 98 entry to view detailed information
  4. Note the processor cores affected and throttling duration
  5. Use PowerShell to query recent thermal events:
Get-WinEvent -FilterHashtable @{LogName='System'; Id=98} -MaxEvents 20 | Format-Table TimeCreated, Id, LevelDisplayName, Message -Wrap

Check current system temperatures using built-in Windows tools:

Get-WmiObject -Namespace "root/WMI" -Class MSAcpi_ThermalZoneTemperature | Select-Object InstanceName, CurrentTemperature
Pro tip: Convert the CurrentTemperature value by subtracting 2732 and dividing by 10 to get Celsius readings.
02

Monitor CPU Performance and Power States

Investigate processor performance states and thermal behavior patterns:

  1. Open Performance Monitor (perfmon.exe)
  2. Add counters for Processor Information% Processor Performance
  3. Add Thermal Zone InformationTemperature counters
  4. Monitor for 15-30 minutes during typical workloads
  5. Use PowerShell to check processor power management settings:
powercfg /query SCHEME_CURRENT SUB_PROCESSOR

Check thermal throttling frequency with WMI:

Get-WmiObject -Class Win32_PerfRawData_Counters_ThermalZoneInformation | Select-Object Name, Temperature, ThrottleReasons

Review processor frequency scaling behavior:

Get-Counter "\Processor Information(_Total)\% Processor Performance" -SampleInterval 5 -MaxSamples 12
Warning: Sustained processor performance below 80% during normal loads indicates active thermal throttling.
03

Inspect Hardware and Cooling Systems

Perform physical inspection and hardware diagnostics to identify cooling issues:

  1. Shut down the system safely and inspect internal components
  2. Check CPU cooler mounting and thermal paste condition
  3. Verify all case fans are operational and properly connected
  4. Clean dust from heat sinks, fans, and air intake filters
  5. Use hardware monitoring tools to verify fan speeds:
Get-WmiObject -Namespace "root/OpenHardwareMonitor" -Class Sensor | Where-Object {$_.SensorType -eq "Fan"} | Select-Object Name, Value

Check system power settings that may affect thermal management:

powercfg /query SCHEME_CURRENT SUB_PROCESSOR PROCTHROTTLEMAX

Verify thermal interface and cooling capacity:

  1. Document current CPU temperatures under load
  2. Compare against manufacturer specifications
  3. Consider thermal paste replacement if temperatures exceed 80°C under normal load
  4. Evaluate cooling solution adequacy for current processor TDP
Pro tip: Modern CPUs in 2026 often include built-in thermal monitoring accessible through manufacturer utilities or UEFI firmware.
04

Analyze Process and Workload Impact

Identify processes and workloads contributing to thermal throttling events:

  1. Use Task Manager to identify high CPU usage processes during thermal events
  2. Correlate Event ID 98 timestamps with process activity:
Get-Process | Sort-Object CPU -Descending | Select-Object -First 10 Name, CPU, WorkingSet

Monitor processor usage patterns around thermal events:

$thermalEvents = Get-WinEvent -FilterHashtable @{LogName='System'; Id=98; StartTime=(Get-Date).AddDays(-7)}
foreach ($event in $thermalEvents) {
    Write-Host "Thermal event at: $($event.TimeCreated)"
    Get-WinEvent -FilterHashtable @{LogName='System'; StartTime=$event.TimeCreated.AddMinutes(-5); EndTime=$event.TimeCreated.AddMinutes(5)} | Where-Object {$_.Id -eq 7036 -or $_.Id -eq 7040}
}

Check for malware or runaway processes:

Get-WmiObject Win32_Process | Where-Object {$_.PageFileUsage -gt 100000} | Select-Object Name, ProcessId, PageFileUsage, CreationDate

Review scheduled tasks that may cause thermal spikes:

Get-ScheduledTask | Where-Object {$_.State -eq "Running"} | Select-Object TaskName, TaskPath, State
Warning: Cryptocurrency mining malware often causes sustained high CPU usage leading to thermal throttling.
05

Configure Advanced Thermal Management

Implement advanced thermal management policies and monitoring solutions:

  1. Configure processor power management for thermal optimization:
powercfg /setacvalueindex SCHEME_CURRENT SUB_PROCESSOR PROCTHROTTLEMAX 90
powercfg /setacvalueindex SCHEME_CURRENT SUB_PROCESSOR PROCTHROTTLEMIN 10
powercfg /setactive SCHEME_CURRENT

Set up proactive thermal monitoring with custom PowerShell script:

$thermalThreshold = 85
while ($true) {
    $temp = Get-WmiObject -Namespace "root/WMI" -Class MSAcpi_ThermalZoneTemperature
    $celsiusTemp = ($temp.CurrentTemperature - 2732) / 10
    if ($celsiusTemp -gt $thermalThreshold) {
        Write-EventLog -LogName "Application" -Source "ThermalMonitor" -EventId 1001 -EntryType Warning -Message "High temperature detected: $celsiusTemp°C"
    }
    Start-Sleep 30
}

Configure Windows Event Forwarding for centralized thermal monitoring:

  1. Create custom event subscription for Event ID 98
  2. Set up automated alerts for thermal throttling events
  3. Implement Group Policy settings for thermal management:
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\893dee8e-2bef-41e0-89c6-b55d0929964c" /v "Attributes" /t REG_DWORD /d 2 /f
Pro tip: Windows 11 2026 includes enhanced thermal telemetry that can be integrated with System Center or Azure Monitor for enterprise thermal management.

Overview

Event ID 98 fires when Windows detects that one or more processor cores have exceeded safe operating temperatures, triggering thermal throttling mechanisms. This event appears in the System log and indicates that the CPU has automatically reduced its clock speed and voltage to prevent permanent hardware damage from overheating.

Thermal throttling is a critical safety feature built into modern processors and managed by Windows power management subsystems. When CPU temperatures reach dangerous levels (typically 90-105°C depending on the processor), the system immediately reduces performance to lower heat generation. This event serves as an early warning that your system's cooling solution may be inadequate or failing.

The event typically includes details about which processor cores were affected, the duration of throttling, and the thermal state that triggered the response. System administrators should investigate these events promptly, as sustained thermal throttling can indicate hardware problems that may lead to system instability, reduced performance, or component failure. Modern Windows versions in 2026 include enhanced thermal monitoring capabilities that provide more granular data about processor thermal states.

Frequently Asked Questions

What does Windows Event ID 98 mean and why should I be concerned?+
Event ID 98 indicates that your processor has exceeded safe operating temperatures, forcing Windows to reduce CPU performance to prevent hardware damage. This thermal throttling event is a critical warning that your cooling system may be failing or inadequate. You should be concerned because sustained thermal throttling can lead to reduced system performance, potential hardware damage, and system instability. The event serves as an early warning system that requires immediate investigation to prevent more serious problems.
How can I tell which specific processor cores are affected by thermal throttling?+
The Event ID 98 details in Event Viewer typically include information about which processor cores experienced thermal throttling. You can view this by opening the event properties and examining the event data section. Additionally, use Performance Monitor to add processor-specific thermal counters, or query WMI thermal zone information with PowerShell to get real-time data about individual core temperatures. Modern processors in 2026 provide more granular thermal data through enhanced sensor arrays.
Is thermal throttling the same as overheating, and will it damage my computer?+
Thermal throttling is actually a protective mechanism that prevents overheating damage. When your CPU approaches dangerous temperatures (typically 90-105°C), thermal throttling automatically reduces processor speed and voltage to lower heat generation. While the throttling itself won't damage your computer, the underlying cause - excessive heat - can cause long-term damage if not addressed. Repeated thermal throttling events indicate that your cooling solution is inadequate and should be improved to prevent potential hardware failure.
Can software issues cause Event ID 98, or is it always a hardware problem?+
While Event ID 98 is fundamentally a thermal hardware event, software issues can definitely trigger it. Malware, runaway processes, cryptocurrency mining software, or poorly optimized applications can cause sustained high CPU usage that overwhelms your cooling system. Additionally, incorrect power management settings, outdated drivers, or BIOS/UEFI configuration problems can contribute to thermal issues. Always investigate both software and hardware causes when troubleshooting thermal throttling events.
How often should I expect to see Event ID 98 in normal system operation?+
In a properly functioning system with adequate cooling, you should rarely or never see Event ID 98 during normal operation. Occasional thermal throttling during extreme workloads (like video rendering or scientific computing) might be acceptable, but regular occurrence during typical tasks indicates a problem. If you see Event ID 98 more than once per week during normal use, or multiple times during high-load scenarios, you should investigate cooling system adequacy, dust accumulation, thermal paste condition, or potential software issues causing excessive CPU usage.
Documentation

References (2)

Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...