Intel X550-T2 ixs.sys bugcheck (minidump provided)

gnif · ‎08-08-2025

I have a system that has been stable under Linux for many years and recently I needed to use Windows 11 on the same platform.

While using the system I get random bugchecks for `DRIVER_IRQL_NOT_LESS_OR_EQUAL`. The minidump shows a stack trace pointing the problem at the ixs.sys driver:

nt!KeBugCheckEx:
fffff806`893005d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffda0b`77afee90=000000000000000a

ffffda0b`77afee88 fffff806`89105e6f     : 00000000`0000000a 00000000`00000002 00000000`0000000f 00000000`00000000 : nt!KeBugCheckEx
ffffda0b`77afee90 fffff806`89105f73     : 00000000`00000002 fffff806`1c534550 00000000`00000000 ffffa389`34be9ca0 : nt!KiExpandKernelStackAndCalloutSwitchStack+0x19f
ffffda0b`77afef00 fffff806`891060bd     : fffff806`1c534550 ffffda0b`77aff030 ffffa389`34cf6910 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x33
ffffda0b`77afef70 fffff806`1c528b98     : ffff6359`c8c5d185 00000000`00000001 ffffa389`3a89a9f0 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffffda0b`77afefb0 fffff806`1c536437     : 00000000`00000002 00000000`00000002 00000000`00000801 ffffa389`38982010 : tcpip!NetioExpandKernelStackAndCallout+0x58
ffffda0b`77aff000 fffff806`1c18a02f     : 00000000`00000000 ffffa389`3a89a9f0 ffffa389`00000000 ffffda0b`00000001 : tcpip!FlReceiveNetBufferListChain+0x1b7
ffffda0b`77aff090 fffff806`1c1899d8     : ffffa389`349268a0 fffff806`1c189b00 ffffa389`00000000 ffffa389`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x4ff
ffffda0b`77aff380 fffff806`1c196908     : ffffa389`3485f068 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisIndicateSortedNetBufferLists+0x58
ffffda0b`77aff3e0 fffff806`1c1874a6     : ffffa389`381861a0 00000000`00000001 00000000`00000000 00000000`00000001 : ndis!ndisMDispatchReceiveNetBufferListsWithLock+0x1e8
ffffda0b`77aff460 fffff806`1c186030     : ffffa389`381861a0 ffffa389`3a89a9f0 ffffa389`349288a0 00000000`00000001 : ndis!ndisMTopReceiveNetBufferLists+0x3f6
ffffda0b`77aff570 fffff806`24b36dce     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffda0b`77affa78 : ndis!NdisMIndicateReceiveNetBufferLists+0xbb0
ffffda0b`77aff790 00000000`00000000     : 00000000`00000000 00000000`00000000 ffffda0b`77affa78 ffffa389`00000801 : ixs+0x16dce

I have installed the latest drivers (30.3) for the X550-T2 and have ensured the NVM is running the correct version for this driver according to the documentation.

As this device is completely stable under Linux and this fault is only evident under Windows it points to a bug in the driver itself.

Platform Details:
CPU: AMD EPYC 7473X
MB: SuperMicro H12SSL-i
RAM: 128GB ECC
OS: Windows 11 Pro (10.0.26100 Build 26100)
BIOS: American Megatrends Inc. T20240304184441, 4/03/2024

MACM · ‎08-08-2025

Hi gnif,

Greetings of the day.

Hope you are doing great.

Could you please confirm if you have purchased this Network card separately or it came along with the system.

So that we can proceed further accordingly.

Best Regards,

Mohammed Ali CM

Intel Customer Support

gnif · ‎08-08-2025

Hi MACM,

This card was purchased separately, it did not come with the system.

MACM · ‎08-08-2025

Hi gnif,

Thank you so much for your response.

We request you to please share us all the error codes and screenshots.

So that we can look into it and proceed further accordingly.

Best Regards,

Mohammed Ali CM

Intel Customer Support

gnif · ‎08-08-2025

Please see my original message which contains all relevant information.

The system randomly BSODs which produces the kernel minidump which I have already provided. There are no other errors and there is no way to screenshot a BSOD, which is useless anyway as the minidump I provided contains all the crash details.

The fault happens completely randomly, but always caused by the ixs driver. In some instances it can take hours to manifest, in others mere seconds after the system has booted.

Azhari_Intel · ‎08-08-2025

Hi gnif,

Good day to you.

Upon checking, it seems like the network card is compatible with Windows 11 as per documented in link below.

