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

Windows Vista 64 tcpip.sys BSOD


  • Please log in to reply

#16
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Any other BSOD's or crashes in the last 15 hours?
  • 0

Advertisements


#17
afrond

afrond

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
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.

  • 0

#18
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
What errors is it reporting?
Also I may have missed your results but did you ever run the memtest program on your memory?
  • 0

#19
afrond

afrond

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
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>
=========================
  • 0

#20
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
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.
  • 0

#21
afrond

afrond

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
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>
==============

Edited by afrond, 09 September 2011 - 05:58 AM.

  • 0

#22
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
How old is the drive and what brand?
  • 0

#23
afrond

afrond

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
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.

  • 0

#24
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
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.
  • 0

#25
afrond

afrond

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
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.
  • 0

Advertisements


#26
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
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.
  • 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