Updated drivers for Windows XP SP3 and Windows 2003 SP2 (x32/x64) for modern hardware

[Dietmar]

@reboot12

Until now it is not stable. Always after 2000-65000 packages it stops.

I compile it for you for 64 bit XP, when it is more stable.

 

@canonkong

It is build from scratch in about crazy 500h of work. No Wlan Sources for XP can be found in Internet.

I build it with the OpenBSD 79 files from 26 April 2026

and with Ubuntu and with the hacked XP SP1 sources, net.zip .

I cant believe for myself, that I succeed and what crazy things I have done for to reach this

Dietmar

Edited May 3 by Dietmar

[K4sum1]

On 4/12/2026 at 9:34 PM, K4sum1 said:

So I have the same issue with this driver, and this is what I found in setupapi.log for it. 

[2026/04/12 16:28:27 260.255]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" "C:\WINDOWS\system32\devmgmt.msc" 
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci\ven_10ec&dev_8125&subsys_7c911462&rev_04,pci\ven_10ec&dev_8125&subsys_7c911462,pci\ven_10ec&dev_8125&cc_020000,pci\ven_10ec&dev_8125&cc_0200
#-018 Searching for compatible ID(s): pci\ven_10ec&dev_8125&rev_04,pci\ven_10ec&dev_8125,pci\ven_10ec&cc_020000,pci\ven_10ec&cc_0200,pci\ven_10ec,pci\cc_020000,pci\cc_0200
#-019 Searching for hardware ID(s): pci\ven_10ec&dev_8125&subsys_7c911462&rev_04,pci\ven_10ec&dev_8125&subsys_7c911462,pci\ven_10ec&dev_8125&cc_020000,pci\ven_10ec&dev_8125&cc_0200
#-018 Searching for compatible ID(s): pci\ven_10ec&dev_8125&rev_04,pci\ven_10ec&dev_8125,pci\ven_10ec&cc_020000,pci\ven_10ec&cc_0200,pci\ven_10ec,pci\cc_020000,pci\cc_0200
#-019 Searching for hardware ID(s): pci\ven_10ec&dev_8125&subsys_7c911462&rev_04,pci\ven_10ec&dev_8125&subsys_7c911462,pci\ven_10ec&dev_8125&cc_020000,pci\ven_10ec&dev_8125&cc_0200
#-018 Searching for compatible ID(s): pci\ven_10ec&dev_8125&rev_04,pci\ven_10ec&dev_8125,pci\ven_10ec&cc_020000,pci\ven_10ec&cc_0200,pci\ven_10ec,pci\cc_020000,pci\cc_0200
#-019 Searching for hardware ID(s): pci\ven_10ec&dev_8125&subsys_7c911462&rev_04,pci\ven_10ec&dev_8125&subsys_7c911462,pci\ven_10ec&dev_8125&cc_020000,pci\ven_10ec&dev_8125&cc_0200
#-018 Searching for compatible ID(s): pci\ven_10ec&dev_8125&rev_04,pci\ven_10ec&dev_8125,pci\ven_10ec&cc_020000,pci\ven_10ec&cc_0200,pci\ven_10ec,pci\cc_020000,pci\cc_0200
#I022 Found "PCI\VEN_10EC&DEV_8125" in c:\new\RTL8125.inf; Device: "Realtek RTL8125 2.5GbE"; Driver: "Realtek RTL8125 2.5GbE"; Provider: "Dietmar"; Mfg: "Dietmar"; Section name: "RTL812x.ndi.NT.5.2".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001.
#I023 Actual install section: [RTL812x.ndi.NT.5.2]. Rank: 0x0000a001. Driver date: 04/12/2026. Version: 0.0.0.16.
#-124 Doing copy-only install of "PCI\VEN_10EC&DEV_8125&SUBSYS_7C911462&REV_04\6&52F7D12&0&0048020A".
#W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\new\rtl8125.inf" for driver "Realtek RTL8125 2.5GbE" will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information.
#-024 Copying file "c:\new\amd64\rtl8125.sys" to "C:\WINDOWS\system32\DRIVERS\rtl8125.sys".
#W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\new\rtl8125.inf" for driver "Realtek RTL8125 2.5GbE" will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [RTL812x.ndi.NT.5.2.Interfaces] from "c:\new\rtl8125.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#E161 Processing of call to class installer failed. Error 87: The parameter is incorrect.

