Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Multiple BSOD can someone help?! (tcpip.sys)


  • Please log in to reply

#1
WilliamV

WilliamV

    Member

  • Member
  • PipPip
  • 16 posts
I been having blue screens lately. Most of the time it says I have a problem with tcpip.sys . I have been looking around for answers and cant quite find any. I need someone who knows what everything means to tell me what i have to do. I have a Laptop Windows 7 x64 Ram:8Gb Core i7.

These are all the blue screens i have had for about 8 months (most i think are about the same thing)

Can someone help i am really worried.
Thanks!!!! in advance

Attached Files


Edited by WilliamV, 20 August 2013 - 08:36 PM.

  • 0

Advertisements


#2
WilliamV

WilliamV

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
I have noticed that this happens when I surf the web.
  • 0

#3
WilliamV

WilliamV

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
THIS IS WHAT I GET. CAN SOMEONE PLEASE TELL ME WHAT I CAN DO... I DONT WHAT TO RESTORE MY LAPTOP TO FACTORY CONDITIONS.



On Sat 8/24/2013 9:47:39 AM GMT your computer crashed
crash dump file: C:\windows\minidump\082413-18595-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x622CE)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001A622CE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Sat 8/24/2013 9:47:39 AM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: netwns64.sys (NETwNs64+0x1F4168)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001A622CE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\netwns64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwns64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 8/23/2013 2:55:38 AM GMT your computer crashed
crash dump file: C:\windows\minidump\082213-28938-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x622CE)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001A622CE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Tue 8/20/2013 3:33:22 AM GMT your computer crashed
crash dump file: C:\windows\minidump\081913-23368-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x622CE)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001A622CE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Sun 8/18/2013 7:56:18 AM GMT your computer crashed
crash dump file: C:\windows\minidump\081813-20233-01.dmp
This was probably caused by the following module: netwsw00.sys (NETwsw00+0x20D4FC)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001A622CE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\netwsw00.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwsw00.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 8/14/2013 8:33:38 PM GMT your computer crashed
crash dump file: C:\windows\minidump\081413-44273-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x622CE)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001C622CE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Sun 8/11/2013 9:06:50 PM GMT your computer crashed
crash dump file: C:\windows\minidump\081113-25755-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6420E)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001A6420E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Sun 8/11/2013 9:00:36 PM GMT your computer crashed
crash dump file: C:\windows\minidump\081113-36270-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x237B86)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001C6420E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows 8®
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 8/10/2013 12:49:56 AM GMT your computer crashed
crash dump file: C:\windows\minidump\080913-32666-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6420E)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001C6420E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Fri 8/9/2013 6:16:50 PM GMT your computer crashed
crash dump file: C:\windows\minidump\080913-25615-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6420E)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001C6420E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Sat 8/3/2013 6:54:54 AM GMT your computer crashed
crash dump file: C:\windows\minidump\080313-21465-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6420E)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001C6420E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Fri 7/26/2013 5:56:35 PM GMT your computer crashed
crash dump file: C:\windows\minidump\072613-18688-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6420E)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001A6420E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Wed 7/24/2013 7:00:38 PM GMT your computer crashed
crash dump file: C:\windows\minidump\072413-18330-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6420E)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001A6420E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Tue 7/23/2013 5:08:45 PM GMT your computer crashed
crash dump file: C:\windows\minidump\072313-19281-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6420E)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001A6420E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.



On Mon 7/15/2013 3:45:31 AM GMT your computer crashed
crash dump file: C:\windows\minidump\071413-25443-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6420E)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001C6420E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.
  • 0

#4
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,818 posts
:welcome: WilliamV

Apologies for the delay in you receiving a reply, this can sometimes happen on such a busy forum.

The NIC (wireless adapter) is shown to be the cause of the crashes, have you tried reverting the drivers for the device back to a version before the issue started, save the downloaded drivers to your desktop, create a system restore point, uninstall the present drivers - run Driver Sweeper and then install the drivers that you saved to your desktop

If no joy;

Please Run the PCPitstop.com OverDrive Full Tests

Here's how:

You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.

Go to: http://www.pcpitstop...pit/default.asp
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)

Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.

The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.

Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.

After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.

While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.

Thanks to rshaffer61 for the PCPitstop information :thumbsup:

