• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

SATA Locking up

N

Nismo

[H]ard|Gawd
Joined
Mar 10, 2000
Messages
1,413
I have a Maxtor 160GB SATA drive on an Adaptec PCI Serial ATA controller.

I can copy small files to it, but when I try bigger 20MB files, it loks up windows xp. I have to hard-reset the machine.

What is the deal with that?

Does it have anything to do with my MB Bios? Should I flash it?
 
Asus P4S8X with an Promise 376 Fastrack SATA controller on-board. That is what my Raptor is plugged into. However, I couldn't get XP to see my Maxtor SATA drive on the second chain(neityher could ASUS techs). So I bought an Adaptec PCI Controller and stuck the maxtor on it.

It saw the drive and can copy small files to it. But bigger files locks the machine up!

Does this have anything to do with needing shielded SATA cables? If so, why would it copy small files just fine?
 
If I read here:
http://www.ata-atapi.com/sata.htm

It says:
Are you thinking about buying a Serial ATA system and drive? If yes, read this... The Serial ATA (or SATA) products that are now shipping and available in your local computer store may not be the most reliable products. Testing of SATA products with tools such ATACT program are finding a variety of problems. These problems are timeout errors, data compare errors, and strange status errors. These problems are being reported by a large number of people doing SATA product testing. Hale's advice at this time is be very careful - make sure you can return the SATA product your purchased if it does not perform as you expect. See the ATACT link above for some ATACT log files showing both normal testing of a parallel ATA (PATA) drive (no errors!) and testing of a SATA drive (lots of errors!).



How do I know it would be a timeout error? I don't get anything! Just a lockup... It sounds like a timeout error.

What do you guys think?
 
Well, here are some thoughts:

1. Maxtor SATA drives are crap and have been causing all sorts of problems due to poor SATA implementation. If the problem is only happening when you copy with the Maxtor then that's your problem. If you have an ATA drive try copying and pasting large files to the maxtor and then try it with the raptor. If you only have problems with the Maxtor then you've found your problem. Better SATA choices would be any other brand.

2. Do you have the latest SiS drivers for your chipset?
http://download.sis.com/

3. If all else fails do a complete clean windows reinstall (meaning reformat your boot disk and reinstall a fresh copy of windows - download the MS updates first and then load the SiS drivers)
 
Forgot the first thing to try. Go into the BIOS and set PCI latency to 96 and see if that helps.
 
1. I'vew had that maxtor drive on SATA MB port 1 as master for 6 months and no copy probs. Thats not it.

2. I'll make sure tonight.

3. Just did that, my reptor is the System drive.

What does this PCI latency partain to? What is the 96 number? I'll check that tonight too.

Thanks for your info.

BTW, I ordered 2 of those cables today.
 
I doubt that the cables are the root cause
they may have no bearing on it, or be a contributing aggravation
but the shielded cables are probably a good investment any way ;)


check your power cables, make sure they are tightly seated with good contact
update the chipset drivers (if available)
and move the card to a different PCI slot
there is possibly a PIRQ conflict with another onboard device
( good overview of PIRQs your table will probably be different)
by default certain PCI slots share PIRQs with onboard devices
(LAN, IDE, Sound) I always try to get any storage controller on a "free" slot if possible, PIRQ routing tables are commonly documented in Workstations and Servers, but hardly ever documented in Desktops, so your often reduced to trial and error, this might be another contributing factor

re: PCI Latency Timer
This feature controls how long each PCI device can hold the bus before another takes over. The larger the value, the longer the PCI device can retain control of the bus. As each access to the bus comes with an initial delay before any transaction can be made, low values for the PCI Latency Timer will reduce the effective PCI bandwidth while higher values improve it.

On the other hand, while increasing the value lets each PCI device access the bus longer, the response time of those PCI devices suffers as a result. That means every PCI device will have to wait longer before they can get access to the bus but when they do get access, they can conduct their transactions for a longer time.

Normally, the PCI Latency Timer is set to 32 cycles. For better PCI performance, a larger value should be used. Try increasing it to 64 cycles or even 128 cycles. Some PCI devices may not agree with longer latency times so if you start facing problems like stuttering sound or a less responsive system, reduce the latency. Higher values will actually reduce performance as too much time may be allocated to each PCI device to the disadvantage of other devices on the bus.
Click to expand...
 
already had the latest SIS drivers. Flashed the BIOS from 1.5 year old BIOS. Moved PCI slot higher to 3rd slot.

Everything seems to be running well now.

In my BIOS I can control the PCI slot IRQ numbers or put them on auto(what they are set at now) What would you assign the SATA PCI controller so that it would not get confussed with any other IRQs? Remember, I have an onboard RAID SATA controller too.
 
