I heard from two sysadmins that Microsoft's windiag is often able to find errors which were not found by memtest. http://oca.microsoft.com/en/windiag.asp M. 2007/11/11, Joris <joris@xxxxx>: > > > Another thing I found wise to check in case of corruption is main > > > memory. 24 hours of memtest86+ usually do the trick. > > > > I have seen corruptions (3rd party Infineon memory running at 400MHz, > > specified for 400MHz) that are not catched by memtest86+ > > reliably. Running Linux kernel compilation repeatedly is more > > stressful than memtest86+. > > For what it's worth: > > From an anecdote I can recommend running memtest86+ for 10 cycles (as > opposed to 24h) with the option for 'all tests', not just the standard > tests. > > > Kind regards, > Joris > > --------------------------------------------------------------------- > dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ > To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx > For additional commands, e-mail: dm-crypt-help@xxxxxxxx > > -- Glauben heißt nicht wissen wollen, was wahr ist ... Nietzsche --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
