[QUOTE=LaurV;443666]Let some breadcrumbs to the little birds too, otherwise they are out of business.[/QUOTE]:tu:

My DC of 40646939 didn't match. Anyone like to TC it?

[QUOTE=richs;449031]My DC of 40646939 didn't match. Anyone like to TC it?[/QUOTE]

I queued it.

[QUOTE=richs;449031]My DC of 40646939 didn't match. Anyone like to TC it?[/QUOTE]

Your result was correct: [url]http://mersenne.org/M40646939[/url]

41645717
[url]http://www.mersenne.org/report_exponent/?exp_lo=41645717&full=1[/url]
Anyone?

[QUOTE=petrw1;449189]Anyone?[/QUOTE]
Me. Long time didn't do a TC...

[QUOTE=ATH;449182]Your result was correct: [url]http://mersenne.org/M40646939[/url][/QUOTE]

Thanks ATH!

[QUOTE=stebbo;448809]Can 44750009 please be triple checked. My machine returned a mismatch on that exponent.

Thanks,
Chris.[/QUOTE]

Ok, so it seems my computer returned a bad result. Not really sure what this means.

This is a new computer that retuned one match and one mismatch with it's first two results, and it has since returned two matched double-checks. I haven't done any overclocking or adjustments on the hardware, simply installed the software and let it run.

Does a bad result indicate a strong possibility of a problem with the hardware, or do they "just happen" from time to time?

Thanks in advance for any info.

Cheers,
Chris.

They shouldn't just happen. I would run a memory test.

[QUOTE=stebbo;449400]Ok, so it seems my computer returned a bad result. Not really sure what this means.

<...>

Does a bad result indicate a strong possibility of a problem with the hardware, or do they "just happen" from time to time?

Thanks in advance for any info.
[/QUOTE]

On one hand, this may happen; for sure I wouldn't ignore it (= it has little sense to "waste" electric power/CPU cycles on a potential flaky machine, just to be proven wrong some time later). Take a look around this thread, as there are many suggestions on what to do in such cases.

Most frequent areas to look after are memory (as Mark already suggested), PSUs, cooling (in case of laptops) even as per dust accumulated inside the machine (but you mentioned it's a new one, so I'd exclude this). Plus some exoteric conflicts with other pieces of hw/sw you might have running in parallel (but again I would let those aside for now).

As you said, it's a new machine: start with a long memtest (>24h), let us know how it goes...

r.

[QUOTE=Mark Rose;449409]They shouldn't just happen. I would run a memory test.[/QUOTE]

On the other hand, sometimes they really do just happen. If a memory test comes up clean and n more DCs match for some value of n, then you're probably fine (which is really vacuous, but I mean that the bad test can in that case be written off to cosmic rays or some such bitflip).