136 lines
8.2 KiB
YAML
136 lines
8.2 KiB
YAML
# WinDiagnostics interpretation rules.
|
|
# Add or revise entries here as new event providers and IDs are understood.
|
|
event_rules:
|
|
- 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."
|
|
|
|
unknown_event_severity: "unanalysed"
|