I tried testing the x86 driver on XP x86 since it didn't work for me there with the old driver, but I encountered a code 10 on both the 8125 and 8126 I'm testing with.

I was also curious about more modern Windows versions, so I tested 8.1, and get a code 31 from both. Would be nice to have something working for the 8126/8127 since it has no native 7/8 driver.

As cool as WiFi card is, I would like to be able to get a working driver to test and finally be able to board swap the RTL8125 PC.

[j7n]

Could working driver releases be collected in the first post now that this thread has been renamed and expanded in scope and length?

[Dietmar]

@reboot12

I am writing this to you from the 9560 Wlan driver on XP SP3,

niccceeeeeee

Dietmar

PS: About 500h work and I build about 2000 not working drivers..

 

Edited May 4 by Dietmar

[reboot12]

29 minutes ago, Dietmar said:

I am writing this to you from the 9560 Wlan driver on XP SP3,

niccceeeeeee

Dietmar

PS: About 500h work and I build about 2000 not working drivers..

Fantastic !!! Respect

[Dietmar]

@reboot12

I was one step away from to give up with the Wlan 9560 driver.

I use old firmware, which is not supported officially for this card.

To come to live for this card is from Ubuntu, Scan is from OpenBSD,

the RX Ring is first part from OpenBSD and updated with a nice idea from Ubuntu, wifi path is from XP SP1.

 

But the most most crazy things were

1,) The CNVi firmware always kills my card with power switch off between 11.000 and 700.000 packages.

For to overcome this I modd my Bios like crazy, to really force any power on.

Later I come to the idea, to look, how OpenBSD and Ubuntu solve this.

Win10, win11 have problems with this too, but I succeed with a simple OpenBSD hack.

 

2.) The CNVi firmware looks for MSI-X. This is something, that XP does not like. Crazy, this I noticed only today.

So I rewrite my driver from IRQ ==> Polling just now. And voila,

see this result, It is much better than my lan result via DSL Speedtest from Computerbild and any Wlan card that I know

Dietmar

PS: The 9560 card I tested on the Asrock N100DC-ITX and just now on the Biostar z690A Valkyrie.

 

Edited May 10 by Dietmar

[we3fan]

WinDbg Video tutorials:
https://www.youtube.com/playlist?list=PLhx7-txsG6t6n_E2LgDGqgvJtCHPL7UFu

[George King]

Ported Drivers Collection v46

Updated release of the ported driver collection.

All drivers are restricted to legacy NT 5.x systems only (no Windows 2000 support).

These drivers are intended exclusively for:

• Windows XP (5.1)
• Windows Server 2003 / XP x64 (5.2)
   

Even when using integrated driver solutions such as DriverPack or similar tools, these drivers should never interfere with newer operating systems like Windows 7 or later.

The entire collection is legacy-focused and specifically designed for NT 5.x compatibility.

---

Important

To use properly signed drivers, import the following certificates before installation.

