Hello,the last days im experiencing one serious problem and i dont know whats the problem.Im Havin CPU :AMD ATHLON 64 X2 4200+ DUAL CORE BOX RAM :Kinhston Hyperx 2GB 2X DIMM DDR 1GB PC3200 (400MHZ) MB :ASUS A8N32-SLI DELUXE :FLOPPY DISK DRIVE 3.5' BLACK HDD1 :WESTERN DIGITAL 320GB WD3200JS 7200RPM SATA2 HDD2 :WESTERN DIGITAL 1TB WD1000FYPS RE2-GP SATA2 DVDROM :LG DVD 16X GDR-8164B DVD RW:NEC DVD+/-R/RW ND-4571 LABELFLASH and before 2 days im having errors like "A parity error was detected on \Device\Scsi\nvgts1 2" and another one thas goes together "The driver detected a controller error on \Device\Harddisk0\D" i check on the internet about that and i check the cables,i did virus scan but didnt solved the problem.Also i had problem sometimes when i boot up,Error loading os,Disk Error but after hours of chdsk(MFT i think) the computer starts. I forget to mention that before 2 weeks i bought one psu thermaltake toughpower 1000w and asus 4870 1GB and i didnt istall any drivers except graphic card drivers and when im checking with diagnostic tools they say that both hdd are healthy MB

It sounds to me like the Radeon memory is set to do parity ECC error checking and this may have some incompatability for your extended memory when your DMA is doing transfers along the system BUS. Look at the control panel for your Radeon video card and see if disabling parity/ECC memory support doesn't help... John W. Borelli IT Specialist OmniIT borelli35

