netio.sys or ndis.sys causing BSOD?

[ajabghajab]

Like most folk in this section of the forum, I too am troubled by the dreaded BSOD. This is not the first time that I got a BSOD, but this is definitely the first time I had such back to back events. I got the BSOD four times in a single day, and finally had to post here.

I did some basic check using windbg and it seems to suggest that netio.sys is the cause for the issue, though I fail to understand how to fix it.

My computer crashes when in Windows 7, and further the internet connection is extremely unstable, on one moment and off the next. And all this in durations of seconds. So for 10 seconds it doesn't work, then works for 4, doesn't work for 6 and so on. I started the machine in Safe Mode with networking and it worked perfectly fine. I uninstalled the latest updates that were done - an Adobe Flash plugin update, and a Nokia connectivity cable driver update, without any success.

Have attached the dump files. Any help would be greatly appreciated.

 

[zigzag3143]

Like most folk in this section of the forum, I too am troubled by the dreaded BSOD. This is not the first time that I got a BSOD, but this is definitely the first time I had such back to back events. I got the BSOD four times in a single day, and finally had to post here.

I did some basic check using windbg and it seems to suggest that netio.sys is the cause for the issue, though I fail to understand how to fix it.

My computer crashes when in Windows 7, and further the internet connection is extremely unstable, on one moment and off the next. And all this in durations of seconds. So for 10 seconds it doesn't work, then works for 4, doesn't work for 6 and so on. I started the machine in Safe Mode with networking and it worked perfectly fine. I uninstalled the latest updates that were done - an Adobe Flash plugin update, and a Nokia connectivity cable driver update, without any success.

Have attached the dump files. Any help would be greatly appreciated.

The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder (3)\032810-13899-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82a02000 PsLoadedModuleList = 0x82b4a810
Debug session time: Sun Mar 28 05:54:06.487 2010 (GMT-4)
System Uptime: 0 days 1:14:15.469
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {1000, 2, 1, 82a490dc}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

 

[Jonathan_King]

Try looking for an updated driver for your network card.

Right-click on the card in Device Manager, and select Update Driver Software.

870ef000 8712d000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8af1d000 8af42000   Rt86win7 Rt86win7.sys Thu Feb 26 04:04:22 2009 (49A65B16)
870ef000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)

I only see one driver dated 2010 or later, so you may also consider using a driver updater like Driver Easy.

 

[ajabghajab]

I did update my drivers, but no luck. What I have noticed is this:

When I start my system fresh, it works great without any issues. However, once uTorrent is started, the network fluctuates for a short while before going kaput. So I tried next time by restarting the system and not using uTorrent. It worked absolutely perfectly for quite some time. And then, the network stopped working.

Sensing the issue to be something with 'over-usage' of the driver - sounds stupid I know - I tried downloading a large file using a Orbit just to be sure. It went well for a while before stopping. The source is great - Microsoft servers, so no issues with that.

What could possibly be the issue?

 

[Jonathan_King]

It is possible the problem is not with your driver but the network card itself.

See if you can borrow a card from someone else.

You can also look up your computer online and see if the manufacturer released any driver updates.

 

[ajabghajab]

I get a confirmation stating the driver is up to date.

 

[Capt.Jack Sparrow]

Hello,

Please post us the MSINOF32 File

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

Good Luck,
Captain

 

[ajabghajab]

Here you go

 

[Capt.Jack Sparrow]

Here you go

Hello,

I guess it might has to do something with your NIC card because NETIO.sys is Network bug. Go to Realtek Website there you'll find some Diagnostic Utility download and run them see whether it comes clean. According to MSINFO32 most of the crashes was with Internet Explorer. When you reinstall the Driver make sure you download the Drvier from Realtek website and disconnect from the Internet and remove the exisiting driver and reboot and reinstall the fresh driver.

Hope this helps,
Captain

 

[ajabghajab]

Thanks, will try that. btw, can you tell me which part of the trace showed this:

According to MSINFO32 most of the crashes was with Internet Explorer.

Would like to be able to debug some stuff myself too

 

[ajabghajab]

Further trial and error is telling me that when I have a lot of connections opened from uTorrent - or any application in general - I face this error. I mean, the network stops working first. Over prolonged periods, this results in a crash.