https://cdrdv2.intel.com/v1/dl/getContent/778690?explicitVersion=true&fileName=Intel+Ethernet+Controller+Products_Release+Notes_30.3.pdf

I would like to check if you have attempt in reinstalling the driver to see if the issue still persists.

If no, kindly to give it a try by referring to the steps in the following links below to uninstall the drivers and to manually update the drivers:

Clean Driver Installation Guide for Intel® Ethernet Connections: https://www.intel.com/content/www/us/en/support/articles/000058304/ethernet-products.html

How to Manually Install Intel® Network Adapter Drivers in Windows*: https://www.intel.com/content/www/us/en/support/articles/000022174/ethernet-products.html

If issue still persists, would you mind sharing with us the SSU log.

How to get the Intel® System Support Utility Logs on Windows*

Looking forward to your response.

Regards,

Azhari_Intel

gnif · ‎08-08-2025

Hi,

The system is a fresh install of Windows 11 with all updates applied. I have done this twice to ensure that there is no external factors involved here.

If you want specific system hardware information I am happy to provide it, but no, I will not be running your tool on my system for security and privacy reasons.

Please know I am a driver developer myself, I am able to obtain and provide whatever information may be required upon request. The minidump provided should be enough for your developers to debug the issue however, I have no idea why you're trying to get more information when you already have exactly what you need.

It should not matter how the drivers were installed, clean or not, there is absolutely no scenario where a bugcheck (BSOD) should occur, this is clearly a fault in your drivers.

Amina_Sadiya · ‎08-09-2025

Hi gnif,

Thank you for your response. Kindly share clear front and back pictures of the adapter, ensuring that the labels are clearly visible.

Best regards,

Amina

Intel Customer Support Technician

gnif · ‎08-12-2025

The system is hundreds of kms away in a remote location, there is no possible way to provide this nor do I understand why it's even required. The driver itself is causing a BUGCHECK due to invalid memory accesses. Please escalate this to a developer who can actually use the minidump provided to see exactly where the fault lies.

MACM · ‎08-12-2025

Hi gnif,

Greetings of the day.

Apologies for the inconvenience caused.

We request you to please try swapping the NIC adapter.

Also share us the screenshot of the network adapter information from device manager.

Best Regards,

Mohammed Ali CM

Intel Customer Support

gnif · ‎08-12-2025

Again, READ the first message. I have provided you with MORE information then any screenshot will give you. It's literally a windows BSOD with the error DRIVER_IRQL_NOT_LESS_OR_EQUAL. There is no other errors or screenshots, it crashes the entire system.

Sazirah · ‎08-12-2025

Hi gnif,

Greetings.

We understand that this may require your assistance for us to get sufficient details for us to be able to solve this issue for you. Therefore, we really appreciate your kind cooperation and understanding throughout this process.

For us to check further regarding the issue reported, we would like to verify some details, as below:

1)Kindly ensure the adapter is using the Windows 11 client driver (PROXGB\Winx64\NDIS68) from Intel’s 30.3 package

https://www.intel.com/content/www/us/en/download/15084/intel-ethernet-adapter-complete-driver-pack.html

2)In Device Manager, please check and verify the Driver Version and Driver File (should be ixs68x64.sys and version 4.1.x).

3)If needed, uninstall the current driver (select Delete the driver software) and manually install the NDIS68 driver from the Intel package.

4)If Intel PROSet/ANS was installed, please proceed to remove it. Please be inform that Intel does not support PROSet/ANS on Windows 11 client.

5)Please check if NVM firmare updated to the latest version and share the NVM version with us.

6)Also, please try to disable Receive Segment Coalescing (RSC) and test again.

We are keen to provide quick resolution to our customer, therefore we look forward for the outcome of the action plan we shared above as part of our process to solve this issue for you.

Regards,

Sazzy_Intel

Intel Customer Support Technician

gnif · ‎08-13-2025

1) The driver you suggested is the Windows 10 Driver, not Windows 11. The driver I am using is in the path `PROXGB\Winx64\W11`

2) ixs68x64.sys is part of the Windows 10 driver, the windows 11 driver uses ixs.sys

3) Why would I install the windows 10 driver on windows 11?

4) PROSet/ANS is not installed or in use

5) As I already stated, the firmware was updated according to the documentation for the 30.3 driver

6) I can't afford more downtime, the card has been replaced but I would like to switch back to it if this problem can be resolved.

Sazirah · ‎08-13-2025

Hi gnif,

Thank you for your response.

Regarding the driver we suggested, please be inform that the driver is compatible with windows 11, you may refer to the Readme text file available.

