Page 2 of 3 FirstFirst 123 LastLast
  1.    13 Jul 2017 #11
    Join Date : Jan 2017
    Karlsruhe
    Posts : 733
    Windows 10 Pro

    All BSOD dumps show e2xw10x64.sys

    This BSOD is from 11.07.2017. The driver e2xw10x64.sys for Killer e2400 PCI-E Gigabit Ethernet Controller is dated 14.09.2016:

    Code:
    0x000000C2:    BAD_POOL_CALLER (11.07.2017 15:18:06) [Windows 10] 
     
    CAUSED BY:     memory_corruption    
                   e2xw10x64.sys [14.09.2016]   
                   fwpkclnt.sys [28.01.1999] * FWP/IPsec Kernel-Mode API (Windows System File) 
     
    PROCESS:       chrome.exe 
     
    Usual causes:  Device driver, ?Memory

    Then u update the driver to driver date 13.04.2017:

    Code:
    0x000000C5:    DRIVER_CORRUPTED_EXPOOL (12.07.2017 13:19:22) [Windows 10] 
     
    CAUSED BY:     memory_corruption    
                   e2xw10x64.sys [13.04.2017]   
     
    PROCESS:       System 
     
    Usual causes:  Device driver, ?Memory

    Since u updated this driver to newer version install the whole Killer Suite from here:
    Killer Control Center 64-bit
    Last edited by BSODHunter; 13 Jul 2017 at 09:27.
      My ComputerSystem Spec
  2.    13 Jul 2017 #12
    Join Date : Jun 2017
    Posts : 11
    windows 10 64bit
    Thread Starter

    what is the best way to fix e2xw10x64.sys
      My ComputerSystem Spec
  3.    13 Jul 2017 #13
    Join Date : Jan 2017
    Karlsruhe
    Posts : 733
    Windows 10 Pro

    Quote Originally Posted by WallyG View Post
    what is the best way to fix e2xw10x64.sys
    Since u updated this driver to newer version install the whole Killer Suite from here:
    Killer Control Center 64-bit
      My ComputerSystem Spec
  4.    13 Jul 2017 #14
    Join Date : Apr 2017
    Posts : 8,761
    windows 10 professional version 1607 build 14393.969 64 bit

    06/18/2017
    Code:
    ffff8301`b7561c78  fffff802`ff4b29f1Unable to load image \SystemRoot\System32\Drivers\dump_iaStorA.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for dump_iaStorA.sys*** ERROR: Module load completed but symbols could not be loaded for dump_iaStorA.sys dump_iaStorA+0xb29f1
    Code:
    iaStorA      iaStorA                iaStorA                Kernel        Boot       Running    OK         TRUE        FALSE        4,096             696,320     0          13/09/2016 15:45:46    C:\WINDOWS\system32\drivers\iaStorA.sys          4,096      iaStorAV     Intel(R) SATA RAID Con Intel(R) SATA RAID Con Kernel        Manual     Stopped    OK         FALSE       FALSE        4,096             593,920     0          19/02/2015 12:08:39    C:\WINDOWS\system32\drivers\iaStorAV.sys         4,096      iaStorV      Intel RAID Controller  Intel RAID Controller  Kernel        Manual     Stopped    OK         FALSE       FALSE        0                 364,544     0          11/04/2011 19:48:16    C:\WINDOWS\system32\drivers\iaStorV.sys
    iaStorA.sys Intel RST (Rapid Storage Technology) driver http://downloadcenter.intel.com/Default.aspx XP


    Code:
    asmtxhci     ASMedia XHCI Service   ASMedia XHCI Service   Kernel        Manual     Running    OK         TRUE        FALSE        8,192             385,024     0          11/07/2016 07:44:28    C:\WINDOWS\system32\DRIVERS\asmtxhci.sys
    Code:
    ffff8301`b7562b98  fffff803`0292425f asmtxhci+0x425f


    06/18/2017
    Code:
    BugCheck C4, {2000, fffff80fb7f2425f, 0, 7067444d}*** WARNING: Unable to verify timestamp for asmtxhci.sys*** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sysProbably caused by : memory_corruption
    Code:
    ffff8201`7a95fc78  fffff80f`b61c29f1Unable to load image \SystemRoot\System32\Drivers\dump_iaStorA.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for dump_iaStorA.sys*** ERROR: Module load completed but symbols could not be loaded for dump_iaStorA.sys dump_iaStorA+0xb29f1
    06/18/2017
    Code:
    BugCheck C2, {7, 3f3a107b, e0337232, ffffad87b33e4498}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
    Probably caused by : NETIO.SYS ( NETIO! ?? ::FNODOBFM::`string'+9d98 )

    Code:
    BugCheck C2, {7, 0, 0, ffffae0836648118}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
    Probably caused by : memory_corruption


    Code:
    BugCheck C2, {7, 0, 8, ffffdd8fb88f0478}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
    Probably caused by : NETIO.SYS ( NETIO!memset+101d2 )
    Code:
    BugCheck C2, {7, 65, 65, ffffb98edb3a2188}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
    Probably caused by : memory_corruption
    Code:
    BugCheck C2, {7, 0, 0, ffffc009535a6c78}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
    Probably caused by : NETIO.SYS ( NETIO!memset+101d2 )
    Code:
    BugCheck C2, {7, 0, 0, ffffcf8550ad5198}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
    *** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck C2, {99, ffffcd89040ae278, 0, 0}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck C2, {7, 0, 0, ffffab8f4e2d0958}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
    Probably caused by : memory_corruption
    Code:
    BugCheck C2, {7, 0, 0, ffffcb0d894f2b28}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
    Probably caused by : memory_corruption
    Code:
    BugCheck C2, {10, ffffe38727f17748, 27f17700, ffffe38727f17770}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck C2, {7, 0, 0, ffffe682f3d80888}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sysunable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPagedPoolEndunable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytesProbably caused by : NETIO.SYS ( NETIO!memset+101d2 )
    Code:
    BugCheck C5, {ffffa70007bc9d8b, 2, 0, fffff803ed71b6d5}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption


    Code:
    e2xw10x64    NDIS Miniport Driver f NDIS Miniport Driver f Kernel        Manual     Running    OK         TRUE        FALSE        0                 122,880     0          13/04/2017 18:09:57    C:\WINDOWS\system32\drivers\e2xw10x64.sys
    Code:
    KillerEth    NDIS Miniport Driver f NDIS Miniport Driver f Kernel        Manual     Stopped    OK         FALSE       FALSE        0                 122,880     0          13/04/2017 18:09:57    C:\WINDOWS\system32\drivers\e2xw10x64.sys
    Code:
    +++ WER2 +++:Fault bucket 116403965258, type 5Event Name: BEXResponse: Not availableCab Id: 0Problem signature:P1: MSI_LiveUpdate_Service.exeP2: 1.0.0.44P3: 5949e886P4: NDA.dll_unloadedP5: 1.0.0.15P6: 581aa4ccP7: 000f650eP8: c0000005P9: 00000008P10:
    Code:
    11/07/2017 13:21    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x05219051
    Faulting process ID: 0x23dc
    Faulting application start time: 0x01d2fa489bc14ca3
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: c4148c35-ba4a-4460-9ce1-de8cc34a285e
    Faulting package full name: 
    Faulting package-relative application ID:11/07/2017 13:13    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x05359051
    Faulting process ID: 0x6dc
    Faulting application start time: 0x01d2fa478ad4ea78
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: d5644888-929a-4009-ad41-1a7c95ea7a4b
    Faulting package full name: 
    Faulting package-relative application ID:10/07/2017 19:25    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x05619049
    Faulting process ID: 0x107c
    Faulting application start time: 0x01d2f9b24f4c612e
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: 5144b3fc-2f5b-41e3-877e-2f76fe82b420
    Faulting package full name: 
    Faulting package-relative application ID:10/07/2017 19:00    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x047e9051
    Faulting process ID: 0xd60
    Faulting application start time: 0x01d2f9aec609d627
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: 9d85d04f-259b-4318-9817-334419ba42cf
    Faulting package full name: 
    Faulting package-relative application ID:10/07/2017 18:56    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x04d59051
    Faulting process ID: 0x1100
    Faulting application start time: 0x01d2f9ae3e5929f8
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: a391be10-ba2e-4d41-9aa1-a8e361dd5c9d
    Faulting package full name: 
    Faulting package-relative application ID:08/07/2017 09:32    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x05399051
    Faulting process ID: 0xd04
    Faulting application start time: 0x01d2f7cd0c1369f9
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: dcece3ba-ba26-4a37-a718-49928b5a7e74
    Faulting package full name: 
    Faulting package-relative application ID:07/07/2017 21:10    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x04b79051
    Faulting process ID: 0x3a24
    Faulting application start time: 0x01d2f7656ab8e3c9
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: b3a37439-6705-4713-b831-8a892409c1f6
    Faulting package full name: 
    Faulting package-relative application ID:
    Code:
    07/07/2017 14:18    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x055d9051
    Faulting process ID: 0x4250
    Faulting application start time: 0x01d2f72bf1f7d026
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: e1cbd33e-94f6-4955-aa3a-889db703a7e0
    Faulting package full name: 
    Faulting package-relative application ID:03/07/2017 11:35    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x05319051
    Faulting process ID: 0x3794
    Faulting application start time: 0x01d2f3f070f4e712
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: 02b73940-5781-42c8-93f8-f055fd5eeb93
    Faulting package full name: 
    Faulting package-relative application ID:03/07/2017 11:32    Application Error    Faulting application name: IAStorDataMgrSvc.exe, version: 15.7.0.1014, time stamp: 0x5936d827
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x05299051
    Faulting process ID: 0x2ffc
    Faulting application start time: 0x01d2f3f00049cbcf
    Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
    Faulting module path: unknown
    Report ID: 533fc0b9-d9da-4502-889e-85a5f7830ba3
    Faulting package full name: 
    Faulting package-relative application ID:
    Code:
    02/07/2017 18:13    Application Error    Faulting application name: DSADesktopUI.exe, version: 0.0.0.0, time stamp: 0x591df182
    Faulting module name: KERNELBASE.dll, version: 10.0.15063.296, time stamp: 0x28e9cf15
    Exception code: 0xc000041d
    Fault offset: 0x000eb802
    Faulting process ID: 0x243c
    Faulting application start time: 0x01d2f35cc7aa53bc
    Faulting application path: C:\Program Files (x86)\Intel Driver Update Utility\DSADesktopUI.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report ID: b0ccc01b-52cb-4f69-beba-97809e773d88
    Faulting package full name: 
    Faulting package-relative application ID:02/07/2017 18:13    Application Error    Faulting application name: DSATray.exe, version: 0.0.0.0, time stamp: 0x591df18d
    Faulting module name: KERNELBASE.dll, version: 10.0.15063.296, time stamp: 0x28e9cf15
    Exception code: 0xe0434352
    Fault offset: 0x000eb802
    Faulting process ID: 0x1b58
    Faulting application start time: 0x01d2f35cc7c4be1d
    Faulting application path: C:\Program Files (x86)\Intel Driver Update Utility\DSATray.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report ID: 2f35a4fb-cf2d-4ae7-81a6-1c38648b1e93
    Faulting package full name: 
    Faulting package-relative application ID:02/07/2017 18:13    Application Error    Faulting application name: DSADesktopUI.exe, version: 0.0.0.0, time stamp: 0x591df182
    Faulting module name: KERNELBASE.dll, version: 10.0.15063.296, time stamp: 0x28e9cf15
    Exception code: 0xe0434352
    Fault offset: 0x000eb802
    Faulting process ID: 0x243c
    Faulting application start time: 0x01d2f35cc7aa53bc
    Faulting application path: C:\Program Files (x86)\Intel Driver Update Utility\DSADesktopUI.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report ID: 1a50b3e2-3781-4462-9b61-29ce5905f8a3
    Faulting package full name: 
    Faulting package-relative application ID:
    Code:
    Unable to produce a minidump file from the full dump file.
    Code:
    Event[5721]:  Log Name: System  Source: Service Control Manager  Date: 2017-07-12T10:52:09.061  Event ID: 7034  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-GFK955D  Description: The MSI Live Update Service service terminated unexpectedly. It has done this 1 time(s).
    Code:
    Unable to produce a minidump file from the full dump file.
    Code:
    Unable to produce a minidump file from the full dump file.
    Code:
    The previous system shutdown at 21:33:01 on ?11/?07/?2017 was unexpected.
    Code:
    Unable to produce a minidump file from the full dump file.
    Code:
    The previous system shutdown at 15:30:40 on ?11/?07/?2017 was unexpected.
    Code:
    The previous system shutdown at 15:23:13 on ?11/?07/?2017 was unexpected.
    Code:
    Event[59]:  Log Name: System  Source: Service Control Manager  Date: 2017-06-25T17:54:40.788  Event ID: 7045  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GFK955D  Description: A service was installed in the system.Service Name:  NDIS Miniport Driver for Killer PCI-E Gigabit Ethernet ControllerService File Name:  \SystemRoot\System32\drivers\e2xw10x64.sysService Type:  kernel mode driverService Start Type:  demand startService Account:
    Code:
    Event[5086]:  Log Name: System  Source: Service Control Manager  Date: 2017-07-11T14:57:06.989  Event ID: 7045  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GFK955D  Description: A service was installed in the system.Service Name:  NDIS Miniport Driver for Killer PCI-E Gigabit Ethernet ControllerService File Name:  \SystemRoot\System32\drivers\e2xw10x64.sysService Type:  kernel mode driverService Start Type:  demand startService Account:





    There were multiple unexpected shutdowns. Are you experiencing hangs?



    1) As BSODHunter posted the new bsod are all displaying e2xw10x64.sys
    That is NDIS Miniport Driver for Killer PCI-E Gigabit Ethernet Controller
    The last entry in the event log for this driver was on 07/11/2017: A service was installed in the system.


    2) Prior to this there were 2 misbehaving drivers identified:
    a) iaStorA.sys
    Intel RST (Rapid Storage Technology) driver
    b) asmtxhci.sys
    Asmedia USB 3.0 driver
    IAStorDataMgrSvc.exe is currently on the list as faulting applications.
    On the computer manufacturer's web site enter the computer's serial or product number and download and install updated drivers for Intel


    3) The Memtest86+ displayed results were 6 passes. There can be false negatives if fewer than 8 passes are performed in one setting.
    If there are any recurrent bsod the Memtest86+ version 5.01 should be performed for at least 8 passes so that RAM /DIMM problems can be ruled in /out.


    4) Uninstall the Intel driver update utility using the control panel and reinstall the Intel driver update utility: Intel® Driver Update Utility


    5) Uninstall /reinstall: MSI Live Update Service


    6) There were approximately 30: Unable to produce a minidump file from the full dump file.
    a) Using file explorer locate the memory.dmp file and post a one drive or drop box share link into the thread.
    b) Check the settings for memory.dmp: In the left lower corner search type: system > to open the system control panel > on the left pane click on advanced system settings > on the system properties pop up locate startup and recovery and click on: settings > on the startup and recovery pop up use the Microsoft snipping tool or print screen paint to capture the image and post into the thread.
      My ComputerSystem Spec
  5.    13 Jul 2017 #15
    Join Date : Jun 2017
    Posts : 11
    windows 10 64bit
    Thread Starter

    Dropbox - MEMORY.DMP the memory dump my pc just crashes not been hanging at all

    ive reinstalled killer control and its drivers, which now up to date.i did redownload asmedia and MSI live update from MSI website and installed it. ive also reinstalled the intel driver update utility but when i scan my pc for drivers i get " No drivers were detected for your product"
      My ComputerSystem Spec
  6.    13 Jul 2017 #16
    Join Date : Apr 2017
    Posts : 8,761
    windows 10 professional version 1607 build 14393.969 64 bit

    Review of today's MEMORY.DMP file

    Code:
    fffff800`1df242a8  fffff80c`612001b8*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys iaStorA+0x901b8
    iaStorA Intel Chipset SATA RAI Intel Chipset SATA RAI Kernel Boot Running OK TRUE FALSE 4,096 782,336 0 17/03/2017 14:32:24 C:\Windows\system32\drivers\iaStorA.sys 4,096 iaStorAV Intel(R) SATA RAID Con Intel(R) SATA RAID Con Kernel Manual Stopped OK FALSE FALSE 4,096 593,920 0 19/02/2015 12:08:39 C:\Windows\system32\drivers\iaStorAV.sys 4,096 iaStorV Intel RAID Controller Intel RAID Controller Kernel Manual Stopped OK FALSE FALSE 0 364,544 0 11/04/2011 19:48:16 C:\Windows\system32\drivers\iaStorV.sys

    iaStorA.sys Intel RST (Rapid Storage Technology) driver http://downloadcenter.intel.com/Default.aspx XP


    Code:
    fffff800`1df23c48  fffff80c`6414b33d*** ERROR: Module load completed but symbols could not be loaded for rzudd.sys rzudd+0x1b33d


    Code:
    rzudd        Razer Mouse Driver     Razer Mouse Driver     Kernel        Manual     Running    OK         TRUE        FALSE        0                 167,936     0          16/06/2016 04:43:26    C:\Windows\system32\drivers\rzudd.sys

    Code:
    fffff800`1df225b8  fffff80c`6463dd55*** ERROR: Module load completed but symbols could not be loaded for dump_iaStorA.sys dump_iaStorA+0x6dd55
    Code:
    fffff800`1df21798  fffff80c`65b44b7b*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x204b7b


    nvlddmkm.sys nVidia Video drivers http://www.nvidia.com/Download/index.aspx
    Get from OEM for laptops

    e2xw10x64

    Code:
    KillerEth    NDIS Miniport Driver f NDIS Miniport Driver f Kernel        Manual     Running    OK         TRUE        FALSE        0                 122,880     0          14/09/2016 21:52:26    C:\Windows\system32\drivers\e2xw10x64.sys
    Code:
    KillerEth    NDIS Miniport Driver f NDIS Miniport Driver f Kernel        Manual     Running    OK         TRUE        FALSE        0                 122,880     0          14/09/2016 21:52:26    C:\Windows\system32\drivers\e2xw10x64.sys


    Code:
    fffff800`1df20e88  fffff80c`632d13ad*** ERROR: Symbol file could not be found.  Defaulted to export symbols for em042_64.dll -  em042_64+0x13ad
    Code:
    fffff800`1df20b08  fffff80c`630d3e10*** ERROR: Module load completed but symbols could not be loaded for epfw.sys epfw+0x3e10
    Code:
    epfw         epfw                   epfw                   Kernel        System     Running    OK         TRUE        FALSE        4,096             36,864      0          25/01/2017 12:40:04    C:\Windows\system32\DRIVERS\epfw.sys



    Code:
    fffff800`1df20c88  fffff80c`6313a811*** ERROR: Symbol file could not be found.  Defaulted to export symbols for em008_64.dll -  em008_64!module_init_entry+0x48e51



    1) reinstall all Intel chipset drivers
    and reinstall Intel rapid storage technology
    Downloads for Intel® Rapid Storage Technology (Intel® RST)

    2) uninstall Razer Rzudd Engine Driver rzudd.sys
    reinstall: Razer Support

    3) Uninstall all Nvidia drivers/softwareThe best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from the NVidia website.
    When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
    Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download

    4) Uninstall all ESET software using control panel followed by
    Uninstall ESET manually using the ESET uninstaller toolESET Knowledgebase

    5) uninstall KillerEth NDIS Miniport Driver f Kernel C:\Windows\system32\drivers\e2xw10x64.sys
    reinstall: Support
      My ComputerSystem Spec
  7.    14 Jul 2017 #17
    Join Date : Jun 2017
    Posts : 11
    windows 10 64bit
    Thread Starter

    I've reinstalled all the drivers you listed and completed the memtest, after reinstalling the drivers i rebooted my PC and it crashed straight away, ive added the latest memory dump file
    Dropbox - MEMORY.DMP
    Attachment 143886
      My ComputerSystem Spec
  8.    14 Jul 2017 #18
    Join Date : Apr 2017
    Posts : 8,761
    windows 10 professional version 1607 build 14393.969 64 bit
      My ComputerSystem Spec
  9.    14 Jul 2017 #19
    Join Date : Jun 2017
    Posts : 11
    windows 10 64bit
    Thread Starter

    Added the DM log
      My ComputerSystem Spec
  10.    14 Jul 2017 #20
    Join Date : Apr 2017
    Posts : 8,761
    windows 10 professional version 1607 build 14393.969 64 bit

    There were 5 new bsod today.
    The memtest86+ was successful with 8 passes.
    There were no new drivers misbehaving in the dump files.
    They were all previously found misbehaving drivers.
    If possible there is one driver that I would like you not to reinstall for several days of troubleshooting.



    1) open file explorer and search for: e2xw10x64.sys
    2) uninstall: NDIS Miniport Driver using device manager
    3) open file explorer and using search type: e2xw10x64.sys
    4) make sure there are no entries found
    5) attempt to connect to the internet with both wireless and wired.
    6) if you are unable to connect to the internet then reinstall the driver:
    Killer Driver Suite
    I think this driver is only for a wired ethernet connection. Please confirm. If you are able to only use wifi then do that for the troubleshooting so that we can see if there are days with no bsod.
    If you must have this driver then download the Killer networking driver without the killer feature ( without bandwidth controller)
    7) using control panel uninstall Intel rapid storage technology
    reinstall: Downloads for Intel® Rapid Storage Technology (Intel® RST)


    Code:
    BugCheck C2, {7, ffffbf05, 945416a0, ffffbf0591379788}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys
    Code:
    BugCheck C2, {7, 0, 0, ffff81048d863918}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys*** WARNING: Unable to verify timestamp for iaStorA.sys*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
    Code:
    BugCheck 19, {20, ffff928177147248, ffff928177147688, a5445e02}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sysProbably caused by : NETIO.SYS ( NETIO!NetioFreeMdl+136e8 )
    Code:
    BugCheck C2, {99, ffff9a8005fbb918, 0, 0}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sysProbably caused by : memory_corruption
    Code:
    BugCheck C2, {99, ffffaa8a4f2592e8, 0, 0}*** WARNING: Unable to verify timestamp for e2xw10x64.sys*** ERROR: Module load completed but symbols could not be loaded for e2xw10x64.sys




    Code:
    e2xw10x64    NDIS Miniport Driver f NDIS Miniport Driver f Kernel        Manual     Running    OK         TRUE        FALSE        0                 122,880     0          13/04/2017 18:09:57    C:\WINDOWS\system32\drivers\e2xw10x64.sys        4,096
    Last edited by zbook; 14 Jul 2017 at 15:36.
      My ComputerSystem Spec

 
Page 2 of 3 FirstFirst 123 LastLast


Similar Threads
Thread Forum
Solved Random crashing of computer with BSOD
89297 I hope this is the correct file. Computer crashes randomly with the BSOD and at one point crashed in the middle of booting. Also got error code 0xc0000221 when telling me of missing or corrupt files. Computer finally boot and no problem at the...
BSOD Crashes and Debugging
BSOD ntoskrnl.exe and crashing
I have a PC running windows 10 and recently it will just crash, I haven't had the typical blue screen error message but the PC will either freeze or restart. It started about a week ago when the PC randomly restarted while I was in the middle of...
BSOD Crashes and Debugging
Frequent BSOD Crashing. Help please.
Hey guys. For the past few days I've been getting frequent BSOD crashes with various errors. Some of the ones I've noticed are: Attempted execute of noexecute memory, cache manager, irql not less or equal, watchdog violation, system service...
BSOD Crashes and Debugging
PC Crashing every 4 hours or so with BSOD
Hello there, I am having a super annoying problem with my PC. Everything was fine up until a few days ago (no new programs, no new hardware, no big updates) when my PC started BSODing every few hours. The Event Logs are useless (Event Id 6008 saying...
BSOD Crashes and Debugging
Win 10 pro crashing at random points, no bsod
So I upgraded to windows 10 exactly 1 week ago, and only today have I started to experience crashes. the screen goes black and my PC restarts on its own, I suspect it may be something to do with running flash player on three separate browsers at the...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:00.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums