ASUS Gaming Desktop

In November of 2021 I purchased an ASUS Gaming Desktop computer. I bought it at Best Buy and had it delivered to my front door.

The model is a ASUS ROG STRIX C15-B11. It comes with an Intel 11700KF CPU, an ASUS TUF Gaming Nvidia RTX 3080 NON LHR GPU, 16GB of rather generic RAM, an ASUS B560 Motherboard that has been modified somewhat, a 500GB NVMe, a 2TB Toshiba hard drive and a 750W power supply.

Positives include, a great price for what you get. Extremely well organized and cable managed inside the slightly small case. Parts that work mostly. I’ll cover this in the cons.

The particular unit that I obtained factory new in the original unopened box had a mouse, a keyboard, the computer itself and some of the usual suspects in the way of stickers and spare parts, etc.

The cons of the unit I have is that out of the box the CPU Heatsink was not performing it’s job in any fashion. First indicator of the issue was when the exhaust fan sounded like a jet engine on take off. I then installed CPUID’s HWMonitor tools and began trouble shooting.

CPU core 1 on the Intel processor was spiking into the 100C thermal throttle zone. Other cores were at approximately 95 C. One core was at 80 C.

I opened the case. I reached in moving my hand NEAR the heat sink/CPU cooler without actually touching it initially. No heat what so ever. Then I touched it gently and it was room temperature cold to the touch. Next I removed the cooler from the CPU and checked the application of thermal compound. It was woefully inadequate. I cleaned the cold plate of the CPU cooler, and the Intel CPU, using rubbing alcohol and microfiber towels. I reapplied Artic MX 4 thermal compound correctly to the TMI of the CPU and then re-installed the CPU cooler provided. Minimal change in results. CPU Core 1 was still approaching 100 C and throttling, the CPU cooler was room temperature to the touch.

I purchased a Noctua NH-U12S Redux CPU cooler and installed per the Noctua instructions.

HWMonitor now reports 75C or lower temperatures for all of the Intel i7 11700KF cores and package under extended load using AIDA64 in Stress test mode for 4 hours. I also removed the somewhat lackluster RAM and installed 32 GB of G.Skill DDR4 3600Mhz in a 4×8 configuration. In addition I put a WD 850 TB NVMe into the PCIe 4.0 4×4 m.2 slot, moving the 500GB WD 750 to the secondary M.2 slot which can only do PCIe 3.0 3×4.

Hardware issues solved, system performs like a demon in games, light work loads, heavy work loads, benchmarks, etc.

On February 10th, I attempt to log into Second life using firestorm’s latest viewer and get a series of dots in an array of colors.

This was immediately proceeded by an Armory Crate update.

I performed a clean install of firestorm to reveal the same symptom. I remove Firestorm viewer and the app data folders, reboot and then install Kokua viewer. Same result.

I uninstall the nvidia driver and do a clean install of the lastest nvidia driver, then reboot and attempt the login again. Same failed results.

My next step was to run an sfc /scannow from an elevated Admin mode command prompt. SFC reported no errors found.

At a total loss and having spent a few hours into the trouble shooting at this juncture I install Windows 10 cleanly. This in turn had deterimental impacts on my Mint 20.3 linux install on a different partition of the system and I chased that back and forth for a while.

Ultimately I reformatted the TB NVMe and installed windows cleanly then rebooted and installed Mint 20.3 cleanly. Things are performing smoothly once again.

I strongly advise my readers avoid ASUS Armory Crate software whenever possible.

AMD Radeon DRIVER GLITCH

AMD Radeon Driver 20.4.1

This is one of the bugs that exist in the recent AMD drivers for the 5700 XT. It may also exist for other AMD cards with this driver or for this card on the 20.4.2 or 20.5.1 driver. This one was very difficult to isolate. I enabled the “Video Replay” feature in the AMD driver panel. A few days later many of my favorite games started to “hitch or stutter” during random events in the games I play. One of my favorite games that worked flawlessly before the change is Kingdom Come: Deliverance. I spent some time searching for any solutions.

I tested temperatures and enabled logging for temperature events, I looked at SMART data for my NVMe drives, I ran the typical sfc /scannow. I checked DirectX diag log files. Spent a lot of time searching for the proverbial needle in the hay stack that changed my performance.

RESULT: Disable the Video Replay in the AMD Video Driver panel and test your results. This solved my problems in Kingdom Come: Deliverance and in other titles on my system.

Userbench fails Sphere graphics test. Possible solution.

If you are experiencing an error running the userbench suite of tests, and the error indicates “ERROR: Sphere GPU benchmark failed, aborting further tests on this GPU” then this MAY solve your issue.