Additionally, since you have mentioned that the card has been replaced and issue still exists, we can try to offer RMA replacement (if possible). However we require additional information for us to verify if it is eligible for RMA replacement process:

1)Serial number of the adapter

Regards,

Sazzy_Intel

Intel Customer Support Technician

gnif · ‎08-13-2025

The card was swapped with out to a different brand, the fault is not with the hardware, as I stated already this card functions perfectly fine under Linux and has done so for years.

When I can afford the time I will re-install the card and test with the NDIS68 driver.

Even if this resolves the issue, the Windows 11 driver should not cause a bug-check and this should still be escalated internally for proper debugging by a developer.

Akshaya1 · ‎08-14-2025

Hi gnif,

Thank you for your response.

Kindly allow us some time to review the details. We will get back to you with an update shortly.

Regards,

Akshaya

Intel Customer support Technician

gnif · ‎08-16-2025

I have reinstalled the card and used the driver specified in the NDIS68 directory. I have also disabled Receive Segment Coalescing and the driver still causes BSODs

STACK_TEXT:  
ffff898d`ad9a6f68 fffff804`7fb05e6f     : 00000000`0000000a 00000000`00000002 00000000`0000000f 00000000`00000000 : nt!KeBugCheckEx
ffff898d`ad9a6f70 fffff804`7fb05f73     : 00000000`00000002 fffff804`12f74550 00000000`00000000 ffffc18d`26b24c80 : nt!KiExpandKernelStackAndCalloutSwitchStack+0x19f
ffff898d`ad9a6fe0 fffff804`7fb060bd     : fffff804`12f74550 ffff898d`ad9a7110 ffffc18d`26de1230 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x33
ffff898d`ad9a7050 fffff804`12f68b98     : ffff10c2`7aa44b95 00000000`00000000 ffffc18d`2ce062a0 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffff898d`ad9a7090 fffff804`12f76437     : 00000000`0000000e 00000000`0000000e 00000000`00000801 ffffc18d`2ab81010 : tcpip!NetioExpandKernelStackAndCallout+0x58
ffff898d`ad9a70e0 fffff804`12bca02f     : 00000000`00000001 ffffc18d`2ce062a0 00060080`00000000 00000000`00000001 : tcpip!FlReceiveNetBufferListChain+0x1b7
ffff898d`ad9a7170 fffff804`12bc72d7     : ffffc18d`2aa798b0 00000000`00000000 00000000`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x4ff
ffff898d`ad9a7460 fffff804`12bc6030     : ffffc18d`2a37b1a0 ffffc18d`2ce062a0 ffffc18d`2a37b1a0 00000001`00000001 : ndis!ndisMTopReceiveNetBufferLists+0x227
ffff898d`ad9a7570 fffff804`1b456d46     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff898d`ad9a7a78 : ndis!NdisMIndicateReceiveNetBufferLists+0xbb0
ffff898d`ad9a7790 00000000`00000000     : 00000000`00000000 00000000`00000000 ffff898d`ad9a7a78 ffffc18d`00000801 : ixs68x64+0x16d46

Attached minidump and screenshot of the driver installed

gnif · ‎08-15-2025

I have reinstalled the device and changed to the NDIS68 driver which has not resolved the issue:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.266 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 45

