Help with random crashes on Windows 11 (netadaptercx)

Question

Help with random crashes on Windows 11 (netadaptercx)

Cruba 0

I built a brand new PC a few weeks ago, and I have been experiencing random crashes. Everything would be just fine, every time I run a diagnosis of some sort, and stress test the system, everything works good. It is random sometimes i could go many hours or using computer and gaming and no issue. Then i would be casually watching a video on youtube and i get the crash. I posted on this site over a week ago for some assistance, see link for that history https://learn.microsoft.com/en-us/answers/questions/5989728/help-please-i-get-random-intermittent-bsod-crashes. From there it was determined that a Logitech surround sound driver was the culprit. I completely removed it and i am still crashing. The minidump file that generates when it crashes does have much info, at least not from what i can tell. it always has generic windows MODULE_NAME: nt. Similar to what i did before (link) I would turn on Driver Verifier. It would never successfully boot windows, then i would eventually be able to boot in safe and turn it off. When i see the generated minidump file it says, MODULE_NAME: netadaptercx. This has been the case for the last few crashes i tried Driver verifier with. I have done everything i found recommended online for this netadaptercx.sys issue. I completed removed and reinstalled all my network drivers. Used the latest available directly from Mediatek (Wifi 7 Lan Card) and Realtek (5GbE Family Controller) directly. These are the onboard equipment on the ASUS Rog Strix x870e-e MoBo. I tried The power option recommendations and cleared the network stack. Nothing seems to work. After some time of PC running perfectly. it would crash again randomly. Does anyone have any idea or suggestions to help me out. See below the link to Latest Minidump files for crashes. https://drive.google.com/drive/folders/1hsIg6Is4kUOk1aGSQTZRdq76oQvXSTG5?usp=sharing

0 comments

2 answers

Your answer

Answer 1

Ivan B 122.5K Independent Advisor

Hi,

You have two errors that are possibly memory-related, two involving the network adapter driver, and one kernel error that might be chipset-related.

Did you perform any BIOS updates or change any BIOS settings?

If possible, run the Windows Memory Diagnostic (search for it in the search bar) to see if it detects any errors.

When reinstalling the drivers, did you install the motherboard driver instead of the MediaTek and Realtek ones?

Are you using a Wi-Fi connection or a wired (cable) connection?

Thanks.

Cruba 0 Reputation points

2026-09-11T15:01:32.23+00:00

Thanks for the reply. I am on the latest Version of the BIOS, have been since the initial build of the PC. I have even reflashed the BIOS since troubleshooting my issues. I don't have any BIOS settings really changed. I do have EXPO for the RAM on, i have had it off in troubleshooting and still same issues. I have even replaced the RAM initially since I thought it may have been a RAM issue, but nothing changed. I have run Windows Memory Diagnostic several times, never had any issues identified. Initially I obtained all drivers from ASUS site for my motherboard. Since having the issues and troubleshooting, I went ahead and updated to latest drivers from MediaTek and Realtek directly since I notice they were a newer version. I am using the Wi-FI connection, which is the onboard one that came with the MoBo using its Antenna it came with.
Ivan B 122.5K Reputation points Independent Advisor

2026-09-11T15:16:18.14+00:00

Hi,

Can't you run a test using just the network cable and disable the Wi-Fi network in the BIOS to confirm if it's a hardware failure of the Wi-Fi card?

Thanks.
Ivan B 122.5K Reputation points Independent Advisor

2026-09-11T15:20:10.76+00:00

Hi,

Since a hardware failure—specifically a defective Wi-Fi/Bluetooth controller—is a possibility, and assuming the motherboard is still under warranty, the best initial way to test this would be to disable the Wi-Fi card in the BIOS and use a wired connection to see if the problem persists.

Thanks.

Answer 2

Since Driver Verifier is consistently surfacing netadaptercx, focus on the network stack and broader stop-code troubleshooting rather than repeating the Logitech driver work already done.

Check Device Manager for both onboard network adapters
- Right-click Start > Device Manager.
- Expand Network adapters.
- For the MediaTek Wi‑Fi adapter and the Realtek 5GbE controller, check whether either device shows an exclamation mark.
- Open each adapter’s properties and review whether Windows reports a device problem.
- If needed, Update driver from there, or temporarily disable one adapter at a time to isolate whether Wi‑Fi or Ethernet is involved.
Use Safe Mode for isolation testing
- Since Driver Verifier can prevent normal startup, use Safe Mode while removing or disabling components.
- Safe Mode loads only the minimum required drivers and services, which helps determine whether a third-party or device driver is involved.
Check Event Viewer around the crash time
- Review the system log in Event Viewer for critical errors that occurred in the same time frame as the stop code.
- Look for entries that help identify the device or driver involved.
Run System File Checker
- Open an elevated Command Prompt and run:
```
     SFC /scannow
```
- This checks for missing or corrupted Windows system files and repairs them when possible.
Check disk and free space
- For file system issues, right-click the drive > Properties > Tools > Check now.
- Also confirm the system drive has sufficient free space. A good target is 10% to 15% free space.
Run Windows Memory Diagnostics
- In Control Panel, search for Memory.
- Select Diagnose your computer's memory problems.
- After the test, review Event Viewer for the MemoryDiagnostics-Results entry.
Install the latest Windows 11 updates
- Go to Start > Settings > Windows Update > Check for updates.
Check for recent hardware, firmware, or compatibility issues
- If any hardware was added or changed recently, remove or reseat it.
- Confirm all cables and expansion boards are properly connected.
- Check with the motherboard manufacturer for updated BIOS/UEFI firmware.
Capture and analyze a dump file if crashes continue
- Verify the PC is configured to generate a memory dump.
- After a crash, copy memory.dmp to another PC if needed.
- Install Debugging Tools for Windows from the Windows SDK, open the dump in WinDbg, and set symbols to the Microsoft public symbol server: https://msdl.microsoft.com/download/symbols
- This is the supported path for deeper analysis when minidumps only show generic modules.
Use Driver Verifier carefully

Since it already causes boot failures, use it only with a restore point and with Safe Mode available as a recovery path.
Risk: Driver Verifier intentionally stresses drivers and can make the system unbootable until it is disabled.

If the crashes only occur when one network adapter is enabled, that strongly points to that adapter, its driver, or related software. If crashes continue with either adapter disabled individually, the issue is more likely broader driver, firmware, memory, or system-file related.