Bsod netio.sys

[lewisrick55]

Hi - I recently updated a few drivers on my Toshiba Tecra R940. Since then I started to receive BSODs identifying NETIO.SYS. I rolled back the wi-fi network adapter driver, but still BSODs. I installed an earlier version of INTEL PROSet/Wireless WiFi utility, but still BSODs. Last night after the last rollback my laptop actually powered off on its own without a BSOD. I've attached the files captured by the SF_Diagnostic_Tool and hope that someone real smart can please help. Thank you.

 

[Arc]

Hi lewisrick55.

Uninstall McAfee Security Scan Plus Using McAfee Removal Tool. It is not something that you want, it came as bloated with some update from adobe.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
5. Apply > OK
6. Accept then restart.

Then (the main thing) enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

_________________________________________

BugCheck 50, {fffffa8015a00000, 0, fffff80003291798, 2}


Could not read faulting driver name
Probably caused by : Fs_Rec.sys ( Fs_Rec!FsRecReadBlock+bb )

Followup: MachineOwner
---------

 

[lewisrick55]

McAfee removed, Driver Verifier set; next step - reboot

Thank you - I had no idea that McAfee was installed - you are correct on how it got there. I removed it and turned on Driver Verifier. As soon as I get to a point after some important work this morning I will reboot to activate. Thank you very much for your help!

 

[lewisrick55]

New BSODs after rebooting with verifier active

Hi - I rebooted with verifier active as instructed. This time on reboot I received a new BSOD - C1 - special_pool_detected_memory_corruption. I rebooted and then received another new BSOD - C9 with indications of PGPwded.sys involvement. My hdd is encrypted by Symantec PGP - as required by my employer.

I then rebooted into Safe Mode and disabled verifier. Rebooted normally and so far no BSODs. Attached are SF diag tool collected logs. Thank you very much for your help.

 

[Arc]

You are supposed to free up the start-up before enabling Driver Verifier.

Disable Verifier, free up startup and enable verifier again.

 

[lewisrick55]

Free up startup

OK, sorry, I freed up the modules I thought were unnecessary and kept the critical ones. Later today I will follow your explicit instructions when I have some time. Thanks again.

 

[Arc]

OK, sorry, I freed up the modules I thought were unnecessary and kept the critical ones. Later today I will follow your explicit instructions when I have some time. Thanks again.

Otherwise, Driver verifier may fail to record a crash dump, as it did.

 

[lewisrick55]

Another test - still no dump

Hi - I disabled all of the startup modules except for the touchpad (I didn't have any for Symantec). I then setup verifier, rebooted and after authenticating to Symantec PGP, I received the BSOD C9 PCPwded.sys - with no dump taken. I'll upload the SF diags anyway. I did some minimal research on PGPwded.sys and there were a few older discussions about it being a victim of the lack of memory when it loads due to a prior driver using memory beyond its allocation. I am not able to bypass PGP since my hard drive is encrypted. Thanks for any help you can provide.

 

[Arc]

Hi - I disabled all of the startup modules except for the touchpad

As per the data uploaded in post #8, you have 32 items set to autostart with windows.

It is the third time I am suggesting you to free up startup, as stated in post #2.

If I notice no change there in your next post, too; I will not say it again, but will understand that I cannot help you, because you dont pay attention to the instructions.

 

[lewisrick55]

Instructions followed

Hi - apologies. The startup items were disabled at the time of the BSOD. What I had done following the failure was to boot into Safe Mode, deactivate verifier and at the same time re-enable the startup items. That is why they were listed in the diags.

1. This time I disabled all startups except for touchpad.
2. Rebooted
3. checked msconfig and found that two additional items were somehow configured to start - they are mandated by my employer so somehow they were automatically re-enabled; everything else was disabled though
4. ran verifier and activated
5. rebooted
6. received BSOD - C9 - PGPwded.sys **Note - no dump is generated in this case**
7. rebooted into Safe Mode
8. checked startups - unchanged - only touchpad and the two extra items
9. ran verifier and deactivated
10. rebooted successfully
11. checked startups - unchanged - only touchpad and the two extra items
12. ran SF diag collector
13. uploaded to this thread

 

[Arc]

• received BSOD - C9 - PGPwded.sys **Note - no dump is generated in this case**

Still no crash dump .... not an usual case. One possible cause is the HDD is becoming inaccessible when the BSOD is taking place.

Anyway, Stop 0xC9 means DRIVER_VERIFIER_IOMANAGER_VIOLATION, which ensures that the DV was active there, and it points the driver PGPwded.sys as a problem causing one.

You said it earlier ....

My hdd is encrypted by Symantec PGP - as required by my employer.

But you can see it clearly that the PGP Storage filter service is causing issues for you. And in that case, you must to get rid of Symantec, at least on a test basis.

From your words it appears that it is an office computer. In that case, as you cannot uninstall Symantec, you contract the IT department of the office. They may have some good idea as to how the BSODs can be stopped without removing Symantec.

 

[lewisrick55]

Thank you very much! I do not understand why the failures began with a BSOD pointing to netio.sys and now is a PGP issue - but only when I run verifier. I still think I will get a random netio.sys BSOD which does produce a dump. When that happens I would appreciate your help diagnosing that. Thank you again.

 

[Arc]

I do not understand why the failures began with a BSOD pointing to netio.sys and now is a PGP issue - but only when I run verifier. I still think I will get a random netio.sys BSOD which does produce a dump.

Many a times it is seen that a natio.sys BSOD is occurred due to the symnets.sys, Symantec Network Security WFP Driver; or teefer2.sys, Symantec Endpoint Protection Firewall.

The other opssibility is the network driver itself, and apparently there is a possible update to your Intel® Centrino® Advanced-N 6235, Intel® PROSet/Wireless Software and Drivers for Windows 7. You should try to apply it.

I have suggested you to uninstall McAfee Security Scan Plus in post #2 but you havent done it, too. Saying it again, it is not something that you want. You have got it unintentionally. This will not do any good for you, and having McAfee in your system is enough of a problem.

One very common source of McAfee Security Scan Plus is flash player update, as the users dont bother to uncheck the bloated things.

View attachment 334089
​

Adobe gets money form McAfee for advertising their product; and you get some trouble due to carelessness.

 

[lewisrick55]

Thanks Arc. Unfortunately my BSOD troubles began with updating the Intel® Centrino® Advanced-N 6235, Intel® PROSet/Wireless Software and Drivers for Windows 7. I had to roll them back and still received BSODs on netio.sys, albeit not every few minutes. Re: McAfee - I did remove it per your instructions. It doesn't show up on my installed software list. I will try it again. I understand how it slips in with other apps - I must have let my guard down one time. After I try the removal tool again is there some way to verify that it is completely gone? Thanks.