Run both commands from an elevated command prompt:

	reg add "HKLM\SOFTWARE\Microsoft\SystemCertificates\Root\Certificates\2516FF09B7786B05CBB7B96B97690821A13B36AF" /v "Blob" /t REG_BINARY /d "5C0000000100000004000000000800000300000001000000140000002516FF09B7786B05CBB7B96B97690821A13B36AF1900000001000000100000006604E2B4AF8E1E311D7D01577BADCE9C14000000010000001400000001A43F9D5BAEBFE4D86C9D007514AA094103C73A0F000000010000001400000080F75388C42C3A5209BC64307A711CE8E258BFFF04000000010000001000000029A595DC50B71061B554EB3F74A2BCED20000000010000001E0400003082041A30820306A00302010202109C4595B4E1845E8B445B11B720F1BC38300906052B0E03021D050030543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D060355040313065850324553443020170D3231313233313232303030305A180F32323231313233313232303030305A30543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D0603550403130658503245534430820122300D06092A864886F70D01010105000382010F003082010A0282010100DC0EAF99F8FD61A19AC1B151DA02347897480373974B34E464C9896298FD513183C31BE742059BF7493A428C0B899F948F432B2EEAE29A617ADE75AEE6D7FBF0055AF5A6944B1AE427551553C05319E2B65301EDC6E7DC03159CDD228129058FFB46EBF26B871B5A1546B158EA8006744BA12DAEAE49BF266ADE97166BCDE424C43E7AE4E951BBFE8F6CA3AAA9A692851B5E5F91409B2071EECE7F5BF2EE372FA40D4DB30FF43062363F8CE499F5960350B49ECFB72559C234A356ABC97F300E7F6389C31A622294707E8143DC219E3A0BBCED4AD5C7A6DE2A44B65587D7FB5E898326C2905D4546EACAFF0A579A8643D99E58410623492DB4535F7502060CB90203010001A381ED3081EA300F0603551D130101FF040530030101FF304F0603551D250448304606082B06010505070303060A2B0601040182370A0305060A2B0601040182370A0306060A2B0601040182370A0307060A2B0601040182370A0308060A2B0601040182370A03093081850603551D01047E307C80106E13AE59A3D4C6AB69BD5A699E28E3F3A15630543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D0603550403130658503245534482109C4595B4E1845E8B445B11B720F1BC38300906052B0E03021D0500038201010033C95C0CB8471EB54CB8DA1B176178F8ADA702DB79FAD0447A2B2E2D5C26143198C643E0F7A566B7A6D7B148A0FD72ABD762B7BCF7B46DF55C5BF5905C53CD3CA6DD4E12DA2AFC2E1355A4AD1658DA3D875E0C33C37C680B3D8E7D057F0183A6458D03B16EBC7D4155B26930EAAA0629E4FAC432DE31A848706DD5BB3D66EDC8E3DE5ED2D17F515EB810B1856B906C8714CC72EF8F8A91813EF65CD3224923ADBD4FD08FBE8147C11AF4D9CF047698E870B3F698B490F4C639713DBE31CBE51334783D8EE325CE803438B6E959F5466BA3B178448569864CE3542B7C31E76A81857993CFB3D6C1818C8D357E4A0B19DBE3DDDC8739A02D2A883C89F0923EBA6A" /f
	reg add "HKLM\SOFTWARE\Microsoft\SystemCertificates\TrustedPublisher\Certificates\B9B6F07ACD8C0A29597BB2AC1EECF59D046697A7" /v "Blob" /t REG_BINARY /d "030000000100000014000000B9B6F07ACD8C0A29597BB2AC1EECF59D046697A75C00000001000000040000000008000019000000010000001000000027114C6CAC4F2A0B4B6D0B1D3FD888AA140000000100000014000000EC77C51CB1021AD6278248DD8D6D474DF123699A0F00000001000000140000007C2BE80346DA6933211FB3E086D2D373454DEF48040000000100000010000000AA5FE38C7A8D84E83EC756AEAB36705920000000010000001B0400003082041730820303A0030201020210AA944720F0F0E89A4C7925C5BD795FDE300906052B0E03021D050030543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D060355040313065850324553443020170D3231313233313232303030305A180F32323231313233313232303030305A30543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D0603550403130658503245534430820122300D06092A864886F70D01010105000382010F003082010A0282010100F0C27E766F7D27BC2BA2CC1B3E0A6E7434589F51AF1554A37BE1C23939B54E601DB393A14C3A223EFD61A47973E1093C1810BCF0298A2D4603684EA80CB5ED303C7D20094CCFFBE903EFA0CDF9FB29CF3F9CFD04E820494100E8E72C2719ED983202DAA59C2FB1DEC68AECBA724DE40173FEBDF9C8D20918538DDEDD7DEF033B69EB584B547910C69166953EF08E226FE26B02310975929C7862AF41B0739C0463A7356988E13AA396DC87195B1744D10EA59E1449F6DA6A6D536F423C81F325870756FBE54BCB0B1A7F8A0B4E165B730CC5A4A1C464CAF6257EB3575ECC38077A8334BF11C7561AF1A8F16D6A570ACD1343510329F6AAB6EF96741FCE7E58E50203010001A381EA3081E7300C0603551D130101FF04023000304F0603551D250448304606082B06010505070303060A2B0601040182370A0305060A2B0601040182370A0306060A2B0601040182370A0307060A2B0601040182370A0308060A2B0601040182370A03093081850603551D01047E307C80106E13AE59A3D4C6AB69BD5A699E28E3F3A15630543123302106092A864886F70D010901161461646D696E6973747261746F724078702E636F6D311C301A060355040A131347656F726765204B696E6720436F6D70616E79310F300D0603550403130658503245534482109C4595B4E1845E8B445B11B720F1BC38300906052B0E03021D050003820101000307298CCD1B761CAEDAABD7BC51E6528CE75CCB8F99C1092146C0E1589CD900D713F3EF97B18B3B43FADE02403F36EEAE7EAE1DD100F1A005F14F095D55653F35A4A44AAA00837DADB5E985388987D9798331AC8A1AB78CA13F457C110B0A87ACC98D3288E482AA403055D4119066C9384DB0A8646A399202117FFE9098DE5B6E9FCF59DD3D2A1050086C52009D5C80A8D677F1FDE7CF2C9B0F2ED11FE847B9DA132A9D9DCE584CC28CB694DC661CFD8F7C2BDB9ECAAA970D191655C327C819F3AB93D4EADBAF67B8B1CF5C2BC4D50944E9ED46CB6584BAC6E70D7F1FFADC72ACC2CCFECFAF1404902174EE0C6620A619F178238DF70D9EFE09E92500E29A1E" /f
	

 

---

x86 Driver Packages

• AMD_SATA — 1.2.001.0337 / 1.2.001.0402 / 3.3.1540.40
• AMD_SD+MMC — 1.0.0.0106
• AMD_USB3 — 1.1.0.0145
• Generic_ACPITime — 6.2.9200.16384
• Generic_AHCI — 1.0.0.0 / 1.0.0.585 / 6.2.7989.0 / 6.2.9200.20652 / 6.3.0.1
• Generic_Disk — 5.2.3790.4171
• Generic_HDABUS — 5.10.01.5013
• Generic_HIDI2C — 6.2.9200.16384
• Generic_MSAHCI — 6.1.7601.26057
• Generic_NVMe — 1.2.0.1 / 1.3.1014.00 / 1.5.1200.00 / 10.4.49.0 / 6.1.7601.23403
• Generic_SD+MMC — 6.2.8056.0
• Generic_UASP — 1.0.0.51 / 6.1.7600.4002 / 6.2.9200.16384
• Generic_USB2 — 5.2.3790.5203
• Generic_USB3 — 6.1.7800.0
• Generic_USB3x — 6.2.9200.21180
• Generic_USBMassStorage — 5.2.3790.5829 / 6.1.7601.25735
• Generic_USBParent — 5.2.3790.5203 / 6.1.7601.24138
• IaNVMe — 4.4.0.1003
• Intel_HCSwitch — 5.0.4.43
• IRST — 16.8.2.1002
• RSTe — 4.7.0.1119
• Samsung_NVMe — 3.3.0.2003
• TPM — 6.1.7601.24564
• WinUSB — 6.2.9200.16384
  

---

x64 Driver Packages

• AMD_SATA — 1.2.001.0337 / 1.2.001.0402 / 3.3.1540.40
• AMD_SD+MMC — 1.0.0.0106
• AMD_USB3 — 1.1.0.0145
• Generic_ACPITime — 6.2.9200.16384
• Generic_AHCI — 1.0.0.0 / 1.0.0.585 / 6.2.7989.0 / 6.2.9200.20652 / 6.3.0.1
• Generic_Disk — 5.2.3790.4171
• Generic_HDABUS — 5.10.01.5013
• Generic_HIDI2C — 6.2.9200.16384
• Generic_MSAHCI — 6.1.7601.26057
• Generic_NVMe — 1.2.0.1 / 1.3.1014.00 / 1.5.1200.00 / 10.4.49.0 / 6.1.7601.23403
• Generic_SD+MMC — 6.2.8056.0
• Generic_UASP — 1.0.0.51 / 6.1.7600.4002 / 6.2.9200.16384
• Generic_USB2 — 5.2.3790.5203
• Generic_USB3 — 6.1.7800.0
• Generic_USB3x — 6.2.9200.21180
• Generic_USBMassStorage — 5.2.3790.5829 / 6.1.7601.25735
• Generic_USBParent — 5.2.3790.5203 / 6.1.7601.24138
• IaNVMe — 4.4.0.1003
• Intel_HCSwitch — 5.0.4.43
• IRST — 16.8.2.1002
• RSTe — 4.7.0.1119
• Samsung_NVMe — 3.3.0.2003
• TPM — 6.1.7601.24564
• WinUSB — 6.2.9200.16384
  

