Page 17 of 24 FirstFirst ... 7 15 16 17 18 19 ... LastLast
Results 161 to 170 of 237
  1. #161
    ROG Enthusiast Array djase PC Specs
    djase PC Specs
    MotherboardASUS ROG CROSSHAIR VIII Dark Hero X570
    ProcessorAMD Ryzen 9 5900X
    Memory (part number)G.Skill Trident Z RGB 32GB 3600CL16-16-16-36
    Graphics Card #1Gainward GeForce RTX 4090 Phantom
    MonitorALIENWARE AW3821DW / BenQ XL2411T / LG55C1
    Storage #1Samsung 980 PRO 1TB Nvme PCIe 4.0
    Storage #2Samsung 850 EVO 500 GB
    CPU CoolerCorsair ICUE H150i Elite LCD
    CaseLian Li PC-O11DX Black
    Power SupplyCorsair RM1000x & CableMod Classic ModFlex C-Series Cable Black/Blue
    Keyboard Corsair K95 RGB Platinum - BROWN -
    Mouse Logitech G502 LIGHTSPEED
    Headset Corsair Virtuoso RGB Wireless CARBON / Sony WH1000XM4
    Headset/Speakers Hisense HS214 2.1
    OS Windows 11 Pro 22H2 64 bit
    djase's Avatar
    Join Date
    Oct 2018
    Reputation
    63
    Posts
    40

    Quote Originally Posted by MoKiChU View Post
    Hi everyone,

    - Intel WiFi Drivers (Drivers Only) :
    Drivers - 9xxx/AXxxx : 22.140.0.2 WHQL [18/04/2022]
    Download - 9xxx/AXxxx : Link


    Thread updated.
    Cheers mate as usual.

  2. #162
    ROG Enthusiast Array RamGuy PC Specs
    RamGuy PC Specs
    Laptop (Model)MacBook Pro 13-inch retina with touch bar 2016
    MotherboardAsus Maximus X Apex @ 1003
    ProcessorIntel Core i7-8700K @ 4.9GHz
    Memory (part number)G.Skill 4266MHz 2x 8GiB (F4-4266C19D-16GTZR)
    Graphics Card #1EVGA GeForce GTX 1080 Ti Hybrid
    Sound CardHegel HD12 External DAC
    MonitorAsus RoG PG348Q + Asus RoG PG278Q
    Storage #1Samsung 960 Pro NVMe 1TB
    Storage #2Samsung 960 Evo NVMe 1TB
    CPU CoolerNZXT Kraken X62
    CasePhanteks Enthoo Evolv ATX Tempered Glass Black
    Power SupplySeasonic Platinum 1200W (SS-1200XP3)
    Keyboard Corsair K70 RGB RapidFire Cherry MX Speed
    Mouse Logitech G Pro
    Headset Sennheiser HD 800
    Mouse Pad SteelSeries QcK Extended
    OS Windows 10 Pro (1709 Fall Creators Update)
    Network RouterGoogle WiFi with 3x nodes (Previously Asus RT-AC5300)
    Accessory #1 Xbox One Elite Controller + Wireless Adapter
    Accessory #2 Zowie Mouse Bungie
    Accessory #3 TPM-Module (Trusted Platform Module)
    RamGuy's Avatar
    Join Date
    Apr 2012
    Reputation
    10
    Posts
    48

    I was struggling with this like crazy. Both the 2.0.1.3 offered directly by Asus and 2.0.1.7 offered directly by Intel was causing non-stop kernel security check BSOD. Had to disable all kinds of virtualization software in Windows 11 such as Hyper-V, Guarded Host, and Microsoft Defender Application Guard.

    Does seem like a massive oversight? I can understand that generic Intel drivers might cause issues, but the fact that Asus themselves list 2.0.1.3 as the only Windows 11 driver for my Asus Z690 Maximus Hero and it doesn't work with common Windows 11 features without causing non-stop BSOD is bad.

  3. #163
    ROG Member Array
    Join Date
    Dec 2021
    Reputation
    10
    Posts
    17

    After more troubleshooting, I've determined the BSOD with virtualization enabled is likely caused by Receive Side Scaling (RSS). I turned this off on my NIC and was able to install the new 2.1.1.7 drivers. Still testing, but the system appears to be stable.

    To turn off, open PowerShell as administrator. Run the following to get the name of your NIC (mine was simply named Ethernet):
    get-netadapter

    Then, run the following to turn off RSS:
    disable-netadapterrss -Name name from previous command


    More Info on RSS:
    https://docs.microsoft.com/en-us/win...e-side-scaling
    https://www.broadcom.com/support/kno...indows-servers

    Edit:

    On a hunch I did some more testing, and this appears to be related to the E-cores on Alder Lake. I am guessing this will end up being a Windows issue. The following is what causes the BSOD in my case:

    • Alder Lake chip with E-Cores enabled
    • Ethernet driver that utilizes the NetAdapterCx miniport driver
    • Ethernet RSS settings at default values
    • Windows virtualization features enabled, such as Windows Sandbox, Subsystem for Linux, and possibly Hyper-V

    I've been testing the following workaround, which will keep RSS from utilizing the E-Cores and causing the BSOD. Before updating to v2 of the ethernet drivers:

    • Open PowerShell as administrator
    • Run the following to get the name of your I225-V NIC (mine was simply named ethernet, and I'll use that for the examples below):
    • get-netadapter
    • Run the following to tell RSS to only use the first 8 cores (which will be your P-Cores):
    • set-netadapterrss -name ethernet -MaxProcessorNumber 14
    • By default, MaxProcessors is set to half the total number of processors:
    • set-netadapterrss -name ethernet -MaxProcessors 4
    • If you run get-netadapterrss -name ethernet, it should look like the below

    Click image for larger version. 

Name:	rss_ps.png 
Views:	3 
Size:	18.3 KB 
ID:	92858

    After the above, you should be able to install the latest 2.1.1.7 drivers with no issue. I've reported this to both Intel and Asus, but no idea who to report to at MS. Hope this is helpful to others with the same issue.
    Last edited by funkyd; 04-29-2022 at 09:29 PM. Reason: Clarified what I meant by "Windows virtualization features enabled"

  4. #164
    ROG Member Array
    Join Date
    Oct 2021
    Reputation
    10
    Posts
    5

    Nice to see I'm not the only one with major issues with all 2.* drivers available so far whether through Asus or Intel. My experience has been that USB hotplug functionality quits working and the driver would quit working at times.
    The current Windows Insider build (22598) will install with virtualization features enabled out the gate if that is an exacerbating feature. Namely, Memory integrity will be on by default from the get-go if installed via Setup. However a Reset will reinstall with Memory Integrity off and require manually turning it on. I'll wait till newer versions to try this new driver model again.

  5. #165
    ROG Member Array
    Join Date
    Feb 2022
    Reputation
    37
    Posts
    23

    Quote Originally Posted by funkyd View Post
    After more troubleshooting, I've determined the BSOD with virtualization enabled is likely caused by Receive Side Scaling (RSS). I turned this off on my NIC and was able to install the new 2.1.1.7 drivers. Still testing, but the system appears to be stable.

    To turn off, open PowerShell as administrator. Run the following to get the name of your NIC (mine was simply named Ethernet):
    get-netadapter

    Then, run the following to turn off RSS:
    disable-netadapterrss -Name name from previous command


    More Info on RSS:
    https://docs.microsoft.com/en-us/win...e-side-scaling
    https://www.broadcom.com/support/kno...indows-servers

    Edit:

    On a hunch I did some more testing, and this appears to be related to the E-cores on Alder Lake. I am guessing this will end up being a Windows issue. The following is what causes the BSOD in my case:

    • Alder Lake chip with E-Cores enabled
    • Ethernet driver that utilizes the NetAdapterCx miniport driver
    • Ethernet RSS settings at default values
    • Windows virtualization features enabled

    I've been testing the following workaround, which will keep RSS from utilizing the E-Cores and causing the BSOD. Before updating to v2 of the ethernet drivers:

    • Open PowerShell as administrator
    • Run the following to get the name of your I225-V NIC (mine was simply named ethernet, and I'll use that for the examples below):
    • get-netadapter
    • Run the following to tell RSS to only use the first 8 cores (which will be your P-Cores):
    • set-netadapterrss -name ethernet -MaxProcessorNumber 14
    • By default, MaxProcessors is set to half the total number of processors:
    • set-netadapterrss -name ethernet -MaxProcessors 4
    • If you run get-netadapterrss -name ethernet, it should look like the below

    Click image for larger version. 

Name:	rss_ps.png 
Views:	3 
Size:	18.3 KB 
ID:	92858

    After the above, you should be able to install the latest 2.1.1.7 drivers with no issue. I've reported this to both Intel and Asus, but no idea who to report to at MS. Hope this is helpful to others with the same issue.
    I never touched anything but the Asus BIOS does have vt-d enabled by default and I never turned it off.

    I don't use any of the newer virtualization based security such as memory integrity (but have before without issue) but do have the older hyper-v based stuff enabled in system information.

    I do not have the hyper-v feature installed to be able to run VM's on this machine.

    I have never had any issues with these drivers running a 12700k on the latest (non-insider) version of Windows 11

    Just wondering what differences between mine and your system that really caused the BSOD.
    Last edited by bigjohns97; 04-29-2022 at 02:11 PM.

  6. #166
    ROG Member Array
    Join Date
    Dec 2021
    Reputation
    10
    Posts
    17

    Quote Originally Posted by bigjohns97 View Post
    Just wondering what differences between mine and your system that really caused the BSOD.
    The BSOD isn't caused by the VT-D BIOS settings and doesn't seem to be related to memory integrity/core isolation. Your post was a bit unclear to me, do you have Hyper-V enabled on your system?

    Below are the features I have enabled:

    Click image for larger version. 

Name:	features.png 
Views:	279 
Size:	17.2 KB 
ID:	92905

    I have confirmed both Windows Subsystem for Linux and Windows Sandbox cause the BSOD independently of each other, but have not tested with only Virtual Machine Platform enabled (which is required for both WSL or WSB to function). I also haven't tested with Hyper-V, but I believe both WSL and WSB use virtual Hyper-V switches, which I believe is the cause of the issue in combination with RSS and Alder Lake E-cores, as I mentioned above.

    Asus support was also able to reproduce the BSOD on their end and recommended reverting to the previous driver version on their site, 1.0.2.14. I requested they escalate to Intel/MS, but obviously have no control over what they do with the info I provided. Intel is still investigating, which is promising.

    Edit: I will also clarify my previous post, by "virtualization features enabled" I am specifically referring to features such as WSL, WSB, and possibly Hyper-V, NOT VT-D or core isolation.
    Last edited by funkyd; 04-29-2022 at 09:25 PM.

  7. #167
    ROG Member Array
    Join Date
    Feb 2022
    Reputation
    37
    Posts
    23

    Quote Originally Posted by funkyd View Post
    The BSOD isn't caused by the VT-D BIOS settings and doesn't seem to be related to memory integrity/core isolation. Your post was a bit unclear to me, do you have Hyper-V enabled on your system?

    Below are the features I have enabled:

    Click image for larger version. 

Name:	features.png 
Views:	279 
Size:	17.2 KB 
ID:	92905

    I have confirmed both Windows Subsystem for Linux and Windows Sandbox cause the BSOD independently of each other, but have not tested with only Virtual Machine Platform enabled (which is required for both WSL or WSB to function). I also haven't tested with Hyper-V, but I believe both WSL and WSB use virtual Hyper-V switches, which I believe is the cause of the issue in combination with RSS and Alder Lake E-cores, as I mentioned above.

    Asus support was also able to reproduce the BSOD on their end and recommended reverting to the previous driver version on their site, 1.0.2.14. I requested they escalate to Intel/MS, but obviously have no control over what they do with the info I provided. Intel is still investigating, which is promising.

    Edit: I will also clarify my previous post, by "virtualization features enabled" I am specifically referring to features such as WSL, WSB, and possibly Hyper-V, NOT VT-D or core isolation.
    Yeah I don't have any of those Hyper-V features enabled.

    I agree this is probably related to the Hyper-V features you are using to either run VM's or WSL/WSB.

    Under More Windows Features

    Hyper-V
    Virtual Machine Platform
    Windows Hypervisor Platform
    Windows Sandbox
    Windows Subsystem for Linux

    Are all unchecked on my machine.

    I believe this is why you are seeing issues while others are not, good to know.

    Maybe someone should report to Intel since this isn't default Windows options it is possible they aren't aware of the issue.

  8. #168
    ROG Guru: Yellow Belt Array
    Join Date
    Dec 2014
    Reputation
    245
    Posts
    249

    Thank you very much, Mokichu.

  9. #169
    ROG Guru: Green Belt Array ahfoo's Avatar
    Join Date
    Jan 2020
    Reputation
    191
    Posts
    684

    Thank you ,Mokichu

  10. #170
    ROG Guru: Yellow Belt Array
    Join Date
    Dec 2014
    Reputation
    245
    Posts
    249

    Thank you, Mokichu.

Page 17 of 24 FirstFirst ... 7 15 16 17 18 19 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •