mh then try the driver provided from your mainboard manufacturer, had a few problems with the windows one too (but intel lan chip) if i remember correctly, no bsod but connection problems
If you are going to try drivers you could try to get the latest available from for example Station-Drivers, the Intel drivers are newer than what MS Update offers.
http://www.station-drivers.com/index.php/downloads/Drivers/Intel/Network-Connections-Software/
(Version 20.0 is WHQL and what I'm using myself, could also get it from Intel's website too if you'd rather get it from the source.)
For other system drivers the Intel Chipset Software usually only has INF files to identify the various components, nothing critical for correct functionality.
(Updating the MEI drivers might help, latest version is backwards compatible but the bios components can be tricky to update unless the mobo manufacturer has it bundled with their latest bios release and if so it's best installed via USB stick flashing, oh and don't install MEI v.9 or v.10 bioses on v.8 motherboards, software is backwards compatible but the bios bit is not.)
The rapid storage drivers hasn't really worked all that well for me so I'm just using the basic drivers from the chipset package but this is probably entirely unrelated to your issue as a faulty storage driver would prevent you from booting into Windows properly.
Updating the bios if you haven't already done so might help but I don't think that's the actual problem here.
I suppose if it's the TCP IP driver that is crashing you could try to disable the network card from the device manager and see if it still bsod's, could of course just be a conflict somewhere causing that part to cause a BSOD while the actual error is elsewhere.
Just some suggestions, better logging functionality in Windows might have been nice to see if one could get some better insight, using the event viewer as someone suggested earlier in this thread could help.
like it have been said, seems like you have probably a driver issue/conflict.
try to remove any program which have custom drivers which interfere with microsoft native ones.
like firewall, antivirus with firewall, network metters, vm's and so.
after that eventually use sfc /scannow in a admin command prompt.
I suppose if it's the TCP IP driver that is crashing you could try to disable the network card from the device manager and see if it still bsod's, could of course just be a conflict somewhere causing that part to cause a BSOD while the actual error is elsewhere.
I only got BSODs during internet activity, pretty much doing anything "web" related in Chrome, so disabling the NIC will surely cure the BSODs and prove nothing about how to fix it I've grabbed the latest Intel NIC drivers from Asus but I'll also get the ones from Intel themselves too, thanks for that.
frogster wrote:
like it have been said, seems like you have probably a driver issue/conflict.
try to remove any program which have custom drivers which interfere with microsoft native ones.
like firewall, antivirus with firewall, network metters, vm's and so.
after that eventually use sfc /scannow in a admin command prompt.
Aye, I'm going to start going through everything that has custom network/etc drivers, I've already removed NetWorx (which had its own passthrough driver) and if it still BSODs today, I'll remove Avast and just use Windows' built-in AV for a few days. I have no VMs installed and firewall is Windows native.
As for sfc? I'm incredibly reticent to run that since I've got a lot of Windows customisation stuff, like Classic Shell, and in my experience sfc tends to put everything back to stock and I don't want it to undo what I've done. It will absolutely be a last resort... and then Global Thermoformatting War as I just table-flip and start afresh.
Thanks guys, I really appreciate the advice and tips
yeah, sfc is the last resort. in most cases i would reinstall windows vs doing a sfc, but if you have altered system files, nothing else will repair them.
dism.exe /online /restorehealth tends to work better. https://technet.microsoft.com/en-GB/library/hh824869.aspx
(Can also use scanhealth and checkhealth to see if there is any corrupted Windows files but if you use modification to say shell32.dll and such those will be detected too and "fixed" if you use the /restorehealth argument)
dism.exe /online /restorehealth tends to work better. https://technet.microsoft.com/en-GB/library/hh824869.aspx
(Can also use scanhealth and checkhealth to see if there is any corrupted Windows files but if you use modification to say shell32.dll and such those will be detected too and "fixed" if you use the /restorehealth argument)
had no ideea that it works in non server editions.
cheers .
If you just wack in a cheapy wireless adapter and see if it happens when using that as the internet connection?
If it doesnt least you've isolated it down to something with your NIC. Is it an onboard nic? Might just be on the fritz and giving up.
Seems odd though.
Easy way to test as the only difference will the the network adapter you are using to connect to the web.
i5 -3570k
8GB DDR 3
Gigabyte GTX 980 Ti Gaming G1
32GB of terrible skill @ FPS games.
I didn't want to say anything just yet, but it *seems* like NetWorx' filtering drive might have been the cause all along. No BSODs yet and I'd have normally had one or two by now :\ Fingers crossed, eh?
I didn't want to say anything just yet, but it *seems* like NetWorx' filtering drive might have been the cause all along. No BSODs yet and I'd have normally had one or two by now :\ Fingers crossed, eh?
Now you set yourself up for a huge disappointment.
I didn't want to say anything just yet, but it *seems* like NetWorx' filtering drive might have been the cause all along. No BSODs yet and I'd have normally had one or two by now :\ Fingers crossed, eh?
Yeah but a slight change in another driver or a Windows update will cause these virtual drivers to crash and burn. Hamachi has had that issue lots of times.
You could try using an older version though, that has often solved it with Hamachi for me.
Aye and it seems, for the first time!, I'm not the only one... Googling "NetWorx BSOD" brings up a lot of results and all of them tcpip.sys or netio.sys, but strangely going back quite a while.. to 2013 at least. I guess I got "lucky" having no trouble until now, if indeed it's NetWorx causing it in the first place.
Still, fingers crossed! And thanks again everyone <3
Just a follow up from nearly a year later; no more network-related BSODs. It really does seem like NetWorx was the cause and removing the program completely fixed the issue! Thanks again to those that helped =)
Sadly, I'm Sabin and my luck never holds for long... system keeps randomly losing primary HDD. It's my SSD so my first thought was that it was on the fritz, but it seems like it happens to either of my two primary SATA ports, they just stop working randomly and it causes my whole system to freeze up and shut down.
It would have to be both cables, since both drives attached to ports 1/2 cut off sometimes. I need to sort this whole system out but the price of an upgrade, thanks to Intel keeping their prices, is exorbitantly expensive
Yeah but they're all full, so even if it *is* the SATA ports.. it means having to lose two drives Buying a new SATA PCI-E card also seems like a temporary plaster on something that's only going to get worse
Yeah but they're all full, so even if it *is* the SATA ports.. it means having to lose two drives Buying a new SATA PCI-E card also seems like a temporary plaster on something that's only going to get worse
I wouldn't be surprised if your mobo is dying. Mine is half dead too by now. Onboard sound for example is completely dead.... muh sweet P67.
They want us to upgrade and ditch our sweet Sandys
Signature/Avatar nuking: none (can be changed in your profile)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
I've grabbed the latest Intel NIC drivers from Asus but I'll also get the ones from Intel themselves too, thanks for that.
