@bi0hzrd Your dxdiag lists a few generic Windows errors, so I'd suggest running a couple of basic checks of your Windows system files:
- Hit Windows key-X
- Choose either “PowerShell (Administrator)” or “Windows Terminal (Administrator),” whichever option is offered
- Inside the window that appears, copy and paste “DISM.exe /Online /Cleanup-image /Restorehealth” without quotes, and enter
- The system will start validating soon. If it throws an error, please list it here
- After it reaches 100%, hit Windows key-X again
- Again, choose “PowerShell (Administrator)” or “Windows Terminal (Administrator)”
- Inside the window, copy and paste “sfc /scannow” without quotes, and enter
- Post the message you receive here
Restart your computer, hit Windows key-i, select Update & Security, and click the box to check for updates. If any install, restart again afterwards.
As a separate matter, do you have any kind of cleaner app installed on your computer? If so, try disabling it. The app might be deleting the cache files for whatever reason. And I know you said you use only Windows Defender, which is disabled, but please look for any other antivirus under installed apps, just in case something is lurking on your system. It wouldn't be the first time someone was surprised to find a third-party antivirus installed.
If the above doesn't help, the AppHangB1 errors in your dxdiag could be related to the graphics driver, although this type of error is somewhat generic. But since the driver was mentioned as a possible issue in the NRaas thread, and your issue only appeared recently, it's worth trying a slightly older driver. You can find them here:
https://www.nvidia.com/en-us/geforce/drivers/
Try the game-ready driver from May 9 or 21. You'll need to clean-uninstall your current driver first, since it's newer than the one you'll install. Here's how:
https://crinrict.com/blog/2019/02/clean-re-install-of-graphics-drivers-with-display-driver-uninstaller-ddu.html
Since some people ask, it's critical to use DDU rather than uninstalling the driver using one of the normal methods—that's the only way to be sure that the issue isn't the driver itself.
And yes, any Store world was fine, and the files appear to be the right sizes, although I don't have ST installed at the moment to compare. But it's unlikely the files would be large and the wrong size, so this is probably working as it should.