Windows 8 and 8.1 Forums


BSOD being caused by on-board NIC?

  1. #1


    Posts : 5
    Windows 8.1

    BSOD being caused by on-board NIC?


    I need a little help and hope someone here can lend a hand.

    I'm having very regular BSOD on my system, which appear to be due to the ethernet card on the motherboard. I think this because at the same time the BSOD occurs, , there is a event log entry from e1dexpress saying a network link has been established. I'm not establishing a connection at the time of the crash. When it occurs is completely random. Sometimes this happens within minutes of starting the computer. Other times it can be hours.

    I've tried using the drivers which come with Win 8.1, the drivers from the Gigabyte website (I have the GA-Z97X-UD3H motherboard) and the latest drivers directly from Intel. Regardless which driver I use, the BSOD continues to occur. It also doesn't seem to be specific to a certain BIOS update.

    I've attached a ZIP file with 3 minidumps. Can someone please take a look to see if it appears to actually be the NIC that's causing me trouble? Also, I'd gladly accept any advice anyone might have regarding how I might resolve this.

    Huge thanks in advance to anyone who offers assistance!

    EDIT:

    I've now added the output from the SF Debug Tool.
    Last edited by goldenegg; 24 Sep 2014 at 23:08.

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Have you updated the UEFI/BIOS on your Gigabyte motherboard? I have seen issues recently with even versions from 2014 being outdated - and the update has fixed the BSOD problems.

    This device is disabled. Is this deliberate? If so, why?
    Oculus Positonal Tracker USB\VID_2833&PID_0201&MI_00\6&1102C499&0&0000 This device is disabled.
    If not needed, I'd suggest uninstalling the software for this device and physically removing it from the system (if it's a physical device). If it is needed, then please enable it and ensure the software is updated to the latest, Win8.1 compatible version. Then feel free to disable it again (once it's updated).

    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
    Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
    Alternate link: Disk-Tools.com
    Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
    Out of 13 memory dumps there were 10 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - missing Windows Updates
    - compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

    You can get a head start on the hardware diagnostics if you'd like - they are located here: Hardware Diagnostics

    Please uninstall the Western Digital software from the system. The wdcsam64.sys driver dates from 2008 and is a known BSOD cause on some Windows systems.

    Please uninstall Gigabyte Easy Saver (gdrv.sys) and, if installed, Gigabyte EasyTune - they are known to cause BSOD's on some Windows systems.

    Please uninstall your XBox USB wireless controller (xusb21.sys ) This driver is known to cause BSOD's on some Windows systems. FYI - there are no updates for this driver, so if it is to blame your only "fix" will be to remove the device from your system.

    Uninstall CPUID GPU-Z as it's drivers date from 2010 (GPUZ.sys)

    Your Acronis drivers (afcdp.sys) date from 2011, so there's a strong possibility that that program may not be compatible w/Win8.1. Please check at the Acronis site to see if it is.

    If all of this doesn't fix it (and if you pass all of the hardware diagnostics), then please run Driver Verifier according to these directions: Driver Verifier Settings

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Wed Sep 24 22:20:27.378 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092414-4390-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:10:22.151
    Probably caused by :WdFilter.sys ( WdFilter!DllInitialize+15efa )
    BugCheck 19, {20, ffffc000f3b8e710, ffffc000f3b8e710, 5000271}
    BugCheck Info: BAD_POOL_HEADER (19)
    Arguments: 
    Arg1: 0000000000000020, a pool block header size is corrupt.
    Arg2: ffffc000f3b8e710, The pool entry we were looking for within the page.
    Arg3: ffffc000f3b8e710, The next pool entry.
    Arg4: 0000000005000271, (reserved)
    BUGCHECK_STR:  0x19_20
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: 0x19_20_WdFilter!DllInitialize
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep 24 22:09:41.210 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092414-5515-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 21:04:11.586
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+10837 )
    BugCheck 1A, {41287, 20000005b, 0, 0}
    BugCheck Info: MEMORY_MANAGEMENT (1a)
    Arguments: 
    Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
        Parameter 2 contains the referenced virtual address.
    Arg2: 000000020000005b
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x1a_41287
    PROCESS_NAME:  nvstreamsvc.ex
    FAILURE_BUCKET_ID: 0x1a_41287_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 23 22:24:51.948 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092314-4921-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:26:27.716
    Probably caused by :ntkrnlmp.exe ( nt!KiPageFault+23a )
    BugCheck D1, {fffff8033b084b36, 2, 8, fffff8033b084b36}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: fffff8033b084b36, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff8033b084b36, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  conhost.exe
    FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Sep 22 22:49:39.339 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092214-5109-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:6 days 8:37:47.985
    Probably caused by :fileinfo.sys ( fileinfo!FIStreamLogForNL+1f9 )
    BugCheck F5, {68, ffffc00190a338f0, ffffc00190a33940, 0}
    BugCheck Info: FLTMGR_FILE_SYSTEM (f5)
    Arguments: 
    Arg1: 0000000000000068, The reason for the failure
    Arg2: ffffc00190a338f0
    Arg3: ffffc00190a33940
    Arg4: 0000000000000000
    BUGCHECK_STR:  0xF5
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: 0xF5_fileinfo!FIStreamLogForNL
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 16 14:09:29.483 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091614-5125-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 14:38:52.714
    Probably caused by :fileinfo.sys ( fileinfo!FIStreamLogForNL+1f9 )
    BugCheck C2, {99, ffffc0007b00d3a0, 0, 0}
    BugCheck Info: BAD_POOL_CALLER (c2)
    Arguments: 
    Arg1: 0000000000000099, Attempt to free pool with invalid address  (or corruption in pool header)
    Arg2: ffffc0007b00d3a0, Address being freed
    Arg3: 0000000000000000, 0
    Arg4: 0000000000000000, 0
    BUGCHECK_STR:  0xc2_99
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: 0xc2_99_fileinfo!FIStreamLogForNL
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Sep 15 21:52:38.070 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091514-5765-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:2 days 21:39:22.715
    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
    Probably caused by :Ntfs.sys ( Ntfs+e3a9e )
    BugCheck 24, {b500190637, ffffd0006c5218f8, ffffd0006c521100, fffff80074b69a9e}
    BugCheck Info: NTFS_FILE_SYSTEM (24)
    Arguments: 
    Arg1: 000000b500190637
    Arg2: ffffd0006c5218f8
    Arg3: ffffd0006c521100
    Arg4: fffff80074b69a9e
    PROCESS_NAME:  Windlands.exe
    BUGCHECK_STR:  0x24
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: 0x24_Ntfs+e3a9e
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Sep 13 00:11:56.412 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091314-4593-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:51:30.058
    Probably caused by :win32k.sys ( win32k!EngAcquireSemaphore+c159 )
    BugCheck 3B, {c0000005, fffff96000208189, ffffd001681edec0, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff96000208189, Address of the instruction which caused the bugcheck
    Arg3: ffffd001681edec0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID: 0x3B_win32k!EngAcquireSemaphore
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep 10 17:27:08.905 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091014-5062-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:01:18.551
    *** WARNING: Unable to verify timestamp for RiftEnabler.sys
    *** ERROR: Module load completed but symbols could not be loaded for RiftEnabler.sys
    Probably caused by :RiftEnabler.sys ( RiftEnabler+b7be )
    BugCheck 3B, {c0000005, fffff800e76597be, ffffd000241fdd80, 0}
    BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
    Arguments: 
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff800e76597be, Address of the instruction which caused the bugcheck
    Arg3: ffffd000241fdd80, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    BUGCHECK_STR:  0x3B
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  3DMark.exe
    FAILURE_BUCKET_ID: 0x3B_RiftEnabler+b7be
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep 10 16:41:15.107 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091014-4562-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:04:47.756
    Probably caused by :ntkrnlmp.exe ( nt!KiPageFault+23a )
    BugCheck D1, {fffff802e5413d1e, 2, 8, fffff802e5413d1e}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: fffff802e5413d1e, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff802e5413d1e, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep 10 16:35:59.015 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091014-4453-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 3:29:11.665
    Probably caused by :ntkrnlmp.exe ( nt!KxWaitForLockOwnerShipWithIrql+14 )
    BugCheck 24, {b500190637, ffffd0016f6afef8, ffffd0016f6af700, fffff8021a95ac1c}
    BugCheck Info: NTFS_FILE_SYSTEM (24)
    Arguments: 
    Arg1: 000000b500190637
    Arg2: ffffd0016f6afef8
    Arg3: ffffd0016f6af700
    Arg4: fffff8021a95ac1c
    PROCESS_NAME:  svchost.exe
    BUGCHECK_STR:  0x24
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    FAILURE_BUCKET_ID: 0x24_nt!KxWaitForLockOwnerShipWithIrql
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep 10 13:00:39.040 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091014-4796-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:11:53.685
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe000386e4028, be000000, 800400}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe000386e4028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep 10 12:38:57.851 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091014-4953-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:2 days 21:51:42.494
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+3b669 )
    BugCheck 18, {0, ffffc001e0008440, 21, e000c861140804bf}
    BugCheck Info: REFERENCE_BY_POINTER (18)
    Arguments: 
    Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
    Arg2: ffffc001e0008440, Object whose reference count is being lowered
    Arg3: 0000000000000021, Reserved
    Arg4: e000c861140804bf, Reserved
        The reference count of an object is illegal for the current state of the object.
        Each time a driver uses a pointer to an object the driver calls a kernel routine
        to increment the reference count of the object. When the driver is done with the
        pointer the driver calls another kernel routine to decrement the reference count.
        Drivers must match calls to the increment and decrement routines. This bugcheck
        can occur because an object's reference count goes to zero while there are still
        open handles to the object, in which case the fourth parameter indicates the number
        of opened handles. It may also occur when the object?s reference count drops below zero
        whether or not there are open handles to the object, and in that case the fourth parameter
        contains the actual value of the pointer references count.
    BUGCHECK_STR:  0x18
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: 0x18_nt!_??_::NNGAKEGL::_string_
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Sep  7 14:05:28.264 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\090714-5906-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 16:34:45.907
    Probably caused by :ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+0 )
    BugCheck 1E, {ffffffffc0000005, fffff800fe3cf26a, 0, ffffffffffffffff}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800fe3cf26a, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME:  MOM.exe
    FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!SwapContext_PatchXRstor
    CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  F7
      BIOS Release Date             06/17/2014
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  Z97X-UD3H
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Wed Sep 24 22:20:27.378 2014 (UTC - 4:00)**************************
    gdrv.sys                    Thu Mar 12 23:22:29 2009 (49B9D175)
    xusb21.sys                  Thu Aug 13 18:10:17 2009 (4A848F49)
    afcdp.sys                   Wed Jul 20 10:46:03 2011 (4E26EA2B)
    ElbyCDIO.sys                Mon Mar  4 04:21:51 2013 (513467AF)
    tib.sys                     Wed Mar 20 05:00:38 2013 (51497AB6)
    fltsrv.sys                  Mon May 13 05:40:09 2013 (5190B4F9)
    snapman.sys                 Wed Aug 14 08:17:26 2013 (520B7556)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    tib_mounter.sys             Mon Sep 30 09:04:20 2013 (524976D4)
    000.fcl                     Fri Oct 18 03:16:31 2013 (5260E04F)
    dc3d.sys                    Thu Dec 12 08:16:35 2013 (52A9B733)
    iwdbus.sys                  Tue Dec 17 17:47:38 2013 (52B0D48A)
    dtsoftbus01.sys             Fri Feb 21 04:49:36 2014 (53072130)
    TeeDriverx64.sys            Thu Mar 13 14:21:52 2014 (5321F740)
    iaStorA.sys                 Thu Apr  3 19:00:05 2014 (533DE7F5)
    dump_iaStorA.sys            Thu Apr  3 19:00:05 2014 (533DE7F5)
    AnyDVD.sys                  Thu Apr 24 17:13:59 2014 (53597E97)
    e1d64x64.sys                Thu Jun 12 06:10:32 2014 (53997C98)
    nvhda64v.sys                Mon Jul 21 10:17:53 2014 (53CD2111)
    RiftEnabler.sys             Sat Aug 23 11:46:18 2014 (53F8B74A)
    nvvad64v.sys                Thu Sep  4 13:10:48 2014 (54089D18)
    NvStreamKms.sys             Sat Sep  6 00:37:11 2014 (540A8F77)
    nvlddmkm.sys                Thu Sep 18 23:49:22 2014 (541BA7C2)
    nvvadarm.sys                Fri Sep 19 00:05:52 2014 (541BABA0)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep 24 22:09:41.210 2014 (UTC - 4:00)**************************
    GPUZ.sys                    Wed Oct  6 12:14:37 2010 (4CACA06D)
    cpuz137_x64.sys             Mon Aug 11 09:27:34 2014 (53E8C4C6)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 23 22:24:51.948 2014 (UTC - 4:00)**************************
    dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Sep 22 22:49:39.339 2014 (UTC - 4:00)**************************
    e1i63x64.sys                Wed Mar 20 03:37:29 2013 (51496739)
    AMDACPKSL.SYS               Tue Mar 11 19:49:44 2014 (531FA118)
    AtihdWB6.sys                Tue Mar 11 19:50:02 2014 (531FA12A)
    atikmpag.sys                Thu Apr 17 21:07:07 2014 (53507ABB)
    amdacpksd.sys               Thu Apr 17 21:54:17 2014 (535085C9)
    atikmdag.sys                Thu Apr 17 22:13:16 2014 (53508A3C)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 16 14:09:29.483 2014 (UTC - 4:00)**************************
    OCUSBVID.sys                Thu Jul 17 23:44:22 2014 (53C89816)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep 10 17:27:08.905 2014 (UTC - 4:00)**************************
    wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Sep 10 16:41:15.107 2014 (UTC - 4:00)**************************
    atikmpag.sys                Fri Jul  4 21:26:52 2014 (53B7545C)
    atikmdag.sys                Fri Jul  4 21:39:13 2014 (53B75741)
    
    http://www.carrona.org/drivers/driver.php?id=gdrv.sys
    http://www.carrona.org/drivers/driver.php?id=xusb21.sys
    http://www.carrona.org/drivers/driver.php?id=afcdp.sys
    http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
    http://www.carrona.org/drivers/driver.php?id=tib.sys
    http://www.carrona.org/drivers/driver.php?id=fltsrv.sys
    http://www.carrona.org/drivers/driver.php?id=snapman.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=tib_mounter.sys
    http://www.carrona.org/drivers/driver.php?id=000.fcl
    http://www.carrona.org/drivers/driver.php?id=dc3d.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=AnyDVD.sys
    http://www.carrona.org/drivers/driver.php?id=e1d64x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    RiftEnabler.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    nvvadarm.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=GPUZ.sys
    http://www.carrona.org/drivers/driver.php?id=cpuz137_x64.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
    http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=amdacpksd.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    OCUSBVID.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 5
    Windows 8.1


    Sorry for the delay. I had a last minute business trip come up, so I can't do much debugging remotely.

    Don't worry about the Oculus Positonal Tracker. It's for the Oculus Rift and I enable\disable it for development purposes.

    Daemon Tools was installed after the BSODs started on the system, so it can't be that.

    The version of Acronis I'm running is True Image 2014, which fully supports Win 8.1. It's strange the driver is so old though.

    There's a possibility the crashes are due to RiftEnabler.sys, which is also part of the Oculus Rift package. I say this because I ran WhoCrashed on my system while waiting for a response here and it pointed out that driver as a potential issue. I've since sent my crash reports to Oculus for analysis. They're currently bogged down at the moment, so I'm not expecting a response for at least another week.

    I'll be back later next week and I'll give the driver verifier a try.
      My System SpecsSystem Spec

  4. #4


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi GoldenEgg ^_^,

    Unfortunately, Usasma is very busy with work and is having system problems as well. Are you having any issue after implementing Usasma's suggestions?

    If yes, I would ask you to remove the Oculus Rift from the system. I mean please detach it physically. If all of this does not solve your problem, then please run the Driver Verifier according to Usasma's advice and then re run the SF Diagnostic Tool and upload it so that it can be analysed ^_^.
      My System SpecsSystem Spec

  5. #5


    Posts : 5
    Windows 8.1


    I've been extremely ill and am just getting back on my feet now.

    Since my original post, I have done a clean install of my OS and removed the majority of the items Usasma mentioned. I'm still getting regular and random BSODs. I'm starting to wonder if my motherboard is defective and might try to do an RMA. I'd still like to know for sure, so this evening I will try to post recent minidumps along with a complete memory dump with driver verifier. I'll only try driver verifier tonight if I'm able to make a backup of my system first, otherwise it'll have to wait a day or two.

    Thank you very much for the assistance here. Hopefully the cause can be tracked down and I can finally have a stable system.
      My System SpecsSystem Spec

  6. #6


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by goldenegg View Post
    I've been extremely ill and am just getting back on my feet now.

    Since my original post, I have done a clean install of my OS and removed the majority of the items Usasma mentioned. I'm still getting regular and random BSODs. I'm starting to wonder if my motherboard is defective and might try to do an RMA. I'd still like to know for sure, so this evening I will try to post recent minidumps along with a complete memory dump with driver verifier. I'll only try driver verifier tonight if I'm able to make a backup of my system first, otherwise it'll have to wait a day or two.

    Thank you very much for the assistance here. Hopefully the cause can be tracked down and I can finally have a stable system.
    Hi Goldenegg ^_^,

    I hope your health is fine now . If you are still receiving BSODs after doing clean install of the system, I think that we might be dealing with a low level driver/hardware problem here. Kindly report back with the diagnostics of the Hardware (thanks Usasma) -
    Hardware Diagnostics

    Also, make sure that you have updated your Windows using Windows Update. Note that it might take several trips to the Windows Update.

    Let us know how it goes ^_^
      My System SpecsSystem Spec

  7. #7


    Posts : 5
    Windows 8.1


    Thanks. I'm definitely feeling better.

    As per the suggestion of someone on another forum, I ran Memtest86 again. This time, I only ran the test with one DIMM at a time. This time, is returned errors. One of the chips gets 1 error every few passes, while the other had 8536 errors by pass 2.

    Needless to say, my RAM is definitely bad. It's really odd how I never had a single error when testing both chips together. I'm going to contact Mushkin tomorrow to get these replaced. I'm going to replace both, as I don't think even a single error should be acceptable.
      My System SpecsSystem Spec

  8. #8


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by goldenegg View Post
    Thanks. I'm definitely feeling better.

    As per the suggestion of someone on another forum, I ran Memtest86 again. This time, I only ran the test with one DIMM at a time. This time, is returned errors. One of the chips gets 1 error every few passes, while the other had 8536 errors by pass 2.

    Needless to say, my RAM is definitely bad. It's really odd how I never had a single error when testing both chips together. I'm going to contact Mushkin tomorrow to get these replaced. I'm going to replace both, as I don't think even a single error should be acceptable.
    Hi Goldenegg ^_^,

    Can you borrow RAM from a friend or some other place? I would like you to make sure that the DIMM Slots are not bad since the way you are describing the problem, it seems that there is a possibility of the RAM Slots not working properly.
    I hope that it doesn't turn out the latter though since it is a pain in replacing the motherboard

    Let me know how it goes ^_^

    Regards,
    Pranav
      My System SpecsSystem Spec

  9. #9


    Posts : 5
    Windows 8.1


    I got my RAM replaced and it looks like all's well.

    It turns out that one of the 2 sticks I had borrowed to test with was also bad, which is why trying the swap RAM previously didn't help.

    Thanks so much for the help! I really appreciate all the time people took to track down the issue.
      My System SpecsSystem Spec

  10. #10


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by goldenegg View Post
    I got my RAM replaced and it looks like all's well.

    It turns out that one of the 2 sticks I had borrowed to test with was also bad, which is why trying the swap RAM previously didn't help.

    Thanks so much for the help! I really appreciate all the time people took to track down the issue.
    Glad to hear that the issue has been solved ^_^

    In case of any further problem, do not hesitate to post back ^_^
      My System SpecsSystem Spec