---

https://www.mediafire.com/file/k1zlg5oiz4on5xc/DP_Ported_DriversCollection_v46.7z/file

[Dietmar]

@reboot12

Here is the 9560 Wlan driver for XP SP3 and XP bit 64.

Free and Checked version each and Source Code.

I notice crazy things: The most most stable run of this driver is on an original XP SP3 from 2008, 4GB.

I got millions of packages without crash, MyPal 13.7 via DSL Speed test.

64 bit XP I have not tested.

Tomorrow I make a try to compile the 77 firmware for to understand it much better.

NO(!!!) 32 GB or something else, those "patches" make whole XP SP3 instable.

Until now no WPA2 only unencrypted, open Wlan, Channel 6 at 2.4 GHZ

Good luck,

Dietmar

https://www.upload.ee/files/19336803/9560m136_m120_nodebug_x64.zip.html

[reboot12]

6 hours ago, Dietmar said:

Here is the 9560 Wlan driver for XP SP3 and XP bit 64.

Unfortunatelly on WinXP 64-bit is error This device cannot start. (Code 10) in Device Manager

Please compile for me version IRQ or write me how fix code to compile IRQ version - I have WDK 7600 installed, compilation time ~3 seconds

Edited May 12 by reboot12

[Dietmar]

@reboot12

I have the same Dell Wyse 5070 as you, same Wlan 9560,

same cpu, same M.2 Sata, same ram and same cpu.

But I have no idea, how to install XP 64 there

Dietmar

 

[Dietmar]

@reboot12

Code 10 means, that this driver is acceptet but just can not start. With Windbg it would be easy to solve.

So, from my side, next step would be to bring the @Mov AX, 0xDEAD Lan-Windbg to XP bit 64

Dietmar

[reboot12]

45 minutes ago, Dietmar said:

But I have no idea, how to install XP 64 there

Simply use my modern ISO - make USB from ISO (how make USB is in my tutorial). I sended you link about year ago to e-mail

[Dietmar]

@reboot12

1. Get DebugView

Important:
Do NOT use the current DebugView 5.x if it does not run on Windows XP x64.
For Windows XP x64, use an older Sysinternals DebugView 4.x version, preferably 4.81 or 4.90.

Microsoft Sysinternals DebugView page:
https://learn.microsoft.com/sysinternals/downloads/debugview

If the Microsoft download only provides the newer 5.x version, search for an older Sysinternals release.

Suggested search terms:
DebugView 4.81 Sysinternals
DebugView 4.90 Sysinternals
DbgView.exe 4.81
DbgView.exe 4.90

After extraction, the executable will usually be named:

Dbgview.exe

or, if included:

Dbgview64.exe

On Windows XP x64, first try Dbgview.exe.
If it does not start and Dbgview64.exe is present, try Dbgview64.exe.


2. Prepare the Dell Wyse 5070 with Windows XP x64

Create these folders:

C:\DBGVIEW
C:\9560LOG

Copy DebugView into:

C:\DBGVIEW

Install the diagnostic x64 driver package:

9560m137_x64_startdiag

Important:
Do not use the nodebug version for this test.
We need DbgPrint output from the driver.

If possible, do not enable the Intel 9560 device in Device Manager before DebugView is already running.


3. Start DebugView

Start DebugView as Administrator: For this you need your password from installation of XP.
I installed XP SP3 without password, and crazy DebugView does not work.

C:\DBGVIEW\Dbgview.exe

If it does not start and Dbgview64.exe is available, try:

C:\DBGVIEW\Dbgview64.exe


