1. #1

    BSOD after upgrading to Windows 8.1

    Hi folks,
    I upgraded to Windows 8.1 and started to have BSODs. I called support they said the diagnostics were all fine. I called the display vendor and they had me remove the add-on NVDIA card. I still get the BSODs, just not as regularly. It used to happen every day or so, now twice in a week. I am attaching the zip, but I deleted the Memory.dmp by mistake while following another companies tech support. Please let me know what I need to do next to get rid of this headache. Thanks so much!

    • Ad Bot



  2. #2

    re: BSOD after upgrading to Windows 8.1


    All of the attached DMP files are of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bug check.

    This indicates that a system thread generated an exception which the error handler did not catch.

    BugCheck 1000007E, {ffffffffc0000005, fffff80000f62697, ffffd00022550288, ffffd0002254fa90}

    ^^ The 1st parameter of the bug check is 0xc0000005 which indicates an access violation occurred:

    3: kd> .exr 0xffffd00022550288
    ExceptionAddress: fffff80000f62697 (ndis!ndisCreateStringStreamEntry+0x000000000000002f)
       ExceptionCode: c0000005 (Access violation)
    ^^ The violation occurred in ndis!ndisCreateStringStreamEntry. This is a network related routine, specifically with ndis.sys.

    The Network Driver Interface Specification (NDIS) is an application programming interface (API) for network interface cards (NICs). The NDIS forms the Logical Link Control (LLC) sublayer, which is the upper sublayer of the OSI data link layer (layer 2). Therefore, the NDIS acts as the interface between the Media Access Control (MAC) sublayer, which is the lower sublayer of the data link layer, and the network layer (layer 3).

    The NDIS is a library of functions often referred to as a "wrapper" that hides the underlying complexity of the NIC hardware and serves as a standard interface for level 3 network protocol drivers and hardware level MAC drivers. Another common LLC is the Open Data-Link Interface (ODI).

    What's likely occurring here is McAfee did not (to no surprise) handle the upgrade transition properly, and it now causing NETBIOS and other network related conflicts, which is leading to kernel corruption.

    1. Remove and replace McAfee with Windows 8's built-in Windows Defender for temporary troubleshooting purposes:

    McAfee removal - How to uninstall or reinstall supported McAfee products using the Consumer Products Removal tool (MCPR)

    Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8

    2. npf.sys is listed and loaded which is the NetGroup Packet Filter Driver, part of the WinPcap packet capture library. Please uninstall this software ASAP.

    3. wdcsam64.sys is listed and loaded which is the Western Digital SES (SCSI Enclosure Services) driver. Please remove this software ASAP as it's troublesome and is also not necessary to the functionality of your system.



Similar Threads

  1. BSOD while running Windows Store on Windows 8.1
    By hacker8 in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 01-15-2014, 09:33 AM
  2. Windows 7 x64 BSOD - PFN_LIST_CORRUPT BSOD
    By emreblt in forum BSOD, Crashes, Kernel Debugging
    Replies: 4
    Last Post: 03-23-2013, 03:23 AM
  3. [SOLVED] BSOD on Upgraded Windows 8 PRO from Windows 7 Home Premium
    By hbeaufelipe in forum BSOD, Crashes, Kernel Debugging
    Replies: 17
    Last Post: 03-21-2013, 01:18 PM
  4. BSoD on Windows Defender Quick Scan in Windows 8
    By akshay2000 in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 12-24-2012, 11:39 PM
  5. Upgrading an impossibly old system to Windows 8
    By JMH in forum News You Can Use
    Replies: 0
    Last Post: 09-21-2012, 11:11 PM

Log in

Log in