BSOD being caused by on-board NIC?
Related Threads
Solved Having randons BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
:ar: THIS THREAD WAS SOLVED BY CHANGING THE MOTHER BOARD. THIS TOPIC WAS CHANGED TO TENFORUMS: Having randons BSOD caused by ntoskrnl.exe - Windows 10 Forums Since I bought my PC, randons BSOD appear (all of them caused by ntoskrnl.exe) >WHEA_UNCORRECTABLE_ERROR, ...
Hi All, I upgraded my PC from win8 to win8.1 and i get BSOD very frequently. Tried to solve it by update all drivers, but it doesn't helps. I ran memory diagnostic before, it show no errors. Please advice.:cry: Attached with my dump files. Thanks in advance
BSOD problems, mostly caused by halmacpi.dll in BSOD Crashes and Debugging
My Dell Venue 8 Pro most of the time reboots when waking up from standby, this also could happen on itself too (mostly by timer wakeups), or somewhen while using it. ================================================== Dump File : 031614-11812-01.dmp Crash Time : 16.03.2014...
BSOD probably caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hi folks - having some trouble troubleshooting a BSOD on a Lenovo Yoga 13. BSOD screen had dpc_watchdog_violation listed, but when running the minidump through Windbg I got to this: Probably caused by : ntoskrnl.exe ( nt+14dca0 ) Wasn't quite sure where to go from here seeing as that...
I have faced a BSOD for days when waking the laptop up from sleep, and then it takes 15 minutes to start up. Refreshing and resetting do not solve the problem. I have attached the SF zip file The crashes are usually caused by: On Tue 1/21/2014 3:10:37 AM GMT your computer crashed crash dump...
BSOD Caused by WudfPf.sys in BSOD Crashes and Debugging
After I installed Windows 8 and update all of my drivers, Sometime I got a short freeze with no warning But only a short freeze(2-5 secs). It is not BSOD,But it makes me annoyed. Thanks in advanced.
BSOD caused by rdboost.sys, but RAM seems OK in BSOD Crashes and Debugging
Hi all, I have some crashes upon booting Win8. This actually always happens right after the boot process is done, right before the lock screen. Upon automatic reboot the system always works as expected. As you will be able to see in the Minidumps the error is almost always caused by...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook