Share via

BUGCODE_NDIS_DRIVER Error

Anonymous
2014-03-25T08:02:59+00:00

Hello,

I recently installed the update, Windows 8.1. Ever since I have been unable to use my computer. I start up my computer, login to my user (since the upgrade I now login using my Microsoft account) and after about 20 seconds a blue screen with a sad face comes up saying my PC has ran into an error and needs to restart, stating the issue is related to bugcode ndis driver.

i have attempted to restart countless times but the same issue occurs, I am unable to use my computer.

If anyone can assist me with this issue that would be fantastic. Succesfully upgrading to windows 8.1 isn't my priority, I just want a computer that works.

Many thanks,

Karl

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

9 answers

Sort by: Most helpful
  1. Anonymous
    2014-03-25T08:48:20+00:00

    Hi,

    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where .DMP files are located, here's how to get to them:

    1. Navigate to the %systemroot%\Minidump folder.

    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

    If you are going to use Onedrive but don't know how to upload to it, please visit the following:

    Upload photos and files to Onedrive.

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.

    If your computer is not generating .DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    4. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-03-25T10:46:59+00:00

    Thanks for the dumps, Karl!

    BUGCODE_NDIS_DRIVER (7c)

    This bug check indicates that a problem occurred with an NDIS driver.

    So there's the basic definition of this particular bug check. Let's get into the debugging, shall we?

    BugCheck 7C, {1d, ffffe00002f321a0, ffffe000062418c0, 0}

    ^^ ^^ The 1st parameter of the bug check is 0x01 which indicates that the 2nd parameter of the bug check is a miniport address.

    Let's look into it:

    3: kd> !ndiskd.miniport ffffe00002f321a0

    MINIPORT

        [Pointer is unavailable; cannot dereference]

        Ndis Handle        ffffe00002f321a0

        Ndis API Version   [Unreadable version value]

        Adapter Context    ffffe00003600000

        Miniport Driver    ffffe00002f33068 - [Unreadable MiniBlock]  [Unreadable version value]

        Ndis Verifier      [Unreadable value]

        Media Type         802.3

        Physical Medium    Native802.11

        Device Path        String with 116 characters [Buffer at ffffc00002e8dc00 is not available]

        Device Object      [DeviceObject at ffffe00002f330a8 is not readable]

        MAC Address        [MAC address at ffffe000035f99f0 is unavailble]

    ^^ We likely cannot read the Miniport driver or DevObj fields because it's not a Kernel-Dump.

    Anyway, from this, we can see that the type of media that disconnected was 802.3, which is WIRED ethernet. However, the physical medium was Native 802.11, which is a software architecture for wireless LAN (WLAN) network topologies that is integrated into the Windows Vista and later operating systems. Native 802.11 provides a framework for an integrated and extensible set of services and drivers.

    STATE

        Miniport Running

        Device PnP         Started

        Datapath Normal

        Operational status [Unreadable value]

        Operational flags  [Unreadable value]

        Admin status       [Unreadable value]

        Media Connected

        Device Power       [Unreadable value]

        Driver Power       [Unreadable value]

        References         [Ref.ReferenceCount at ffffe00002f33328 is not readable]

        User Handles       0

        Total Resets       0

        Pending OID        None

    ^^ From the above, the Miniport is Running, the PnP is Started, the Datapath is Normal, and finally the Media status is Connected. Well, this is all normal... so why is ndis.sys calling a bugcheck?

    --------------------------

    With all of the above said, I took a venture into your loaded modules list, and I noticed Norton is installed. I am going to take an educated guess and assume that this is the same Norton from BEFORE the upgrade? One of the most common faults during upgrades is the antivirus not transitioning during the upgrade process properly, because of various reasons. Also, in general, it's because the pre-upgrade antivirus version and drivers do not comply with the new OS.

    1. Remove and replace Norton with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it is very likely causing conflicts:

    Norton removal -https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

    Windows Defender (how to turn on after removal) -http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html

    2. You have various Asus bloatware drivers listed and loaded (AiCharger.sys, etc). Please uninstall any/all installed Asus software.

    Regards,

    Patrick

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2014-03-26T11:39:55+00:00

    Glad to hear!

    Regards,

    Patrick

    0 comments No comments
  4. Anonymous
    2014-03-26T11:23:32+00:00

    Hi Patrick,

    Thanks for spending the time to look into this for me. I uninstalled norton but it still came up with the same error and my computer insisted on restarting after around 20 seconds each time I turned it on. I ended up restoring my computer and starting again, it's only a few weeks old so it wasn't an issue. It now works and I won't bother with the 8.1 update.

    Anyway, thanks again for your time,

    Karl

    0 comments No comments
  5. Anonymous
    2014-03-25T10:25:51+00:00

    Hi Patrick,

    Thanks for looking into this for me, I have located the DMP files, zipped them and uploaded them on to Onedrive, please see link below:

    https://onedrive.live.com/redir?resid=93C53971881D1C39%21113

    I wasn't able to find any Kernel-Dumps.

    Thanks again,

    Karl

    0 comments No comments