Computer Setup

[DeVaultSetter]

Updated the thread there, happens with just the Evnia 27″. The only hope is a DP 1.4 cable which can be procured from the local outlet. Funny, couldn’t locate the DP info in Adrenalin, is it visible on yours?
The cheapo monitors over here will never sport anything like a luxurious HDR toggle, the manufacturers could have at least included one which would have the effect of next to nothing, in an attempt to make us feel as if we have kept up with the Joneses. 😛

[Spastic Hamburger]

Don’t see the DisplayPort specs in Adrenaline but we do have a display specs section under Settings -> Display -> Display Specs at the bottom. Doesn’t say anything at all about the interface, though. Nothing wrong with DisplayPort. In fact, it has some good benefits over HDMI. They mostly reached feature parity several years ago so the 10-bit color is no longer DP exclusive but the cable itself locks in to the ports so there’s less chance of it getting loose. Also, you can daisy-chain DP cables so that you can use several monitors with only a single port. Wonderful feature as it keeps the cables neat and tidy. That’s how I had things set up. Only issue is that TVs don’t support DP cables.

Does hardware HDR cause issues, then? I know Windows has had it in the settings menu for years but I never had a screen that supported it

[DeVaultSetter]

Good to know, oops – completely forgot about the 1.4 cable, so will pop in there next week. 🙂
All of a sudden, the svchost is running “NETWORK SERVICE” at full bore after hibernate resume. Only supposed to happen on cold boot, Delivery Optimization is off, and Network Discovery is turned off for public networks if that is a thing. Windows Resume Application in BCD is as per usual, There are also events 7011 & 7046, and an issue with kb5052093, now pending restart here – hopefully will fix. 🙂
Edit: Rebooting is no change, in case of something choking DNScache, trying the following:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

[Spastic Hamburger]

Yep, flushdns is pretty useful. Used to use it often back in the DSL days when the network information changed but the cache didn’t update for whatever and resetting the network connection didn’t do the trick. Pretty sure it was a Windows bug in XP at the time. Looks like they suggest trying the Pi Hole in the GitHub issue, which has come up before but is lost due to the broken search function 🙁 But, yeah, splitting the blocking out to a different device may help take the load off the system. 🙂

Still haven’t gotten around to experimenting with a Pi. I really should one day. Always been curious about the Pis

[DeVaultSetter]

There’s a long wait before svchost.exe frees up other processes on the Ryzen, so boosted it a little with the help of this from W10 forums. The value in the registry setting for SvcHostSplitThresholdInKB was increased from the 380000 default to 600000 (6GB) RAM. Not the full 8gb as other process won’t get a look-in. 😛
Reminder to self: In case internet drops, get a FAT flash stick to update the TUF B450 mobo for the rig.

[Spastic Hamburger]

Yeah, Windows has always been slow to get everything up to speed, even on a fresh install with an SSD. I’m assuming Windows is installed on the HDD? The SSD will definitely boot faster than the HDD if you want to go that route. Would mean moving the install, though, which can be a bit of a pain

[Spastic Hamburger]

As I mentioned elsewhere, PopOS was updated the other week with COSMIC and Wayland as the defaults. Things haven’t exactly been going swimmingly. There are a few bugs in the combination, such as screen flickering after the display gets blanked by the power settings. The fix is to log out and back in again. Additionally, mouse scrolling in the pager doesn’t work properly in the terminal emulator and the overrides are ignored.

Those are relatively minor, however. The biggest issue I’m noticing is that I can’t get games working right. The Witcher doesn’t load properly at all and Workers and Resources runs but not in fullscreen and the mouse only maintains focus for about 75% of the interior of the window, making it unplayable regardless. No Man’s Sky doesn’t load at all from what I can tell.

I’ll need to poke at things later on, see if there’s a way to get things working properly.

• This reply was modified 7 months ago by Spastic Hamburger.

[DeVaultSetter]

