/r/intel

Photograph via snooOG

/r/Intel is a community run subreddit to discuss anything related to Intel Corporation and their products. Come and talk about Intel CPUs (Core Ultra, i5, i7, i9, etc.), Graphics (ARC, Xe, UHD), Networking, OneAPI, XeSS, and all other Intel-related topics are discussed here.

/r/intel

890,338 Subscribers

8

Introducing Q-Dashboard – Visual motherboard utility for easy port/slot usage display and quick control access, exclusive to ASUS Z890 motherboards.

ASUS is known for innovative UEFI BIOS/Firmware features and functions as well as ASUS Q-Centric design all with the focus of improving the PCDIY experience for builders. In the last few years alone, we’ve seen the introduction of M.2 Q-Latch, Q-Release, DIMM Detect, DIMM Flex, Q-Antenna, AiOC and Process Utilization tracking, and AiCooling.  

An area often overlooked is the UEFI Firmware or what some call the BIOS. ASUS has long been known as the industry-leader in offering well-designed firmware options for both novices and enthusiasts alike.

For this generation we have some exciting updates which include MyHotKey. While it’s not an entirely new feature, it does have new functionality. To add additional options during POST, simply go into ASUS MyHotKey via the UEFI BIOS and you can configure the F3 and F4 buttons to allow you to boot directly into Q-Flash or change the boot order.

While this subtle addition is welcomed, we did not stop there; instead, we spent a lot of time looking at common pain points of builders, which includes having an easy way to see what ports and slots are being used and how to access the subsections in the UEFI to control those slots and or ports.

What Is Q-Dashboard?

Q-Dashboard is the new ASUS-exclusive integrated utility found within the ASUS UEFI BIOS that displays an overview of the motherboard from a top-down perspective and a head-on shot of the I/O ports. Each port, header, fan connector, PCIe Slot, M.2 Slot, and DIMM slot is identified and labeled on the page. With the exception of USB headers, the only items excluded are the front panel headers you normally connect to your chassis. Lastly, Q-Dashboard features a legend at the bottom-right to quickly switch between each type of connector.

This allows for builder to quickly have a “birds-eye view” of their system before the OS is installed and after the primary POST to see that devices are installed/registered correctly.

What Else Does the Q-Dashboard Show?

The Q-Dashboard also denotes which of the connectors are populated with a green dot, and clicking on a populated connector will list the device connected to it.

  • Check which USB devices you plugged into the I/O without having to physically go behind your system to check.

https://preview.redd.it/y5080aovgh6e1.png?width=975&format=png&auto=webp&s=2ff35fbf7777932dd8b31b14b1a07c8c146382b3

  • Check which M.2 SSDs you installed into each M.2 slot without taking off the heatsink.

https://preview.redd.it/jvmpadmwgh6e1.png?width=975&format=png&auto=webp&s=a5918afb1f6f9f52fd3363df961377b4907d7ad2

  • Check which port you have your HDD, SSD or ODD connected to without opening your chassis and tracing cables.

https://preview.redd.it/p4m379exgh6e1.png?width=975&format=png&auto=webp&s=0d2b9d13186c84242ac8476f512cdc13e47f4581

  • Check which fan headers you’ve already plugged a device into and see how many you have left if you want to add more.

https://preview.redd.it/yaefdgcygh6e1.png?width=975&format=png&auto=webp&s=6680542fa7fd398c423683c7016b9c9dca435636

*Note - ASUS also offers a great UEFI BIOS screenshot function if you want to share this with friends, the community, or even service and support. It can streamline and improve understanding when providing feedback for upgrade discussions, debugging and more.*

With the quick links to corresponding control subsections, you don’t need to know where the respective “control sections” are in the UEFI for a specific port and/or slot. In this example, you can see how easy it is to control the connected fans by clicking on a fan header option and be quickly moved to the Q-Fan Configuration page.

https://preview.redd.it/90sffyi1hh6e1.png?width=975&format=png&auto=webp&s=e41e41333080a4ff4a075999fb620901dd58bfe5

How Can I Access Q-Dashboard?

First go into your UEFI BIOS on your ASUS Z890 series motherboard. Click on the Tools button and select Start Q-Dashboard, or you can simply click on the Q-Dashboard menu at the bottom (or press Insert). You can also use a great feature often overlooked in ASUS motherboards called MyFavorite, allowing you to create your own primary set of quick links to sections of the UEFI, which can include Q-Dashboard.

https://preview.redd.it/l4wmfrm2hh6e1.png?width=975&format=png&auto=webp&s=602342caf43563c658ef602d5627595a2ec4e83e

