BSOD Windows 10 Dump File Help Needed

Hello,

Recently for the past 2 or so weeks, I've been getting multiple blue screens. I have a minidump of my most recent crash, but I'm not sure how to interpret this file. I used WinDbg and It says that "NETIO.SYS" is the problem, but I am not sure how to go about fixing it.

My specs are:
16gb RAM
intel core i7-6700 CPU 3.40 GHz
118gb SSD
906gb HDD
nvidia geforce gtx 960

Here is the dump file: https://1drv.ms/u/s!AvWL0t0x1bRFtD_MxljeLtqLR2lp
12 answers Last reply
More about bsod windows dump file needed
  1. Hi, try updating your KilllerNetworking drivers.
    https://www.killernetworking.com/driver-downloads

    Dump file info: https://pste.eu/p/GYsW.html
    File: 080518-4843-01.dmp (Aug 5 2018 - 17:17:58)
    BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
    Probably caused by: memory_corruption (Process: KillerService.)
    Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 38 Sec(s)

    "KillerService" was mentioned in the dump file. NETIO.SYS is a networking driver. Both of those point towards KillerNetworking drivers.

    I see 2015 and 2016 KillerNetworking drivers on your system. Maybe updating them will help.
  2. click the other downloads link on killer site, it will show you just the drivers. you don't need the rest :)
  3. MERGED QUESTION
    Question from epiclordreaper : "Another BSOD Windows 10 Error, Help"

    Hi,

    I posted earlier on this forum about a BSOD I got due to my Killer Network drivers not being up to date. That issue seems to have been resolved. However, I got another BSOD, but it was a different error this time.

    Specs:
    16gb RAM
    intel core i7-6700 CPU 3.40 GHz
    118gb SSD
    906gb HDD
    nvidia geforce gtx 960

    dump file: https://1drv.ms/u/s!AvWL0t0x1bRFtECxXZIFaiy0F3SM


    dump file:
  4. What is inpoutx64.sys part of? Its described as DLL and driver for direct access to hardware ports. Here is the web site http://www.highrez.co.uk/Downloads/InpOut32/default.htm

    Quote:
    InpOut32 is an open source windows DLL and Driver to give direct access to hardware ports (for example the parallel and serial port from user level programs. It is originally developed by the people at Logix4U for Windows 9x and 32bit variations of NT (NT/2000/XP/2003 etc.).

    I have ported the original code (written by Logix4U) it to Windows XP 64bit Edition (XP/2003/Vista/7/8/8.1 x64 Editions) because the 32bit driver will not install or run on x64 systems. My new version supports both 32bit and 64bit systems running under WOW64 as 32bit applications, and with a new x64 DLL, pure x64 applications.


    Its also from 2008 and isn't a windows 10 driver -
    Quote:
    I am pleased to say that InpOutx64 now fully supports Windows Vista, 7 and 8.1 x64
    so it hasn't been updated since 2015.

    I can't read dumps but gardenman can. The above is just based on a file he created on last dump Is it still blaming netio.sys as another thing you can try is run an anti virus scan
  5. I ran the dump file through the debugger and got the following information: https://pste.eu/p/5sJ9.html

    File: 080518-4562-01.dmp (Aug 6 2018 - 01:11:08)
    BugCheck: [ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)]
    Probably caused by: memory_corruption (Process: League of Legends)
    Uptime: 0 Day(s), 2 Hour(s), 41 Min(s), and 56 Sec(s)

    This one doesn't specifically point to a driver, maybe Colif has more ideas than I do about it. Wait for additional replies. Good luck.
  6. gardenman said:
    I ran the dump file through the debugger and got the following information: https://pste.eu/p/5sJ9.html

    File: 080518-4562-01.dmp (Aug 6 2018 - 01:11:08)
    BugCheck: [ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)]
    Probably caused by: memory_corruption (Process: League of Legends)
    Uptime: 0 Day(s), 2 Hour(s), 41 Min(s), and 56 Sec(s)

    This one doesn't specifically point to a driver, maybe Colif has more ideas than I do about it. Wait for additional replies. Good luck.


    Got 2 more crashes. They both happened moments after a league game ended. I am wondering whether this is coincidence or not.

    Dump file 1: https://1drv.ms/u/s!AvWL0t0x1bRFtEHolMZYhpPkjj6H
    Dump file 2: https://1drv.ms/u/s!AvWL0t0x1bRFtEMEBONN2H-hgFtW
  7. I ran the dump files through the debugger and got the following information: https://pste.eu/p/gCkL.html

    File: 080618-4937-01.dmp (Aug 6 2018 - 19:14:19)
    BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    Probably caused by: nvlddmkm.sys (Process: csrss.exe)
    Uptime: 0 Day(s), 0 Hour(s), 40 Min(s), and 58 Sec(s)

    File: 080618-4875-01.dmp (Aug 6 2018 - 18:33:01)
    BugCheck: [KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE (162)]
    Probably caused by: win32kbase.sys (Process: CUE.exe)
    Uptime: 0 Day(s), 1 Hour(s), 20 Min(s), and 02 Sec(s)

    The first one was a NVIDIA crash. The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

    In the second one, CUE.EXE crashed. That doesn't mean it's at fault, just that it crashed. It might be a part of "Corsair Utility Engine". You may want to check for updates for it. Colif may know more about it.

    Sometimes it takes a while to drill down and finally figure out what is causing the problem. Sometimes it multiple problems too. Hang in there.
  8. I am still curious what you use the old 2008 driver for. Do you have a printer?

    Is this an MSI Nightblade? https://www.msi.com/Desktop/Nightblade-X2/Specification

    The motherboard in your PC has been used in several models of the Nightblade, its not a simple question to answer just having the motherboard code itself. The only way I can tell it might be this one is it uses Killer internet, the other model NIghtblades all have Intel LAN & WIFI.

    but the BIOS code on your board doesn't match any on the web site. Your system reports VERSION: 9.0E whereas the web site shows 820.

    None of the other variety of NIghtblade match LAN or BIOS codes either -
    https://www.msi.com/Desktop/Nightblade-MI2/Specification - Realtek LAN/Intel WiFi
    https://www.msi.com/Desktop/Nightblade-X2B/Specification - Killer LAN/Intel WiFi, only BIOS listed is 920
    https://www.msi.com/Desktop/Nightblade-MI3/Specification - this has wrong CPU/GPU combo (newer)

    Knowing what you have can let us figure out what is cause.
  9. Colif said:
    I am still curious what you use the old 2008 driver for. Do you have a printer?

    Is this an MSI Nightblade? https://www.msi.com/Desktop/Nightblade-X2/Specification

    The motherboard in your PC has been used in several models of the Nightblade, its not a simple question to answer just having the motherboard code itself. The only way I can tell it might be this one is it uses Killer internet, the other model NIghtblades all have Intel LAN & WIFI.

    but the BIOS code on your board doesn't match any on the web site. Your system reports VERSION: 9.0E whereas the web site shows 820.

    None of the other variety of NIghtblade match LAN or BIOS codes either -
    https://www.msi.com/Desktop/Nightblade-MI2/Specification - Realtek LAN/Intel WiFi
    https://www.msi.com/Desktop/Nightblade-X2B/Specification - Killer LAN/Intel WiFi, only BIOS listed is 920
    https://www.msi.com/Desktop/Nightblade-MI3/Specification - this has wrong CPU/GPU combo (newer)

    Knowing what you have can let us figure out what is cause.


    Yes it's an MSI Nighblade X2B - 203TW. I'm not sure what the 2008 driver is for, I don't have a printer.
  10. You might have the release bios installed, you might want to think about updating to 920 - bios tab here has instructions as to how to do it - https://www.msi.com/Desktop/support/Nightblade-X2B

    Do you have anything attached to Serial or Parallel ports on PC? I found one reference to MSI and this file -

    Quote:
    Its an "open source" 64bit driver used to access "old fashioned" ports like the parallel port, serial port and others directly.

    It is certainly not essential for running your computer and if you don't know how you got it, then its probably installed by some software you have installed, most commonly, Ive seen it used with software for controlling LCD screens. Do you have anything connected to a parallel port or serial port that requires special software to operate? There are plenty of other specialist things it *could* be used for but I would say its very unlikely to be "common" everyday use type of software. I have heard of people using it to send keystrokes and mouse inputs directly to the keyboard buffer at a low level so if you have anything that simulates keyboard or mouse movements/buttons, that would be something to check!

    You need to find out what software is using it to work out if you can delete it without impacting your useage. If you search for Inpout32.dll or inpoutx64.dll on your hard disks, you may find that DLL along with the software that is using Inpout32.sys. The InpOut32.dll is responsible for installing the .sys driver file, and I would expect it either to be with the software thats using it, or in the Windows\system folder (which will make it less easy to work out whats using it!)

    In theory, (usually) deleting drivers is not quite as simple as deleting the file. however, with InpOut32/x64 the driver is only loaded when the software using it is running, so you are probably safe to just delete the file. If you can't delete it, then you will need to uninstall the driver first and thats not quite so easy! It does not show up in device manager because it is a legacy driver and windows 10 seems like it simply does not list it. So for now I will hope you can delete the file.

    Regarding the BSOD itself - very odd - I would expect that the software using the driver must be running at the time the BSOD occurs (which may help you narrow down what is using it I guess). While its a very simple driver that does not do very much, it hasn't been updated for about 7 years so it may just not be 100% compatible with windows 10.

    Please note, the driver was developed for 32bit windows by Logix4u (no longer around it seems) they open sourced it and I simply ported it (recompiled it) for 64bit windows (it sounds like you will have my port). Personally I haven't used the thing myself for about 7 years, but others are free to use and distribute it with their software - which is probably how you got it!.


    http://forums.highrez.co.uk/viewtopic.php?t=3861

    It might not be the problem, I am just curious what it does. If you don't use Serial/parallel ports on PC, you can try running this and stop it loading at startup - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

    Swap nvidia drivers if you haven't already, its always possible it was the GPU drivers were cause.
  11. I tried all the software solutions, but none of them seemed to work. So I opened my PC and cleaned out all the dust from everything. The CPU, GPU, the fans, etc... And the crashing has not occurred in over 3 days. I'm still not 100% certain that the dust was the problem, I'll have to test it out some more.
  12. Heat and dust can cause errors if parts start to run hot and misbehave. Its unlikely it was cause of all the BSOD but if you stop getting BSOD, who is going to complain, right :)
Ask a new question

Read More

windows 10 Blue Screen