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 w/ DRIVER_IRQL_NOT_LESS_OR_EQUAL tcpip.sys


  • Please log in to reply

#1
Digi_Lutea

Digi_Lutea

    Member

  • Member
  • PipPip
  • 11 posts
My Dell Inspiron 1545 has recently been BOSD'ing since Friday night. I haven't had any issues with BSOD's before but this is very annoying and I've lost all my patience with it. I managed to get some logs. I'm not all that tech savy but this is probably the worse that i've experienced with this laptop so far.

I thought it was caused by a USB hub that i bought the same night but after unplugging it overnight, the BSOD's continues. I turned off my internet for 3 hrs and no BSOD. I rebooted my computer and turned it back on, less than 15 mins later it BSOD.

I have a Dell Inspiron 1545, 4gb of ram, Pentium Dual Core CPU 2.20ghz running Windows 7 Home premium and I use Avast! antivirus if that helps with anything.

The laptop itself is about 3 yrs old, the hard drive is 2 yrs old. The orginial one that came with the system failed back in 2011.

WhoCrashed and BlueScreenView info is below. If there is anything else needed let me know and I can see if i can grab it.

Hopefully I'll get the answers I'm looking for and hope this is fixable >.<

==================================================
Dump File         : 122913-18969-01.dmp
Crash Time        : 12/29/2013 12:44:51 AM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`0000001c
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`0188a65e
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122913-18969-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,144
Dump File Time    : 12/29/2013 12:45:43 AM
==================================================

==================================================
Dump File         : 122913-17378-01.dmp
Crash Time        : 12/29/2013 12:20:57 AM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`0000001c
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`0195b65e
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122913-17378-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,144
Dump File Time    : 12/29/2013 12:21:52 AM
==================================================

==================================================
Dump File         : 122813-24242-01.dmp
Crash Time        : 12/28/2013 11:56:07 PM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`0000001c
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`018d765e
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122813-24242-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,144
Dump File Time    : 12/28/2013 11:57:28 PM
==================================================

==================================================
Dump File         : 122813-24757-01.dmp
Crash Time        : 12/28/2013 10:49:00 PM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`0000001c
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`0187665e
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122813-24757-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,144
Dump File Time    : 12/28/2013 10:53:34 PM
==================================================

==================================================
Dump File         : 122813-26145-01.dmp
Crash Time        : 12/28/2013 5:27:55 PM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`0000001c
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`0193f65e
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122813-26145-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,144
Dump File Time    : 12/28/2013 5:33:57 PM
==================================================

==================================================
Dump File         : 122813-20607-01.dmp
Crash Time        : 12/28/2013 2:41:52 AM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`0000001c
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`0187c65e
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122813-20607-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,144
Dump File Time    : 12/28/2013 2:42:43 AM
==================================================

==================================================
Dump File         : 122713-19234-01.dmp
Crash Time        : 12/27/2013 11:39:19 PM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`0000001c
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`0190f65e
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122713-19234-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,144
Dump File Time    : 12/27/2013 11:40:10 PM
==================================================

==================================================
Dump File         : 122713-19047-01.dmp
Crash Time        : 12/27/2013 10:16:37 PM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`0000001c
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`0189d65e
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122713-19047-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,144
Dump File Time    : 12/27/2013 10:17:26 PM
==================================================

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

computer name: MAE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Inspiron 1545 , Dell Inc., 0G848F
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4400 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4253405184 total
VM: 2147352576, free: 1952407552




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 12/29/2013 3:49:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122813-24757-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6365E) 
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF8800187665E)
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 12/29/2013 3:49:00 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6365E) 
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF8800187665E)
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 12/28/2013 10:27:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122813-26145-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6365E) 
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF8800193F65E)
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 12/28/2013 7:41:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122813-20607-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6365E) 
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF8800187C65E)
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 12/28/2013 4:39:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122713-19234-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6365E) 
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF8800190F65E)
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 12/28/2013 3:16:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122713-19047-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6365E) 
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF8800189D65E)
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

Advertisements


#2
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 24,039 posts
:welcome: Digi_Lutea

Try doing the following from the command prompt;

1.To open a command prompt, click Start and then type CMD in the Search programs and files.
2.Right-click CMD.exe icon in Programs and choose Run as administrator.
3.When the User Account Control box pop up, click Yes.
4.At the command prompt, copy and paste (or type) the following command and then press ENTER:

netsh int ip reset c:\resetlog.txt

Note If you do not want to specify a directory path for the log file, use the following command:

netsh int ip reset resetlog.txt

5.Reboot the computer.

