diff --git a/reports/2026-09-14-system-stability-diagnostic-notes.yaml b/reports/2026-09-14-system-stability-diagnostic-notes.yaml new file mode 100644 index 0000000..42eb720 --- /dev/null +++ b/reports/2026-09-14-system-stability-diagnostic-notes.yaml @@ -0,0 +1,453 @@ +id: "BEF-2026-09-14-DIAG-001" + +organization: "Beffroi" + +title: "System Stability Investigation — Diagnostic Test Record" +subtitle: "Windows repair, storage, memory, CPU and graphics validation — internal technical notes" + +report_type: technical +theme: default + +status: "open" +severity: "medium" + +metadata: + Date: "2026-09-14" + Device: "DESKTOP-DH4HOT6" + Platform: "ASUS GA402RJ" + BIOS: "American Megatrends International, LLC. GA402RJ.318 — 2023-03-09" + OS: "Windows 11 Pro — 10.0.26200 / build 26200" + SystemDrive: "Micron_2450_MTFDKBA1T0TFK — 953.87 GiB NVMe SSD" + Graphics: "AMD Radeon(TM) Graphics + AMD Radeon RX 6700S" + GraphicsDriver: "32.0.21045.5002 — 2026-08-17" + Author: "Maximilien Rigaut" + Purpose: "Internal diagnostic notes; not intended as hierarchy-facing incident synthesis" + +summary: > + A structured diagnostic session was performed on 2026-09-14 following the + earlier investigation into hard freezes, shutdown anomalies and firmware / + NVRAM-related warnings. Windows component-store corruption and protected + system-file corruption were confirmed and successfully repaired. Subsequent + integrity, filesystem, memory, CPU and initial graphics tests completed + without reproducing a freeze and without producing relevant storage, WHEA or + display-driver errors. The system drive currently reports Healthy / OK and + NTFS reports no filesystem errors or bad sectors. Windows Memory Diagnostic + reported no memory errors. CPU WinSAT and Desktop Window Manager graphics + WinSAT completed normally. A sustained discrete-GPU test has not yet been + performed. The root cause of the historical freezes therefore remains + unproven. + +timeline: + - time: "12:13" + event: "Baseline system inventory" + notes: > + Windows reported Windows 11 Pro 10.0.26200, build 26200. At this point + LastBootUpTime was 2026-09-04 17:27:40. + + - time: "12:13" + event: "Firmware inventory" + notes: > + BIOS identified as American Megatrends International, LLC. GA402RJ.318, + release date 2023-03-09. + + - time: "12:13" + event: "Storage inventory" + notes: > + Windows exposed one physical disk: Micron_2450_MTFDKBA1T0TFK, NVMe SSD, + approximately 953.87 GiB usable, HealthStatus Healthy and + OperationalStatus OK. + + - time: "~12:15" + event: "Current storage/WHEA event review" + notes: > + No disk, stornvme, Ntfs, volmgr or WHEA-Logger events were returned for + the current boot interval. + + - time: "~12:20" + event: "NVMe reliability telemetry review" + notes: > + Get-StorageReliabilityCounter reported temperature 47 C, historical + maximum 83 C, wear 0, maximum read latency 550 ms, maximum write latency + 861 ms. Windows did not expose read/write error counters or power-on + hours for this device. + + - time: "~12:25" + event: "DISM component-store repair" + notes: > + DISM /Online /Cleanup-Image /RestoreHealth completed at 100 percent with + "The restore operation completed successfully" and "The operation + completed successfully." + + - time: "~12:29" + event: "SFC repair" + notes: > + sfc /scannow reported that Windows Resource Protection found corrupt + files and successfully repaired them. + + - time: "12:30" + event: "Controlled restart" + notes: > + System restarted normally. Windows subsequently reported + LastBootUpTime 2026-09-14 12:30:11. + + - time: "~12:31" + event: "Post-repair event review" + notes: > + Only DistributedCOM Event 10016 warnings and two Kernel-PnP Event 219 + WUDFRd warnings were observed in the supplied boot-time event output. + No disk, NVMe, NTFS, WHEA or Kernel-Power failure was observed in that + output. + + - time: "~12:32" + event: "Post-repair SFC verification" + notes: > + sfc /verifyonly completed successfully and reported no integrity + violations. + + - time: "~12:35" + event: "Online NTFS scan" + notes: > + chkdsk C: /scan completed successfully. Windows reported no filesystem + problems, no further action required, 0 bad file records and 0 KB in bad + sectors. + + - time: "13:08" + event: "Windows Memory Diagnostic result" + notes: > + Microsoft-Windows-MemoryDiagnostics-Results Events 1201 and 1101 both + reported that the computer's memory was tested and no errors were + detected. + + - time: "13:21-13:23" + event: "CPU WinSAT assessment" + notes: > + winsat cpuformal completed normally in approximately 81.76 seconds. + No crash, freeze or relevant system event was observed during or + immediately following the assessment. + + - time: "~13:25" + event: "Graphics inventory" + notes: > + Windows reported AMD Radeon(TM) Graphics and AMD Radeon RX 6700S, both + with Status OK and driver version 32.0.21045.5002 dated 2026-08-17. + Both display devices also reported PnP status OK. + + - time: "~13:25" + event: "Recent graphics event review" + notes: > + No Display, amdwddmg or nvlddmkm provider events were returned from the + previous 14 days by the supplied query. + + - time: "13:26-13:27" + event: "Desktop graphics WinSAT assessment" + notes: > + winsat dwmformal completed normally. Desktop graphics performance test + ran for approximately 10.47 seconds and reported video memory throughput + of 23540.20 MB/s. No relevant display or AMD event followed the test. + + - time: "13:27" + event: "Attempted WinSAT D3D assessment" + notes: > + winsat d3dformal did not execute because the assessment name is not valid + on the installed Windows version. This is recorded as a test-command + limitation, not a system failure. + +findings: + - title: "Windows component-store corruption" + severity: "medium" + status: "repaired" + evidence: > + The previously identified repairable component store was repaired with + DISM /Online /Cleanup-Image /RestoreHealth. DISM completed successfully. + assessment: > + This was a genuine Windows integrity issue. It is now repaired. It may + have contributed to instability, but the available evidence does not + establish whether it caused the historical hard freezes or resulted from + previous forced shutdowns. + + - title: "Protected Windows system-file corruption" + severity: "medium" + status: "repaired" + evidence: > + Following DISM, sfc /scannow found corrupt files and successfully + repaired them. After restart, sfc /verifyonly reported no integrity + violations. + assessment: > + The repair has been validated after reboot. Windows system-file integrity + is currently clean. + + - title: "System NVMe device health" + severity: "info" + status: "currently-normal" + evidence: > + Micron_2450_MTFDKBA1T0TFK reports HealthStatus Healthy and + OperationalStatus OK. Reliability telemetry reports wear 0, current + temperature 47 C and historical maximum temperature 83 C. No current + boot-session disk, stornvme, Ntfs, volmgr or WHEA-Logger events were + returned by the supplied query. + assessment: > + There is currently no direct evidence of an actively failing system NVMe + device. The historical maximum temperature is worth retaining in the + record but does not by itself demonstrate failure. + + - title: "Historical storage errors require device attribution" + severity: "medium" + status: "open" + evidence: > + Historical logs reviewed during this session contain disk Event 51 + paging errors, disk Event 11 controller errors and NTFS Event 50 delayed + write failures against \Device\Harddisk1\DRx paths. The currently + enumerated internal Micron system drive is Disk 0 and only one physical + disk is presently visible. + assessment: > + Historical Harddisk1 errors must not be automatically attributed to the + current Micron NVMe. They may have involved a second, removable or + external storage device. Device attribution remains unresolved. + + - title: "NTFS filesystem integrity" + severity: "info" + status: "confirmed-clean" + evidence: > + chkdsk C: /scan found no problems. It reported 0 bad file records and + 0 KB in bad sectors, with no further action required. + assessment: > + No offline CHKDSK repair or sector scan is presently justified by the + available filesystem evidence. + + - title: "System memory" + severity: "info" + status: "test-passed" + evidence: > + Windows Memory Diagnostic completed and Events 1201 and 1101 both state + that the computer's memory was tested and no errors were detected. + assessment: > + No memory fault was detected by the Windows diagnostic. This lowers the + priority of RAM as an explanation for the freezes, while not excluding + rare or workload-specific intermittent faults. + + - title: "CPU stability under WinSAT workload" + severity: "info" + status: "test-passed" + evidence: > + winsat cpuformal completed all CPU compression, encryption and hashing + assessments in approximately 81.76 seconds without freeze, restart or + relevant error event. + assessment: > + No CPU instability was reproduced by this short controlled workload. + This is not equivalent to a long-duration thermal or power stress test. + + - title: "Graphics device enumeration and initial graphics test" + severity: "info" + status: "initial-test-passed" + evidence: > + AMD Radeon(TM) Graphics and AMD Radeon RX 6700S both report status OK. + Both use AMD driver 32.0.21045.5002 dated 2026-08-17. winsat dwmformal + completed successfully with 23540.20 MB/s video-memory throughput and no + relevant display/AMD event observed afterward. + assessment: > + Basic desktop graphics acceleration is functioning. This test is too + short and too light to clear the discrete GPU, graphics power delivery, + thermals or hybrid-GPU transitions as possible intermittent causes. + + - title: "Background DCOM warnings" + severity: "info" + status: "observed" + evidence: > + Repeated Microsoft-Windows-DistributedCOM Event 10016 warnings were + present after restart and during later testing. + assessment: > + These warnings are retained for traceability but are not currently + considered explanatory for the hard-freeze symptom. + + - title: "Kernel-PnP WUDFRd warnings" + severity: "low" + status: "observed" + evidence: > + Two Kernel-PnP Event 219 warnings were observed immediately after the + controlled restart, including HID\VID_0B05&PID_19B6&MI_01 and + ROOT\WINDOWSHELLOFACESOFTWAREDRIVER\0000, both with status 0xC0000365. + assessment: > + No direct link to the freeze has been established. Retain for comparison + if future freezes correlate with device initialization or power-state + transitions. + + - title: "Machine identity discrepancy with September 4 reports" + severity: "high" + status: "open" + evidence: > + The reports currently stored for the 2026-09-04 investigation identify + DESKTOP-SAU019H, PC Specialist / Clevo hardware, Insyde firmware and an + Intel/NVIDIA configuration. The device tested on 2026-09-14 identifies + as DESKTOP-DH4HOT6 with ASUS GA402RJ firmware, AMD integrated graphics + and AMD Radeon RX 6700S. + assessment: > + These records cannot safely be treated as one hardware inventory without + reconciliation. Either the September 14 session is being performed on a + different affected machine, the earlier reports contain mixed-machine + data, or the investigation thread has combined separate incidents. This + discrepancy should be resolved before using historical device-specific + conclusions such as RaidPort2, Clevo BIOS or Intel/NVIDIA observations + to guide remediation on the current ASUS system. + +sections: + - title: "Commands and results — Windows integrity" + content: + - type: bullets + items: + - > + DISM /Online /Cleanup-Image /RestoreHealth — completed at 100%; + restore operation completed successfully. + - > + sfc /scannow — found corrupt files and successfully repaired them. + - > + Controlled restart — successful; new boot time + 2026-09-14 12:30:11. + - > + sfc /verifyonly after restart — no integrity violations. + + - title: "Commands and results — storage" + content: + - type: bullets + items: + - > + Get-PhysicalDisk / Get-Disk — one Micron 2450 1 TB-class NVMe + device, Healthy / OK. + - > + Get-StorageReliabilityCounter — 47 C current, 83 C maximum, + wear 0, read latency max 550 ms, write latency max 861 ms. + - > + Current-boot event review — no disk, stornvme, Ntfs, volmgr or + WHEA-Logger events returned. + - > + chkdsk C: /scan — no filesystem problems, 0 KB bad sectors, + no further action required. + + - title: "Commands and results — memory" + content: + - type: bullets + items: + - > + Windows Memory Diagnostic — completed successfully. + - > + Event 1201 — memory tested; no errors detected. + - > + Event 1101 — memory tested; no errors detected. + + - title: "Commands and results — CPU" + content: + - type: bullets + items: + - > + winsat cpuformal — completed normally in 00:01:21.76. + - > + Representative results: CPU LZW 1171.05 MB/s; AES256 + 15944.45 MB/s; Vista compression 3029.33 MB/s; SHA1 + 10319.55 MB/s. + - > + No hardware, WHEA, storage or driver failure was observed in the + supplied event review following the test. + + - title: "Commands and results — graphics" + content: + - type: bullets + items: + - > + Win32_VideoController — AMD Radeon(TM) Graphics and AMD Radeon + RX 6700S, both Status OK. + - > + Get-PnpDevice -Class Display — both display devices Status OK. + - > + Driver version for both adapters: 32.0.21045.5002 dated + 2026-08-17. + - > + Fourteen-day display-provider query returned no Display, + amdwddmg or nvlddmkm events. + - > + winsat dwmformal — completed successfully; video memory + throughput 23540.20 MB/s. + - > + winsat d3dformal — invalid assessment name on this Windows + installation; no test was performed. + + - title: "Interpretation at this checkpoint" + content: + - type: callout + title: "Current state" + kind: "info" + text: > + The system has not frozen during the controlled 2026-09-14 test + sequence. Windows corruption was real and has been repaired, but + there is presently insufficient evidence to conclude that it was the + sole root cause of the historical freezes. + + - type: bullets + items: + - "No active storage failure has been demonstrated." + - "No filesystem corruption remains after repair." + - "No memory fault was detected by Windows Memory Diagnostic." + - "No CPU instability was reproduced by WinSAT." + - "Initial graphics acceleration testing passed." + - "A sustained discrete-GPU workload has not yet been performed." + - "Combined CPU/GPU thermal and power-load testing has not yet been performed." + - "Firmware/NVRAM retention testing remains outstanding." + - "Historical TPM / Measured Boot findings have not yet been revalidated on this specific hardware identity." + +actions_title: "Recommended continuation" + +actions: + - title: "Reconcile machine identity" + status: "pending" + text: > + Confirm whether DESKTOP-DH4HOT6 / ASUS GA402RJ is the same intended + incident target as the 2026-09-04 reports describing DESKTOP-SAU019H / + PC Specialist-Clevo. If separate machines are involved, separate their + diagnostic records and avoid carrying device-specific conclusions + between them. + + - title: "Perform sustained discrete-GPU test" + status: "pending" + text: > + Exercise the Radeon RX 6700S under a controlled sustained 3D workload + while connected to the normal AC adapter and using the normal power / + GPU profile. Record start and end timestamps, temperatures if available, + and any freeze, artifact, driver reset, black screen or unexpected + restart. + + - title: "Review events after GPU workload" + status: "pending" + text: > + Inspect System and Application logs immediately after the GPU test for + Display, AMD, amdwddmg, WHEA-Logger, Kernel-Power and related events. + + - title: "Perform combined power and thermal test" + status: "pending" + text: > + If the discrete-GPU test is stable, proceed to a controlled combined + CPU/GPU workload. The purpose is to exercise cooling, platform power + delivery and shared thermal limits rather than benchmark performance. + + - title: "Test firmware/NVRAM retention" + status: "pending" + text: > + Record BIOS date/time and relevant settings, perform a complete shutdown + and unpowered interval, then verify that firmware state remains intact. + Record whether the previous NVRAM warning recurs. + + - title: "Correlate any future freeze" + status: "pending" + text: > + If another hard freeze occurs, record the exact wall-clock time before + forcing power off. After recovery, inspect approximately five minutes on + either side of the incident for WHEA, display-driver, storage, + Kernel-Power, device-init and power-management events. + +closing: > + The 2026-09-14 diagnostic session establishes a substantially cleaner + software and filesystem baseline than the earlier investigation. Windows + corruption was found and repaired, and all completed post-repair validation + tests passed without reproducing the hard freeze. The investigation remains + open because no test has yet reproduced the original symptom and sustained + discrete-GPU, combined thermal/power and firmware-retention testing remain + outstanding. Before device-specific historical conclusions are reused, the + discrepancy between the September 4 Clevo inventory and the September 14 + ASUS GA402RJ inventory must be reconciled. \ No newline at end of file