That’s … nice. Only this recent Reddit link mentions protondb:

Steam games not launching when they were yesterday
byu/Critical_Bonus_7589 inpop_os

Somewhere else mentioned concerns with Wayland config – sorry not much help. 🙁

[Spastic Hamburger]

Yeah, I wasn’t able to come up with much either. For some of the other problems, there were some open issues but no feedback on them.

Thanks, will try that soon. 🙂

Also going to try messing with the Proton settings to see if that helps when I’m not so tired. Don’t want to risk messing anything up!

[DeVaultSetter]

After a couple of hiccups here and here, the new machine is setup just about.
https://valid.cpuid.com/j2jys8n3
Our local Mr Fixit put it all together rather smoothly until I presented him with an old SATA drive that was thought to be okay – but had an invalid status with the read only flag permanently on. 😛
It sports the old SB soundcard and the black chassis of the old “Ob” machine to allay the full payload of the shock of the new. 🙂

[Spastic Hamburger]

No AMD? 🙁

And don’t forget to turn on the virtualization support if you’ll be running VMs or DOSBox! 🙂

Sounds good. 🙂

[DeVaultSetter]

Aw snap, something happened to the Micron 3400 SSD. Not long after resume from hibernation Windows detected an error, after which the PC would boot up to the BIOS. No boot device found. No idea what the cause is – other than a power spike which got through the UPS or too hot from a fan fail?

[Spastic Hamburger]

You could try reseating it. That sometimes helps

[DeVaultSetter]

Mr Fixit came back with the drive H/W as okay, after reseating and re-installing the drive. Will pick up the rig next week. Not 100% sure of the health of the drive as some programs exhibited a little glitchiness – could be a memory thing too.

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

As we know, continued use of hibernation is venturing in murky waters it seems. In explaining the above, somehow the Gigabyte bootloader and consequently the Windows Boot Manager got corrupted, so the C: lettering of the M.2 SSD got changed.

The rig also has a permanent non-bootable 3.5 in. sata drive, maybe in such situations we can use it as an alternative boot with light weight windows:
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-install-on-a-hard-drive–flat-boot-or-non-ram?view=windows-11
Or better
https://github.com/cmartinezone/WinPEBuilder

Had a Simplecom SATA 3.5 in. hard drive dock which is pretty much plug-and-play, and worked well. A few weeks back I pulled out the drive but left the station connected. Windows event manager logged errors for this, so disconnected the thing entirely. AI indicates it could have had a direct impact – although two clean boots later, it happened. Ghosts in the machine?
AI suggests in the UEFI to:

Locate CSM Support (Compatibility Support Module) and set it to Disabled (pure UEFI mode is required for modern NVMe boot routing).

and

Navigate to Settings > IO Ports.
Look for VMD setup menu or Intel VMD Controller.
Change it from Enabled to Disabled.

The AI scrapes a fair bit from this article, for good reason too. 🙂
https://rossmanngroup.com/symptoms/nvme-ssd-not-detected-bios

[Spastic Hamburger]

It sounds like there could have been an outage during a critical Windows process. Windows is much less forgiving about those situations than *nix. It’s possible you may need to reinstall the OS

If I remember correctly, CSM is mostly for older technologies such as IDE that pre-date SATA drives (as well as older add-in cards). Granted, it’s been a while since I really looked at those settings.

[DeVaultSetter]

It’s now back and the logs only give up BugCheckProgress: 0x00040049.
The original C: Drive SSD was installed with Windows in late July. Mr Fixit added in an old Working SATA (not the faulty one above) in early August. There exists a 2GB dump dated that day in LiveKernelReports which most likely relates to that enumeration of that drive. It was I: on the deceased rig, and there may have been issues of drive enumeration on the old system which have somehow bled onto the drive? He later showed me some issue of an extra ghost drive in the system, so if it wasn’t resolved then, it’s sure to be fixed now. 🙂
Famous last words. 😛

[Author]

Posts