ASUS ROG STRIX Z690-E GAMING WIFI - Event 17, WHEA-Logger (Update)

aus-rog-strix-z690-e-gaming-wifi.png

After troubleshooting I decided to move the M.2 from slot M.2_1 to slot M.2_3. The thinking behind this was to move the M.2 SSID off the Intel 12th Gen Processor lanes to the Intel Z690 Chipset lanes. I was on BIOS version 0702 and it immediately began detecting both the M.2 SSID and GPU. I flashed the BIOS back to version 0811 and reinstalled all of the drivers. So far I'm back in business, however, skeptical. Everything ran great initially when using the M.2_1 slot then after some period of time things started to go south. fingers crossed.


ASUS ROG STRIX Z690-E GAMING WIFI - Event 17, WHEA-Logger

aus-rog-strix-z690-e-gaming-wifi.png

I'm having issues with the ROG STRIX Z690-E GAMING WIFI build. Had everything up and running and what appeared to be stable. After a few hours came back and something didn't feel right. The PC kept stuttering. I checked the event viewer and saw a bunch of Event 17, WHEA-Logger errors...


A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express) Primary Bus:Device:Function: 0x0:0x1:0x1 Secondary Bus:Device:Function: 0x0:0x0:0x0 Primary Device Name:PCI\VEN_8086&DEV_462D&SUBSYS_86941043&REV_02 Secondary Device Name:

A reboot will fix this right? Reload and nothing, just a blank screen and a lovely D6 error. After further investigation I noticed that the motherboard doesn't recognize the NVMe drive either. After resetting the BIOS (0811) with no luck I down graded to 0803 then 0702 before I gave up. Did I fry my NVMe drive? Did my GPU blow up?

Transferred everything back to the old rig and it boots up perfectly. No clue what's going on but pretty disappointed with ASUS right now. First the Z690 HERO and now the Z690-E.

I've searched high and low and can't find anything related to this issue. Has anyone also experienced the same or know how to get the NVMe drives detected?


Xbox Wireless Adapter for Windows - This Device Cannot Start (Code 10)

xbox-wireless-adapter-for-windows.jpg

If you have an Xbox Wireless Adapter for Windows and get the error "This device cannot start. (Code 10)" perform the following steps to fix the issue.

  1. Open device manager and right click and select properties for the "Xbox Wireless Adapter for Windows" device.
    • Navigate to the Advanced tab.
    • Selective Suspend: Disable
    • Remove the Xbox Wireless Adapter and plug it back in.

ASUS ROG STRIX Z690-E GAMING WIFI Build

aus-rog-strix-z690-e-gaming-wifi.png

Due to the potential risks of the ASUS MAXIMUS Z690 HERO motherboard catching on fire I built this temporary rig until ASUS figures out the problem. The Z690 HERO is definitely a nicer board. If I didn't have a wife, children, and dogs I would have probably kept running it. Below are the details of the build.

ASUS ROG STRIX Z690-E GAMING WIFI Configuration

  1. Update the BIOS from Version 0503 to 0811.
  2. Configure initial BIOS settings to load Windows 11.
    • Boot
      • CSM
        • Launch CSM: Disabled
      • Secure Boot
        • OS Type: Windows UEFI mode
        • Secure Boot Mode: Custom
  3. Restart and load Windows 11 for the first time.
  4. Upgrade Intel ME Consumer Firmware from 16.0.0.1423 to 16.0.15.1605 (automatic restart).
  5. Upgrade ALC4080/ALC4082 firmware from 4.501.0000-0013.0000 to 4.501.0000-0020.0000.
  6. Upgrade USB PD controller to Version 004.
  7. Reinstall Intel Chipset Driver Version 10.1.18838.8284 (automatic restart).
  8. Reinstall Intel MEI Driver Version 2131.1.4.0 (automatic restart).
  9. Install Intel Serial IO Driver Version 30.100.2131.26 (automatic restart).
  10. Install Intel Thunderbolt Driver Version 1.41.1229.0 (automatic restart).
  11. Install Realtek USB Audio Gen2 Driver Version 6.3.9600.2307 (automatic restart).
  12. Configure BIOS for overclock.
    • Ai Tweaker
      • Ai Overclock Tuner: XMP II
      • Intel(R) Adaptive Boost Technology: Enabled
      • ASUS MultiCore Enhancement: Enabled - Remove All limits
      • Performance Core Ratio: AI Optimized
      • Efficient Core Ratio: AI Optimized
    • Advanced
      • PCI Subsystem Settings
        • Re-Size BAR Support: Enabled
    • Run the Qfan Control to profile the fans (I don't run AI Suite 3).
    • This netted me a 71% overclock (5.5 GHz).

Notes

  1. Noctua NH-D15 wouldn't fit in the horizontal direction so I had to install it vertically (airflow goes from bottom to top).
  2. Coming from an ASUS ROG MAXIMUS Z690 HERO I was disappointed to see only one USB 3.2 Gen 1 header.
  3. I get the feeling this motherboard has USB issues. When trying to connect a Xbox Wireless Adapter for Windows via a USB hub it throws an error. My mouse froze twice through the same USB hub. On the Z690 Hero and previous build this was never an issue. I'm still testing and will update as I learn more.

An Error Occurred During an Attempt to Read the Federation Metadata

windows-server.jpg

During a routine updating of certificates I noticed this error within the AD FS management console. After further investigation it looks like some relaying party’s are now using TLS 1.2 instead of the legacy 1.0 and 1.1 protocols.

To fix simply run the following commands as an administrator in Power Shell. This machine happened to be running Windows Server 2012 R2.


New-Item 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -Force | Out-Null

New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -name 'Enabled' -value '1' -PropertyType 'DWord' -Force | Out-Null

New-ItemProperty -path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client' -name 'DisabledByDefault' -value 0 -PropertyType 'DWord' -Force | Out-Null

New-ItemProperty -path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -name 'SchUseStrongCrypto' -value '1' -PropertyType 'DWord' -Force | Out-Null

Once complete close the AD FS management console and reopen. Right click your relying party trust(s) that have the error and click “Update from Federation Metadata”.