Page 1 of 1

How do I know if I have a bad dump?

Posted: 08.05.16, 04:41
by osity
When creating a dump, how would I know if its a good dump or if i need to remove and clean the chip better, to create a new dump?
When scanning for ECC on a particular case I get lots of red "Has been fixed but has errors".
Would this possibly indicate an unclean chip and poor quality dump?

Re: How do I know if I have a bad dump?

Posted: 10.05.16, 22:28
by Roman_TS
Hello!

One of the most critical and actual problem - a huge number of bit errors after dump reading. Exist several methods how we can reduce the number of bad's after reading. There is no any point to try READ dump better, because every time a huge number of bit errors will appear.

THe best way fix all errors AFTER reading process with 3 main steps:

1. Launch ECC and fix as much errors as possible:
http://blog.acelab.eu.com/pc-3000-f ... 1-ecc.html

2. Than, if there are still too much errors, you can try readout with ReadRetry:
http://blog.acelab.eu.com/pc-3000-f ... adout.html

3. Finally, if even after several pathes of readout you see that number of errors still high, you can try voltage power supply changing:
http://blog.acelab.eu.com/pc-3000-f ... ol-p3.html


Usually this 3 steps could help you fix around 90-95% of errors - it more than enough for successful recovery.

Re: How do I know if I have a bad dump?

Posted: 11.05.16, 01:51
by osity
ok Great thanks!