GABRIEL · PERSONAL EQUIPMENT OBSERVATION
Open the software scanner for disk and process observations
Start continuous local monitoring on your HP laptop
Investigate the delay. Try one correction. Check the outcome.
This page reviews CPU and memory readings from your own Windows laptop. Files are processed in this page’s memory and are not uploaded or saved by this page. Reloading clears them.
This personal test is separate from the nine company pilots. It establishes no company acceptance, live connection, electrical measurements or equipment control.
Next: collect a before recording in PowerShell, then choose that file in step 2.
Your corrective trial
Describe one slow task, collect its starting readings, then test one reversible change. Gabriel guides the trial; you operate your applications.
Cause identification needs process or page evidence. These aggregate readings do not establish why the task is slow.1 · Collect a recording
Keep PowerShell open. Copy the collector below, paste it into PowerShell, and press Enter. If the continuation prompt remains, press Enter on an empty line. Type before, then use alias MY-LAPTOP-01. Keep applications unchanged for about one minute.
The collector reads CPU activity and available memory and saves a JSON file in your Documents folder. It makes no network requests and changes no settings. Stop with Ctrl+C.
Download collector source2 · Review before the change
Use the exact path printed after “Saved:” in PowerShell. No serial number or account credentials are required.3 · Make one deliberate change, then compare
Save your work and close one unused application normally. Keep Gabriel open. Use the controls below to log your single change. Wait 60 seconds after logging it, run the same collector again, type after, and use the same alias.
Click only after actually closing it. This logs your report; it does not close or verify any application. Existing recordings remain available for comparison, but a corrective trial needs a before collection preceding this action.4 · Check the same task
After reporting faster, use the same task for five minutes. Then choose the follow-up. Leave other applications and settings comparable.
The download includes laptop summaries and your observations. Review it before sharing. This page does not save or upload it.What this test can establish
Gabriel reports the observed time window, CPU activity, available memory, and differences between recordings. Increased load alone is not a fault. A before recording is an observation, not a validated healthy baseline. The beginning of a problem, its responsible process and future propagation remain unknown from these aggregate readings.
Next investigation: compare application memory use in Task Manager and repeat the test under similar conditions. A physical voltage, temperature or wiring investigation needs separate supported measurements.