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.
- Open an elevated Command Prompt and run:
- 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.dmpto 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.