Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD for a few months (netio.sys)

18 Feb 2010   #1
PeaceFrog

windows 7
 
 
BSOD for a few months (netio.sys)

Hello guys!

I have bought a new pc 4 months ago, and very soon I started to have BSOD, IRQL NOT LESS OR EQUAL. File Netio.sys is detected as possible couse.

My specs are:

Windows 7 32-bit
Intel Core 2 quad CPU Q8300 2.50 Ghz
4 GB ram
Nvidia GTS 250
Realtek PCIe GBE family controller (network adapter)
Asus P5QL/EPU
ntel® P43/ICH10

I have installed NOD 32, if that has anything to do with this...

Please help, I have tried many "solutions" during this time, including registry cleaners, updating and rolling back drivers, windows update... Wierd thing is that some of these solutions actually helped, or to be precise, BSOD didn't show up for some time... But it always comes back again, like a terminator...

Please help!


My System SpecsSystem Spec
.
19 Feb 2010   #2
PeaceFrog

windows 7
 
 

Hey guys, no one answered...

I am really starting to get desperade, BSOD now shows up almost every hour... I can't work or do anything on pc...

Please if someone have a solution to this problem...
My System SpecsSystem Spec
19 Feb 2010   #3
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by PeaceFrog View Post
Hello guys!

I have bought a new pc 4 months ago, and very soon I started to have BSOD, IRQL NOT LESS OR EQUAL. File Netio.sys is detected as possible couse.

My specs are:

Windows 7 32-bit
Intel Core 2 quad CPU Q8300 2.50 Ghz
4 GB ram
Nvidia GTS 250
Realtek PCIe GBE family controller (network adapter)
Asus P5QL/EPU
ntel® P43/ICH10

I have installed NOD 32, if that has anything to do with this...

Please help, I have tried many "solutions" during this time, including registry cleaners, updating and rolling back drivers, windows update... Wierd thing is that some of these solutions actually helped, or to be precise, BSOD didn't show up for some time... But it always comes back again, like a terminator...

Please help!

Hi there
pcoouple of questions
1-where did you get your win 7 image? its not the correct build and I suspect not a real microsoft image.

the cause of this one is you wifi driver

Let us know

Ken






Code:

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


Loading Dump File [C:\Users\K\Desktop\021810-46769-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82a4f000 PsLoadedModuleList = 0x82b97810
Debug session time: Thu Feb 18 08:43:39.482 2010 (GMT-5)
System Uptime: 0 days 1:57:07.918
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 D1, {5706f72, 2, 0, 8bef5555}

Unable to load image \SystemRoot\system32\DRIVERS\Rt86win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt86win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt86win7.sys
***** 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : NETIO.SYS ( NETIO!MdpFree+32 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
.

19 Feb 2010   #4
PeaceFrog

windows 7
 
 

Win 7 image? Hmm, my OS (win 7) came with the pc I bought....

Second, what is wifi driver? I am fairly a begginer in all of this so all the help I can get is very much appriciated!

Edt: I see that wifi has something to do with network, or LAN... But what do I actually need to update? Realtek network adapter or something else? Hm, I have Thomson modem, but I don't see it in device manager...

Sorry if these are a noob questions
My System SpecsSystem Spec
Reply

 BSOD for a few months (netio.sys)




Thread Tools




Similar help and support threads
Thread Forum
Bsod netio.sys
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...
BSOD Help and Support
Bsod - netio.sys
I need help. My PC has given me trouble with the BSOD before, a few months ago, and I did a system restore. I've done this a few times actually, and each time it has temporarily fixed my problem, yet it keeps arising. SO, I decided it's time to get a little help. I've read that Netio.sys has to do...
BSOD Help and Support
BSOD netio.sys
It happened after i updated my drivers..
BSOD Help and Support
Bsod - netio
Hi My new custom built system just experienced a BSOD. Using the Windows debugging tool for x64 system I found the error was related to NETIO!CompareSecurityContexts+6a. This error seem to have multiple possible causes and I am seeking help on how to further debug this issue. The system...
BSOD Help and Support
BSOD NETIO.sys
I fairly regularly get a BSOD when doing various tasks. Mainly I notice it when I have many active internet connections. My drivers are fully update for my network card and my card is a Atheros AR928X.
BSOD Help and Support
Microsoft: Windows 7 RC in 2 Months, RTM in as Early as 6 Months
:D Microsoft: Windows 7 RC in 2 Months, RTM in as Early as 6 Months - Official confirmation of RC and RTM deadlines - Softpedia
News


Our Sites

Site Links

About Us

Find 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 02:47.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App