tcpip.sys Crash

[ChudaPati09]

My computer just randomly crashes.
I can't really read everything, cause the computer would just turn off before I could read everything.

But I did get this,
It had to do something with tcpip.sys
And I think it said Memory Dump.

This hasn't happened to me since I installed Windows 7.

I'm using Build 7068

 

[baarod]

Hold down the Windows key, press Pause. Click Advanced system settings, then Settings under Startup and recovery. You should see this:
View attachment 7216
Uncheck Automatically restart.
Next time it happens write down everything exactly as it's shown on the blue screen and post it here and I will try to fix it for you.

 

[ChudaPati09]

Hold down the Windows key, press Pause. Click Advanced system settings, then Settings under Startup and recovery. You should see this:
View attachment 7216
Uncheck Automatically restart.
Next time it happens write down everything exactly as it's shown on the blue screen and post it here and I will try to fix it for you.

Thanks,

I will post it when it happens again.

Just out of curiosity, what is this called, Is it called blue screen of death.

 

[baarod]

Thanks,

I will post it when it happens again.

Just out of curiosity, what is this called, Is it called blue screen of death.

Well, it's certainly not the pink screen of happiness.

Official terminology is a BUGCHECK but people have called it the "BSoD" or "Blue Screen of Death". Mostly folks blame Windows when 99% of the time it's some hardware vendor hiring substandard developers to code their device drivers.

 

[ChudaPati09]

oh ok,

Ya so today morning around 10ish it happened again.
I wrote it down and this is what it said.
Hope it helps.
Thanks for your help

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

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 yuour hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or sofware. 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, 0x88EA42A7)

*** tcpip.sys - Address 88E42A7 base at 88E1C000, DateStamp 49c57dd0

Collecting data for crash dump ...
Initializing disk for crash dump ...

 

[baarod]

oh ok,

Ya so today morning around 10ish it happened again.
I wrote it down and this is what it said.
Hope it helps.
Thanks for your help

Update your network adapter driver to fix this. What network hardware are you using? Ethernet or WiFi? Make and model please...

 

[ChudaPati09]

Umm,

I'm using Wireless,
I don't know what model.
But the laptop is a Lenovo Y510.
I looked in Device Manager, I think this might be the model I'm not sure
Intel(R) PRO/Wireless 3945ABG Network Connection

 

[baarod]

Use the download link below to get the latest driver-only update for your hardware. There were several tcpip.sys crashes noted during a search of online errata.

Confirm Download

 

[ChudaPati09]

Ok thanks,
I will report back in 2 - 3 days on how well the new driver did.
Thanks

 

[ChudaPati09]

Ok,

So The computer was fine for the last couple days,
I didn't know if i installed the driver right.
So I uninstalled it and then reinstalled it using, iProDifX.exe. I ran it under "Run As Administrator".

It was alrite till I connected to my wireless router.
After I type in my password, it will try to identify it. but then it crashed.

*** tcpip.sys - Address 88EC02A7 base at 88E38000, DateStamp 49c57dd0

Thats the error message I got.

Then I had a backup of the driver and I installed that and same thing after entering password and trying to identify it. Computer will crash.

This is what I got that time.
*** tcpip.sys - Address 890B02A7 base at 89028000, DateStamp 49c57dd0

Then I had an external wireless card, that connected via USB.
I installed the drivers and same thing happened.
But I got a different error message.

*** tcpip.sys - Address 88EBE2A7 base at 88E36000, DateStamp 49c57dd0

Now this time I went and disabled the Intel Wireless driver, through Device Manager, and connected my external wireless card and now I'm back on.

So I don't know what happened, but it's not working.
Well my internal Wireless Card.

 

[ChudaPati09]

Alrite this is just getting really werid.

Now the computer just randomly crashes.
***STOP: 0x000000D1 (0x00000000, 0x00000002, 0x00000008, 0x00000001)

This is all I got.
Nothing else.

I was connected using my external Wireless Card when this happened.

 

[itaish100]

shut down unexpectedly BSOD

I have a similiar problem also with the BSOD also identified as related to tcpip.sys and an address given (FFFFF88001636028)
I would really appreciate any help that will help me stop this random blue screen

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1037

Extra information about the problem
BCCode: 116
BCP1: FFFFFA8005818160
BCP2: FFFFF8800F181CF8
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Bucket ID: X64_0x116_TdrBCR:2_Tdr:2_IMAGE_nvlddmkm.sys
Server information: 0e40bb1e-fe99-45ff-8778-a9c04995cc67

thanks, ITAI

 

[ChudaPati09]

I have a similiar problem also with the BSOD also identified as related to tcpip.sys and an address given (FFFFF88001636028)
I would really appreciate any help that will help me stop this random blue screen

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1037

Extra information about the problem
BCCode: 116
BCP1: FFFFFA8005818160
BCP2: FFFFF8800F181CF8
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Bucket ID: X64_0x116_TdrBCR:2_Tdr:2_IMAGE_nvlddmkm.sys
Server information: 0e40bb1e-fe99-45ff-8778-a9c04995cc67

thanks, ITAI

I don't know what I did, but it just stopped crashing. Have you installed an updated driver? If not, here is the latest driver for Windows 7 64-bit.

This driver is for the following products:
-Intel® PRO/Wireless 3945ABG Network Connection
-Intel® Wireless WiFi Link 4965AGN
-Intel® WiMAX/WiFi Link 5350

I found this driver from here.

 

[Tob1as89]

HElp

help me!

 

[kelz]

Recently I had a customer machine with the same issue. Fought to remove CA from the system thinking it might be an issue as it usually is. Did not fix the problem. Created a temp user account and the problem was gone. Transferred all the user data into the new account and deleted the old account with the BSOD TCPIP.sys issue.

 

[Corpsecrank]

Recently I had a customer machine with the same issue. Fought to remove CA from the system thinking it might be an issue as it usually is. Did not fix the problem. Created a temp user account and the problem was gone. Transferred all the user data into the new account and deleted the old account with the BSOD TCPIP.sys issue.

That's kind of a harsh work around though. I guess it saves reloading windows though.

I just had a crash myself. I have had many lately since reloading windows. Some were from the ati drivers but those were solved the latest was from tcp/ip and was caused by a buffer overrun.

My error had a stop line in it 0x000000F7

That is probably the most significant piece of information I found because checking the event viewer confirmed everything. This particular stop is made to prevent the system from being compromised.

Read:

Cause A driver overran a stack-based buffer (or local variable) in a way that would have overwritten the function's return address and jumped back to an arbitrary address when the function returned.
This is the classic "buffer overrun" hacking attack. The system has been brought down to prevent a malicious user from gaining complete control of it.

Resolution Use the kb (Display Stack Backtrace) command to get a stack trace.
The last routine on the stack before the buffer overrun handlers and bug check call is the one that overran its local variable.




My suggestion would be to look for malware on the system because this is apparently either malicious software or an older remote attack on the system. Sure it could be something else but those are some of the most likely causes.


I know this topic is old but it felt relevant enough to post the information I found since I just had this issue tonight and came across this thread in my hunt for a solution. Looks like i will be hunting malware now instead