Windows 8 and 8.1 Forums

MSI GT70 Dominator Dragon Edition Laptop Random BSOD's

  1. #1

    Posts : 3
    Windows 8.1

    MSI GT70 Dominator Dragon Edition Laptop Random BSOD's

    Hello and Good Evening,

    I bought this laptop 6 months ago and did not use it much at the beginning to notice any crashes. I have been using it heavily the last three months and have been experiencing random BSOD crashes often. As I am not a savvy computer or software tech, my extend of modifications to the laptop are limited only to installing games, two utility applications; GeForce Experience and MSI Live Update for keeping the drivers up to date. BSOD crashes occurred while playing diablo 3, starcraft 2, watching movies on popcorn time (movie downloader), browsing the web, having a chat session with Microsoft tech and when they were accessing my laptop with remote assistance. As far as I can tell, all of my drivers and windows components were up to date. BSOD crashes happened sometimes 10 minutes into playing a game, some time couple of hours. As the frequency was getting more, I finally decided to do a complete system restore last night. Wiped the hard drive too. Spent the whole day today, downloading and updating drivers and windows 8.1. No BSOD crashed for almost 16 hours and I got my first one about an hour ago:


    Faulting application name: KLM.exe, version: 1.0.1304.2201, time stamp: 0x5174c962
    Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eeb460
    Exception code: 0xe0434352
    Fault offset: 0x00012f71
    Faulting process id: 0x1490
    Faulting application start time: 0x01cfd844c113da7e

    Before the system restore, I had downloaded a utility to keep a track of the errors, and I was getting 10 to 12 different errors which were repeating, however, the IRQL one was one the most common errors.

    I have been reading around the web a lot the last couple of months, with my little understanding of BSOD crashes, I believe my network adaptor and/or sound/graphic card drivers might be the most likely culprits but I just don't know.

    Any advice and help would be much appreciated and thank you in advance for your time, consideration and assistance.

    Kindest Regards,


      My System SpecsSystem Spec

  2. #2

    Posts : 3
    Windows 8.1

    Update 1

    Good Morning, got another BSOD few hours ago:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffd00025a19004, 0x0000000000000000, 0xfffff80271feca6f, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 092514-5312-01.


    I have received a link with a suggestion, I am trying it out, for those of you who own a MSI gaming laptop and who are experiencing similar issues, please see below for the link:

    MSI USA - Online Technical Support FAQ
    Last edited by gsaykan; 25 Sep 2014 at 15:41. Reason: New info
      My System SpecsSystem Spec

  3. #3

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

    Sorry for the delay in responding. There just aren't that many people who do BSOD analysis, so at times we get a bit overwhelmed!

    The IRQL_NOT_LESS_OR_EQUAL error (this is a STOP 0xA error) is very similar to the "bugcheck was: 0x00000050" (this is a STOP 0x50 - PAGE_FAULT_IN_NONPAGED_AREA). Both are most often caused by driver issues, and both can often be persuaded to reveal the cause by running Driver Verifier.

    The error in quotes is due to your MSI lighted keyboard app (MSI keyboard LED Manager (KLM)).
    Faulting application name: KLM.exe
    Please do the following:
    - download the latest, Win8.1 compatible version of this app (it's located in the Utility section of the downloads)
    - uninstall the version that's currently installed on your system
    - install the freshly downloaded version of the app
    - monitor for further problems.

    Also, there is a firmware update available for your backlit keyboard (and for the non-backlit keyboard). I'd suggest installing it also.

    The Killer Network Service has been a problem previously.
    The link that you provided is the second BSOD that MSI says was caused by the Killer service (and, interestingly, they have reused the link!)
    Unfortunately, there is no date on the link.
    FWIW - I stopped seeing these problems on MSI laptops several months ago - and I find that Qualcomm Killer drivers dated from 2014 won't have the BSOD issues that earlier drivers had.
    FWIW and FYI - here's my canned speech about the previous driver problems with the Killer Network Manager:
    At times the Killer Network Manager may cause BSOD problems:
    NOTE: See this link first: BSOD while playing on msi gt70 dragon edition 2 (thanks to kaelaan) It appears that the Killer Service problem was solved with the latest release of the Qualcomm versions of the drivers (so try updating to a version dated from later in 2014).
    The Qualcomm Atheros Killer Service/KillerNetManager is known to cause BSOD's. Please follow the workaround instructions here:
    First, open the Run dialog (Win + R keys) and type in "services.msc" (without the quotes) and press Enter
    Scroll down and locate the "Qualcomm Atheros Killer Service" and right click on it. Select "Stop"
    Right click on it again and this time select "Properties"
    In the dropdown box for "Startup type", select "Disabled", then click on the "OK" button at the bottom of the window

    Next, open Task Manager (right click on TaskBar and select "Task Manager")
    Click on the "More details" dropdown (if present)
    Click on the "Startup" tab
    Scroll down and locate the "KillerNetManager" entry, right click on it and select "Disable"
    There may also be an Install Shield (with the Killer gaming K next to it), if so Right click on it and select "Disable"
    Finally, restart the system in order for the changes to take affect.
    At times the Killer Network Manager will continue to load. If so, it's usually listed in the MSINFO32...Software Environment...Startup Programs section. If it is, please try this:
    It may be that the instructions aren't stopping everything.
    In some cases, there's a program running out of the Program Files/Program Files (x86) directory.
    "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" (NOTE: killer~1.exe is most likely killernetmanager.exe)
    In other cases, there's a program running out of c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe (the long string of letters and numbers may change)

    Here's some things to try
    1) Please see if there are any entries in the Startup tab of Task Manager that are related to Qualcomm/Atheros/Killer Network Manager (and NOT the card itself) and disable them (please let us know what you find) Be careful as the wrong selection can disable the network card.
    2) Check in "msconfig" for any entries that aren't in the Startup tab of Task Manager. Let us know if you find any Qualcomm/Atheros/Killer entries there (we'll disable them differently if they are there).
    3) Locate the "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" and rename the .exe to .BAD (the killer~1 is actually a filename that starts with killer and ends with .exe) There will be an error in event viewer, but it'll stop the bugger from loading.
    4) Locate the "c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe" entry and rename the last .exe to .BAD (the long string of letters and numbers may change)

    Just FYI - here are the MSI workaround instructions: MSI USA - Online Technical Support FAQ
    Your UEFI/BIOS dates from August 19 of 2013, please check for updates and update it using the MSI Live Update utility (it's safer than flashing it manually). Here's the info on your current BIOS:
    BIOS Version: American Megatrends Inc. E1763IMS.70E, 8/19/2013
    Once this is updated, please uninstall it (the MSI Live Update utiliity). As the version that you are using uses the NTIOLib_X64.sys driver - which is known to cause BSOD's on some Windows systems.

    These devices have problems in Device Manager:
    Bluetooth Audio Device BTHENUM\{61118058-486C-4BB0-B4B8-ACE4DCADEC44}_LOCALMFG&0000\8&147F8D6D&0&000000000000_00000000 This device cannot start.

    Virtual Bluetooth Support (Include Audio) BTHENUM\{CBECAB40-A2C8-4AB3-ADC1-DE0FE95D8600}_LOCALMFG&0000\8&147F8D6D&0&000000000000_00000000 This device is not working properly because Windows cannot load the drivers required for this device.

    Bluetooth LWFLT Device BTHENUM\{DD533152-01F4-435C-ABFE-984BC21A2A65}_LOCALMFG&0000\8&147F8D6D&0&000000000000_00000000 This device is not working properly because Windows cannot load the drivers required for this device.

    Killer e2200 Gigabit Ethernet Controller (NDIS 6.30) PCI\VEN_1969&DEV_E091&SUBSYS_10EC1462&REV_13\4&39E5DA20&0&00E2 This device is not working properly because Windows cannot load the drivers required for this device.
    Please visit the MSI support website for your system and download/install the latest, Win8.1 compatible Bluetooth drivers for your system. This includes the latest SCM (System Control Manager) utility. Link to how to upgrade SCM: MSI Global - Computer, Laptop, Notebook, Desktop, Motherboard, Graphics and more and Just FYI, bluetooth drivers for Win8 sometimes have BSOD issues when loaded in Win8.1 - updating is mandatory!

    Also download and install the latest, Win8.1 compatible version of the drivers for the Killer 32200 Gigabit Ethernet controller (this will affect the workarounds that you made previously, so check them again.

    Lots of Windows Update failures in the WER section of MSINFO32. Please check to be sure that you have ALL available Windows Updates. If you're unable to get them, please post over in the Windows Updates & Activation forum for some expert assistance in fixing that problem.

    Only 1 BSOD listed in the WER section of MSINFO32 (and only 1 dump file in the uploaded reports). This means that the other one wasn't captured. We may have to look for it later on.

    While I suspect the Killer Network Manager, we don't have a definite driver to blame.
    Please run Driver Verifier according to these directions: Driver Verifier Settings

    Uninstall your Norton, then download and install the latest, Win8.1 compatible version.

    Uninstall the Cyberlink software, it's drivers date from before Win8.1 was released

    Update the Intel Management Engine software (you'll find it at the MSI download site).

    Update the Killer wireless driver - as it dates from before Win8.1

    Post back with the results of Driver Verifier and we'll move on from there.

    The following is for informational purposes only.
    **************************Wed Sep 24 18:08:53.446 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\092414-5796-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 10:08:34.178
    Probably caused by :ntkrnlmp.exe ( nt!KiInsertTimerTable+18b )
    BugCheck A, {fffffffffffffff7, 2, 0, fffff802f6eb30db}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
    Arg1: fffffffffffffff7, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff802f6eb30db, address which referenced memory
    PROCESS_NAME:  KillerService.
    FAILURE_BUCKET_ID: AV_nt!KiInsertTimerTable
    CPUID:        "Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2394
      BIOS Version                  E1763IMS.70E
      BIOS Release Date             08/19/2013
      Manufacturer                  Micro-Star International Co., Ltd.
      Product Name                  GT70 2OC/2OD
    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.
    **************************Wed Sep 24 18:08:53.446 2014 (UTC - 4:00)**************************
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    NTIOLib_X64.sys             Wed Oct 20 02:45:49 2010 (4CBE901D)
    SRTSPX64.SYS                Tue Nov 15 17:30:55 2011 (4EC2E81F)
    SYMNETS.SYS                 Tue May  8 04:53:44 2012 (4FA8DF18)
    rikvm_38F51D56.sys          Mon May 14 03:49:40 2012 (4FB0B914)
    SYMEFA64.SYS                Fri May 18 21:29:56 2012 (4FB6F794)
    Ironx64.SYS                 Wed May 23 13:14:39 2012 (4FBD1AFF)
    SYMEVENT64x86.SYS           Wed May 23 20:52:24 2012 (4FBD8648)
    SYMDS64.SYS                 Wed May 23 21:11:58 2012 (4FBD8ADE)
    SRTSP64.SYS                 Thu May 24 02:28:47 2012 (4FBDD51F)
    ccSetx64.sys                Fri May 25 15:34:57 2012 (4FBFDEE1)
    SynTP.sys                   Fri Aug 24 19:20:26 2012 (50380C3A)
    HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
    btath_rcp.sys               Tue Dec 18 04:54:50 2012 (50D03D6A)
    btath_hcrp.sys              Tue Dec 18 04:54:54 2012 (50D03D6E)
    akw8x64.sys                 Wed Jan 23 14:18:12 2013 (51003774)
    RtsPer.sys                  Fri Feb  1 02:09:27 2013 (510B6A27)
    iaStorA.sys                 Mon Mar 18 19:36:36 2013 (5147A504)
    dump_iaStorA.sys            Mon Mar 18 19:36:36 2013 (5147A504)
    intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    nvkflt.sys                  Thu Aug 29 17:39:47 2013 (521FBFA3)
    bwcW8x64.sys                Thu Apr 10 11:40:24 2014 (5346BB68)
    btfilter.sys                Thu Apr 24 23:01:52 2014 (5359D020)
    iwdbus.sys                  Tue Jun 17 17:54:22 2014 (53A0B90E)
    RTKVHD64.sys                Tue Jul 15 06:53:15 2014 (53C5081B)
    igdkmd64.sys                Tue Aug  5 11:47:18 2014 (53E0FC86)
    EX64.SYS                    Mon Aug 11 06:19:41 2014 (53E898BD)
    ENG64.SYS                   Mon Aug 11 06:25:04 2014 (53E89A00)
    IDSvia64.sys                Wed Aug 20 18:48:56 2014 (53F525D8)
    eeCtrl64.sys                Tue Aug 26 14:21:20 2014 (53FCD020)
    EraserUtilRebootDrv.sys     Tue Aug 26 14:21:21 2014 (53FCD021)
    nvvad64v.sys                Thu Sep  4 13:10:48 2014 (54089D18)
    NvStreamKms.sys             Sat Sep  6 00:37:11 2014 (540A8F77)
    BHDrvx64.sys                Wed Sep 10 17:51:01 2014 (5410C7C5)
    nvlddmkm.sys                Sat Sep 13 15:59:50 2014 (5414A236)
    nvpciflt.sys                Sat Sep 13 16:02:34 2014 (5414A2DA)
    Last edited by usasma; 29 Sep 2014 at 04:49.
      My System SpecsSystem Spec

  4. #4

    Posts : 3
    Windows 8.1

    Dear John,

    First off, thank you for taking your time to provide me with all of the above information. The detailed, step by step, multi layered solutions you have provided are just incredible. I am very grateful.

    Since I have disabled the killer network manager from msconfig and startup, I have not experienced any more BSOD crashes and it has been over 48 hours. But you have highlighted so many other areas that I need to fix and update that once I am done with all of it, I think I am going to be one happy camper.

    I will mark this post as resolved for now, and update and/or report if anything else comes up in the future. Once again, thank you very much and keep up the great work you are doing.

    Kindest Regards,

      My System SpecsSystem Spec

  5. #5

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

    As you haven't had any problems for 48 hours, I'd leave well enough alone for now.
    Wait a couple of weeks and see if you get any further BSOD's

    BSOD's are sometimes very complicated - and that's why I give so many suggestions.
    But at times it's just a simple problem (such as the Killer Network Manager), and all the steps aren't needed.

    Good luck!
      My System SpecsSystem Spec

MSI GT70 Dominator Dragon Edition Laptop Random BSOD's

Similar Threads
Thread Forum
MSI GT70 often random BSOD's
Hi, I have a MSI GT70 20D-039US DRAGON EDITION 2 and get random crashs since the first day I have it. I upgraded my laptop to win8.1 after the first crash and it didn't work and then i have updated all my drivers to latest from MSI Global GT70 Dragon Edition 2 and also killer network...
BSOD Crashes and Debugging
MSI GT70 2OD,Random BSOD while browsing or gaming at times
This issue happened from the first day I got my computer and I read that its a driver related issue. however I did try to fix it many times until I got to the point where the BSOD doesnt happen as often anymore but I still got this one today "will upload files on attachment". wish I could...
BSOD Crashes and Debugging
New msi GT70 2OC random BSOD
I bought this PC on january, and since then I got random BSOD at various moments, I already tryed to restore the computer, I already did this and i still got a lot of BSOD, my drivers are updated.
BSOD Crashes and Debugging
BSOD while playing on msi gt70 dragon edition 2
hello everyone ,,, 2 days ago i bought a new MSI GT70 DRAGON EDITION 2 system specs :~ i7-4700mq processor nividia geforce gtx780m 750gb +128g ssd(super raid) ram 32gb os: windows 8 ... and i got BSOD like 5 times until now while playing league of legends and each time with different...
BSOD Crashes and Debugging
GT70-2OC Random BSODs
Hello all, I recently purchased an MSI notebook GT70-2OC from After receiving the product, upon startup, I received different BSOD throughout the session. This went on for a couple weeks, since I was on vacation. After returning from my trip, I cleaned the SSD (the boot...
BSOD Crashes and Debugging
MSI GT70-20D windows 8.1 X64 random BSOD while playing
hello, I've read a lot about BSOD which are related to 3rd party software and hardware. I've upgraded all my driver using Driver Genius pro 12 which reduce BSOD from happening but I still get BSOD even everything is running well. please help me so I can go to MSI maintenance service & tell them...
BSOD Crashes and Debugging
New MSI GT70 random BSOD's
Hi, I have a new GT70 2OD 058au (less than 2 weeks old). I ran updates the day I received the computer which included updating to Windows 8.1. I have been getting BSODs randomly most days since I got the computer, sometimes with different codes and while doing different tasks. I have...
BSOD Crashes and Debugging

Eight Forums Android App Eight Forums IOS App Follow us on Facebook