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 D1 Blue Screen Crash (Minidump included)


  • Please log in to reply

#1
MusicFabian

MusicFabian

    New Member

  • Member
  • Pip
  • 4 posts
Hello,

I recently began getting these crashes regarding the tcpip.sys file. I've lost quite a bit of data and the crashes are incessant. They happen at randomized times as well. The attached minidump is from the latest crash, although I have previous ones as well. I would really like to understand what is causing the crash, and how (if possible) to fix it. I greatly appreciate anyone's support.

Thanks
  • 0

Advertisements


#2
MusicFabian

MusicFabian

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
I can't seem to find if the minidump was included or not, so I'm trying again.

Attached Files


Edited by MusicFabian, 03 October 2011 - 02:54 PM.

  • 0

#3
SRX660

SRX660

    motto - Just get-er-done

  • Technician
  • 4,345 posts
There are 2 hot fixes that may fix your problem. They can be hit or miss on all computers.

http://support.microsoft.com/kb/977067
or
http://support.microsoft.com/kb/976527

The first one is for 0x000000D1 errors. try this one

The second one is for 0x00000050 errors.

All your errors were TCPIP D1 errors.

SRX660
  • 0

#4
MusicFabian

MusicFabian

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Hello, thanks for the response!

I downloaded both hotfixes, in the order you recommended, but while initiating the install, they both stated they were not applicable on my computer. So unfortunately, neither fixed it.

Are there any other possible suggestions?
  • 0

#5
SRX660

SRX660

    motto - Just get-er-done

  • Technician
  • 4,345 posts
Please run this software and copy and paste the results here.

http://www.resplendence.com/whocrashed

Whocrashed will tell you what you need to update on your computer.

SRX660
  • 0

#6
MusicFabian

MusicFabian

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Thanks, I downloaded the program and ran it. Here are the results, I am currently searching myself, but any help would be much appreciated

begin dump:

System Information (local)
--------------------------------------------------------------------------------

computer name: ZETA-KATZE
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 Duo CPU P7350 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4260319232 total
VM: 2147352576, free: 1945489408



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 10/3/2011 8:31:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100311-38111-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000011.sys (Unloaded_Unknown_Module_00000000`00000011+0xFFFFFFDC)
Bugcheck code: 0xD1 (0xFFFFFA800C374000, 0x2, 0x0, 0xFFFFF88001907B07)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: unknown_module_00000000`00000011.sys .
Google query: unknown_module_00000000`00000011.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Sun 10/2/2011 2:31:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100111-36972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA800ADD4000, 0x2, 0x0, 0xFFFFF880018EEB07)
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 Sat 10/1/2011 2:12:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093011-36629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA8009641000, 0x2, 0x0, 0xFFFFF8800192CB07)
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 9/27/2011 3:50:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092611-24632-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA800B648000, 0x2, 0x0, 0xFFFFF8800193AB07)
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 9/27/2011 2:39:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092611-25802-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA800BAF0000, 0x2, 0x0, 0xFFFFF880018FAB07)
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 Mon 9/26/2011 8:39:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092611-28017-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA8009F80000, 0x2, 0x0, 0xFFFFF880018C7B07)
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 Mon 9/26/2011 7:52:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092611-37596-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA8009DEF000, 0x2, 0x0, 0xFFFFF880018F1B07)
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 Mon 9/26/2011 12:53:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092511-37487-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA800997A000, 0x2, 0x0, 0xFFFFF88001967B07)
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 9/25/2011 4:24:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-40809-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA800BA0C000, 0x2, 0x0, 0xFFFFF88001957B07)
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 Sat 9/24/2011 7:35:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-37081-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA8009AD1000, 0x2, 0x0, 0xFFFFF880018C3B07)
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 Sat 9/24/2011 6:20:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092311-39842-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA8009C42000, 0x2, 0x0, 0xFFFFF88001881B07)
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 9/23/2011 12:09:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092211-23337-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA8009A7D000, 0x2, 0x0, 0xFFFFF880018F7B07)
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 9/22/2011 10:58:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092211-23977-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA80099AF000, 0x2, 0x0, 0xFFFFF880018ECB07)
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 9/22/2011 6:31:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092111-28735-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA800B18C000, 0x2, 0x0, 0xFFFFF88001903B07)
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 Wed 9/21/2011 11:41:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092111-25786-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFA800AACC000, 0x2, 0x0, 0xFFFFF880018ABB07)
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
--------------------------------------------------------------------------------

19 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

unknown_module_00000000`00000011.sys

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.
  • 0

#7
Paul Jason

Paul Jason

    New Member

  • Member
  • Pip
  • 1 posts
Re: BSOD CRASH DUMP ERROR

If you can start Windows,System Restore is the easiest thing to try first. It can undo recent changes to your computer's system files that might have caused the problem. System Restore doesn't affect your personal files, such as e‑mail, documents, or photos.

More information: http://www.techyv.co...error-windows-7
  • 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