BSOD after d/l's

Results of Full HD diagnostic test. Can someone please verify that there is a problem with my HD, please. Oh, and please let me know if HD should be replaced.

Thanks all.

SeaTools Desktop v3.02.04
Copyright (c) 2005 Kroll Ontrack Inc.

2/13/2007 @ 10:29 PM

The following information has been generated by SeaTools Desktop. Use
this information to help you recognize and resolve potential data access
problems.


System Information:
BIOS Date 02/08/06
Conventional Memory size 639 K
Extended Memory size 58532 K
IO Channel type PCI



Drive Information:
SIZE MODEL
--------- ---------------------
80 GB BIOS Drive 0x80


Serial Number = N/A
Int13 Num = 80, PHYS CHS = 0x0x0.
ParmTable CHS, Rsvd = 9729x255x63

PARTITION CYLINDER SIZE
---------- ------------ ----
# Type Start End MB
PRIMARY
1 NTFS 0 9727 80020


Diagnostic Results:

Full Diagnostic Scan Result: Passed



File Structure Test Result:

Partition 1 (NTFS (80 GB) ) Result: Failed with critical Errors

The following errors were found while scanning the volume:
- One or more errors were found in metadata file records


NOTE: Any report of possible errors in the file system tests are for
informational purposes only. We suggest you should consider testing with
the official file system diagnostic utilities for your operating system.
Seagate is not able to assist with troubleshooting or reviewing
file system test results.



******************************************


Recommendation:
All selected physical diagnostics passed.

If you are not experiencing data loss and SeaTools reports File
System Structure errors, they may be caused by a lock-up or
failure to shutdown Windows correctly. Many times, these errors
may be repaired through normal system maintenance which
includes using the Windows provided "Defrag" and
"Scandisk / Chkdsk / Error Checking" utilities.

If you are experiencing a hardware error, you should isolate
the cause and replace the failing component. If you are unsure how
to proceed with repairs, contact a computer professional. After
completing any maintenance tasks, run SeaTools again to
verify that all errors have been repaired. If errors continue to
occur, the system may not be stable. Again, contact a computer
professional.




========================================================

 

The user dump is used for debugging application problem within windows and it does not cause blue screen. Minidump is used for debugging blue screen problem. How often do you get the blue screen?

 

I don't know if this will help ..but.....

I noticed an article and pdf download on Tech Republic's site...

http://downloads.techrepublic.com.com/download.aspx?docid=172527&tag=nl.e101

the title of the article is ... Extract troubleshooting info from Windows XP BSOD error messages it might be of some assistance.....Carl

 

Hello Sportsaholic,

Did you run chkdsk and defrag? You don't mention them.

Have you checked the Event Viewer?

Right click on My Computer, then Manage.
On the left you will see Event Viewer. Expand that (click on the plus sign).

Then click on System. See if there are any errors being logged by the system when the problem occurs.

Right clicking on a line and then clicking on Properties will give you a window with more info concerning that line. You'll see in the top section right below the down arrow, a text graphic sysmbol. Clicking on that will place the error info text into your clipboard (memory). Bring up Notepad and right click and paste, that will transfer it to Notepad. You can then paste the text into your next post here.

Regards - Charles

 

Ok, I ran chkdsk /r and it fixed 1 or more errors on the volume. Should I assume I will no longer see any BSOD's and my HD is fine now? If I do get more BSOD's should i believe there are problems with my HD and it needs to be replaced? Please let me know.

thanks for the help.

No errors in event viewer.

 

Hi Sportsaholic,

Hopefully chkdsk resolved something. And I would start backing up your data if you haven't already. If this continues, then yes, I would consider a HD replacement.

Did you download and run System Information for Windows SIW? I gave you the link in an earlier post. I assume your HD is S.M.A.R.T enabled. See if there are any S.M.A.R.T errors.

Regards - Charles

 

Charles, Left computer alone for 20 minutes returned to

stop 0x000000f4, (0x00000003, 0x81eddcd0, 0x81edde44, 0x805d140), I have to assume there are HD issues wouldn't you?

 

bump

 

Yes, I agree.

Regards - Charles

 

Hi, Sportsaholic.

I think you should study the suggestions in this recent thread where I helped someone resolve a Stop 0x000000f4, (0x00000003,...) error.

Please let us know if you discover anything as a result of the information in that linked thread.

 

Mailman, Are you saying you think my HD is connected to the middle connector on my IDE data cable instead of the end of it? If so, that would make the techie who fixed it an idiot and it wasn't me. Please let me know if that is what you are saying, please?

 

That is one possibility. There are also other possibilities described in that thread. That's why I suggested you study that thread.

If your hard drive is an IDE (PATA) drive and the drive is connected to the data cable properly, then perhaps the IDE drive is jumpered incorrectly or the data cable between the hard drive and motherboard is faulty and should be replaced.

It is possible that the techie jumpered your IDE hard drive as a "Slave" when (s)he was "fixing" it and forgot to move the jumper back to the "Master" pins on the back of the hard drive before returning the hard drive back to you. If this is the case, it should be relatively easy for you to jumper the drive correctly. You might have to remove the hard drive from the computer case to easily see where the jumper is connected. Be sure the power to the computer is off when handling the hardware inside of the case.

If your hard drive is a SATA drive, connect the hard disk cable to a master channel SATA connector on the motherboard. If the SATA drive is already connected correctly, then perhaps the SATA cable is faulty and should be replaced. (I am not intimately familiar with SATA yet so there may be other SATA configuration issues I am not aware of that should be addressed.)


Even if the data cable between the hard drive and your motherboard appears to be OK, it is possible the wiring inside the cable may be faulty (especially since the cable apparently had to be handled if the hard drive was removed from the computer before the techie's fixing procedures).

It is also possible that your particular motherboard model may be at the heart of the problem (according to the Microsoft KB article linked in that thread).

 

It is a sata drive and the red cable could only fit in one slot on the mobo so I know that's not the problem. The cable itself is less than a year old so i doubt that is the case either. Either way I would say that it is surely a HW problem, do we at least agree with that? I appreciate other responses as well.

 

LOL, I've looked back thru this thread and I find no mention of having your Computer fixed.

What was fixed?

Regards - Charles

 

My bad, I should of said looked at and determined that it wasn't HW related but I insist that it is, do you agree?

 

I would still be sure the SATA cable is seated firmly in the connectors and I would replace the SATA cable with a new SATA cable just to be sure (since cables are relatively inexpensive and easy to replace).

I would also double check the motherboard diagram in your motherboard manual to be sure the cable is connected to the master channel connector.

I'd also check that Microsoft KB article from time to time to see if Microsoft posts any updates to the "some motherboards" issue they reported in that article.

If I discover any other possible causes of your issue, I'll post here to let you know.

 

Guys, Please read this thread from another site as she is getting the same errors as me. Look what her problem was.

http://www.geekstogo.com/forum/Blue_Screen_Issues-t148721.html

Let me know what you think, please.

 

Those suggestions at Geeks to Go! seem reasonable to me.

Have you also tried SIW - System Information for Windows by Gabriel Topala as Charles suggested (twice)?

 

Do you believe the person who originally looked at my pc and said there was nothing wrong with it finally agreed it needed a new HDD.

 

Bad paging space maybe related to hard disk error. CHKDSK can only fix software error and it cannot fix hardware problem.