In closing, Q-Dashboard is easiest way to make sure you’ve connected everything during installation and also refresh your memory where you plugged-in certain components during installation long after you can no longer remember.

Here are the current ASUS Intel motherboards that support this feature:

What do you think about this new feature? What other features or information would you like to see added to Q-Dashboard in an update or future motherboard?

1 Comment
2024/12/12
21:27 UTC

26

[Digital Foundry] Intel Arc B580 Review + Benchmarks: Great Performance + 12GB VRAM For 250$!

1 Comment
2024/12/12
16:45 UTC


59

Intel Arc B580 'Battlemage' GPU Review & Benchmarks vs. NVIDIA RTX 4060, AMD RX 7600, & More

7 Comments
2024/12/12
14:10 UTC

188

Intel Arc B580 Review, The Best Value GPU! 1080P & 1440p Gaming Benchmarks

48 Comments
2024/12/12
14:10 UTC

32

Intel ARC B580 12GB Review - Just the Benchmarks

1 Comment
2024/12/12
14:04 UTC

82

The $250 GPU the industry NEEDS right now!

4 Comments
2024/12/12
14:01 UTC

29

Intel Core Ultra 9 285K vs. Intel Core i9 14900K, 45 Game Benchmark

28 Comments
2024/12/10
10:06 UTC

89

Intel Promises Battlemage GPU Game Fixes, Enough VRAM and Long Term Future (feat. Tom Petersen)

14 Comments
2024/12/09
17:27 UTC

15

ASUS UEFI BIOS updates for ASUS Intel Motherboards W49 - Z890 Microcode (0x113) for system stability, compatibility, and improving gaming performance in OS balanced mode; Enhanced system performance, stability for Z790/B760; and more - B760, Z790, Z890 - 24 motherboards updated

https://preview.redd.it/ki56de2hrp5e1.png?width=1920&format=png&auto=webp&s=ae7f54955adb6e9512c8bff30f0f91e328c95d3f

This group of updates primarily serves our Z790 motherboards, our ProArt B760 motherboards, and our new Pro WS Z890-ACE SE workstation motherboard we announced for channel availability this week.

If you don't see your board here, please check the previous weeks:

- WK48WK47&46 - WK45 - WK44 - WK43 - WK41&42 - WK39 -

*PLEASE NOTE – IF YOUR MOTHERBOARD IS LISTED AND NOT YET AVAILABLE ON THE WEBSITE, IT MAY TAKE UP TO A FEW EXTRA DAYS FOR IT TO SHOW UP. PLEASE BE PATIENT.*

New UEFI BIOS updates For ASUS Intel motherboards – W49

*Please do not ask about motherboards not listed. Please review the FAQ below for details.

Release notes –

For Z890 boards -

  • Intel microcode updated to 0x113.
  • Enhance system stability and compatibility.
  • Enable EPP Grouping by default, further improving gaming performance in OS balanced mode.
  • Updating this BIOS will simultaneously update the corresponding Intel ME to version 19.0.0.1753v4.

For most Z790 and B760 boards -

  • Enhanced system performance, stability and allows the C1E power state to be disabled.
  • Updating this BIOS will simultaneously update the corresponding intel ME to version 16.1.32.2473.

For the TUF Gaming Z790-PRO WIFI -

  • Improve system performance
  • Updating this BIOS will simultaneously update the corresponding Intel ME to version 16.1.32.2473v3.

Intel

Z series – Z890, Z790

X series –

B series – B760

H series –

Q series –

C series –

W series –

R series -

Mini-PC -

Workstations -

UEFI BIOS update list noted below – A total of 24 boards with a UEFI BIOS update.

W is in relation to the workweek; December 2th - December 8th 2024

Intel – B760, Z790, Z890

FAQ -

Why is my motherboard not listed?

If you are looking for your motherboard/model, please visit https://www.asus.com/us/support/ and check if it has been updated recently. UEFI's BIOS updates are commonly released in waves; as such, it can take a series of motherboards, weeks, or months to have all motherboards have the same corresponding UEFI BIOS update issued. Furthermore, remember that not all updates apply or apply to all models. Due to inherent design differences and specification and feature variation, an update may only apply to a specific model.

How long are motherboards supported with UEFI BIOS updates? How long should I monitor for an update?

