I backed up several TB into an encrypted vault on Drime and, due to my own foolishness, lost access to it.
It was not a huge deal as the data was easily replaceable, so I deleted the vault.
I didn't get the space back, however. My Drime home page still shows the 2TB being used. Is there something I need to do to reclaim the space?
I'm not trying to start a panic, but I downloaded the Drime desktop client for Win11 and ran a backup. Eventually I had to restart my laptop and on restart, Bitdefender flagged DrimeShellExt.dll as a Gen:Variant.Lazy and quarantined it. I assumed it was a false positive and submitted the file to VirusTotal and a good number of AV companies are flagging it.
Then I submitted DrimeShellHost.exe as well and it got flagged as a Trojan.
Is this all still false positives or is there a problem?
My x15 R1 recently lost almost all GPU performance. A game that previously ran smoothly at max settings now grinds to a halt. HWiNFO logging shows the GPU clock is pegged at 210–225 MHz under 100% GPU load for the entire session — it never boosts. The "Performance Limit: Power" flag fires in 119 out of 125 samples consistently across multiple test runs.
The strangest part: GPU temperatures are completely normal — 44–49°C throughout. This is not a thermal issue. The repaste is recent and doing its job.
GPU-Z confirms the root cause: Board Power Draw reads a constant 752.7W at idle and under load. That number never changes. An RTX 3070 laptop GPU cannot draw 752 watts — this is clearly a phantom/stuck sensor value. The GPU's own firmware is comparing that 752.7W reading against its ~85W power limit, concluding it has catastrophically exceeded budget, and locking the clock down to idle frequency as a protective measure.
Every software and configuration layer has been systematically eliminated:
In all cases GPU-Z continues to show Board Power Draw at exactly 752.7W. The value is completely static — it does not respond to actual load, idle state, driver version, or any firmware setting we've been able to reach.
HWiNFO data across three separate test runs (different driver versions, different BIOS Optimus settings):
| Metric | Value |
|---|---|
| GPU clock under 100% load | 210–225 MHz (should be 1,400–2,000+ MHz) |
| GPU temperature (peak) | 49°C |
| Performance Limit: Power samples | 119/125, 118/122, 143/145 |
| Board Power Draw (GPU-Z) | 752.7W constant |
| GPU VRAM at Epic settings | 84.9% of 8GB |
| RAM pressure | Up to 93.5% physical / 98.6% virtual |
The 752.7W figure appears to be a corrupted or stuck value in either the EC (Embedded Controller) firmware or the GPU VBIOS power sensor table. Because it sits below the OS and driver layer, nothing we can do from Windows touches it. The GPU behaves as though it is perpetually in a severe overcurrent protection state.
The trigger may have been the installation of a second M.2 SSD (Samsung 990 EVO Plus 1TB) — the degradation began around that time — but removing the drive has not resolved the issue, so the drive itself is likely not the ongoing cause. Opening the machine may have disturbed something, or the SSD installation may have coincided with a driver or firmware update that corrupted the power table.
Happy to share the full HWiNFO CSV logs or additional GPU-Z screenshots if useful. Thanks in advance.
