BSOD caused by ndis.sys, NETIO.SYS and ntoskrnl.exe

[Daithi26]

http:// Pictures of dmp


This has been a problem for 2 weeks now, I've have updated drivers, refreshed Win10, reinstalled win10 and I keep get bsod bad_pool_caller and the problem is these ndis.sys, NETIO.SYS and ntoskrnl.exe. I don't know what else to do. Help would be appreciated, Thanks.

 

[Colif]

can you download and run this: http://www.resplendence.com/whocrashed
it looks at error logs and displays them in easier to understand terms
It might show another cause apart from pointing at ntoskrnl and saying "that did it" as it didn't, its one of the most important parts of windows and only does shit if pushed to by another driver

Paste the results in here

 

[johnbl]

a bugcheck in netio.sys is will be caused by the network driver you have installed.
This can be a wired or wireless driver (wifi or even a bluetooth driver)
if you are using a USB wireless driver it can be caused by old USB drivers also, or even bugs in the USB support in the BIOS.

so, you will need to update the drivers starting with the ethernet driver. if you have a USB ethernet device you would update the USB driver, the CPU chipset drivers and the BIOS in addition to the ethernet driver itself.

 

[Daithi26]

can you download and run this: http://www.resplendence.com/whocrashed
it looks at error logs and displays them in easier to understand terms
It might show another cause apart from pointing at ntoskrnl and saying "that did it" as it didn't, its one of the most important parts of windows and only does shit if pushed to by another driver

Paste the results in here

Thank you so much, WhoCrashed scan revealed it was Malwarebytes causing the bsod, all fixed now

 

[Colif]

can you download and run this: http://www.resplendence.com/whocrashed
it looks at error logs and displays them in easier to understand terms
It might show another cause apart from pointing at ntoskrnl and saying "that did it" as it didn't, its one of the most important parts of windows and only does shit if pushed to by another driver

Paste the results in here

Thank you so much, WhoCrashed scan revealed it was Malwarebytes causing the bsod, all fixed now

Malwarebytes probably got set off by the other drivers John mentioned, I would run a program like Driver Booster and see what other old drivers you have on pc. I did the fix you did - deleted Malwarebytes - just to find later my Ethernet drivers were from January last year and needed an upgrade.

 

[Daithi26]

It did turn out to be Malwarebytes lol

 

[johnbl]

generally the malwarebytes driver is just the victim of a old network driver. When you install your next virus scanner it also might fail.

can you download and run this: http://www.resplendence.com/whocrashed
it looks at error logs and displays them in easier to understand terms
It might show another cause apart from pointing at ntoskrnl and saying "that did it" as it didn't, its one of the most important parts of windows and only does shit if pushed to by another driver

Paste the results in here

Thank you so much, WhoCrashed scan revealed it was Malwarebytes causing the bsod, all fixed now

 

[Colif]

generally the malwarebytes driver is just the victim of a old network driver

can you download and run this: http://www.resplendence.com/whocrashed
it looks at error logs and displays them in easier to understand terms
It might show another cause apart from pointing at ntoskrnl and saying "that did it" as it didn't, its one of the most important parts of windows and only does shit if pushed to by another driver

Paste the results in here

Thank you so much, WhoCrashed scan revealed it was Malwarebytes causing the bsod, all fixed now

I mentioned that in a previous post. He may notice eventually.