XP slows to a crawl transfering files on new computer

[ClickRight]

I just built a new computer for a customer, 3.0GHz E8400, 4GB RAM, Asus P5KPL-CM motherboard, Windows XP Pro X64, etc. When transferring files from one drive to another via SATA, the computer slows to a CRAWL. It won't do anything but transfer the files.

I opened the task manager (which took about 2 mins) and it shows 10% CPU usage, just under 512MB RAM being used.

I have all the latest drivers installed, and both drives I'm transferring from are in good shape. Any ideas?

 

[abe]

check in device manager if the controller is set to enable dma

 

[ClickRight]

check in device manager if the controller is set to enable dma

Enabled and write caching on.

Will try different cables as per ACG's suggestion.

 

[MM PC Solutions]

Have you installed the latest intel driver?

I'm just thinking of the sata controller thats all...

 

[ClickRight]

Have you installed the latest intel driver?

I'm just thinking of the sata controller thats all...

Yes, and I actually just tried using the "Standard Dual Channel PCI IDE Controller" driver from MS as well, with the same result. This is really puzzling me. I have tried a new cable on one of the drives, going to try the other now.

 

[ClickRight]

Update: Swapped the other cable, same thing. One thing I've noticed now though, is it's only big files that seem to do this, say a single 80GB file.

I have run HD Tune benchmarks on both drives and they're both great, with maximum reads above 80 MB/s and less than 2% CPU usage. I still can't find the problem though. These are the only two devices connected to the SATA controller.

 

[Starsky]

Are you only using the windows copier? Try using a third-party copier, i would recommend supercopier2 or something similar, these programs have better memory management. I would not be surprised if it was just windows crapping itself when dealing with files that large. You could also try a boot disk of a Linux operating system or something and see if it works in a different environment. Lastly, try copying the file over a network rather than locally.

Good luck.

 

[Bobbing]

Solution to your problem

It is a problem with the OS (X64, 2003) not the hardware.
You need to make this registry change.

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then right-click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\MemoryManagement
3. Point to New, and then click DWORD Value.
4. Type SystemCacheDirtyPageThreshold, and then press ENTER.
5. Double-click SystemCacheDirtyPageThreshold.
6. In the Value data box, type 0x20, and then click OK.

Notes
* "0x20" corresponds to a decimal value of 32 MB.
* The range of values for the SystemCacheDirtyPageThreshold registry entry are as follows:
Minimum value: Total physical RAM in MB divided by 64
Maximum value: Total physical RAM in MB divided by 2
Default value: 0

The default value is a nonexistent key. If you add values that are out of range, your computer will revert to the default behavior. The value that you add is measured in MB.
7. Exit Registry Editor.

 

[ClickRight]

It is a problem with the OS (X64, 2003) not the hardware.
You need to make this registry change.

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then right-click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\MemoryManagement
3. Point to New, and then click DWORD Value.
4. Type SystemCacheDirtyPageThreshold, and then press ENTER.
5. Double-click SystemCacheDirtyPageThreshold.
6. In the Value data box, type 0x20, and then click OK.

Notes
* "0x20" corresponds to a decimal value of 32 MB.
* The range of values for the SystemCacheDirtyPageThreshold registry entry are as follows:
Minimum value: Total physical RAM in MB divided by 64
Maximum value: Total physical RAM in MB divided by 2
Default value: 0

The default value is a nonexistent key. If you add values that are out of range, your computer will revert to the default behavior. The value that you add is measured in MB.
7. Exit Registry Editor.

Awesome, thanks. I'm delivering the system on Saturday, so I'll add that registry key.

PS. Looks like we're very close geographically; I'm in Coquitlam.

 

[NYJimbo]

Awesome, thanks. I'm delivering the system on Saturday, so I'll add that registry key.

PS. Looks like we're very close geographically; I'm in Coquitlam.

Just in case you need all the nitty gritty about this one:

http://support.microsoft.com/kb/920739/

 

[ClickRight]

Just in case you need all the nitty gritty about this one:

http://support.microsoft.com/kb/920739/

Thanks, that was the first page I went to after I looked over the info.

 

[Bobbing]

I grew up in Coquitlam.
Why does the client need X64?