• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2352
  • Last Modified:

TCPIP.SYS blue screen

Hi.

Everytime i'm trying to access my shared folder i get a BSOD.

'View workgroop computers' ---> MsHome ---> MyPcName ---> SharedDocs ''Double Click'' ----> BSOD (TCPIP.SYS)

This Doesnt happen when i click on a shared Printer.

How can i fix that?
0
CodedK
Asked:
CodedK
1 Solution
 
MereteCommented:
that is because there is an incorrect user name.
Try this  r/click my computer properties computer name
rename it to like your name CodedK  make sure you have the same Mshome in the other computers
reboot all the computers if posible or just yours.
in the tcp/ip you must have a unique number if you are not using obtain an ip address auto then your ip adress should be 192.168.1.?? you fill in but must be different from everyone else.
Check in control panel administrative tools event viewer applications, look at the error and note its event id number specifics please post that back here


0
 
MereteCommented:
Completely unistall your network card drivers, restart and reinstall .
Your network card maybe in trouble.If possible try another.
I would start investigating memory or CPU overheating, then HDD failure.

0
 
CodedKAuthor Commented:
Hi Merete :)

i've allready uninstalled and reinstalled network card.
I reinstalled the original mobo drivers.
I've renamed computer name.
Currently there are no computers attached to work with.
I use obtain ip automatically.
(No joy)

Event Viewer:
The computer has rebooted from a bugcheck.  
The bugcheck was: 0x100000d1 (0x0200000c, 0x00000002, 0x00000000, 0xeb57c987).

I'll create another bsod now to recheck the event viewer and repost...
Thanks for your help.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
CodedKAuthor Commented:
Again the same....
The computer has rebooted from a bugcheck.  
The bugcheck was: 0x100000d1 (0x0200000c, 0x00000002, 0x00000000, 0xeb961987).
0
 
MereteCommented:
it's late for me will post back tomorrow.
view your Error Log via:

[1] Start Menu
[2] Help and Support
[3] Pick a Task
[4] Tools
[5] Advanced System Information
[6] View the Error Log
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Possible solution - BIOS Update (reference http://www.mcse.ms/archive61-2004-11-985500.html )

Try newer - or older - drivers for the network card

If none of that works, try looking for minidumps in C:\Windows\Minidump and post a few on ee-stuff - http://www.ee-stuff.com/

Then we can analyze them.
0
 
cpc2004Commented:
The crash may be caused by faulty ram or device driver error (ie video, sound card, modem and etc). The system event log and the minidump has the most useful diagnostic information. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \windows\minidump. Check system event 1001 and 1003 and it has the detail of the blue screen.

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......

Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here

Zip 5 to 6 minidumps to a zip file and attach it at any webspace. I will study the dump and find out the culprit. If you can't provide the minidumps, run memtest to stress test the ram. Make sure that your windows is not infected with spyware, adware adn chkdsk /r.
http://www.memtest86.com/.

Get public webspace
Use a free service like rapidshare to attach the minidumps and post the url of the mimidumps at this thread.
http://www.rapidshare.de/
0
 
CodedKAuthor Commented:
The computer has rebooted from a bugcheck.  
The bugcheck was: 0x100000d1 (0x0200000c, 0x00000002, 0x00000000, 0xeba59987).
A dump was saved in: C:\WINDOWS\Minidump\Mini052506-03.dmp.


http://www.geocities.com/kalatz_gr_fisher/TheFiles/mini.zip
0
 
MereteCommented:
:) guys you saved me some work thanks, as I had to work else where. Cheers Merete
0
 
CodedKAuthor Commented:
Cpc2004 its not ram.
I'm sure coz the bluescreen appears only when i open the shared folder.
To be more sure i checked it :)
Spyware, adaware free.
Allready flashed bios.
Uninstalled network adapter and installed all drivers.

When i sent the event to microsoft, the reply was (A device driver blablabla...) but after some
time it replied that its the video card.

Now... I've got my card to the shop to be replaced almost 2 weeks now because it had some problems.
The problem with BSOD appeared before 1 month or more. I have 2 spare cards to work with.
BSOD appears with both cards.

THE strange thing:
I can access my share folder from:

'My computer'--->'Shared documents'
and
'My computer'--->'Network places'--->'SharedDocs on 64 (Pc64)'

but when i try:
'My computer'--->'Network places'--->'View workgroop computers'--->64(PC64)--->'SharedDocs
I get the bsod.


Looking at the errors in system event viewer (22/05/2006),
i saw something strange that merete allrteady mentioned above...
The error (error code:2505) was:
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
The server could not bind to the transport \Device\NwlnkIpx
because another computer on the network has the same name.  The server could not start.
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
The server could not bind to the transport \Device\NwlnkNb
because another computer on the network has the same name.  The server could not start.
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Merete mentioned something about changing the name. I've done that.

7 minidumps uploaded here:
http://www.geocities.com/kalatz_gr_fisher/TheFiles/7minis.zip

0
 
MereteCommented:
'My computer'--->'Network places'--->'View workgroop computers'--->64(PC64)--->'SharedDocs
I get the bsod.
I have had this same problem one of my spare computers would reboot when I attempted to access the shared folder.
My problem was as i owned both computers the computer named became confused somehow even though they had different names, however teh regestration name was the same.
So what I did was, on the spare>> r/click the computer/properties/computer name. Now here you have two panels to select from,
 computer description and Full computer Name