Let us know how it goes.

Instructions courtesy of MS.
  • 0

#3
Digi_Lutea

Digi_Lutea

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
Thanks for the reply!

I typed the command out and rebooted, I'm going to leave my laptop on for a few hrs and see if it does anything. I'll come straight back as soon as I run to any problems. ^^
  • 0

#4
Digi_Lutea

Digi_Lutea

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
Whoop, seems it crashed just like I thought it would. Same error as before.

==================================================
Dump File         : 122913-16348-01.dmp
Crash Time        : 12/29/2013 5:15:16 PM
Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x000000d1
Parameter 1       : 00000000`0000001c
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff880`018e165e
Caused By Driver  : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\122913-16348-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 277,144
Dump File Time    : 12/29/2013 5:23:28 PM
==================================================


  • 0

#5
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 24,039 posts
Do the following for us please;

1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"

2. Run the Driver Verifier -
Go to START | type verifier | make these selections -

1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -▪ Special Pool
▪ Pool Tracking
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8)
▪ Miscellaneous Checks4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
8. Re-boot*** IMPORTANT - PLEASE READ:

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

- After re-start, you may not be able to log on to normal Windows
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1

- For Driver Verifier status
--- select last option, 1st screen -or-
--- type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.
  • 0

#6
Digi_Lutea

Digi_Lutea

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
Ran the DV and it did run into a violation, i'll turn everything back on and leave my system running for a few mins. Shouldn't take too long for it to crash again, if it does.

Will report back if i run into any problems.
  • 0

#7
Digi_Lutea

Digi_Lutea

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
i just realized something too when i had got the bsod after i did the DV. I don't have the file but i had wrote it down

BAD_POOL_CALLER

STOP 0xC2

Smartdefragdriver.sys

is that anything I should be worried about btw?
  • 0

#8
Digi_Lutea

Digi_Lutea

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
I followed the DV steps and it had crashed about 4 hrs of waiting. I rebooted and see no minidmp that was mentioned in the instructions. I must've done something wrong. >.<

Edit 12/30/13 5:54pm I uninstalled smartdefrag, ran the DV now I'm waiting for another crash to happen. I'll provide the log when I can get it

Edited by Digi_Lutea, 30 December 2013 - 05:03 PM.

  • 0

#9
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 24,039 posts
Do you by chance have Iobit software on your computer and one in particular called smartdefrag - if yes please uninstall it and then run Chkdsk /r

Go to Start and then to Search
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y

If the window doesn't shutdown on its own then reboot the system manually.
On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for an hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will hopefully boot the system back into Windows.

While chkdsk / r is running please read miekiemoes blog regarding so called optimizer/wonder programs provided by companies such as Iobit, see here

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

#10
Digi_Lutea

Digi_Lutea

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
Ran Driver Verifier for 4+ hrs and it finally crashed, but its not creating the dump files. It says that it is and it just freezes. I left it alone for a few more hrs and it still didn't create them.
  • 0

#11
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 24,039 posts
The fact that no dumpfile was available when you ran DV the first time was why I asked you to run Chkdsk /r .
Have you run Chkdsk /r .

BTW have you searched for c:\windows\minidump
  • 0

#12
Digi_Lutea

Digi_Lutea

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts

The fact that no dumpfile was available when you ran DV the first time was why I asked you to run Chkdsk /r .
Have you run Chkdsk /r .

BTW have you searched for c:\windows\minidump


I had ran chkdsk /r after uninstalling Smartdefrag, I turned off DV and ran chkdsk /r one more time and I'm currently running DV again as I have for the past 4+ hrs. Gonna let my computer idle and hope it generates a log this time.
  • 0

#13
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 24,039 posts
:thumbsup:
  • 0

#14
Digi_Lutea

Digi_Lutea

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
Its been 2 days so far and I haven't had any BSOD so far, I went ahead and turned off DV so I could get some work done and I'm currently not having any problems. I have no clue what would've caused it but I'm glad to have my laptop back in working order.

I've noticed that pages are FINALLY loading properly. Before I've had issues with webpages just not loading correctly and it took about 5-8 refreshes to get it to work, and it wasn't my internet because nobody else in my household wasn't having this issue. So I guess it was just something screwing with my network card maybe? I've had that issue for over 3 months, glad to see its fixed.

Nevertheless, thank you so much and happy new year ^^

If I happen to have any more issues I'll be sure to come back here for support.
  • 0

#15
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 24,039 posts
Happy New Year Digi_Lutea :)

Thanks for the update and yes please come here if the issue returns :thumbsup:
  • 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