u/zentsang

I can probably ask any AI this question, but I want to be part of, and contribute to this community.

.

My Specs:

I'm running the latest version of Windows 11 Pro and fully up to date on an Samsung M.2 1TB drive. My system specs are AMD Ryzen 9 3900x, 32GB DDR4 RAM, and MSI Ventus 3 Geforce RTX 4070 OC edition (12GB). All other drives are a mix of SSDs all 500GB (Samsung, Crucial, and Western Digital).

.

My question:

I've been testing local AI in a Virtualbox guest session running Linux Mint 22.3 (up to date). I provide my specs because the one thing I know about Virtualbox is it using virtual hardware. I also run a Proxmox node and know I can pass the GPU through to the VMs and Containers if needed. So my question is, do WSL1 or 2 use my physical hardware (i.e. the AI will have use of the Nvidia GPU or other physical hardware) or is WSL like Virtualbox and just emulates hardware?

OK, so I saw another post from 7 years ago that has been archived. They were receiving on-screen errors. I, however, do not get any visual errors. No BSODs, no hits in the Event Viewer or Reliability History, no log or mini-log dumps about it. The whole PC just randomly crashes and 95% of the time is during gaming.

.

My Specs:

- AMD Ryzen 9 3900x

- ASUS TUF Gaming X570-plus wifi (updated with the latest motherboard firmware)

- G.Skill Ripjaw 32GB DDR4 (2x 16GB RAM sticks)

- MSI Ventus 3 RTX 4070 12GB OC-edition (latest Nvidia Game-Ready driver v610.88 as of this post date)

- 1TB Samsung 980 Pro M.2 for the main OS drive (Windows 11 fully updated)

- All other drives are a mix of 500GB Crucial, Samsung, and Western Digital SSDs (all of which check out fine in CrystalDiskInfo).

- Steel Series Arctis Nova 7 Wireless headset (using 2.4Ghz and not Bluetooth)

- Case's internal are all clean as if new ... no dust bunnies in there.

.

Scenario: Using my PC for a while, YouTube videos, Facebook, Gmail, a little Python programming, Remoting into a Work PC ... no issues for hours. A few buddies hop online in Steam or Ubisoft and I fire up a game to play. Usually either Wreckfest 1 or 2, Tom Clancy's Division 2, Valheim, Peak, or recently Phasmophobia. Sometimes there are no issues at all and a whole night of gaming has no issues. But other times... after a few minutes of playing or sometimes after an hour... the entire PC just crashes as if I pressed the Hard Reset button in the middle of a heated battle.

.

I get no visual errors. No BSODs. No Event Viewer or Reliability History indicators other than the PC has restarted from an unexpected shutdown. Usually the only things I see listed prior to the crashing is with the Microsoft GamingInput Device or an Xbox GameBar warning. So at least I've zeroed in on a possible glitch with those. On a side note, I'm a Keyboard/Mouse gamer and rarely use the Xbox One Controller. When not in use, the controller is always turned off.

.

Anyway, I hope I've provided enough detail in my efforts to figure out what is going on.

SOLVED: I haven't changed anything locally, yet I noticed starting about a week or 2 ago, not a single TV episode is being moved to their designated folders. No path names have changed. No renaming of folders has occurred. Yet nothing is automatically being moved after download and extraction. Anyone else seeing this or know how to fix it? I just checked and I'm on the latest version of Sonarr. The files are downloading completely and I have verified they all work fine. They just aren't being moved for some reason.

UPDATE ADDITION: No APIs have changed. All tests of Download Clients and Indexers come back successful. Just no indication of why automatically moving or importing to their folders is not working.

UPDATE #2 - FIXED: So after a helpful tip to ... DUH! ... check the logs I found that for some reason Sonarr was being denied access to the hard drive. Even though this PC only has 1 user account with is an Admin and the hard drive is installed in the same PC. After doing some further digging ... and even though it's worked for a decade ... apparently running Sonarr as a Service versus as launching the app at login was jacking something up. As soon as I switch from a service to a Startup app... all the things jammed up in the Sonarr queue cleared out themselves without my intervention. So some recent update (either Windows or Sonarr) caused this to occur. It's fixed now. Here are the steps I followed to switch from Service to Startup app:

Reason for failure and fix description: Running Sonarr as a Windows Service causes 90% of permission errors on Windows. Switching it to run as a startup tray application forces it to run exactly under your Admin account you're logged in with, which instantly resolves the error.

Steps:

1. Press Windows Key + R, type services.msc, and press Enter.
2. Scroll down to find Sonarr (or NzbDrone).
3. Right-click it, select Properties, change the Startup type to Disabled, click Stop, and hit OK.
4. Open your Windows Start Menu, look for Sonarr, and launch it manually.
5. If it works, press Windows Key + R, type shell:startup, and press Enter to open your Windows Startup folder.
6. Right-click your desktop's Sonarr shortcut, copy it, and paste it directly into that Startup folder. It will now automatically launch under your Admin account whenever your PC boots.

Again... this resolved my issue. Your results may vary.