NETIO.SYS BSOD Windows updates + Remove XP Pro Boot


  1. mfx
    Posts : 74
    Windows 7 Ultimate x64
       #1

    NETIO.SYS BSOD Windows updates + Remove XP Pro Boot


    Hi

    Another BSOD with W7x86 upgrade from XP to W7 Home/Family edition.

    Recently installed the update over exisiting XP Pro which I was going to reinstall all going fine.
    • Updated all W7 files and drivers, Windows7 installed.
    • Installed few minor apps everything ok.
    • Installed MS Office 2007 again ok
    • Went to update after office install via Windows 7 startmenu.
    • Finds 21security updates and 2 optional, selected all (and tried selecting just essentials)


    Start to download and install from Windows7 Update in start menu and then BSOD with NETIO.SYS issue.

    Message on reboot :

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 1000008e
    BCP1: C0000005
    BCP2: 8BAD8028
    BCP3: 9C84B614
    BCP4: 00000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\123010-93656-01.dmp
    C:\Users\ALUM7\AppData\Local\Temp\WER-127687-0.sysdataxml
    Have attached both in ZIP files (hope that's ok not sure if there's any personal data so let me know asap).

    2) Before the upgrade I was going to reinstall XP and I have a Bootup option in DOS for Windows7 or Windows XP Professional Installation. This didn't have anything to do with the BSOD as was fine fora couple of days till installed MS Office and attempting latest windows update.

    Have used BCD and W7 is reporting W7 as the only boot option, guessing it's somewhere deeper in the MBR so need some advice please.

    System hardware is old but scores around 4.0 in the W7 compatibility whichis fine as it's just a basic office machine.
    Last edited by mfx; 30 Dec 2010 at 15:58. Reason: BSOD Updated files as per forum rules-:)
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    mfx said:
    Hi

    Another BSOD with W7x86 upgrade from XP to W7 Home/Family edition.

    Recently installed the update over exisiting XP Pro which I was going to reinstall all going fine.
    • Updated all W7 files and drivers, Windows7 installed.
    • Installed few minor apps everything ok.
    • Installed MS Office 2007 again ok
    • Went to update after office install via Windows 7 startmenu.
    • Finds 21security updates and 2 optional, selected all (and tried selecting just essentials)


    Start to download and install from Windows7 Update in start menu and then BSOD with NETIO.SYS issue.

    Message on reboot :

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 1000008e
    BCP1: C0000005
    BCP2: 8BAD8028
    BCP3: 9C84B614
    BCP4: 00000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\123010-93656-01.dmp
    C:\Users\ALUM7\AppData\Local\Temp\WER-127687-0.sysdataxml
    Have attached both in ZIP files (hope that's ok not sure if there's any personal data so let me know asap).

    2) Before the upgrade I was going to reinstall XP and I have a Bootup option in DOS for Windows7 or Windows XP Professional Installation. This didn't have anything to do with the BSOD as was fine fora couple of days till installed MS Office and attempting latest windows update.

    Have used BCD and W7 is reporting W7 as the only boot option, guessing it's somewhere deeper in the MBR so need some advice please.

    System hardware is old but scores around 4.0 in the W7 compatibility whichis fine as it's just a basic office machine.

    Where do we start.

    1-Zone alarm is causing these crashes. remove it and replace with the built in win 7 driver.

    2-Eset remove it and replace with Microsoft Security essentials

    3-Old drivers needing updating

    Code:
    pnp680.sys    11/13/2007 14:26:50    0x4739fa7a    0x8bb6d000    0x8bb82000        0x00015000                    
    anodlwf.sys    3/6/2009 5:09:51    0x49b0f66f    0x8bfb3000    0x8bfbb000        0x00008000                    
    epfwwfpr.sys    4/9/2009 7:42:42    0x49dded42    0x99208000    0x99221000        0x00019000                    
    eamon.sys    4/9/2009 8:00:19    0x49ddf163    0x94338000    0x943f4000        0x000bc000                    
    ehdrv.sys    4/9/2009 8:01:29    0x49ddf1a9    0x8c2c7000    0x8c2e4000        0x0001d000
    Beyond that, please run Verifier with these settings:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.
    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

    Using Driver Verifier to identify issues with Windows drivers for advanced users


    Ken J
      My Computer


  3. mfx
    Posts : 74
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thanks W7Forum and Ken - genius and a massive time saver.

    Think my issue was the Sil680 PCI ATA expansion card. Downloaded and installed drivers manually as they were actually part of the MSWindowsUpdate. This driver I believe was the core issue of my rig.

    BIG TIP - scouring the internet and all advice seems Zonealarms is not healthy for W7i86 however my main rig has the x64 installed on W7Ultimatex64 and all fine! Basically for 32 get the ZA removal tool and clean it all out :) Download MS Security Essentials.


    Updated EsetNod32 from their website (my version was a 2009 from backup).

    No BSOD now for 24+hours and kept things running, scanning and defragging.

    Ran MS Updates and NO CRASH HURRAH....seems the problem may have been solved, we shall see.

    Thanks again


    Thanks Ken,

    Was wondering if it was ZA, have an i7 rig Ultimate64 with ZA but it's a different beast.

    Will try the uninstalls and ms security essentials (old habits hard to beat out of the system)!

    Will follow the rest of your advice on further events after removal.

    Thanks for a quick and solid response, will post back developments/result ?:)

    Happy New Year ...
    Last edited by mfx; 31 Dec 2010 at 16:49. Reason: Update Day 2
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 18:50.
Find Us