NB: An example of the url that we require and the information that it leads to http://www.pcpitstop.com/betapit/sec.asp?conid=25271813
  • 0

#5
WilliamV

WilliamV

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
Thanks for the reply.

For the first method I know what needs to be done but the process is what i will need help on. I consider my self being able go know my way around a computer but for this i might need a step by step guide so I wont mess up more my laptop. I would be grateful if you could help me trough the process.

Here is the link for the overdrive test: http://pcpitstop.com...?conid=25410751
  • 0

#6
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,818 posts
You have four network adapters installed and enabled on the notebook so we must first establish which one you are actually using so that you can then disable the three that you are not using + uninstall the drivers and hopefully alleviate the crashes;

What is the brand and model name or number of the notebook please.

The network devices that you presently have installed/enabled;

Net Microsoft Microsoft Virtual WiFi Miniport Adapter #2
Net Microsoft Microsoft Virtual WiFi Miniport Adapter
Net Realtek Realtek PCIe GBE Family Controller
Net Intel Corporation Intel® Centrino® Advanced-N 6235


You are welcome BTW :thumbsup:
  • 1

#7
WilliamV

WilliamV

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
The laptop is a Samsung Series 7 Chronos
  • 0

#8
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,818 posts
Is itThis
  • 0

#9
WilliamV

WilliamV

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
Yes, but with Windows 7
  • 0

#10
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,818 posts
The 3 entries that I have highlighted below (one a duplicate) are not even listed on the driver download list, has your network card been replaced, if not follow the steps below;

Create a restore point, leave the Intel Corporation Intel® Centrino® Advanced-N 6235 enabled then do the following

Net Microsoft Microsoft Virtual WiFi Miniport Adapter #2 Uninstall both the device and the drivers for this.
Net Microsoft Microsoft Virtual WiFi Miniport Adapter Disable the device and uninstall the drivers for this.
Net Realtek Realtek PCIe GBE Family Controller Disable the device and uninstall the drivers for this.

Restart the notebook and see how it goes.
  • 1

Advertisements


#11
WilliamV

WilliamV

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
Ok.. i went to system properties and made a system restore point from there.

When a went to device manager, I disabled all the drivers and uninstalled them, but as i was going to uninstalled the Realtek..family controller i forgot to click a box that said uninstall software from it. But as I was restarting an error message puped up but i couldnt read it before it restarted. As i logged on a small window pop-up came on and said it was installing something. I checked Device Manager and all the drivers were there.

The second time i did the same but clicked the little box before uninstalling the Net Realtek... and the error came up again. But when logging in the only driver that uninstalled was the family controller one.
  • 0

#12
WilliamV

WilliamV

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
I also noticed that in Device Manager under Other Programs there is Ethernet Controller and it says in the properties:

The drivers for this device are not installed. (Code 28)

There is no driver selected for the device information set or element.

To find a driver for this device, click Update Driver.


Should I be concerned?
  • 0

#13
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,818 posts
Can I just confirm that you followed the exact steps below;

Net Microsoft Microsoft Virtual WiFi Miniport Adapter #2 Uninstall both the device and the drivers for this.
Net Microsoft Microsoft Virtual WiFi Miniport Adapter Disable the device and uninstall the drivers for this.
Net Realtek Realtek PCIe GBE Family Controller Disable the device and uninstall the drivers for this.


Unless you use the Ethernet connection you do not need the drivers installed or the device enabled.

Tip;

If you have something to add while waiting for a reply use the edit tab – bottom right of the dialogue input box and this will ensure that no information that you provide is overlooked (this can happen if your topic has more than one page) thank you for understanding.


  • 0

#14
WilliamV

WilliamV

    Member

  • Topic Starter
  • Member
  • PipPip
  • 16 posts
To be sure when you say Uninstall both the device and the drivers for this it means from Device Manager , right click, then click uninstall . (will this uninstall the device and driver)

I think i am confuse, I know you disable the device on device manager, but where to you uninstall the driver from? from the same place in Device Manager?
  • 0

#15
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,818 posts
Net Microsoft Microsoft Virtual WiFi Miniport Adapter #2 Choose uninstall for this duplication.

Initially only disable the following two and ensure that you still have access to the internet please.
Net Microsoft Microsoft Virtual WiFi Miniport Adapter
Net Realtek Realtek PCIe GBE Family Controller
  • 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