In most cases, after a year, boards tend to reach a certain maturity level and see fewer updates. Mature releases can often be seen within the first six months. All non-BETA releases pass qualification and validation. If you feel you have an issue dependent on a UEFI release, please submit a support ticket. Some boards can sometimes see updates for more than 24 months. Also, user experience can vary considerably based on end-use-defined parameters and system configurations ( such as overclocking/performance tuning ). Users running stock operating parameters will experience the least amount of issues.

I want to update, but I am unsure how to update the UEFI "BIOS"?

If you want guidance on how to flash/update your UEFI BIOS, please watch the video linked below. It will guide you through the flashing process and provide insight into essential items to keep in mind when flashing/updating the UEFI BIOS.

How to Flash / Update your UEFI BIOS on ASUS Motherboards -

https://www.youtube.com/watch?v=scK8AP8ZACc

Should I update the UEFI if my system is stable and running without issue?

If your system is running without issue, especially if overclocked in any way (including DRAM), it is recommended you stay on the build/release you are on. Changes to underlying auto rules and other operating parameters can change the OC experience and require you to retune a previously stable OC value. This does not mean the UEFI is not a functioning/reliable release but that changes in the underlying code base must be accounted for when tuning a system. As many of these values are low-level, it is best to retune from UEFI defaults. Verifying the UEFI's system stability is also recommended via a stress test, like Passmark Burn-in Test, OCCT, AIDA64, or a similar stress test.

Users who update from stock to stock settings will generally experience the smoothest transition experience.

Will a UEFI update improve my overclocking experience?

A UEFI update can improve multiple aspects of the OC experience, whether extending frequencies or stabilizing them, improving general system stability, or adding new options relative to overclocking. It is important to note that overclocking has inherent mitigating factors, including silicon variance, which cannot be overcome purely from a UEFI update.

Will a UEFI update change my operating experience? Power consumption, temperatures, etc?

Changes to underlying auto rules and other operating parameters can affect aspects like CPU boosting behaviors. There can also be changes to UEFI BIOS auto rules. A UEFI BIOS update can affect operating temperature, performance scores, power consumption, etc. Comparisons should be made at like-to-like values, ideally meaning the same settings, applications, etc. It is also recommended this occur at F5 defaults.

Sometimes, you may need to reinstall the OS after a UEFI BIOS update to gauge its stability correctly. This means that the end operating experience should be first verified with default operating values (F5) and, ideally, a fresh installation of chipset drivers, an updated build of Windows, and a non-modified Windows power profile.

What if the UEFI BIOS listed is a BETA? Should I update?

BETA UEFI releases are for enthusiasts who want access to the latest features, functions, microcode enhancements, and overall UEFI improvements. They are not recommended for day-to-day/long-term use. Users who plan to use their system in this capacity and want to ensure the best interoperability/compatibility, stability, and performance should wait for a formal release.

Not every user should update/flash their UEFI BIOS. Again, if you are running without issue(s), you are advised to stay on the release you are running.

Notes to consider -

* When flashing, please perform the update process at UEFI BIOS defaults. Do NOT flash with an overclocked system/profile.

Your warranty is still applicable under the use of a UEFI BIOS update.

  1. I recommend updating the UEFI BIOS on your motherboard for new PC builds. This helps to ensure the best interoperability, compatibility, and performance. If you are building a PC and have not installed the OS, I recommend updating the UEFI.
  2. Remember that flashing/updating the UEFI will reset all defined parameters/settings and operating profiles. You cannot restore defined values using a UEFI Profile, as profiles are not interoperable between builds. You should note or screenshot (F12) your values before flashing if they are complex. Upon completing a flash, I recommend you load UEFI defaults after the fact, perform a reboot, and shut down before reloading or entering any customized UEFI values.
  3. When you update the UEFI and reload UEFI defaults depending on your defined initial BOOT values, you may need to adjust CSM settings, enabling or disabling CSM. If you experience BOOT-related issues after an update, please change the CSM accordingly.
  4. Be advised that in some cases, a rollback to a prior UEFI is not possible. This can occur when an update includes a CPU microcode ( such as an AMD AEGSA or Intel ME ). This means you may be unable to "flashback" to a prior release.
  5. While not always necessary, some UEFI updates may require clearing the CMOS to reset the UEFI and ensure normal functionality. You may need to CLR the CMOS to have the system POST after you flash. You can clear the CMOS via the CLR CMOS button if your motherboard supports it or by removing the onboard CMOS battery for at least a few minutes. You can also attempt to locate the CLR CMOS jumper on the motherboard and short the pins to clear the CMOS.
  6. Some updates will cause PCIe remapping and reinitialization of onboard controllers/devices. In these cases, you may need to reinstall drivers including your chipset drivers, graphics drivers or other PCIe or USB linked based devices.

 

