Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD Netio.Sys


  • Please log in to reply

#1
AngelaT

AngelaT

    Member

  • Member
  • PipPip
  • 10 posts
Having repeated BSODs (especially when running u torrent).

Windows 7. lenovo x220 netbook.

Error code below. Minidump attached.

Any help trying to figure out what to do in tangible terms would be MUCH Appreciated. not technically savy, so may require a bit of a step by step explanation!

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: NETIO.SYS

DRIVER_IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x000000d1 (0x00000014, 0x00000002, 0x00000000, 0x8ccc4bf2)

*** NETIO.SYS - Address 0x8ccc4bf2 base at 0x8ccbe000 DateStamp 0x4ce78963

Attached Files


  • 0

Advertisements


#2
AndroidOS

AndroidOS

    Junior

  • GeekU Junior
  • 700 posts
Hi AngelaT, and welcome to Geeks To Go. :happy:

Your log shows memory coruption as the cause fo the BSOD. This is usually caused by either a faulty driver or faulty hardware, usually ram. Before I go any further however, you have only included one log, and I would prefer at least two so that I can compare them. Are there any more logs in your Minidumps folder? To get there type in %systemroot%\Minidump in Windows Explorer.
  • 0

#3
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
If it is a driver you can do the following.



Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads



If you want more exact logs you can do the following:

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
To check the memory you can do the following.

If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#5
AndroidOS

AndroidOS

    Junior

  • GeekU Junior
  • 700 posts
I'll let you take this one then rshaffer61. :happy:
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
You are good AndroidOS. I'm just offering some assistance to try and make it easier for you. :thumbsup:
You started with the topic and I am here to offer help if needed.
  • 0

#7
AndroidOS

AndroidOS

    Junior

  • GeekU Junior
  • 700 posts
OK then. :thumbsup: I appreciate the help you gave. :thumbsup:
  • 0

#8
AngelaT

AngelaT

    Member

  • Topic Starter
  • Member
  • PipPip
  • 10 posts
Who Crash Log below. Blue Screen View attached. Its not hardware it seems. would send the remaining dump files in next post.

On Sun 22-Apr-12 1:47:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042212-21418-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCEABF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 22-Apr-12 1:47:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!RtlCopyBufferToMdl+0x1C)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCEABF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 22-Apr-12 10:15:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042212-28017-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCC4BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 22-Apr-12 9:31:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042212-31262-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCC8BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 22-Apr-12 3:47:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042212-13852-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCCFBF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 22-Apr-12 3:01:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042212-13665-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CD6EBF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 21-Apr-12 6:49:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042212-14086-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCD6BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 21-Apr-12 6:11:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-13431-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCD9BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 21-Apr-12 12:40:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-13837-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCE8BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 21-Apr-12 8:31:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-13665-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCC4BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 21-Apr-12 8:14:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-13041-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCD6BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 21-Apr-12 6:51:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-13603-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCF6BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 20-Apr-12 6:43:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-21871-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCCEBF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 20-Apr-12 2:59:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042012-15334-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCD5BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 19-Apr-12 4:23:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041912-21403-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6BF2)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFFFF8CCE8BF2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

18 crash dumps have been found and analyzed. Only 15 are included in this report.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#9
AngelaT

AngelaT

    Member

  • Topic Starter
  • Member
  • PipPip
  • 10 posts
last three minidumps attached.

Attached Files


  • 0

#10
AndroidOS

AndroidOS

    Junior

  • GeekU Junior
  • 700 posts
Thanks for them Angela. :thumbsup:

While I read through the logs, could you please run Windows Update, and make sure that all of your drivers are up to date. Let me know when you have done that.

Edited by AndroidOS, 22 April 2012 - 08:28 AM.

  • 0

Advertisements


#11
AngelaT

AngelaT

    Member

  • Topic Starter
  • Member
  • PipPip
  • 10 posts
windows update is upto date.

Drivers updated- within my limits of expertise.
  • 0

#12
AndroidOS

AndroidOS

    Junior

  • GeekU Junior
  • 700 posts
Sorry for the delay in replying Angela.

Before we go any further, can you please tell me if you are still recieving the bsod's, and can you please follow the advice rshaffer61 gave you concerning memory.
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

windows update is upto date.

Drivers updated- within my limits of expertise.



Just curious if there was a USB update in your Windows updates?
  • 0

#14
AngelaT

AngelaT

    Member

  • Topic Starter
  • Member
  • PipPip
  • 10 posts
Yes, its still BSODing itself out.

Havent done a mem scan yet- laptop doesnt have a CD drive. Therefore, would take till evening to get it figured out. Its a brand new laptop- so hardware is relatively less likely. However, would check it when I am back home.

Lastly, yes, i think there as a USB update that I picked up in the past.
  • 0

#15
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Do the memory diagnostics first please and if no bad memory then do the following.

Download DriverMax and have it scan your system. It will open their website with all the out of date drivers you can update. With the free version you can update only 2 drivers per day so if you have a lot of them it will take a few days to get everything updated. I have been using it for about 4 months now and like it better then any other utility out there for keeping my drivers up to date.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP