Windows 8 and 8.1 Forums


Random BSOD once a day, mini dumps attached

  1. #1


    Posts : 3
    Windows 8.1

    Random BSOD once a day, mini dumps attached


    Okay guys, for the record, i'm overclocked. I've ran stress test on both the CPU,RAM, and Video card. I've never had an issue with heat (i monitor it closely) or during a time of intense gaming/processing. I get a random crash/reboot whenever i'm using relatively low processing power(browsing or in the lobby before a game starts). Ive gone to my motherboard manufacture website and updated all the drives and BIOS. Windows it up to date. Nothings changed. Here are the links to my last 2 mini dumps. Any help is appreciated. Any help is appreciated.

    Also wanted to add, that I tried running driver verifier and I kept constantly crashing during boot.

    https://www.dropbox.com/s/c4mx2wttq4...65-01.dmp?dl=0

    https://www.dropbox.com/s/vzgme16p0a...90-01.dmp?dl=0

      My System SpecsSystem Spec

  2. #2


    Hi stanielz and welcome to Eight Forums,
    BSOD's are frustrating for everyone and many times difficult to find the cause, look it over carefully. Take a screen shot of it with a digital camera to print out so we can know wich BSOD you are having and we will help you out.
      My System SpecsSystem Spec

  3. #3


    Posts : 3
    Windows 8.1


    I would need to wait for it to do it and, but since it only happens once every couple of days it might be a bit. I was able to pull a dump file from my driver verifier BSODs and got this.

    "DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    FAULTING_IP: nt!ViGenericSystemControl+0fffff801`cac93b90 4c8b05d12cc8ff mov r8,qword ptr [nt!pXdvIRP_MJ_SYSTEM_CONTROL (fffff801`ca916868)]
    MODULE_NAME: LGVirHid
    IMAGE_NAME: LGVirHid.sys"

    Looked up that driver and saw that it was logitech driver, I own a logitech mouse. Checked the driver and saw it was outdated, and had to manually update it because "check for updates" wasn't finding it even though I trusted it.Did some more digging, found that I didnt have a proper audio driver installed (was using generic instead of Realtek as per MSI website). Do you guys think this stuff would be responsible? Driver Verifier BSOD:https://www.dropbox.com/s/58qaljy8lf...71-02.dmp?dl=0
      My System SpecsSystem Spec

  4. #4


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


    Turn off Driver Verifier. To do this open up verifier.exe and select "Delete existing settings", then click on Finish and reboot the system.

    Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum): Blue Screen of Death (BSOD) Posting Instructions Please use Option 1 as it provides Event Viewer logs.

    You're correct about the Logitech driver. Also, Logitech doesn't update them very often.
    I'd suggest temporarily uninstalling the Logitech software to see if that helps.
    If it doesn't, then try another mouse.

    The last memory dump points to the mouse, but the other 2 are generic hardware errors.
    Not all of your drivers appear updated, there are several that date from before Win8.1 was released.
    Double check at the manufacturer's website for Intel Tuning (in the Utilities section) and Intel Watchdog updates

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Aug 26 07:43:31.104 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9171-02.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.767
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff801cac93b90, ffffcf80b422ad80, ffffe0001505a5b0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff801cac93b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf80b422ad80, IRP address.
    Arg4: ffffe0001505a5b0, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 04:50:49.129 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-5265-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:2 days 16:50:25.891
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe0018179d028, bf800000, 124}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe0018179d028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  LolClient.exe
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
    CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3400
      BIOS Version                  V1.4
      BIOS Release Date             06/27/2014
      Manufacturer                  MSI
      Product Name                  MS-7917
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 18 15:18:41.800 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\071814-4390-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:26.561
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe00093fca028, bf800000, 124}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe00093fca028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  XtuUiLauncher.
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
    CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3400
      BIOS Version                  V1.4
      BIOS Release Date             06/27/2014
      Manufacturer                  MSI
      Product Name                  MS-7917
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Tue Aug 26 07:43:31.104 2014 (UTC - 4:00)**************************
    MBfilt64.sys           Thu Jul 30 23:40:32 2009 (4A7267B0)
    LGBusEnum.sys          Mon Nov 23 20:36:48 2009 (4B0B38B0)
    LGVirHid.sys           Mon Nov 23 20:36:48 2009 (4B0B38B0)
    AcpiCtlDrv.sys         Tue Jul 17 13:07:16 2012 (50059BC4)
    ICCWDT.sys             Mon Aug 12 13:59:08 2013 (5209226C)
    intelppm.sys           Thu Aug 22 04:46:35 2013 (5215CFEB)
    nvhda64v.sys           Thu Nov 28 08:38:09 2013 (52974741)
    ISCTD.sys              Wed Jan 22 14:37:35 2014 (52E01DFF)
    iocbios2.sys           Tue Feb 18 14:51:45 2014 (5303B9D1)
    TeeDriverx64.sys       Thu Mar 13 14:21:52 2014 (5321F740)
    e22w8x64.sys           Wed Mar 26 11:58:37 2014 (5332F92D)
    nvvad64v.sys           Fri Mar 28 09:32:06 2014 (533579D6)
    INETMON.sys            Thu Apr  3 12:50:43 2014 (533D9163)
    bwcW8x64.sys           Thu Apr 10 11:40:24 2014 (5346BB68)
    iaStorA.sys            Fri May  2 19:06:56 2014 (53642510)
    dump_iaStorA.sys       Fri May  2 19:06:56 2014 (53642510)
    nvlddmkm.sys           Wed Jul  2 13:42:02 2014 (53B4446A)
    RTKVHD64.sys           Tue Jul 15 06:53:15 2014 (53C5081B)
    NvStreamKms.sys        Fri Jul 25 07:35:56 2014 (53D2411C)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 04:50:49.129 2014 (UTC - 4:00)**************************
    ikbevent.sys           Fri Jan 10 12:52:53 2014 (52D03375)
    imsevent.sys           Fri Jan 10 12:52:53 2014 (52D03375)
    RTKVHD64.sys           Tue Mar  4 07:26:03 2014 (5315C65B)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Jul 18 15:18:41.800 2014 (UTC - 4:00)**************************
    nvlddmkm.sys           Mon May 19 19:08:44 2014 (537A8EFC)
    NvStreamKms.sys        Thu May 22 12:43:14 2014 (537E2922)
    
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
    http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
    http://www.carrona.org/drivers/driver.php?id=AcpiCtlDrv.sys
    http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=ISCTD.sys
    http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=INETMON.sys
    http://www.carrona.org/drivers/driver.php?id=bwcW8x64.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=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=ikbevent.sys
    http://www.carrona.org/drivers/driver.php?id=imsevent.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
      My System SpecsSystem Spec

  5. #5


    Posts : 3
    Windows 8.1


    I attached the requested info. I went to the website Intelо Driver Update Utility
    and it gave me this

    Graphics Driver
    Product Detected NVIDIA GeForce GTX 770
    Current Driver Installed 9.18.13.4052
    This device is unknown or unsupported. Please contact the manufacturer for possible updates. More information>>



    Intel Chipset Software Installation Utility (Chipset INF)
    Product Detected
    Current Version Installed 10.0.17
    This version is valid.



    Audio Driver for Intel Desktop Board
    Product Detected NVIDIA High Definition Audio
    Current Driver Installed 1.3.30.1
    This device is unknown or unsupported. Please contact the manufacturer for possible updates. More information>>



    Wireless Networking (WiFi)
    Product Detected Killer e2200 Gigabit Ethernet Controller (NDIS 6.30)
    Current Driver Installed 8.1.0.23
    This device is unknown or unsupported. Please contact the manufacturer for possible updates. More information>>



    Wired Networking
    Product Detected Killer e2200 Gigabit Ethernet Controller (NDIS 6.30)
    Current Driver Installed 8.1.0.23
    This device is unknown or unsupported. Please contact the manufacturer for possible updates. More information>>


    It didnt actually mention anything was out of date and all those questionable drivers it mentions up here ^^ are up to date as far as i can tell. I updated the logittech stuff.

      My System SpecsSystem Spec

  6. #6


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


    FYI - I scan drivers by date, not by version (doing it by version would take much, much more time).
    Anything that's from before the OS was released is suspect.
    But there are a number of earlier released drivers that work just fine.
    Also (because we're only looking at the date), it's possible that the driver isn't the problem - but that other components of the installation package are to blame.

    If you'll notice, I didn't highlight the MBfilt64.sys driver even though it dates from 2009.
    That's because it's the latest version and it seems to work quite well w/Win8.1
    The intelppm.sys driver is the latest version also (and it's actually a driver from Microsoft - not from Intel)

    I don't suspect that the Intel stuff is out of date (that's why it's not highlighted) - but it's always best to check, especially when it's older than Win8.1 is. FYI - I have had issues with the Intel driver scanner not working properly for me - so I don't use it any more. I suspect that it's due to the drivers from the OEM manufacturer's (they rebrand/modify some of the Intel drivers for their own purposes - which may include compatibility fixes).

    On to the reports......

    Only 56 Windows Updates installed. Most systems have 70 to 90 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

    Don't worry about the specific number, it's just important that you have checked and installed any updates that were available (and didn't experience any errors).

    Riva Tuner (along with MSI Afterburner and EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install them immediately!

    If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

    The last 21 memory dumps all were Driver Verifier Enabled and all blame the Logitech software.
    If, after turning Driver Verifier off, the BSOD's continue - please uninstall the Logitech software.
    If the mouse doesn't work without it's software - or it doesn't stop the BSOD's, then try another mouse temporarily.
    I suspect the mouse hardware because the previous (before Driver Verifier) memory dumps were all STOP 0x124's - which are most often indicative of a hardware problem (but not 100% of the time).

    Just FYI - in most cases there's not an updated Logitech driver dated later than 2009 (and in most cases they work just fine). I have a Logitech wired USB Trackball and the drivers for it date from 14 March 2014 (but I have no idea where I got them from!)

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Aug 26 07:42:38.239 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9671-02.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:26.902
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff801dcf00b90, ffffcf8181d74d80, ffffe0016d46b960}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff801dcf00b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf8181d74d80, IRP address.
    Arg4: ffffe0016d46b960, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:41:31.294 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9171-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.957
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff8031f295b90, ffffcf816f144d80, ffffe000c0402d20}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff8031f295b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf816f144d80, IRP address.
    Arg4: ffffe000c0402d20, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:40:35.296 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9593-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:26.959
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff8035969cb90, ffffcf80fd28cd80, ffffe000c5d555b0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff8035969cb90, The address in the driver's code where the error was detected.
    Arg3: ffffcf80fd28cd80, IRP address.
    Arg4: ffffe000c5d555b0, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:39:22.745 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9156-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.424
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff800a9afeb90, ffffcf8143bccd80, ffffe0009f43a9b0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff800a9afeb90, The address in the driver's code where the error was detected.
    Arg3: ffffcf8143bccd80, IRP address.
    Arg4: ffffe0009f43a9b0, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:38:27.297 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9640-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:26.959
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff80068cf8b90, ffffcf81e6ce8d80, ffffe000408f48e0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff80068cf8b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf81e6ce8d80, IRP address.
    Arg4: ffffe000408f48e0, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:18:50.638 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9203-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.302
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff803a7c94b90, ffffcf80bf4ccd80, ffffe001b89acc00}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff803a7c94b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf80bf4ccd80, IRP address.
    Arg4: ffffe001b89acc00, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:16:38.463 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9578-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.126
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff8017fe9fb90, ffffcf8156a6ed80, ffffe0005163a820}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff8017fe9fb90, The address in the driver's code where the error was detected.
    Arg3: ffffcf8156a6ed80, IRP address.
    Arg4: ffffe0005163a820, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:11:24.108 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9359-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.770
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff80161f0db90, ffffcf81d9e56d80, ffffe00136387b80}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff80161f0db90, The address in the driver's code where the error was detected.
    Arg3: ffffcf81d9e56d80, IRP address.
    Arg4: ffffe00136387b80, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:10:27.392 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9875-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.056
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff8022cd0ab90, ffffcf81f6c70d80, ffffe0015bdfc270}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff8022cd0ab90, The address in the driver's code where the error was detected.
    Arg3: ffffcf81f6c70d80, IRP address.
    Arg4: ffffe0015bdfc270, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:04:09.203 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9265-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:26.866
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff802636fab90, ffffcf82167c0d80, ffffe00157fd23f0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff802636fab90, The address in the driver's code where the error was detected.
    Arg3: ffffcf82167c0d80, IRP address.
    Arg4: ffffe00157fd23f0, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 07:03:09.212 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9515-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:26.875
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff8008229db90, ffffcf81e628ed80, ffffe00159564480}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff8008229db90, The address in the driver's code where the error was detected.
    Arg3: ffffcf81e628ed80, IRP address.
    Arg4: ffffe00159564480, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:56:22.925 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9625-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.590
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff803ca70cb90, ffffcf81263f6d80, ffffe0001fbda710}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff803ca70cb90, The address in the driver's code where the error was detected.
    Arg3: ffffcf81263f6d80, IRP address.
    Arg4: ffffe0001fbda710, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:55:29.792 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9968-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:25.456
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff801ad111b90, ffffcf81df1aad80, ffffe000d814dda0}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff801ad111b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf81df1aad80, IRP address.
    Arg4: ffffe000d814dda0, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:53:56.345 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-10015-02.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:28.008
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff801262fdb90, ffffcf8188a82d80, ffffe00127d64080}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff801262fdb90, The address in the driver's code where the error was detected.
    Arg3: ffffcf8188a82d80, IRP address.
    Arg4: ffffe00127d64080, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:51:19.415 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9718-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:28.079
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff8010050db90, ffffcf81e38c2d80, ffffe001a0712080}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff8010050db90, The address in the driver's code where the error was detected.
    Arg3: ffffcf81e38c2d80, IRP address.
    Arg4: ffffe001a0712080, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:49:58.257 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-10109-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.921
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff801e7689b90, ffffcf81e5b02d80, ffffe0002e1ad850}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff801e7689b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf81e5b02d80, IRP address.
    Arg4: ffffe0002e1ad850, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:48:30.772 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9765-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:28.436
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff801f9ca4b90, ffffcf807fc46d80, ffffe0012ea94620}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff801f9ca4b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf807fc46d80, IRP address.
    Arg4: ffffe0012ea94620, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:42:24.546 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9734-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:37.210
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff801f20f9b90, ffffcf812b87ad80, ffffe0002ae73a40}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff801f20f9b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf812b87ad80, IRP address.
    Arg4: ffffe0002ae73a40, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:41:14.201 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-10078-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.865
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff800944a0b90, ffffcf80cc22cd80, ffffe001d5194160}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff800944a0b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf80cc22cd80, IRP address.
    Arg4: ffffe001d5194160, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:36:54.822 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-9671-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:27.485
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff8028d6a0b90, ffffcf82250d2d80, ffffe000a30c8a90}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff8028d6a0b90, The address in the driver's code where the error was detected.
    Arg3: ffffcf82250d2d80, IRP address.
    Arg4: ffffe000a30c8a90, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 06:35:39.391 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-10015-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:0 days 0:00:25.054
    *** WARNING: Unable to verify timestamp for LGVirHid.sys
    *** ERROR: Module load completed but symbols could not be loaded for LGVirHid.sys
    Probably caused by :LGVirHid.sys ( LGVirHid+624 )
    BugCheck C9, {220, fffff801c8f0ab90, ffffcf808e558d80, ffffe0019b477c80}
    BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    Arguments: 
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff801c8f0ab90, The address in the driver's code where the error was detected.
    Arg3: ffffcf808e558d80, IRP address.
    Arg4: ffffe0019b477c80, ProviderId.
    BUGCHECK_STR:  0xc9_220
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc9_220_LGVirHid+624
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 04:50:49.129 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\082614-5265-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    System Uptime:2 days 16:50:25.891
    Probably caused by :GenuineIntel
    BugCheck 124, {0, ffffe0018179d028, bf800000, 124}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe0018179d028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_GenuineIntel
    PROCESS_NAME:  LolClient.exe
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
    CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3400
      BIOS Version                  V1.4
      BIOS Release Date             06/27/2014
      Manufacturer                  MSI
      Product Name                  MS-7917
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Tue Aug 26 07:42:38.239 2014 (UTC - 4:00)**************************
    MBfilt64.sys           Thu Jul 30 23:40:32 2009 (4A7267B0)
    LGBusEnum.sys          Mon Nov 23 20:36:48 2009 (4B0B38B0)
    LGVirHid.sys           Mon Nov 23 20:36:48 2009 (4B0B38B0)
    AcpiCtlDrv.sys         Tue Jul 17 13:07:16 2012 (50059BC4)
    ICCWDT.sys             Mon Aug 12 13:59:08 2013 (5209226C)
    intelppm.sys           Thu Aug 22 04:46:35 2013 (5215CFEB)
    nvhda64v.sys           Thu Nov 28 08:38:09 2013 (52974741)
    ISCTD.sys              Wed Jan 22 14:37:35 2014 (52E01DFF)
    iocbios2.sys           Tue Feb 18 14:51:45 2014 (5303B9D1)
    TeeDriverx64.sys       Thu Mar 13 14:21:52 2014 (5321F740)
    e22w8x64.sys           Wed Mar 26 11:58:37 2014 (5332F92D)
    nvvad64v.sys           Fri Mar 28 09:32:06 2014 (533579D6)
    INETMON.sys            Thu Apr  3 12:50:43 2014 (533D9163)
    bwcW8x64.sys           Thu Apr 10 11:40:24 2014 (5346BB68)
    iaStorA.sys            Fri May  2 19:06:56 2014 (53642510)
    dump_iaStorA.sys       Fri May  2 19:06:56 2014 (53642510)
    nvlddmkm.sys           Wed Jul  2 13:42:02 2014 (53B4446A)
    RTKVHD64.sys           Tue Jul 15 06:53:15 2014 (53C5081B)
    NvStreamKms.sys        Fri Jul 25 07:35:56 2014 (53D2411C)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Aug 26 04:50:49.129 2014 (UTC - 4:00)**************************
    imsevent.sys           Fri Jan 10 12:52:53 2014 (52D03375)
    ikbevent.sys           Fri Jan 10 12:52:53 2014 (52D03375)
    RTKVHD64.sys           Tue Mar  4 07:26:03 2014 (5315C65B)
    
    http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
    http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
    http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
    http://www.carrona.org/drivers/driver.php?id=AcpiCtlDrv.sys
    http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=ISCTD.sys
    http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=e22w8x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=INETMON.sys
    http://www.carrona.org/drivers/driver.php?id=bwcW8x64.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=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=imsevent.sys
    http://www.carrona.org/drivers/driver.php?id=ikbevent.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
      My System SpecsSystem Spec