4. Enable DebugView capture options

In DebugView, open the menu:

Capture

Enable these options:

Capture Win32
Capture Kernel
Enable Verbose Kernel Output

Optional but useful:

Options -> Clock Time
Options -> Show Milliseconds

Then clear the current output:

Edit -> Clear Display

DebugView should now be empty and waiting for new output.


5. Set the filter

Open:

Edit -> Filter/Highlight

Use this Include filter first:

9560

If too little is captured, use:

9560;NDIS;Miniport;Wifi

Leave the Exclude field empty.

Press OK.


6. Enable logging to file

Open:

File -> Log to File

Use this filename:

C:\9560LOG\DBGVIEW_9560_X64_CODE10.LOG

If DebugView asks whether to append or overwrite, choose Overwrite.


7. Reproduce the Code 10 problem

Open Device Manager:

devmgmt.msc

Then use one of these methods:

Method A:
Right-click the Intel 9560 device.
Choose Disable.
Then right-click it again.
Choose Enable.

Method B:
Right-click the Intel 9560 device.
Choose Update Driver.
Choose manual installation.
Choose Have Disk.
Select the 9560.inf from the m137_x64_startdiag package.

Method C:
If the device already shows Code 10:
Uninstall the device.
Then choose Scan for hardware changes.
Install the driver again using the 9560.inf file.

Keep DebugView open during the whole process.


8. Important lines in the DebugView log

We need the startup sequence of the 9560 driver.

Look for lines like:

9560nn56: NdisMInitializeScatterGatherDma
9560nn56: query resources pass0
9560nn56: query resources pass1
9560nn56: resources count
9560nn56: resource[0]
9560nn56: resource[1]
9560nn56: resource[2]
9560nn56: mapped resources mmio
9560nn56: NdisMRegisterInterrupt
9560nn56: embedded fw hdr ver
9560nn56: alive wait end
9560nn56: bootstrap status
9560m8c: WifiInitialize success

If Code 10 appears, the last 9560 line before the failure is usually the most important one.


9. Save the log

After Code 10 appears:

File -> Save As

Save as:

C:\9560LOG\DBGVIEW_9560_X64_CODE10_FINAL.LOG

Also keep this file if Log to File was enabled:

C:\9560LOG\DBGVIEW_9560_X64_CODE10.LOG


10. What to send back

Please zip and send to me these files:

C:\9560LOG\DBGVIEW_9560_X64_CODE10.LOG
C:\9560LOG\DBGVIEW_9560_X64_CODE10_FINAL.LOG


11. If DebugView shows nothing

Try these steps:

A:
Run DebugView as Administrator.

B:
Disable and re-enable:

Capture -> Capture Kernel

C:
Make sure this is enabled:

Capture -> Enable Verbose Kernel Output

D:
Remove the filter completely.
Leave the Include field empty.

E:
Start DebugView before installing or enabling the driver.

F:
Try a different DebugView 4.x version.
For example:
try 4.81 instead of 4.90,
or 4.90 instead of 4.81.

G:
If there is still no output, we need a special 9560 x64 diagnostic build that writes the init status into the registry instead of using DbgPrint.


12. How to interpret the result

If the log stops around:

query resources
mapped resources

Possible cause:
PCI / UEFI / ACPI resource problem, BAR/MMIO mapping problem.

If it stops around:

NdisMRegisterInterrupt

Possible cause:
IRQ / INTx / UEFI / ACPI interrupt routing problem.

If it reaches:

embedded fw hdr

The driver reached firmware loading.

If it shows:

alive wait end alive=0

Possible cause:
Firmware did not start, awake/reset/boot/power problem.

If it shows:

bootstrap status alive=1

Firmware started successfully; the failure is later in the init path.

If it shows:

WifiInitialize success

The driver initialization itself succeeded.
Then Code 10 is probably caused by a later NDIS status, wrong return value, binding issue, or another post-init failure.

 

Edited May 12 by Dietmar

[reboot12]

OK, send me diagnostic driver 137

DbgView 4.90 not work on XP but 4.81 yes:
https://web.archive.org/web/20180926162235/https://download.sysinternals.com/files/DebugView.zip

Edited May 12 by reboot12