Annoying Repetitive Bluescreen!

[WolfireSounds]

I was trying to use my pc and all of a sudden it bluescreened. It was right after I just installed the Nvidia Drivers but I got rid of those quickly before it bluescreened again. It still bluescreens and I can't even use my computer. My pc works in safe mod so its an issue with drivers, also because the error code says something about drivers. I can't do the specific steps including opening command prompt and typing "perfmon /report" because it opens up and then says something along the lines of "Unknown location" or similar. For some reason, probably because safe mod disables the drivers, I cannot use the internet while in safe mode. I only was able to get the dump files and a screenshot. Although Baidu said something about "Autorun.inf" or something like that and I was able to remove that in safe mode but still bluescreened when booting into normal mode. I have Windows 10 64 bit, Windows 10 was originally installed. I have had to reinstall it for odd reasons like videos in Adobe Media Encoder weren't rendering but that fixed the issue. I completely reinstalled it this time because before I couldn't install nay windows updates. The os is a full retail version, The age of the system of me using it is 6 months. But the hardware is a few years old or a year. (EVGA GTX 1070 SC, i5-7500, Ballistix 8GB 2400mhz DDR4), OS is a couple of months old but I just yesterday reinstalled it because I though it might fix the issue. I've reinstalled it 3 times since of got the pc for various issues, CPU model is an i5-7500, Video card is a EVGA Geforce GTX 1070 SC, Motherboard is a Gigabyte GA-B250M-DS3H, Power supply is a EVGA Supernova G1 120-G1-0650-XR 80+ Gold 650w Fully Modular Power supply, There is no system manufacturer because I built it. No model number because I built it, it is a desktop. All of the parts are new except for the video card which was used for a few months but it wasn't bitcoin mined on. The dump files will be in a link right here because it is a zip file ---> http://www.mediafire.com/file/4x67jw8e4ms2gxq/Dump Files.zip

[Radium_Angel]

@WolfireSounds

 

I'm at work so I can't get a mediafire link, got somewhere else to host it?

 

It sounds to be like you have bad hardware, like RAM or video card.

[WolfireSounds]

1 minute ago, Radium_Angel said:

@WolfireSounds

 

I'm at work so I can't get a mediafire link, got somewhere else to host it?

 

It sounds to be like you have bad hardware, like RAM or video card.

Is there an ideal location you would like me to post it?

[WolfireSounds]

21 minutes ago, Radium_Angel said:

@WolfireSounds

 

I'm at work so I can't get a mediafire link, got somewhere else to host it?

 

It sounds to be like you have bad hardware, like RAM or video card.

I can open them and send screenshots if that’d be a prefered method

[indrora]

This sounds like bad RAM. Grab a copy of memtest86 and see what it has to say. Posting the dump here isn't too helpful without having a copy of the Windows debugging tools and a bit of special sauce.

 

I'm going to assume you're running a clean, otherwise unadulterated install of 10. No tweaks or silly patches, just a clean install of 10 and your drivers.

 

DRIVER_IRQL_LESS_THAN_OR_NOT_EQUAL boils down to two possible options:

