* de Almeida, Valmor F. <[EMAIL PROTECTED]> 19. Nov 07: > >>From: Mark Shields [mailto:[EMAIL PROTECTED] > >On Nov 19, 2007 12:03 PM, de Almeida, Valmor F. <[EMAIL PROTECTED]> > wrote: > > >Is this execution time expected?
Yes, I can confirm that. In addition you should run it more than one time... > In fact I don't have a clue when it is going to end. It will never end. If it finished all tests it will start over again. > There are 2 fields with varying percentage values; but they get > cleared from time to time. Another field is called "Test" and it was > #3 (I think), and now it is at #4. So far it has taken 20:35h. On the > upside, no errors detected. In the table below you have a field "Pass", probably 0 right now. This will increment after the first turn. In upper area you have another "Pass" and a progress bar right of it. That's the progress of the current pass. One pass involves several tests (configurable by pressing c). (Disclaimer: everything from my mind.) To be sure make at least a second run, because some memory faults will only manifest after hardware is heated. The more passes the better. Last words: if memtest86+ doesn't find any errors, even not after days, you still can't be totally sure that your memory is okay. But if it finds a damaged address there is for sure a problem with hardware. Second last words: if it finds a problem there can be other broken parts beside memory. Basically everything involved on the path from memory to CPU: memory, Northbridge, memory controller, CPU... HTH, kind regards, Frank. -- Sigmentation fault -- [EMAIL PROTECTED] mailing list
