reportist/plugins/diagnostics/renderer/rules.yaml

385 lines
25 KiB
YAML
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# WinDiagnostics interpretation rules.
# Add or revise entries here as new event providers and IDs are understood.
event_rules:
- provider: "Microsoft-Windows-WER-SystemErrorReporting"
id: "1001"
severity: "critical"
confidence: 100
rationale: "Windows reports a reboot following a kernel bugcheck. The stop code and saved dump are evidence of a crash, but do not identify the responsible driver or hardware on their own."
resolution_steps:
- "Preserve the referenced minidump and the System event log."
- "Open the dump in WinDbg and run !analyze -v; review the bugcheck parameters and stack before attributing the crash to a component."
- "Correlate the crash with nearby storage, device, and driver events. Apply targeted OEM driver or firmware fixes supported by the dump analysis."
- "Reproduce the original workload and verify that no new bugcheck occurs in a subsequent capture."
reference_url: "https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2"
reference_label: "Microsoft bugcheck reference"
- provider: "volmgr"
id: "162"
severity: "info"
confidence: 100
rationale: "The collector message records successful crash-dump generation. This is supporting crash evidence, not an additional storage failure."
remediation: "Preserve the dump and investigate the associated bugcheck."
- provider: "stornvme"
id: "11"
severity: "critical"
confidence: 92
rationale: "Storage controller path reported an I/O controller error."
remediation: "Back up important data first. Identify the disk behind the reported port, then update its firmware and the OEM storage/chipset driver. Recheck disk health and confirm Event 11 does not return under normal load."
- provider: "Microsoft-Windows-TPM-WMI"
id: "1040"
severity: "critical"
confidence: 85
rationale: "Pre-attestation health checks reported a critical component failure."
remediation: "Inspect the referenced MeasuredBoot JSON and install applicable OEM BIOS or TPM firmware updates. Do not clear the TPM unless recovery keys are backed up and the failed check specifically requires it."
- provider: "Service Control Manager"
id: "7000"
fading: true
severity: "warning"
confidence: 90
rationale: "A configured service or driver failed to start."
remediation: "Identify the named service, verify that its executable path exists, then repair, update, or remove the owning application or driver. Reboot and confirm the service starts without a new Event 7000."
reference_url: "https://learn.microsoft.com/en-us/troubleshoot/windows-client/setup-upgrade-and-drivers/system-log-event-id-7000-7026"
reference_label: "Microsoft Event 7000 guidance"
- provider: "Service Control Manager"
id: "7009"
fading: true
severity: "warning"
confidence: 82
rationale: "A service did not connect before the Service Control Manager timeout."
remediation: "Identify and update or repair the named service first. Check its dependencies and startup behavior; only consider changing the service timeout when the service is healthy but consistently needs longer to initialize."
- provider: "Microsoft-Windows-NDIS"
id: "10317"
severity: "warning"
confidence: 78
rationale: "A network miniport failed a transition to operational power; review the adapter driver and power management if connectivity symptoms correlate."
remediation: "Install the current OEM network driver, reboot, and retest sleep/resume. If the event correlates with connectivity loss, review the adapter's Power Management settings before changing them."
reference_url: "https://learn.microsoft.com/en-us/windows-hardware/drivers/network/how-ndis-sets-the-power-policy-for-a-network-adapter"
reference_label: "Microsoft NDIS power-policy guidance"
- provider: "Application Error"
id: "1000"
fading: true
severity: "warning"
confidence: 75
rationale: "An application terminated unexpectedly; assess the named application, module, and exception code."
remediation: "Update or repair the named application and its related driver or module, then reproduce the original workflow. Consider it dealt with after the application remains stable and no matching Event 1000 recurs."
- provider: "Microsoft-Windows-WindowsUpdateClient"
id: "20"
fading: true
severity: "warning"
confidence: 88
rationale: "An update installation failed."
remediation: "Restart Windows, retry the named update, and confirm it installs successfully. If failures persist, repair DISM/SFC findings first and retry Windows Update afterward."
- provider: "Application Hang"
id: "1002"
fading: true
severity: "warning"
confidence: 70
rationale: "An application stopped responding and was closed."
- provider: "MsiInstaller"
id: "1043"
fading: true
severity: "warning"
confidence: 80
rationale: "Windows Installer could not finish a transaction."
remediation: "Retry the named installer after a reboot. If it fails again, repair or uninstall the affected application using its supported installer and inspect the installer log for the recorded error code."
- provider: "Volsnap"
id: "36"
severity: "warning"
confidence: 82
rationale: "A volume shadow-copy operation was aborted."
remediation: "Run vssadmin list shadowstorage from an elevated terminal and check the configured limit and free disk space. Increase the limit only if backups or restore points require it, then verify a new shadow copy succeeds."
- provider: "Service Control Manager"
id: "7043"
fading: true
severity: "warning"
confidence: 75
rationale: "A service did not shut down cleanly."
remediation: "Update or repair the application that owns the named service, then perform a normal shutdown and confirm the event does not recur."
- provider: "Microsoft-Windows-DistributedCOM"
id: "10010"
severity: "info"
confidence: 65
rationale: "A DCOM registration timeout is usually contextual unless repeated or correlated with symptoms."
remediation: "No cleanup is normally required for an isolated occurrence. Investigate the referenced component only if the event repeats or matches a user-visible failure."
- provider: "EventLog"
id: "6008"
severity: "warning"
confidence: 95
rationale: "Windows recorded that the previous shutdown was unexpected; this confirms an unclean stop but does not identify its cause."
remediation: "Ask whether power was removed or the machine was forcibly restarted. If not, correlate the same timestamp with Kernel-Power Event 41, bug-check Event 1001, hardware errors, thermal history, and recently changed drivers or updates."
reference_url: "https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-unexpected-reboots-system-event-logs"
reference_label: "Microsoft unexpected-reboot investigation"
- provider: "Service Control Manager"
id: "7023"
fading: true
severity: "warning"
confidence: 88
rationale: "A service terminated and returned an error; impact depends on the named service and whether its function is needed."
remediation: "Identify the owning application or driver for the named service, update or repair it, then restart the service or reboot. Confirm the service remains running and Event 7023 does not recur."
- provider: "MsiInstaller"
id: "11704"
fading: true
severity: "warning"
confidence: 92
rationale: "Windows Installer reported a suspended installation that blocked another product transaction."
remediation: "Finish or roll back the suspended installation, reboot if requested, and retry the affected installer. Confirm that both products complete without another installer event."
- provider: "MsiInstaller"
id: "11722"
fading: true
severity: "warning"
confidence: 92
rationale: "A program executed by an MSI package did not complete as expected, so the installation was not successful."
remediation: "Reboot and retry the named product's current supported installer. If it fails again, collect a verbose MSI log and repair or remove the affected product before retrying."
- provider: "VSS"
id: "12344"
severity: "warning"
confidence: 82
rationale: "A Volume Shadow Copy writer failed during its freeze operation; backups or restore points near that time may be incomplete."
remediation: "Run vssadmin list writers from an elevated terminal and identify any failed writer. Reboot or restart the owning service, verify system and registry health, then create and validate a new shadow copy or backup."
- provider: ".NET Runtime"
id: "1022"
severity: "info"
confidence: 80
rationale: "The process could not initialize profiler-attach support; this is normally contextual unless diagnostics, monitoring, or profiling was expected for that process."
remediation: "No action is normally required. If a profiler or monitoring agent was expected, update or repair that agent and reproduce the attach operation."
- provider: "Waterfox Default Browser Agent"
id: "5"
severity: "info"
confidence: 55
rationale: "The captured event has no message, so it provides no actionable evidence by itself."
remediation: "No action is recommended from this empty event alone. Update or repair Waterfox only if browser-default handling is visibly failing or the event repeatedly correlates with a symptom."
# Additional provider/ID pairs observed in the SAURON capture.
- provider: "Microsoft-Windows-Kernel-Boot"
id: "29"
severity: "warning"
confidence: 92
rationale: "Windows failed Fast Startup; the status and adjacent shutdown events do not establish the underlying cause."
remediation: "Compare a normal Restart with shutdown/startup. Test with Fast Startup disabled through Power Options, then review firmware and drivers if failures recur. Preserve adjacent shutdown and bug-check events."
- provider: "Service Control Manager"
id: "7031"
severity: "warning"
confidence: 95
rationale: "A service terminated unexpectedly; Windows may schedule a recovery action."
remediation: "Identify each named service and correlate application crashes at the same time. Repair the owning component and verify the service stays running after restart."
- provider: "Microsoft-Windows-DeviceAssociationService"
id: "3505"
severity: "warning"
confidence: 70
rationale: "Device association failed while enumerating pairing ceremonies; the message does not identify a failed hardware component."
remediation: "Check whether device pairing actually fails. Identify the affected peripheral, retry pairing, and review its driver and device-association logs if reproducible."
- provider: "Microsoft-Windows-HAL"
id: "15"
severity: "warning"
confidence: 90
rationale: "The IOMMU reported an error. The raw device identifier alone does not identify the graphics adapter or prove physical hardware failure."
remediation: "Preserve the full event XML and map the device to its PCI location before blaming a component. Review OEM firmware and chipset/device drivers and correlate recurrence with device activity. Keep DMA protection enabled."
- provider: "Microsoft-Windows-HAL"
id: "21"
severity: "warning"
confidence: 90
rationale: "The ACPI time/alarm method failed while Windows attempted to set the hardware real-time clock."
remediation: "Check firmware time and Windows time synchronization after reboot. Review applicable OEM BIOS fixes and retest shutdown/resume. This event alone does not diagnose a dead CMOS battery."
- provider: "usbaudio2"
id: "38"
severity: "warning"
confidence: 90
rationale: "A USB audio control request failed."
remediation: "Identify the USB audio device, reconnect it directly, and test another port or cable. Review device firmware/drivers and confirm normal playback or recording without recurrence."
- provider: "ESENT"
id: "419"
severity: "critical"
confidence: 95
rationale: "The database engine could not read a database page. Inspect the recorded error; -1018 indicates a checksum/read-verification failure."
remediation: "Back up important data and preserve the event/database context. Check storage and memory stability, then use the owning application’s supported recovery procedure. Verify that the database can be read and the workload succeeds."
reference_url: "https://learn.microsoft.com/en-us/windows/win32/extensible-storage-engine/jet-err-enumeration"
reference_label: "Microsoft database error definitions"
- provider: "ESENT"
id: "474"
severity: "critical"
confidence: 98
rationale: "A database page failed checksum verification. This confirms corruption in the read data but does not isolate disk, RAM, CPU, driver, or power as the cause."
remediation: "Back up important data. Check storage health and run memory diagnostics at stock settings. Repair the affected database through its owning component only after investigating stability, then verify the failed workload and absence of new checksum errors."
reference_url: "https://learn.microsoft.com/en-us/windows/win32/extensible-storage-engine/jet-err-enumeration"
reference_label: "Microsoft database error definitions"
- provider: "ESENT"
id: "907"
severity: "critical"
confidence: 95
rationale: "ESENT detected a transient memory problem; this is a stability signal, not proof that a particular RAM module is defective."
remediation: "Back up data and run Windows Memory Diagnostic or OEM memory tests. Retest at stock CPU/RAM settings and review OEM firmware guidance. Investigate CPU, RAM, storage and drivers if corruption recurs."
reference_url: "https://learn.microsoft.com/en-us/windows/win32/extensible-storage-engine/jet-err-enumeration"
reference_label: "Microsoft database error definitions"
- provider: "ESENT"
id: "908"
severity: "critical"
confidence: 95
rationale: "The database process terminated because of a fatal error. Inspect its error code and enforcement tag and correlate adjacent ESENT events."
remediation: "Preserve the full message and investigate associated checksum/memory errors before retrying the workload. Verify stability and repair the owning component through its supported recovery procedure."
reference_url: "https://learn.microsoft.com/en-us/windows/win32/extensible-storage-engine/jet-err-enumeration"
reference_label: "Microsoft database error definitions"
- provider: "Microsoft-Windows-Defrag"
id: "264"
severity: "warning"
confidence: 92
rationale: "Storage optimization did not complete; the message supplies the reason. An unsupported filesystem is not evidence of a failing disk."
remediation: "Check the named volume and error. For 0x8900002F on exFAT, review optimization scheduling; do not format or convert the volume just to remove this event. Investigate other errors according to their actual cause."
# Reviewed against the native schema 2 capture and linked vendor guidance.
# Entries without a URL interpret the captured message only; no root cause is inferred.
- provider: "Microsoft-Windows-WLAN-AutoConfig"
id: "10002"
severity: "info"
confidence: 85
rationale: "A WLAN extension stopped. This can accompany adapter shutdown or reset; it does not establish a driver defect."
remediation: "Investigate only if wireless loss coincides with this timestamp. Review adjacent adapter errors before changing software."
- provider: "Microsoft-Windows-DistributedCOM"
id: "10016"
severity: "info"
confidence: 90
rationale: "DCOM denied an activation request. Common Windows component instances are expected; this event alone does not establish a fault."
remediation: "Leave COM permissions unchanged unless a reproducible application failure and the affected component require targeted investigation."
reference_url: "https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/event-10016-logged-when-accessing-dcom"
reference_label: "Vendor guidance"
- provider: "Netwtw10"
id: "6062"
severity: "info"
confidence: 60
rationale: "The driver logged an LSO trigger. The message alone does not explain its cause or establish adapter failure."
remediation: "Use adjacent error events and actual connection symptoms; do not change offload settings from this notification alone."
- provider: "Microsoft-Windows-Hyper-V-Hypervisor"
id: "167"
severity: "warning"
confidence: 90
rationale: "The hypervisor reports that VM side-channel mitigations were not enabled with HyperThreading. This is a security configuration signal, not evidence that virtualization caused a crash."
remediation: "Review VM isolation requirements, firmware and applicable Windows mitigation guidance. Verify scheduler and guest settings before deciding whether SMT changes are necessary."
reference_url: "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/about-hyper-v-scheduler-type-selection"
reference_label: "Vendor guidance"
- provider: "volmgr"
id: "161"
severity: "warning"
confidence: 95
rationale: "Windows could not create a crash dump. This reduces crash evidence but does not identify the cause of the crash or prove disk failure."
remediation: "Check dump configuration, pagefile and destination capacity. Preserve any other dumps and correlate the associated bugcheck."
reference_url: "https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/memory-dump-file-options"
reference_label: "Vendor guidance"
- provider: "Microsoft-Windows-WinRM"
id: "10149"
severity: "info"
confidence: 90
rationale: "WinRM is not listening for remote-management requests. This may be intentional."
remediation: "Check listener and service configuration only if remote management is required; do not enable remote access just to remove this event."
reference_url: "https://learn.microsoft.com/en-us/windows/win32/winrm/installation-and-configuration-for-windows-remote-management"
reference_label: "Vendor guidance"
- provider: "winsrvext"
id: "100"
severity: "info"
confidence: 85
rationale: "The named process delayed shutdown. A brief delay does not establish system instability."
remediation: "Investigate the application if shutdown delays recur or visibly affect use."
- provider: "Netwtw10"
id: "5005"
severity: "warning"
confidence: 95
rationale: "The Intel wireless driver reported an internal adapter error and failure."
remediation: "Correlate wireless disconnects, device status and firmware/OEM driver changes. This message does not distinguish driver, firmware and hardware causes."
reference_url: "https://www.intel.com/content/www/us/en/support/articles/000089544/wireless.html"
reference_label: "Vendor guidance"
- provider: "Netwtw10"
id: "5032"
severity: "warning"
confidence: 90
rationale: "The Intel wireless miniport reset watchdog was triggered."
remediation: "Review nearby adapter failure events and retest connectivity and sleep/resume with the OEM-supported configuration."
- provider: "Netwtw10"
id: "5002"
severity: "warning"
confidence: 95
rationale: "The Intel driver reported an adapter malfunction."
remediation: "Inspect the adapter status and correlate loss of connectivity. Review OEM driver and firmware guidance before attributing hardware failure."
reference_url: "https://www.intel.com/content/www/us/en/support/articles/000089544/wireless.html"
reference_label: "Vendor guidance"
- provider: "Netwtw10"
id: "5010"
severity: "warning"
confidence: 95
rationale: "The wireless adapter returned an invalid value to the Intel driver."
remediation: "Preserve recurrent errors and test the OEM-supported wireless configuration. A published fix for another driver version does not prove this capture has that defect."
reference_url: "https://www.intel.com/content/www/us/en/support/articles/000089544/wireless.html"
reference_label: "Vendor guidance"
- provider: "Microsoft-Windows-Perflib"
id: "1008"
severity: "warning"
confidence: 90
rationale: "A performance-counter provider failed to open; counters for that service may be unavailable. This is not a hardware failure diagnosis."
remediation: "Check the named service and whether monitoring is affected. Repair its counter registration only after identifying the provider and preserving the existing configuration."
reference_url: "https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/lodctr"
reference_label: "Vendor guidance"
- provider: "Microsoft-Windows-WMI"
id: "63"
severity: "info"
confidence: 90
rationale: "A WMI provider registered with LocalSystem privileges. The warning describes a privilege boundary, not proof of exploitation or repository corruption."
remediation: "Verify that the provider belongs to expected software. Investigate impersonation or access problems only if independently observed."
reference_url: "https://learn.microsoft.com/en-us/windows/win32/wmisdk/hostingmodel"
reference_label: "Vendor guidance"
- provider: "Microsoft-Windows-Winlogon"
id: "6004"
severity: "warning"
confidence: 80
rationale: "A Winlogon notification subscriber failed a notification. Impact depends on the subscriber and the affected sign-in or servicing operation."
remediation: "Correlate sign-in, shutdown and servicing symptoms with the named subscriber. Preserve adjacent events before attempting repair."
- provider: "Microsoft-Windows-RestartManager"
id: "10010"
severity: "info"
confidence: 85
rationale: "Restart Manager could not restart an application across the reported security identity boundary."
remediation: "If an installer left an application closed, restart it normally in the intended user session; do not change account permissions from this event alone."
- provider: "Microsoft-Windows-Search"
id: "10024"
severity: "warning"
confidence: 85
rationale: "Windows Search terminated a filter host that stopped responding. Indexing or a file-format filter may be affected."
remediation: "Check whether search/indexing fails repeatedly. Identify the file or third-party filter involved before rebuilding the index."
- provider: "Microsoft-Windows-CodeIntegrity"
id: "3116"
severity: "info"
confidence: 95
rationale: "Policy signature metadata was recorded; this message does not report a blocked driver."
remediation: "No repair is indicated by signature metadata alone."
- provider: "Microsoft-Windows-CodeIntegrity"
id: "3099"
severity: "info"
confidence: 95
rationale: "An App Control policy was loaded; activation is not itself a driver failure."
remediation: "Review the policy details only when diagnosing a related block event."
reference_url: "https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/operations/event-id-explanations"
reference_label: "Vendor guidance"
- provider: "Microsoft-Windows-CodeIntegrity"
id: "3085"
severity: "info"
confidence: 90
rationale: "WHQL signing requirements were not enforced for this boot. This does not mean all signature checks or memory integrity are disabled."
remediation: "Review intended signing policy if required; this event alone does not justify changing boot security."
reference_url: "https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/operations/event-id-explanations"
reference_label: "Vendor guidance"
- provider: "Microsoft-Windows-CodeIntegrity"
id: "3076"
severity: "warning"
confidence: 95
rationale: "App Control audit policy would have blocked a file; audit mode did not block it."
remediation: "Identify the file, signer and policy. Review trust and compatibility before changing enforcement."
reference_url: "https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/operations/event-id-explanations"
reference_label: "Vendor guidance"
- provider: "Microsoft-Windows-CodeIntegrity"
id: "3077"
severity: "warning"
confidence: 95
rationale: "App Control blocked a file that did not satisfy its policy."
remediation: "Identify the file and owning software, verify its signature and obtain a supported replacement. Preserve security enforcement."
reference_url: "https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/operations/event-id-explanations"
reference_label: "Vendor guidance"
unknown_event_severity: "unanalysed"