Windows Vista 64 tcpip.sys BSOD
Started by
afrond
, Aug 28 2011 10:14 AM
#16
Posted 07 September 2011 - 10:48 AM
#17
Posted 07 September 2011 - 11:18 AM
I just had another BSOD, same kind, and SeaTools is reporting errors on the same drive again. I guess the repair didn't help.
Edited by afrond, 07 September 2011 - 11:18 AM.
#18
Posted 07 September 2011 - 11:51 AM
What errors is it reporting?
Also I may have missed your results but did you ever run the memtest program on your memory?
Also I may have missed your results but did you ever run the memtest program on your memory?
#19
Posted 08 September 2011 - 04:55 AM
It was just the short test, it didn't say anything specific. I'll do the longer DOS test again soon.
I did the memory test, forgot to mention, no errors were reported.
There's a new error in the event viewer though:
=========================
Log Name: Application
Source: ESENT
Date: 8.9.2011 3:32:57
Event ID: 508
Task Category: Performance
Level: Warning
Keywords: Classic
User: N/A
Computer: Tietokone-PC
Description:
Windows (3184) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 5545984 (0x000000000054a000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.micro.../events/event">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">508</EventID>
<Level>3</Level>
<Task>7</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-09-08T00:32:57.000Z" />
<EventRecordID>3218</EventRecordID>
<Channel>Application</Channel>
<Computer>Tietokone-PC</Computer>
<Security />
</System>
<EventData>
<Data>Windows</Data>
<Data>3184</Data>
<Data>Windows: </Data>
<Data>C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb</Data>
<Data>5545984 (0x000000000054a000)</Data>
<Data>8192 (0x00002000)</Data>
<Data>62</Data>
</EventData>
</Event>
=========================
I did the memory test, forgot to mention, no errors were reported.
There's a new error in the event viewer though:
=========================
Log Name: Application
Source: ESENT
Date: 8.9.2011 3:32:57
Event ID: 508
Task Category: Performance
Level: Warning
Keywords: Classic
User: N/A
Computer: Tietokone-PC
Description:
Windows (3184) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 5545984 (0x000000000054a000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (62 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="http://schemas.micro.../events/event">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">508</EventID>
<Level>3</Level>
<Task>7</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-09-08T00:32:57.000Z" />
<EventRecordID>3218</EventRecordID>
<Channel>Application</Channel>
<Computer>Tietokone-PC</Computer>
<Security />
</System>
<EventData>
<Data>Windows</Data>
<Data>3184</Data>
<Data>Windows: </Data>
<Data>C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb</Data>
<Data>5545984 (0x000000000054a000)</Data>
<Data>8192 (0x00002000)</Data>
<Data>62</Data>
</EventData>
</Event>
=========================
#20
Posted 08 September 2011 - 07:11 AM
This error only indicates it took longer to write data that it should have and again it points to faulty hardware.
I'm really beginning to suspect the hard drive at this point.
I'm really beginning to suspect the hard drive at this point.
#21
Posted 09 September 2011 - 05:57 AM
I ran the long hd diagnostics again but this time it passed the test, even though it didn't pass the short test before. No idea what happened in between. Anyway it does seem like this is a hardware problem, if the hd errors keep appearing I might return the drive for warranty.
Edit: seems a new kind of error has occurred:
==============
Log Name: Application
Source: System Restore
Date: 9.9.2011 2:04:38
Event ID: 8193
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Tietokone-PC
Description:
Failed to create restore point on volume (Process = H:\DirectX\DXSETUP.exe /silent; Descripton = ôWw; Hr = 0x80070057).
Event Xml:
<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='System Restore'/><EventID Qualifiers='0'>8193</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2011-09-08T23:04:38.000Z'/><EventRecordID>3300</EventRecordID><Channel>Application</Channel><Computer>Tietokone-PC</Computer><Security/></System><EventData><Data>H:\DirectX\DXSETUP.exe /silent</Data><Data>ôWw</Data><Data>0x80070057</Data><Binary>5700078002020000D60100000000000032CA19E58CAF4DCB010000000000000000000000</Binary></EventData></Event>
==============
Edit: seems a new kind of error has occurred:
==============
Log Name: Application
Source: System Restore
Date: 9.9.2011 2:04:38
Event ID: 8193
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Tietokone-PC
Description:
Failed to create restore point on volume (Process = H:\DirectX\DXSETUP.exe /silent; Descripton = ôWw; Hr = 0x80070057).
Event Xml:
<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='System Restore'/><EventID Qualifiers='0'>8193</EventID><Level>2</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2011-09-08T23:04:38.000Z'/><EventRecordID>3300</EventRecordID><Channel>Application</Channel><Computer>Tietokone-PC</Computer><Security/></System><EventData><Data>H:\DirectX\DXSETUP.exe /silent</Data><Data>ôWw</Data><Data>0x80070057</Data><Binary>5700078002020000D60100000000000032CA19E58CAF4DCB010000000000000000000000</Binary></EventData></Event>
==============
Edited by afrond, 09 September 2011 - 05:58 AM.
#22
Posted 09 September 2011 - 07:35 AM
How old is the drive and what brand?
#23
Posted 09 September 2011 - 07:59 AM
It is a 500 GB Seagate Barracuda GT 7200.11, about 2½ years old. I actually had some problems about a year ago with my other drive (identical, but not the one the errors are occuring on now), it didn't spin up at all one day. I found out the serial number was from a faulty batch and sent it to the manufacturer where they updated the firmware and got it working again. The drive I have problems with now was not faulty according to the serial number but I updated its firmware aswell at the time. I checked Seagate's website and it seems it's still the latest update.
Edited by afrond, 09 September 2011 - 08:00 AM.
#24
Posted 09 September 2011 - 08:15 AM
OK I would contact Seagate and first see if the drive is still under warranty.
Second I would either explain to them the issue and tests we have run or supply them a link to this topic.
We could try a couple other steps to make sure if it is the OS itself.
Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.
Second I would either explain to them the issue and tests we have run or supply them a link to this topic.
We could try a couple other steps to make sure if it is the OS itself.
Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.
#25
Posted 19 September 2011 - 05:47 PM
Hi, been out of town for a couple weeks so it took a while to reply. I ran SFC but it didn't find any corrupt files. I already checked the warranty info before, it expires in 2013 so no hurry there. I will get in touch with Seagate pretty soon if no other cure can be found for this problem.
#26
Posted 19 September 2011 - 05:57 PM
OK I would follow the steps to replace the drive then. If there is any data you wish to save this would be the time to guarantee it is backed up before replacing the drive. If this is the main drive make sure you have recovery disks or the original OS installation disk.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users