Microsoft (R) Windows Debugger Version 10.0.27871.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\User\Desktop\081625-10859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (48 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff805`dd800000 PsLoadedModuleList = 0xfffff805`de6f4c40
Debug session time: Sat Aug 16 12:06:16.298 2025 (UTC + 10:00)
System Uptime: 0 days 0:32:51.009
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
............................................................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`ddd005d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff903`0d75ef70=000000000000000a
12: kd> !analyze -v
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
............................................................
Loading User Symbols

Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000002, memory referenced
Arg2: 000000000000000f, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for ixs68x64.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1671

    Key  : Analysis.Elapsed.mSec
    Value: 7692

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 765

    Key  : Analysis.Init.Elapsed.mSec
    Value: 19765

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 123

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27871.1001

    Key  : Analysis.Version.Description
    Value: 10.2505.01.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2505.1.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Bugcheck.Code.TargetModel
    Value: 0xd1

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_ixs68x64!unknown_function

    Key  : Failure.Hash
    Value: {5318bd2a-9ac0-dabf-2cfe-f12252b98194}

    Key  : Faulting.IP.Type
    Value: Null


BUGCHECK_CODE:  d1

BUGCHECK_P1: 2

BUGCHECK_P2: f

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  081625-10859-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffde04f97be040

READ_ADDRESS: fffff805de7c44c0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000000000000002 

PROCESS_NAME:  System

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:  
fffff903`0d75ef68 fffff805`ddb05e6f     : 00000000`0000000a 00000000`00000002 00000000`0000000f 00000000`00000000 : nt!KeBugCheckEx
fffff903`0d75ef70 fffff805`ddb05f73     : 00000000`00000002 fffff805`70f34550 00000000`00000000 ffffde04`f9b35c80 : nt!KiExpandKernelStackAndCalloutSwitchStack+0x19f
fffff903`0d75efe0 fffff805`ddb060bd     : fffff805`70f34550 fffff903`0d75f110 ffffde04`f9d5b590 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x33
fffff903`0d75f050 fffff805`70f28b98     : ffff5aa2`95166b23 00000000`3f484909 ffffde05`3d60cc60 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x1d
fffff903`0d75f090 fffff805`70f36437     : 00000000`0000000c 00000000`0000000c 00000000`00000801 ffffde05`36c7e010 : tcpip!NetioExpandKernelStackAndCallout+0x58
fffff903`0d75f0e0 fffff805`70b8a02f     : 00000000`00000001 ffffde05`3d60cc60 00060080`00000000 00000000`00000001 : tcpip!FlReceiveNetBufferListChain+0x1b7
fffff903`0d75f170 fffff805`70b872d7     : ffffde05`30a62460 00000000`00000000 00000000`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x4ff
fffff903`0d75f460 fffff805`70b86030     : ffffde05`2e3eb1a0 ffffde05`3d60cc60 ffffde05`2e3eb1a0 00000001`00000001 : ndis!ndisMTopReceiveNetBufferLists+0x227
fffff903`0d75f570 fffff805`81896d46     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff903`0d75fa78 : ndis!NdisMIndicateReceiveNetBufferLists+0xbb0
fffff903`0d75f790 00000000`00000000     : 00000000`00000000 00000000`00000000 fffff903`0d75fa78 ffffde05`00000801 : ixs68x64+0x16d46


SYMBOL_NAME:  ixs68x64+16d46

MODULE_NAME: ixs68x64

IMAGE_NAME:  ixs68x64.sys

STACK_COMMAND: .process /r /p 0xffffde04f1aaa040; .thread 0xffffde04f97be040 ; kb

BUCKET_ID_FUNC_OFFSET:  16d46

FAILURE_BUCKET_ID:  AV_ixs68x64!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5318bd2a-9ac0-dabf-2cfe-f12252b98194}

Followup:     MachineOwner
---------

I will now disable RSC and see how things go.

gnif · ‎08-18-2025

It seems your anti-spam messed up the post ordering here. Tests both with and without RSC were performed both faulting exactly the same way.

MACM · ‎08-21-2025

Hi gnif,

Greetings of the day.

Hope you are doing great.

We request you to please provide the below information.

> Could you please try the Windows Inbox drivers and see if BSOD still occurs?

> As you have mentioned that BSOD is random. Is it tied to any workload? Does it happen with any specific app? We request you to provide any details.

> Can we get the current NVM version. is it 3.70?

> Did you try any other version other than the drivers in 30.3 and NDIS85 from the same package?

Best Regards,

Mohammed Ali CM

Intel Customer Support

gnif · ‎08-21-2025

> Could you please try the Windows Inbox drivers and see if BSOD still occurs?

By "inbox" I assume you mean the inbuilt drivers that Microsoft provide as part of the default OS install, or via windows update. There are no "Windows Inbox" drivers for the X550 T2 on Windows 11, you should know this.

> As you have mentioned that BSOD is random. Is it tied to any workload? Does it happen with any specific app? We request you to provide any details.

I have had it happen just sitting idle on the desktop, running applications, and on a few occasions during windows login (the first mini-dump in my original post shows the system up-time was less then a minute). The fault is completely random and is not induced by a specific workload.

> Can we get the current NVM version

Yes, as I stated I updated it according to the 3.70 documentation to the correct version.

> Did you try any other version other than the drivers in 30.3 and NDIS85 from the same package?
You already know this, you made me try NDIS68 after I had already been using the Win11 driver.

Again, please escalate this to someone who can actually inspect the minidumps! Stop just forwarding this to tech support, a developer is required to look at this issue. I am a kernel developer, I know that even if I have faulty hardware (which I do not), your driver should NEVER induce a windows bug check even if things go wrong. Graceful error handling is a requirement of windows driver development along with error recovery.

I have had the device removed from the server and I am proceeding to replace all my Intel devices with a competitors, I am rather shocked that your lack of real support here is so abysmal and I will not be endorsing or using your products into the future.