BSOD each time I open Battle.net

Dude Of Food

Reputable
Dec 14, 2014
4
0
4,510
I have spent the last 48 hours in constant search for an answer to my problem. I have recently installed an MSI RX 480, along with the optional downloads, being XSplit, Windows Live, Msi Kombuster, MSI Gaming App. I had installed it on the 4th of December, and it started with my screen getting all grainy. As if a small pattern was repeated over and over again, pixelated with random colors in a grid. Now I am getting a BSOD each time I open Battle.net. I was previously able to open a game through the launcher for a brief time, but now I cannot get in the menu to launch a game, before I get blue screened. I have downloaded many updates on drivers, which was brought about because of the netio.sys line of text directing it towards the problem. I have yet to try uninstalling and reinstalling the rx 480 driver. My Motherboard is a Gigabyte 990fxud3. I use Avast, IObit, and Advanced Care System. I have cleaned the registery, and I have used whocrashed to check and see if there was any usable solution, but after going without sleep for almost 2 days, I am too burned out to make heads or tales of this.
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 12/11/2016 2:10:05 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88001921A1D)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001921A1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 12/11/2016 10:45:51 AM your computer crashed
crash dump file: C:\Windows\Minidump\121116-138372-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001625A1D)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001625A1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 12/11/2016 9:26:06 AM your computer crashed
crash dump file: C:\Windows\Minidump\121116-124910-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001625A1D)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001625A1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

If anyone could help me with this, I would be truly grateful. If you need anymore info that I have likely to have forgotten to put in, please do let me know.
 
Solution
you would want to boot into bios and confirm the BIOS was updated by finding the firmware version of the installed bios. Just compare it to the version you downloaded and installed. you should be able to just run the installer for the network card after you download it from the motherboard vendor website.

if you still get a bugcheck, copy a current memory dump from c:\windows\minidump directory to a web storage site like Microsoft onedrive, google docs or media fire. share the memory dump file for public access and post a link. I can take a quick look at in the windows debugger to see why windows shut your system down with a bugcheck.
bummer, you have a driver that is trying to access a bogus memory location.
memory location 8. most likely some driver has overwritten over the other drivers data with data of its own.

the good point will be that it is most likely going to be your network driver.
I would go to your motherboard vendors website and update the Ethernet network driver.
(or maybe a Bluetooth network driver or USB wireless network driver, I can not tell with the data provided)

on some msi systems you will want to update the BIOS and the network driver as some have network functions implemented in the BIOS and the BIOS should be updated at the same time.
 


I had went to the motherboard website, but when I tried to update the latest version of my bios and driver, it did not say anything after executing the file, to signify that it worked. After trying to download a patch on battle.net as soon as it hit the final mark, and was about to finish, I was bsod'd. After I restarted, I had to reinstall my game. I am currently doing so, hoping that it will not be a similar occurrence. But if it is, does that mean I need to uninstall the network driver/Bios, and attempt to reinstall it after?
 
you would want to boot into bios and confirm the BIOS was updated by finding the firmware version of the installed bios. Just compare it to the version you downloaded and installed. you should be able to just run the installer for the network card after you download it from the motherboard vendor website.

if you still get a bugcheck, copy a current memory dump from c:\windows\minidump directory to a web storage site like Microsoft onedrive, google docs or media fire. share the memory dump file for public access and post a link. I can take a quick look at in the windows debugger to see why windows shut your system down with a bugcheck.
 
Solution