📎 AI Summary:
The forum thread discusses a BSOD error caused by the ndis.sys file, with the original poster seeking help to debug their dump files. A responder analyzes the dumps and identifies the likely cause as an outdated Ethernet driver (e22w10x64.sys), recommending an update via the motherboard support page and suggesting troubleshooting steps like disabling antivirus software if issues persist. The original poster expresses gratitude for the assistance, indicating a positive and constructive exchange.
Q

Quyeno

New Member
Member details
Joined
Aug 6, 2016
Messages
5
Thread Author #1
Hi

I've been get an ndis.sys BSOD the past few days. I've done a system file scan and no issues were found. I would really appreicate it someone could please debug my dump files? I've attached the 3 dump files from the past few days, the latest being today.

Thanks
Quyeno
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff8010039e039}

*** WARNING: Unable to verify timestamp for e22w10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w10x64.sys
Probably caused by : e22w10x64.sys ( e22w10x64+6cab )

Followup: MachineOwner
Hi,
all three dump...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#2
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff8010039e039}

*** WARNING: Unable to verify timestamp for e22w10x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w10x64.sys
Probably caused by : e22w10x64.sys ( e22w10x64+6cab )

Followup: MachineOwner
Hi,
all three dump files were the same and point to your ethernet driver,

e22w10x64.sys Mon Apr 27 20:36:50 2015; Killer e2200 PCI-E Gigabit Ethernet Controller. Please update this driver using your motherboard support page. You will see its a slightly later version found in the windows 10 64bit section, at the top, called Bigfoot Lan driver.
GIGABYTE - Motherboard - Socket 1151 - GA-Z170X-Gaming 5 (rev. 1.0)

If you find the above driver doesnt seem to work then disable your anti virus, uninstall and then reinstall making sure the AV suite is disabled... I use the same driver so know some of its idiosyncrasies.

Please post any new dump files
 

Upvote 1 Downvote
Solution
You must log in or register to reply here.