It is also recommended you back up your system before any flash/update. Ideally, it would be best to load UEFI BIOS defaults (F5) before performing a flash/update; do not flash with an overclocked configuration.

Ensure you reboot before flashing once you have loaded (F5 defaults).

The board model/name is on the right-hand side, and the version number is on the left-hand side. To download the UEFI BIOS, please go to https://www.asus.com/support/

 

Intel UEFI BIOS Releases –

  1. PRO WS Z890-ACE SE - 1101
  2. PROART B760-CREATOR - 2801
  3. PROART B760-CREATOR D4 - 2801
  4. PROART B760-CREATOR WIFI - 2801
  5. PROART Z790-CREATOR WIFI - 2801
  6. ROG MAXIMUS Z790 APEX - 2801
  7. ROG MAXIMUS Z790 APEX ENCORE - 1801
  8. ROG MAXIMUS Z790 DARK HERO - 1801
  9. ROG MAXIMUS Z790 EXTREME - 2801
  10. ROG MAXIMUS Z790 FORMULA - 1801
  11. ROG MAXIMUS Z790 HERO - 2801
  12. ROG MAXIMUS Z790 HERO BTF - 1801
  13. ROG MAXIMUS Z790 HERO EVA-02 - 2801
  14. ROG STRIX Z790-A GAMING WIFI - 2801
  15. ROG STRIX Z790-A GAMING WIFI D4 - 2801
  16. ROG STRIX Z790-A GAMING WIFI II - 1801
  17. ROG STRIX Z790-A GAMING WIFI S - 1801
  18. ROG STRIX Z790-E GAMING WIFI - 2801
  19. ROG STRIX Z790-E GAMING WIFI II - 1801
  20. ROG STRIX Z790-F GAMING WIFI - 2801
  21. ROG STRIX Z790-F GAMING WIFI II - 1801
  22. ROG STRIX Z790-H GAMING WIFI - 2801
  23. ROG STRIX Z790-I GAMING WIFI - 2801
  24. TUF GAMING Z790-PRO WIFI - 1806
7 Comments
2024/12/09
00:07 UTC

133

Intel Battlemage GPU Deep-Dive Into a Frame | Engineering Discussion ft. Tom Petersen

19 Comments
2024/12/08
21:35 UTC

18

Extreme Tuning Utility - ALL FIXES for uninstall issues, partial downloads, reinstallations, and file corruption.

Hey guys! I've been so frustrated for the last several months because Intel's XTU (Extreme Tuning Utility) only partially uninstalled when I last uninstalled it. I was having issues and wanted to uninstall and then reinstall, but then I kept getting error messages saying drivers were missing, there was already an installed version of XTU, etc.

I dove deep into figuring out the solution, and after months of research, yesterday I finally found a file within the .exe installer file, by using 7-Zip to open it like an archive, that held the answers. So, if you're having issues with XTU, try these steps:

  1. Open cmd AS AN ADMINISTRATOR

  2. Download the installer file for XTU from Intel's website

  3. In your command prompt window, type in: cd Downloads (assuming you opened cmd from your home folder, if you don't know what that means then you should continue with the steps.)

  4. Type in XTU and then press tab to auto-complete the file name of the installer

  5. Press space bar and type one of the 3 following commands based on your situation:

/install , /uninstall , or /repair

For me, the solution was to repair, uninstall, install.

Hope this helps!

Here's a snippet of what I found. The file I found was titled "u2" in the main directory of the .exe archive:

<?xml version="1.0" encoding="utf-8"?>
<WixLocalization Culture="en-us" xmlns="http://schemas.microsoft.com/wix/2006/localization">
  <String Id="Caption">[WixBundleName] v[WixBundleVersion] Setup</String>
  <String Id="Title">[WixBundleName]</String>
  <String Id="ConfirmCancelMessage">Are you sure you want to cancel?</String>
  <String Id="HelpHeader">Setup Help</String>
  <String Id="HelpText">/install | /repair | /uninstall | /layout [directory] - installs, repairs, uninstalls or
   creates a complete local copy of the bundle in directory. Install is the default.
/passive | /quiet -  displays minimal UI with no prompts or displays no UI and
   no prompts. By default UI and all prompts are displayed.
/norestart   - suppress any attempts to restart. By default UI will prompt before restart.
/log log.txt - logs to a specific file. By default a log file is created in %TEMP%.</String>
  <String Id="HelpCloseButton">&amp;Close</String>
1 Comment
2024/12/08
19:34 UTC

Back To Top