Language:

Homepage » DLL Q & A

Blue Screen Stop Error In Netio.sys In Vista

Download Now


Netio.sys blue screen

DOROTHY MCBRIDE asked on January 8, 2013. Status: Answered & Closed.

Blue Screen Stop Error In Netio.sys In Vista

» I've been getting several BSODs in netio.sys the last few days and now they're happening every time I log into windows. I'd appreciate if someone could help me figure out the cause of this. I'm running Windows Vista Business x86 SP2.


Best Answer

» The reasons behind BSOD can be a hardware conflict, driver's failure, or a corrupt registry, it can also result from a virus, such as Trojan:Win32/Medfos.A. Now we just talk about the driver's failure, the driver files with the .sys extension are actually dll files, and are the basic reasons for BSOD. If you are not one of the lucky ones who can fix the BSOD with a reboot, then you will need to do some diagnosis to resolve the problem. With all the possible reasons for the BSOD ranging from software to hardware, or hardware drivers, it is very difficult to list a precise set of instructions for every possibly BSOD. Don't be panic about it. Here is a simple way for you to repair blue screen, provided that you have already downloaded DLL Suite, which is a professional dll file error fixer.

Firstly, reboot the computer in safe mode: press the F8 key before the Windows screen appears. This will boot the computer into the Advanced Options screen where you can choose advanced boot options. Choose "Safe Mode" and press "Enter", wait for the Windows screen to appear, then click DLL Suite, run it and the blue screen will be repaired automatically, just because DLL Suite has built-in feature of fix BSOD.

THOMAS MUNSON replied on January 16, 2013


All Answers:

  1. HISHAM ASHOOR replied on January 8, 2013: » Here are my general purpose instructions for figuring out what is really causing your BSOD:Since the Microsoft Answers forum implementation does not prompt for any kind of system information when a new question is asked, we know absolutely nothing about your system. Not knowing fundamental information about a problem prolongs the frustration and agony of resolving these issues.

    Thank you MS Answers, for making the resolution of simple problems as frustrating and time consuming as possible.

    Please provide additional information about your system as best you can:What is your system make and model?What is your XP Version and Service Pack?

    Describe your current antivirus and anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc.

    Can you make the system crash any time you want? For example, would you say that there is any particular system activity that coincides with the crashes (like watching videos, playing games, etc.).

    The next time your system crashes, provide more information about what you see.

    Here is a BSOD example showing information you need to provide:

    http://techrepublic.com.com/i/tr/downloads/images/bsod_a.jpg

    Send the information pointed to with the red arrows (3-4 lines total).

    Send the entire *** STOP message line since there are clues in the 4 parameters.

    If there is a file name listed under the STOP message, be sure to include that information too.

    Skip the boring text unless it looks important to you. We know what a BSOD looks like, we need to know what your BSOD looks like.

    Now provide more information about your system and information from the most recent crashes.

    Click Start, Run and in the box enter: msinfo32

    Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.

    There will be some personal information (like System Name and User Name), and whatever appears to be private information to you, just delete it from the pasted information. This will minimize back and forth Q&A and eliminate guesswork.

  2. DOROTHY MCBRIDE replied on January 9, 2013: » I already updated my drivers through windows update before and it didn't solve the problem. I tried doing a clean boot and it worked, so I slowly added programs back into the start up list. It didn't crash at all even with them all back in. Then later on today it crashed again on boot up. Seems like its just too inconsistent to be able to figure out from slowly adding items to the start up list.

  3. ALEXANDER RATA replied on January 9, 2013: » Notice the 08 (double fault) as 1st parameter means the are likely two causes. Be sure to Update your drivers manually as using Windows Updates only finds certified drivers and Microsoft and the Device makers are far behind in that process. Update NIC, WiFi, BIOS and Video/Display and other major drivers.

    Are you running ZoneAlarm or ANY 3rd party Firewall? Those could be at least part of the issue. Have you added hardware or updated drivers recently? Check Control Panel - Windows Updates to see if any drivers have been updated there just before this started happening.

  4. DOROTHY MCBRIDE replied on January 11, 2013: » Well I already ran memtest86 and it didn't give any errors. I ran SFC and chkdisk, neither of which returned any errors. I updated my BIOS, network drivers, and sound card drivers. None of that helped. Around the time this started occurring, I got a new G15 keyboard. But I don't really see how a keyboard could cause this. I am running a third party firewall, Comodo, but I've had it since I switched to vista about 2 years ago and haven't had any problems with it. It hasn't been updated recently so its not like it got an update that broke it. I'm also running Avast AV, which I've had for even longer and again, I haven't had any problems with it.

    I decided to just reformat my computer. Between this and the slow startup/shut down times, I figured I was better off just starting fresh. Since Comodo might have been the cause I'm going to avoid installing it again if I can, but I would prefer to have some kind of alternative firewall. Windows firewall just doesn't cut it for me. It has terrible outbound protection since it lets programs auto add themselves as exceptions.

  5. STEVEN HOFFMAN replied on January 14, 2013: » I almost always think this is a very bad idea. Besides all the work of doing this, if you reformat and reinstall without finding out what caused your problem, you will very likely repeat the behavior that caused it, and quickly find yourself back in exactly the same situation.

DLL Q & A you might like:

  1. System32 DRIVERs Pci.sys Error »
  2. Bsod With Igdkmd64.sys Error »
  3. Deleted System32\Drivers\Comp-batt.sys At Computer Startup »
  4. Get Win32.sys Blue Screen When Opening Google Chrome »
  5. Hiber_nvraid.sys Blue Screen on Hibernate »
  6. Intelppm.sys Blue Screen »
  7. Atibtmon.exe Microsoft Visual C++ Runtime Library Error »