Random BSOD once a day, mini dumps attached
Related Threads
I've been experience random freezes which may be related to the CPU, but i have the i7-4700MQ Processor which should be pretty decent. Here is my system specs with Speccy : 54541
BSOD Random Mini Dump Error in BSOD Crashes and Debugging
I keep getting a Mini dump Error, tried to copy n paste it, wouldn't allow, then took screenshot, and lost it - so next time it happens i`ll edit and upload it - in mean time here is my reports, hope rar is ok....
Random DPC_WATCHDOG_VIOLATION (logs attached) in BSOD Crashes and Debugging
Hi, I've been getting random DPC_WATCHDOG_VIOLATION errors. The first thing that will happen is Chrome will usually stop responding. I can still use the computer for a bit (chrome won't open again though). Then, after a few minutes, everything goes downhill and I get the violation error. ...
Hi everyone, Recently bought a MSI Dragon Edition 2 for gaming, keep getting BSOD and tried returning it to get told they can only repair it. ( will ship to America to get serviced, in Saudi Arabia, don't trust these people ) So I'm stuck with it! Was going to take it back for an Alienware...
Hi, firstly thankyou for helping me with this! I have a new i3 system for my home theater that crashes after resuming from sleep sometimes(about half the time). It works for about 5 min after resuming and then crashes. Ive tried windows updates,latest bios,latest mobo drivers and have...
W8 Clock_watchdog_timeout (dumps attached) in BSOD Crashes and Debugging
Found similar posts, but none of the solutions worked for me. The PC crashes, typically when there is heavy load, and the sound sort of repeats itself until the BSOD and CLOCK_WATCHDOG_TIMEOUT appears. I run a desktop with Intel CPU and Windows 8. Dump is attached. Thanks for any help.
BSOD (Dumps attached) in BSOD Crashes and Debugging
I am not sure what is going on, but I keep getting BSOD with the following setup: AMD A6-5400K ASRock FM2A75M-DGS FM2 AMD A75 CORSAIR XMS 8GB (2 x 4GB) I tried RMA'ing the RAM, but I am still getting issues with the new RAM. Is something else wrong? Thanks!
Eight Forums Android App Eight Forums IOS App Follow us on Facebook