hard to say without the rest of the picture
also many (Most?) BIOS manual IRQ assignments are overridden by the OS w\ ACPI enabled (PNP OS)

If its working now, Id leave it.
 
Got another question:

Chipset Clock Mode: Synchronous or Asyncronous
If you set it to Syncronous, it adjust AGP/PCI frequency with the CPU frequency.

I selected Syncronous, right? Should be more stable that way.
 
When set to Synchronous, the PCI and likewise the AGP frequency is a function of the FSB, meaning that overclocking the CPU FSB will increase the PCI and AGP frequencies as well.

if your not overclocking synchronous is fine
on the other hand if you are, under no circumstances use synchronous, that will mangle your data storage faster than just about anything else, the tolerance of various controllers attached to the PCI bus is highly variable to overclocking, most cant take much of an increase (if any) reliably
 
Do I need to arrange the jumpers on these 2 SATA drives any way? I just left them how they came cause I didn't think it mattered with SATA.
 
You don't have to do anything other than attach the cabling and make sure the SATA controller is enabled in the BIOS.
 
good move
they will eventually be functional...for power options
 
Man, this thing STILL locks up windows. Here is the pattern.

Off for the night. Go to work still off. Come home, turn on PC. Boots to windows.

Sometimes is lockes up right after windows loads. Sometimes it locks up when I try and access data on D:

If it does, I wait for 1 minute and get a Kernal_Data_InPage_Error.

Restart and Windows freezes at the black XP load screen. Hard power off and power on and windows loads again.

After all that, I can access data just fine off D: !!!! WTF?!

When I turn the system off for the night, it seems to start the cycle all over agian.

Do you think it's IRQ related since it's only intermittent?

If so, should I assign an IRQ in the BIOS to the PCI slot that the SATA controller is on? What IRQ would be safe to assign?

Damn guys, this is really making me upset! I've been troubleshooting for 2 weeks now.
 
this may sound strange
but error codes are your friend :p
actually getting one is your first step towards resolving an issue
always write it down
use the pause button if necessary

was there four 0x0000000 codes?
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR

The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.

Interpreting the Message
This Stop message has four parameters:

Lock type value (0x00000001, 0x00000002, 0x00000003, or page table entry (PTE) address).
I/O status code.
If the lock type is 0x00000001, this parameter represents the current process. If the lock type is 0x00000003, this parameter represents the virtual address.
The virtual address that could not be read into memory.
Frequently, the cause of this error can be determined from the second parameter, the I/O status code. Some common status codes are:

0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks (sectors) on the hard disk.
0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.
0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination, defective storage controller hardware, or defective disk cabling, or two devices attempting to use the same resources.
For information about other possible status codes that might be returned, see the file Ntstatus.h of the Windows XP Professional Driver Development Kit (DDK). For more information about the DDK, see the Driver Development Kits link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources.

Resolving the Problem
The following suggestions are specific to Stop 0x7A errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix. For more information about Autochk and Chkdsk, see "Troubleshooting Disks and File Systems" in this book.
Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
Check the hardware manufacturer's Web site for updates to disk adapter firmware or drivers that improve compatibility. Verify that your disks and controller support the same set of advanced features, such as higher transfer rates. If necessary, select a slower transfer rate if an update is not yet available. Consult your hardware or device documentation for more information.
Important

You can install disk controller drivers not present on the Windows XP Professional operating system CD by responding to the following prompt shortly after starting Setup:
Press F6 if you need to install a third party SCSI or RAID driver.
Press F6, and when prompted, provide the appropriate storage controller driver (ATA or SCSI) supplied by the manufacturer.
The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. For more information about Stop 0x77 messages, see "Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR" earlier in this appendix.
For more information about Stop 0x7A messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x0000007A, and 0x7A.
Click to expand...
 
Yeah, that is what this was...

Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR


I already knew almost all of that though. Something is causing this, but I just don't know what is...

Should I try the IRQ thing?
 
as I mentioned before, Im not even sure your BIOS would be able to assign IRQs (PIRQs) and make it stick, Im sure your running a Plug and Play OS with Advanced Configuration and Power Interface (PNP \ ACPI)

easier and surer to swap PCI slots
but the probability that is the issue is still really low

what I would do
1. Run Chkdsk and see if there are bad sectors
2. Test my memory
3. if there are bad sectors backup with an image (ghost) and run chkdsk /f (and review the other chkdsk parameters here

in the event that chkdsk repairs your filesystem past recovery :p
(it should fix it, but if the bad sectors coincide with critical system files....)
you would always be able to image it back to another HDD and recover data
 
You must log in or register to reply here.
Back
Top