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.
Last edited by ChudaPati09; 09 Apr 2009 at 23:58. Reason: Spelling
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.
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
Quote