• The driver in question is poorly designed (in this case, it's netio.sys that's failing. I'm going to rule this one out for now)
• a chunk of memory has gone wonky and is causing corruption, leading to the driver trying to access memory it shouldn't (this is much, much more likely and the cause of 90% of these)

Easy test is to run your system with only one stick. Repeat with each stick until you can determine that it isn't that stick. If no sticks will boot cleanly, then there might be an issue with your motherboard -- Reset your BIOS settings to default would be my suggestion. 

 

However, I also have a silly set of questions:

• When's the last time you cleaned your case?
• What's the temperature outside? inside? 

I've seen a few cases where packed dust/dirt had collected and shorted lines on the RAM. 

[WolfireSounds]

3 minutes ago, indrora said:

This sounds like bad RAM. Grab a copy of memtest86 and see what it has to say. Posting the dump here isn't too helpful without having a copy of the Windows debugging tools and a bit of special sauce.

 

I'm going to assume you're running a clean, otherwise unadulterated install of 10. No tweaks or silly patches, just a clean install of 10 and your drivers.

 

DRIVER_IRQL_LESS_THAN_OR_NOT_EQUAL boils down to two possible options:

• The driver in question is poorly designed (in this case, it's netio.sys that's failing. I'm going to rule this one out for now)
• a chunk of memory has gone wonky and is causing corruption, leading to the driver trying to access memory it shouldn't (this is much, much more likely and the cause of 90% of these)

Easy test is to run your system with only one stick. Repeat with each stick until you can determine that it isn't that stick. If no sticks will boot cleanly, then there might be an issue with your motherboard -- Reset your BIOS settings to default would be my suggestion. 

 

However, I also have a silly set of questions:

• When's the last time you cleaned your case?
• What's the temperature outside? inside? 

I've seen a few cases where packed dust/dirt had collected and shorted lines on the RAM. 

I just cleaned my case last week, temperature outside is 68 and inside is 73. I’ll try running the memory test. I’ll tell you the results when I’m done

[WolfireSounds]

28 minutes ago, indrora said:

This sounds like bad RAM. Grab a copy of memtest86 and see what it has to say. Posting the dump here isn't too helpful without having a copy of the Windows debugging tools and a bit of special sauce.

 

I'm going to assume you're running a clean, otherwise unadulterated install of 10. No tweaks or silly patches, just a clean install of 10 and your drivers.

 

DRIVER_IRQL_LESS_THAN_OR_NOT_EQUAL boils down to two possible options:

• The driver in question is poorly designed (in this case, it's netio.sys that's failing. I'm going to rule this one out for now)
• a chunk of memory has gone wonky and is causing corruption, leading to the driver trying to access memory it shouldn't (this is much, much more likely and the cause of 90% of these)

Easy test is to run your system with only one stick. Repeat with each stick until you can determine that it isn't that stick. If no sticks will boot cleanly, then there might be an issue with your motherboard -- Reset your BIOS settings to default would be my suggestion. 

 

However, I also have a silly set of questions:

• When's the last time you cleaned your case?
• What's the temperature outside? inside? 

I've seen a few cases where packed dust/dirt had collected and shorted lines on the RAM. 

How would I install the usb version?

[indrora]

The USB stick download ("Image for creating bootable USB Drive") includes ImageUSB, which will write the bootable image to a USB disk. You can also find a copy of memtest86 on pretty much any ubuntu install CD you have. 

[Radium_Angel]

1 hour ago, WolfireSounds said:

Is there an ideal location you would like me to post it?

Google Drive

 

I have the tools to debug.

But if these BSoD errors all say something different, then you've got a RAM issue. For an ideal test, you'll need to run it overnight.

Oh, if you are overclocking anything, don't. Set it back to default.

[WolfireSounds]

Sorry for tagging you radium for the wrong thing but I don’t have anything overclocked. Except for the stock factory over lock for the gpu and turbo boost for the cpu but I don’t think that counts as overclocking

[WolfireSounds]

1 hour ago, indrora said:

This sounds like bad RAM. Grab a copy of memtest86 and see what it has to say. Posting the dump here isn't too helpful without having a copy of the Windows debugging tools and a bit of special sauce.

 

I'm going to assume you're running a clean, otherwise unadulterated install of 10. No tweaks or silly patches, just a clean install of 10 and your drivers.

 

DRIVER_IRQL_LESS_THAN_OR_NOT_EQUAL boils down to two possible options:

• The driver in question is poorly designed (in this case, it's netio.sys that's failing. I'm going to rule this one out for now)
• a chunk of memory has gone wonky and is causing corruption, leading to the driver trying to access memory it shouldn't (this is much, much more likely and the cause of 90% of these)

Easy test is to run your system with only one stick. Repeat with each stick until you can determine that it isn't that stick. If no sticks will boot cleanly, then there might be an issue with your motherboard -- Reset your BIOS settings to default would be my suggestion. 

 

However, I also have a silly set of questions:

• When's the last time you cleaned your case?
• What's the temperature outside? inside? 

I've seen a few cases where packed dust/dirt had collected and shorted lines on the RAM. 

I also tested Windows memory diagnostics and nothing came up.

[WolfireSounds]

33 minutes ago, Radium_Angel said:

Google Drive

 

I have the tools to debug.

But if these BSoD errors all say something different, then you've got a RAM issue. For an ideal test, you'll need to run it overnight.

Oh, if you are overclocking anything, don't. Set it back to default.

Here are the dump files: https://drive.google.com/open?id=1A5CiVU9r1FF69qwvXSfufkQyf_c9tDrn

[Radium_Angel]

25 minutes ago, WolfireSounds said:

Here are the dump files: https://drive.google.com/open?id=1A5CiVU9r1FF69qwvXSfufkQyf_c9tDrn

Thanks, give me a few minutes to look them over.

BTW, to be certain with memtest, you should let it run for 24 hours minimum...

[WolfireSounds]

2 minutes ago, Radium_Angel said:

Thanks, give me a few minutes to look them over.

BTW, to be certain with memtest, you should let it run for 24 hours minimum...

How do I get It to run for 24 hours

[thedangerine]

I had a similar issue once and it ended up being ram related. I would use memtest86 to test for errors. if that comes back clean try running with a single stick at a time and see how that goes.

[Radium_Angel]

17 minutes ago, WolfireSounds said:

How do I get It to run for 24 hours

Nevermind. I found the issue.

 

NETIO.sys

From another thread on the matter:

 

There appears to be a program installed that may be causing problems with your network connectivity and may be contributing to the BSOD with the netio.sys.
That program is the NVIDIA Network Access Manager program.
The NVIDIA Network Access Manager is an optional program that may be offered during the installation of NVIDIA network adapter drivers.  You can decline the invitation to install the NVIDIA Network Access Manager during any installation of NVIDIA adapter drivers, if it is offered.
The NVIDIA Network Access Manager software is not necessary and has been known to cause issues. 
For now I would suggest to uninstall the NVIDIA Network Access Manager program using "Uninstall a program".
Then restart the computer and check the situation in the Device Manager concerning the Microsoft Teredo Tunneling Adapter which is presently disabled.

 

So it's nVidia driver related, but not video card, but rather network. See if you can uninstall that part...

[Radium_Angel]

This is the full thread:

https://social.technet.microsoft.com/Forums/windows/en-US/8aabb1a2-49d0-4bc2-92ca-dce7ddf5af73/netiosys-causing-my-windows-to-bsod?forum=w7itprogeneral

 

[WolfireSounds]

6 minutes ago, Radium_Angel said:

Nevermind. I found the issue.

 

NETIO.sys

From another thread on the matter:

 

There appears to be a program installed that may be causing problems with your network connectivity and may be contributing to the BSOD with the netio.sys.
That program is the NVIDIA Network Access Manager program.
The NVIDIA Network Access Manager is an optional program that may be offered during the installation of NVIDIA network adapter drivers.  You can decline the invitation to install the NVIDIA Network Access Manager during any installation of NVIDIA adapter drivers, if it is offered.
The NVIDIA Network Access Manager software is not necessary and has been known to cause issues. 
For now I would suggest to uninstall the NVIDIA Network Access Manager program using "Uninstall a program".
Then restart the computer and check the situation in the Device Manager concerning the Microsoft Teredo Tunneling Adapter which is presently disabled.

 

So it's nVidia driver related, but not video card, but rather network. See if you can uninstall that part...

I knew it had to be Nvidia because all was fine before I installed that! I’ll try it

[Radium_Angel]

13 minutes ago, WolfireSounds said:

I knew it had to be Nvidia because all was fine before I installed that! I’ll try it

Good luck, let us know how it turns out

[WolfireSounds]

1 minute ago, Radium_Angel said:

Good luck, let us know how it turns out

Well, it’s not under my control panel so I don’t know how to uninstall it.

[Radium_Angel]

45 minutes ago, WolfireSounds said:

Well, it’s not under my control panel so I don’t know how to uninstall it.

add/remove programs. Or whatever the hell they call it in Win10.

Did you download the latest drive from nVidia? You might have to uninstall that, and when you re-install, choose "custom install" and just do the GFX driver

[WolfireSounds]

42 minutes ago, Radium_Angel said:

add/remove programs. Or whatever the hell they call it in Win10.

Did you download the latest drive from nVidia? You might have to uninstall that, and when you re-install, choose "custom install" and just do the GFX driver

I’m saying that it isn’t there. This happened because I downloaded the latest drivers. I uninstalled them but it still blue screens. I don’t know if the network thing is hiding somewhere

Edited June 27, 2018 by WolfireSounds

[Radium_Angel]

5 hours ago, WolfireSounds said:

I’m saying that it isn’t there. This happened because I downloaded the latest drivers. I uninstalled them but it still blue screens. I don’t know if the network thing is hiding somewhere

If you uninstall the gfx drivers, the bundled nic drivers should go with it.

Otherwise it's wipe and re-install time, paying careful attention to what you install from nvidia

[WolfireSounds]

2 minutes ago, Radium_Angel said:

If you uninstall the gfx drivers, the bundled nic drivers should go with it.

Otherwise it's wipe and re-install time, paying careful attention to what you install from nvidia

Already reinstalled again. I'm gonna double check anything from Nvidia next time

[Radium_Angel]

7 hours ago, WolfireSounds said:

Already reinstalled again. I'm gonna double check anything from Nvidia next time

Yeah, I'm not a fan of them bundling everything-and-the-kitchen-sink into their drivers, but I take it it's working right now?