CRC problems

KaBar

KaBar

KaBar

Associate
Joined
12 Aug 2006
Posts
59
built a new system recently and its driving me nuts. Virtually any compressed files I download are not opening and reporting CRC errors and I am a bit uncertain where to begin on figuring out where the problem is. Not sure if it's my HDD playing up, using a SATA drive now on a DS4 board with latest BIOS/Drivers, or whether its software. Using XP SP2 same CD that came with previous system and using same d/l software and uncompressing programs.

Main problems are:

1) when using utorrent etc to d/l anything that comes as a multipart archive there are always a number of the parts that flag up with crc errors and its not always consistent eg. when unpacking it will show files 1, 3 and 7 as having errors I re d/l the offending sections and on trying again it'll either work or now say files 2 and 9 are corrupt etc. never had this problem in the 5 yrs had previous system.

2) large .zip files from web pages are showing as corrupt too, being trying to d/l a 192Mb game patch that d/l fine but will never open as there is one bit difference between the unpacked size and the size reported within the zip. tried the same file several times from different sources and always the same problem

3) when installing games and programs from CD/DVD I am getting frequent errors saying for example CRC error file xxx doesn't match the one in setup.cab, abort retry or ignore

hooking up my old laptop HDD drive externally tomorrow to see if I am still getting problems with that disk and I've ran a full virus scan and chkdsk but have no real idea why i am getting so many problems with apparently corrupt data :mad:
 
ran the version of memtest that runs within windows and almost immediately got the error:

'Memory error detected Pair 81137650 does not store values accurately'

followed by
'Memory error detected Copying between 4a95eac and 4a95bf2 did not result in accurate copy'
etc. etc.
0.7% coverage and 30 errors so far
 
Last edited:
bit confused now.
have an E6300 on a DS4 Board with 2GB of 800mhz Geil Memory

system was running (I thought stable, originally orthos stable last week anyway) at 2.27Ghz (325Mnz FSB) with a memory clock of 2 (so underclocking a bit at 650Mhz) and at the suggested voltage changes in the DS4 owners thread.

However just reset everything back to default stock speeds and ran memtest again and it seems to be running with no errors now.
 
try with a higher mem voltage if you put your clock back up and run memtest86 for a couple of hours *before* you boot into windows, just to make sure the memory is stable (you don't want a corrupt OS!)
 
any way of telling if I have a corrupt OS already?

I don't quite 'get it' on the memory front. I was previously running my 800Mhz Geil at 650Mhz and 2.1v (The voltage stated on the memory itself) and failing memtest. Now I've reset to default which in the new BIOS for the DS4 automatically detects the memory as 800Mhz and runs it at this even at stock CPU FSB and a default voltage of 1.8v and now memtest was fine for at least an hour (in windows however yet to test outside)
So lower than rated speed and recommended volts doesn't work but full speed and under voltage does? makes little sense.
 
KaBar said:
any way of telling if I have a corrupt OS already?

I don't quite 'get it' on the memory front. I was previously running my 800Mhz Geil at 650Mhz and 2.1v (The voltage stated on the memory itself) and failing memtest. Now I've reset to default which in the new BIOS for the DS4 automatically detects the memory as 800Mhz and runs it at this even at stock CPU FSB and a default voltage of 1.8v and now memtest was fine for at least an hour (in windows however yet to test outside)
So lower than rated speed and recommended volts doesn't work but full speed and under voltage does? makes little sense.
Click to expand...
It's a bit bizarre that it runs under-volted at stock speed, but stock voltage and under-clocked is messed up.

Download and burn the iso which Bledd has linked to, then go back to your overclock (although not as high as it was previously - go for a 'safe' medium). Leave your memory at the rated speed and let memtest86 run through a couple of times - there's about 8 tests to run through and should be less than an hour for the full set.

If there are any errors (they show up as red) - you'll have to reset and go back to bios. Memtest86 will tell you exactly what frequency your memory is running at (sometimes it lies in bios - I've seen this on an Asus P4P800-e and some Asrock P.O.S. board), the voltage and also the timings which they are running at. Make sure that they are all within spec to start with (esp timings) If they are, pop the VDIMM up a notch and see what happens in memtest. If it fails again, you can try another notch up (admittedly, Inever used GeIL ram, but I would expect it to be able to take 0.2V over rated) - or you can try slackening off the timings - the one which will make the most difference is the cas rating.

Once you get that stable at the rated frequency, boot into Windows and fire up Prime / Orthos - whatever your preference and leave that running on max priority overnight (I tend to go for 8 - 12 hours for an interim O/C and 48 hours for my final O/C, or it's not prime stable, but that's me...)

Slowly edge up the fsb (running memtest86 each time) and run prime to check stability.
 
You must log in or register to reply here.
Back
Top Bottom