"i didnt istall any drivers except graphic card drivers ..." Whenever you load Windows from a regular Windows CD (or DVD) from scratch, after Setup is finished you must load the drivers for the mboard, particularly the main chipset drivers, in order for Windows to have the proper drivers for and information about your mboard hardware, including it's AGP or PCI-E, ACPI, and hard drive controller support. If you have a generic system and have the CD that came with the mboard, all the necessary drivers are on it. If you load drivers from the web, brand name system builders and mboard makers often DO NOT have the main chipset drivers listed in the downloads for your model - in that case you must go to the maker of the main chipset's web site, get the drivers, and load them. ...... You often find specific information if you search using the exact error message, or several words in a row in it. Search using: A parity error was detected on \Device\Scsi\nvgts1 2 Apparently that's an error you only get if your mboard has a NVidia main chipset and you are using the NVidia SATA drive controller. It's probably caused by a software bug - NOT your hardware. It's likely a main chipset drivers problem. If you loaded those from the CD that came with the mboard and got that error, I suggest you load updated NVidia main chipset drivers for your particular main chipset, if you haven't already (go to the NVidia web site). If that doesn't help, NVidia has a reputation of not fixing problems with their main chipset drivers (and video drivers) - if you can find an OLDER version than you are using of them, try that (if you have not loaded the main chupset drivers from the CD that came with the mboard yet, they are probably older). If that doesn't help... - if your mboard has a secondary SATA driver controller, connect your SATA drives to that instead of the NVidia SATA one (see your mboard manual). The drivers for that controller are on the CD that came with the mboard, or on the mboard maker's site in the downloads for you model, and they must have been loaded. - if it doesn't, get yourself a SATA drive conroller card and connect the drives to that. You must have SCSI before any hard drive in your bios boot order in order to boot from a drive connected to the card. If you reload Windows, if Setup does not see your SATA drives, you need to change bios settings to have the SATA in IDE compatible mode or similar (you can change that to SATA or RAID SATA mode after Setup is finished, after you load the SATA controller drivers); otherwise you need to press F6 near the beginning of Setup, and load the drivers for the SATA controller chipset from a floppy disk in a floppy drive - Setup will not read anything else except a floppy disk in a regular floppy drive at that stage, unless you have one of a very small number of USB connected floppy drive models XP recognizes. Info found here: http://forums.nvidia.com/index.php?... That "hit" and more here: http://ca.search.yahoo.com/search?p... .... Search using: controller error on \Device\Harddisk0\D "...I found solution for my system. Probably it will help other users. I noticed when I switching memory usage from "System cache" to "Programs" the problem disappeared. I started digging these symptoms and I found interesting articles: http://support.microsoft.com/?kbid=... (Second part after MORE INFORMATION). http://www.microsoft.com/technet/pr... http://www.microsoft.com/technet/pr... I think this can explain why this error can cause EVENT ID -51 on many different systems. WORKAROUND: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\SystemPages setting value: 0xFFFFFFFF works fine." That found here: http://www.hardwareanalysis.com/con... That "hit" and more here: http://ca.search.yahoo.com/search;_... ......... "MB :ASUS A8N32-SLI DELUXE" "RAM :Kinhston Hyperx 2GB 2X DIMM DDR 1GB PC3200 (400MHZ)" Not enough info - if it does not have one of these ID strings - part numbers - it may not be 100% compatible with your mboard model: http://www.ec.kingston.com/ecom/con... There is NO ECC ram listed there for your mboard. It is quite possible your mboard model cannot use ECC ram, in which case there would be no setting for ECC ram in your bios Setup. (see your mboard manual, and your bios Setup) "...after hours of chdsk(MFT i think) the computer starts." I should not take that long, unless there's serious data corruption. The NVidia main chipset drivers problem may have corrupted the data on your hard drive. Once you cure the first error, you may need to re-load Windows from scratch. And/or your hard drive or it's connection may have a problem... ..... Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and the mboard - it should not move when you merely brush your hand against it near the socket - if it does, use another SATA data cable that does "latch", or tape the connector in place. (There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged) ....... "im checking with diagnostic tools they say that both hdd are healthy" Which diagnostics tools? Check your hard drive with the manufacturer's diagnostics. See the latter part of response 1 in this: http://www.computing.net/windows95/... (thanks to Dan Penny for this link:) Hard Drive Diagnostics Tools and Utilities http://www.tacktech.com/display.cfm... If you don't have a floppy drive, you can get a CD image diagnostic utility from most hard drive manufacturer's web sites, but obviously you would need to make a burned CD, preferably a CD-R for best compatibilty, on another computer if you need to. If the hard drive itself tests okay, any data problems found can be fixed, one way or another. ............ "DVDROM :LG DVD 16X GDR-8164B" E-IDE / ATAPI It doesn't require an 80 wire data cable, if connected by itself, or if on the same cable as another drive that doesn't require one. "NEC DVD+/-R/RW ND-4571 LABELFLASH" UK, Europe only model http://www.komplett.co.uk/k/ki.asp?... Interfaces 1 x IDE/ATAPI - 40 PIN IDC DVD±RW (±R DL) / DVD-RAM - 5.25" x 1/2H Read Speed 48x (CD) / 16x (DVD) Write Speed 48x (CD) / 16x (DVD±R) / 8x (DVD±R DL) CD / DVD Rewrite Speed 32x (CD) / 6x (DVD-RW) / 8x (DVD+RW) / 5x (DVD-RAM) 16x (DVD±R) indicates.... You MUST use an 80 wire data cable with this drive, whether it is by itself on a data cable or the cable has another hard or optical drive connected to it, because it is capable of UDMA 66 (UDMA 4 in XP) max speed - the drive cannot reach it's max speed and is likely to generate data errors, and your burning software may not recognize it properly, if it's connected to a 40 wire data cable. ..... If you have problems with your optical drives... It is common to un-intentionally damage IDE data cables, especially while removing them - the 80 wire ones are more likely to be damaged. What usually happens is the cable is ripped at either edge and the wires there are either damaged or severed, often right at a connector or under it's cable clamp there, where it's hard to see - if a wire is severed but it's ends are touching, the connection is intermittant, rather than being reliable. Another common thing is for the data cable to be separated from the connector contacts a bit after you have removed a cable - there should be no gap between the data cable and the connector - if there is press the cable against the connector to eliminate the gap. 80 wire data cables are also easily damaged at either edge if the cable is sharply creased at a fold in the cable. Try another data cable if in doubt. ...... "I forget to mention that before 2 weeks i bought one psu thermaltake toughpower 1000w and asus 4870 1GB...." I assume that a single 4870, not a 4870 X2 (two video chipsets on one card). The 4870 chipset requires your system power supply capacity is a least 500 watts - did you install it before you installed the 1000 watt PS , or at the same time as the 1000 watt power supply? It's a PCI-E X16 2.0 compatible card - that spec requires your mboard can supply more current than a PCI-E X16 spec mboard slot. This video card draws closer to the max than the min current. If your mboard PCI-E X16 slot is not rated PCI-E X16 2.0, it's possible your mboard wiring could be damaged by you using this card. See your mboard manual, or specs on the manufacturer's web site.