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

tcpip.sys error


  • Please log in to reply

#1
littlemeow

littlemeow

    New Member

  • Member
  • Pip
  • 2 posts
Hi all,

My laptop has started crashing often recently with blue screens (BSOD) and while waiting for the physical memory dump to be completed, the error states that it has something to do with 'tcpip.sys' I am absolutely clueless as to what is happening to my computer and is extremely desperate to get help for this issue. I would love for someone to please diagnose this and recommend a solution. I have attached the minidump file in this post.

I am using a Dell XPS 17 64 bit Windows 7 Professional.

Thank you very much!

Adeline

Here is the crash analysis:


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 10/23/2011 5:10:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102311-19047-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF880018E3378)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 10/23/2011 5:10:56 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mfenlfk.sys (mfenlfk+0x133E)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF880018E3378)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\mfenlfk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee NDIS Light Filter 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: mfenlfk.sys (McAfee NDIS Light Filter Driver, McAfee, Inc.).
Google query: mfenlfk.sys McAfee, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Fri 10/21/2011 9:53:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102211-22370-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF88001935378)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/20/2011 10:21:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102111-19437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF880018F6378)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/20/2011 10:00:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102111-27050-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF880018B7378)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 10/7/2011 4:12:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100711-18236-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF88001861378)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 10/6/2011 10:34:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100711-20592-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF880018CC378)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 10/4/2011 6:40:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100511-24850-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF880018A4378)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 10/2/2011 8:16:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100211-29936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF88001913378)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



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

9 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

mfenlfk.sys (McAfee NDIS Light Filter Driver, McAfee, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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.

Attached Files


Edited by littlemeow, 23 October 2011 - 12:11 PM.

  • 0

Advertisements


#2
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Welcome to GeekstoGo

Do this first please
http://service.mcafe...033&id=TS100507

Please NOTE - IMPORTANT

1. Uninstall using Programs and Features etc first.
2, Run the uninstaller from the link.
3. Reinstall the latest edition

PLEASE NOTE the special instructions if by chance it is OEM loaded software on the Dell when you bought it.
  • 0

#3
littlemeow

littlemeow

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts
Hello Macboatmaster,

Thank you for your quick reply. I shall uninstall the OEM loaded Macafee and reinstall the lastest version and cross my fingers that it is the only issue causing the blue screen. I am however, still unsure what is ntoskrnl.exe and if it is also contributing to the BSOD. :) Will report back on the situation!
  • 0

#4
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
ntoskrnl is NT - the operating sysytem. of Windows - krnl is kernel.
So we have an error in the kernel of the O/S.
However that is common when there is an error caused by something else and the ntoskrnl error is caused by the other error.
  • 0

#5
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
littlemeow

Will report back on the situation!


That quote from you was some eight days ago.
How is it going please.
  • 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