I isolated this error on my system to the Nahimic service that is a part of the Realtek Audio driver package. To verify this as the cause on your system:

  1. Open the control panel.
  2. Administrative Tools applet. *You may need to change the view in your control panel to large icons to see this as an icon. Check the drop down menu at the top right area of your control panel.*
  3. Click on Services.
  4. Disable the Nahimic service by right clicking on it in the list, properties, then disable. Reboot for that change to take effect.
  5. Test userbench.

IF userbench now runs successfully, then Nahimic service IS the cause. The real solution is to update the Nahimic service to the latest version. In my case I have an ASUS Z370-E Motherboard and there is an update package on the ASUS Support page. IF you have a Z370-E here is the link for the audio driver update. You probably will need to find the update that corresponds to your motherboard at the manufacturer’s web site of YOUR motherboard.

Steps:

  1. Download the update.
  2. Extract or unzip or unpack the update.
  3. Run the Setup.exe file.
  4. Say yes to the prompt to uninstall your existing driver and install the new one.
  5. Reboot when it suggests.
  6. Wait for the installer to resume after the reboot.
  7. Reboot again after the install completes.
  8. Run the AsusSetup.exe to update the Nahimic service, this won’t work correctly if the service is disabled. Enable it and reboot if necessary. Reboot again AFTER the AsusSetup.exe completes it’s install.
  9. Test userbench with the new version of the Nahimic service running.

Your mileage MAY vary. Good Luck!

Linux Mint 19.2 Install of Netgear A-7000 USB 3.0 Wireless adapter

The following outlines the procedure to install the “rtl8814au” driver for Linux Mint 19.2

The kernel recommended is 5.0 or greater.

sudo apt install build-essential
sudo apt install bc
sudo apt install linux-headers-$(uname -r)
sudo apt install git dkms
sudo apt update && sudo apt upgrade
git clone https://github.com/tpircher/rtl8814AU
cd rtl8814au
make
sudo make install
sudo cp -R . /usr/src/rtl8814au-4.3.21
sudo dkms build -m rtl8814au -v 4.3.21
sudo dkms install -m rtl8814au -v 4.3.21

Fedora 18 firewall.

I upgraded to Fedora 18.  Then verified my web server was running.  Then attempted to visit this site.  I was not able to.    The problem was the new firewall daemon in Fedora 18.   Despite the config file indicating that port 80 was open for http traffic, it was not.

I had to install firewall-config.

yum install -y firewall-config

Then I used firewall-config enable traffic for port 80.  This solved the problem.

Apache web server 2.4 on Fedora 18

I recently upgraded my web server system from Fedora 17 to Fedora 18.  I used fedup to do so.  The upgrade went fairly smooth.

A couple days later I noticed that Apache ( httpd ) was not running.   In the course of trouble shooting I had to disable selinux.    When I enabled selinux again, there was a new issue.

The first issue I noticed is that by default, the ServerName directive in the apache config (httpd.conf) file is remarked out.

The error shows up as the following in your /var/log/httpd/error_log file.

Could not reliably determine the server’s fully qualified domain name

The solution for that error is to edit your /etc/httpd/conf/httpd.conf file.

Change the line (line 95 in my file) that reads

#ServerName

to

ServerName localhost

The next error:

No such file or directory: AH01762: Failed to create shared memory segment on file /run/httpd/authdigest_shm

Which had the following error hand in hand with it:

no such file or directory: AH01760: failed to initialize shm – all nonce-count checking, one-time nonces, and MD5-sess algorithm disabled

Both of these errors can be fixed by creating the /run/httpd directory and then changing the ownership to apache and group to apache.  This seems to be a result of disabling and then enabling selinux.

mkdir /run/httpd/

chown -R apache /run/httpd

chgrp -R apache /run/httpd

 

 

Howto: LiveUSB – request by students of Long Beach City College.

Howto:
LiveUSB

1) Download the latest live image.  You can download it from the official Fedora mirrors.

a) Fedora 15 Live Images – Live Images for Fedora 15

2) Download and install LiveUSB Creator.

a) Windows – LiveUSB-Creator

b) Linux – run su -c yum install liveusb-creator -y

3) Install the LiveUSB Creator program.

4) Insert the flash drive you want to LiveUSB to run on.

5) Open the LiveUSB Creator Program.

6) Browse to the folder you saved the Live iso image to in step 1).

7) Select a size for the persistent image.  I use 1024M.

8) Click on create now.

Go grab a cup of java. This part can take up to 15 minutes. When it completes, you have a boot-able LiveUSB drive.