A dashboard that fits
Choose up to 16 sensor cards, drag them into place, and follow recent history and alert status. Your layout is there when you return.
Overview / custom layoutsWINDOWS HARDWARE MONITOR
Your hardware,
in view.
CPU, GPU, memory, storage, and network.
One workspace to
see what's happening,
follow a change, and keep a record.
vDavin / monitorILLUSTRATIVE
CPU24.6 %
GPU38.2 %
Physical memory12.8 / 32.0 GiB
Storage128.4 MiB/s read
Network↓ 4.2 MiB/s ↑ 128 KiB/s
| Sensor | Current | Min | Max |
|---|---|---|---|
| Utilization | 24.6 % | 2.1 % | 68.5 % |
| Temperature | 61.0 °C | 42.0 °C | 72.0 °C |
| Package power | 28.4 W | 8.6 W | 46.2 W |
| Frequency | 4.20 GHz | 1.40 GHz | 4.80 GHz |
☆ Favorites · Device tree · Search & filters
24.6 %
−1 minutenow
monitoring.workspace
$ echo "Your hardware, in view."
// CPU · GPU · memory · storage · network
01
// A closer look
From a quick glance to a recorded session.
Every reading, organized
A device tree, current / minimum / maximum values, search, and favorites. Find a sensor without losing the rest of the picture.
Sensors / one workspaceCompare what changes
Plot up to 16 metrics on a shared time axis. Pause to inspect the last one or five minutes and see how readings relate.
History / comparison chartsSet a boundary
Configure thresholds and durations, then follow trigger and recovery events. Unavailable samples stay distinct from valid readings.
Alerts / trigger & recovery
SUPPORTED AREASDevice support varies
- CPU
- Per-core load, frequency, supported Intel / AMD temperature and package power
- GPU
- Multiple adapters, load, memory, supported NVIDIA / AMD native telemetry
- Memory
- Physical memory and system-wide committed memory
- Storage
- Throughput, IOPS, active time, and local volume space
- Network
- Connection state, upload / download rates, traffic totals, and link speeds
02
// Get up and monitoring
A portable folder. No development tools required.
01
Download a test build
Get the Windows x64 ZIP and its SHA-256 checksum from the public release page.
02
Extract everything
Keep the DLLs, assets/, and
vDavinIo.sys beside vDavin.exe.
03
Launch vDavin
Accept the administrator prompt and read the test notice. Start with Overview or explore Sensors.
Windows x64TEST BUILD
Public releases
Windows 10 / 11 · Portable ZIP
Runtime libraries included
· No PDBs
Test builds are published by the maintainers.
Verify your download in PowerShell
PowerShell
Get-FileHash -Algorithm SHA256 -LiteralPath '.\vDavin-<version>-windows-x64.zip'
Compare the hash with the matching
.zip.sha256 file. This checks the archive without
running the application.
03
// A few things to know
Before you start.
Why does vDavin request administrator permission?
Native CPU telemetry uses the bundled monitoring driver. The application manages its service automatically and performs cleanup on normal exit. Administrator permission is requested at startup.
Why is a reading unavailable?
Readings depend on the CPU, GPU, firmware, installed drivers, and Windows support. One unavailable backend does not mean every sensor has failed. A missing reading is shown as unavailable, rather than replaced with zero.
Can I record readings and keep my settings?
Yes. Start background CSV recording in Sensors and choose a save directory. Preferences, favorites, alert rules, and layouts persist between launches. CSV recording starts off each session; charts and statistics cover the current session.
Does vDavin support hardware tuning?
Monitoring is read-only. Hardware tuning, disk SMART health, motherboard / fan sensors, and per-process network traffic are not currently implemented.
Where can I report a problem?
Use the public issue tracker. Include the version and build commit from Settings → About, your Windows version, relevant hardware, and steps to reproduce. Review logs and screenshots before sharing personal paths or device identifiers.
04
// Project notes
INTERNAL TEST VERSION
vDavin may contain many bugs, and hardware coverage is still incomplete. Read the reminder shown at each launch.
AI has been deeply involved in this project. All code modifications have been performed by AI, and the code has been PARTIALLY reviewed by humans. This is primarily a toy project and an experiment exploring the safety boundaries of AI-generated code running with elevated privileges. Absolute safety is not guaranteed.
The vDavinIo driver source code is currently kept private by the project maintainers for security reasons.
Built by vDavin Contributors
Application development takes place in a private
repository.
Public downloads and issue reports have a
home on GitHub.