Reference_By_Pointer

[seekermeister]

A type of crash that I have not seen before. While attempting to change the DNS settings on my secondary unit, it popped a window saying that Explorer had crashed, so I selected the option for it to be restarted. At first, that appeared to solve the problem, but when I went back into the network, the moment that I selected a function, it BSODed with an error named in the title of this thread, and a 0x18 error code.

On reboot, it produced another error by the Windows Boot Manager, saying that there was a problem communicating with some device. It suggested disconnecting a removeable storage device, such as an external USB drive, hard drive or CD-rom. The status given is a oxc00000e9 error. I have no external devices on that rig, except mice and keyboard, so I disconnected the mice, but that didn't solve the problem.

Sometimes, upon reboot, it appears to be loading Windows, but then it produces a black screen wanting to run chkdsk, which I let it do. However, each time that it appears that Windows is going to load, I get the same chkdsk screen again. The succeeding chkdsk runs produce a list of orphan files, which it deletes, but trying again, it produces another list of orphan files repeating the same action.

Since I can't reach Safe Mode, I suspect that I shall have to reinstall the OS, but before doing so, I would like to figure out what is causing the problem...ideas?

EDIT: The Startup Launch Repair on the boot menu gets the same results as I described. Maybe trying the repair from the installation CD might help, but I don't yet know.

 

[seekermeister]

I have tried running the Startup Repair Facility from the DVD several times, and on each occasion it pops windows complaining about corrupt files, and suggests running chkdsk. An odd thing is that the drive that it shows as the OS volume is labeled D; rather than C: as shown within the OS.

Considering the corruption that is apparent, I'm guessing that the harddrive itself has gone south, but I will need to do some more testing to confirm this. If it is the harddrive that is the problem, then I'm beginning to lose faith in Seagate, because I have had much more trouble with their drives than others that I have had. I have a little Maxtor 80GB drive in the rig that I have owned for ~ five years, and when I checked it just a few days ago with SpeedFan, it showed no problems with it, except the amount of time that it has been powered on.

If I do have to replace this drive, I'm not sure what I will replace it with, because my experience with WDC hasn't been good either.

 

[zigzag3143]

I have tried running the Startup Repair Facility from the DVD several times, and on each occasion it pops windows complaining about corrupt files, and suggests running chkdsk. An odd thing is that the drive that it shows as the OS volume is labeled D; rather than C: as shown within the OS.

Considering the corruption that is apparent, I'm guessing that the harddrive itself has gone south, but I will need to do some more testing to confirm this. If it is the harddrive that is the problem, then I'm beginning to lose faith in Seagate, because I have had much more trouble with their drives than others that I have had. I have a little Maxtor 80GB drive in the rig that I have owned for ~ five years, and when I checked it just a few days ago with SpeedFan, it showed no problems with it, except the amount of time that it has been powered on.

If I do have to replace this drive, I'm not sure what I will replace it with, because my experience with WDC hasn't been good either.

Similar experience with seagate recently. I had 3 500 gig drives go south for no apparent reason within a year of purchase. Western Digital for me

Good luck mate

Ken J+

 

[seekermeister]

Sound like we may have had the same model of harddrives. Mine are ST3500320AS.

 

[seekermeister]

Weird! When I copied the model number of the drives from the quick reply box, to run a Google, the context menu had two entries at the top that I have never seen before....e'staing and ptomaine. Neither of these have anything to do with computers. Doing the same thing after posting didn't produce these on the context menu.

EDIT: After posting this, I went back to the quick reply to duplicate the problem, and the two words reappeared. I went ahead and selected ptomaine, but nothing seemed to happen, yet when I went back and tried this again, both words had disappeared.

 

[seekermeister]

I ran SeaTools, and it confirmed that there is a problem on the harddrive, but it also said that there is a problem with the harddrive controller. More than that, there are two controllers listed, but the second one is labeled unknown, and it's not possible to run a test on it.

Merely speculation, but as I posted in another thread, I have not been able to get the nForce 4 drivers to install on the IDE ATA/ATAPI controllers, so that may be at least part of the problem. However, all of the controllers show MS drivers installed, and are marked as working properly.

The question now is whether the harddrive just went bad, or if it was caused by a bad controller(s). or if not having the nForce 4 drivers install in the controller section is the root of these evils?

 

[seekermeister]

I'm posting the SeaTools log file, in hope that someone understands it better than I do:

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

1/1/2010 @ 4:31 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 06/06/06
Conventional Memory size 639 K
Extended Memory size 58532 K
IO Channel type PCI



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


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

PARTITION CYLINDER SIZE
---------- ------------ ----
# Type Start End MB
PRIMARY
1 NTFS 12 60800 500032


Diagnostic Results:



File Structure Test Result:

Partition 1 (NTFS (500 GB) ) Not Tested

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:
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.




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

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

1/1/2010 @ 4:46 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 06/06/06
Conventional Memory size 639 K
Extended Memory size 58532 K
IO Channel type PCI



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


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

PARTITION CYLINDER SIZE
---------- ------------ ----
# Type Start End MB
PRIMARY
1 NTFS 12 60800 500032


Diagnostic Results:



File Structure Test Result:

Partition 1 (NTFS (500 GB) ) Not Tested

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:
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 first portion is the test I ran on the harddrive, the second portion is the test that I ran on the controller...but it looks about the same as the first test. I'm trying to determine if this test truly reflects a problem with the controller or not?