I changed the Full computer  then put all the computers to MSHOME.
No more rebooting.
Putting them all in MSHOME instead of WORKGROUP helped. Workgroup actually is not a name.
Is this the actual name of your computer>>64(PC64) It may not apprecaite this name. Try using a simple one word name. No brackets or repeating any numbers. Just  PC64

Also I have found that in the c drive documents and settings All Users, there is a folder actually called shared documents, but it is not shared, and everytime I have had to manually full share it.

Faulty video card??
Event Source: System Error
Event Category: (102)
Event ID: 1003

 make sure that you have the latest certified nVidia driver for Windows XP installed. You can get it from
http://www.nvidia.com/content/drivers/drivers.asp

 If that fails to solve the problem use a generic card, or boot the computer to advanced options choose start in vga mode then unstall the driver and update it with the new installed.
reboot.

You could also test the display using the directx.
.It will inform you if the drivers are wrong or what problems if any with the card and xp what version of directx you have.
At start /run /type in dxdiag press enter
Check this site out same error
http://www.duxcw.com/dcforum/DCForumID7/727.html

0
 
CodedKAuthor Commented:
Hi Merete.
I changed the name.
There are no computers connected at the moment with this computer.
What ever computer i connect i get the bsod when i open my sharedocs.
I am in Mshome.

>>make sure that you have the latest certified nVidia driver for Windows XP installed
For the spare cards i use at the moment there are no XP drivers :(
(2 old Tnt available) but the problem was there even with my good card.
No problems detected with DxDiag. (During checking the screen went black for a moment)
I've disabled hardware acceleration (to the minimum).
Main driver for the card : vga.dll (Generic)
Direct3d Acceleration : Not available.
AGP Texture Acceleration : Not available.

Device : Nothing recognized.
DirectX ver : 9.0c (last)
DirectX files : No problems.

PS:
(Stand by) ability is gone !
But i guess this is because the card isnt recogized. (...E.E PAQ)
0
 
MereteCommented:
I'll have to give this some thinking. Scan the old grey cells for inspiration.
What ever computer i connect i get the bsod when i open > my sharedocs.<
 One thing we have not tried,
Create a new account for yourself.

For the spare cards i use at the moment there are no XP drivers :( <---could be as this not compatible card.
Are you using wireless anywhere?

Blue Screen of Death
http://en.wikipedia.org/wiki/Blue_screen_of_death

0
 
CodedKAuthor Commented:
Sorry for not posting.
The same thing happens when i got in from another admin account.
No wireless.
0
 
MereteCommented:
Hello CodedK how are you,
this is what I would do, unpower fully, open the side case and unscrew the network card and take it out.
Now boot with out it, see if the BSOD goes.
leave it out for a day use teh machine solo.

Sometimes taking out the card put it back can fix it.. make sure you are using the correct cross over cable.

Look in system  tools system information problem devices.

Understanding BSOD
The blue screen of death (BSOD), is the informal name given by users to the Windows general protection fault (GPF) error.
How to fix a general protection fault:
http://www.computerhope.com/issues/ch000224.htm


0
 
MereteCommented:
0
 
CodedKAuthor Commented:
Hi Merete. Thank you for your help :)

Unfortunately the card is onboard  :/
I've flashed the Bios several times. I've tried the drivers that comes with mobo cd and new drivers also.

I'll check the links you gave me.
0
 
CodedKAuthor Commented:
Well thats strange...
I was looking at your links ... in the 1st picture :
http://my.resnet.uww.edu/configure_xp.php

I saw that the connection in the picture uses only :
Client for Microsoft Networks
File and Printer Sharing
Internet Protocol (TCP/IP)
~-~-~-~-~-~-~-~-~-~-~-~-~-
I was using:
Client for Microsoft Networks
File and Printer Sharing
QoS Packet Sheduler
NWlink NetBios
NWLink IPX/SPX/NetBios Compatible Transport Protocol
Network monitor driver
Internet Protocol (TCP/IP)

So i unchecked the following:
~-~-~-~-~-~-~-~-~-~-~-~-~-
QoS Packet Sheduler
NWlink NetBios
NWLink IPX/SPX/NetBios Compatible Transport Protocol
Network monitor driver
~-~-~-~-~-~-~-~-~-~-~-~-~-
I rebooted... Now in my "Network Places" appeared 2 folders with same name:
SharedDocs on Pc64 (Pc64c) i deleted the one and i got in... ONCE.
When i tried again the BSOD appeared.
The strange thing is that i changed the name ... and the old name was there.... Pc64 !

I Changed the name again... rebooted... and now it works !

So the solution ... i guess... was to change the name as you said Merete, right from the beggining.
:) THANKS :) :)
0
 
MereteCommented:
awe windowsxp don't you just luv it , xp is really simple HA!
 I think it is highly likely you had a computer name created twice, unfortunately the 2nd consurance would be hidden, that is until you rename it. I had the same problem with spare computer sits here beside me, and I could not for the life of me understand why I BSOD when accessing its shared folders, I need this pc to do my work..I eventually tracked it down to one small fact, both are regestered in my name of course. So I changed the name of the computer presto worked..

cool cool.
:)
Have a great day..
Merete
0
 
CodedKAuthor Commented:
You too :) Thanks.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now