Prime95 v27.7 crashes - Page 2

kladner · 2012-06-20, 00:13

Quote:

Originally Posted by x3r

i am currently using memtest86+ v5.00b1 to test the memory as we speak. quick q - why is RAM being read as 800 MHz (vs. 1600 MHz as advertised)?

1600 is the DDR equivalent speed.

x3r · 2012-06-20, 02:34

Quote:

Originally Posted by x3r

i will go ahead and try different % of ram and get back to you. ram type: CORSAIR Vengenance 16GB (4 x 4GB)

i am currently using build 2 of 27.7.

passes 1 and 2 gave no error whereas pass 3 started giving error. attaching pic for detailed info.

Dubslow · 2012-06-20, 02:59

Edit: Posted before pic.

To add to what Batalov said, to help narrow it down, try testing one stick at a time by removing the rest. If all but one pass, then it's probably a bad stick. If they all individually fail, then it's either the mem bus or mem controller as Batalov said.

Batalov · 2012-06-20, 03:08

Quote:

Originally Posted by x3r

passes 1 and 2 gave no error whereas pass 3 started giving error. attaching pic for detailed info.

There you go - you have found the problem. This may be the memory or the bus or the memory controller of the CPU. Could the PSU.

You would want to find a stable area of parameters, no matter what the reason is. Downclock by 5% and run more memtest. You can always restore clocks later. You can read some advices on the overclocking forums. Maybe you will need to tune the voltage - but take time to read plenty. Good luck.

Batalov · 2012-06-20, 03:49

P.S. Could be a bug of the memtest, too! (don't laugh)

Here (though the addresses are not exactly the same, post #29; errors in very low addresses in test #5)

Dubslow · 2012-06-20, 03:49

Except Prime95 also crashes, and we're pretty sure that's bug-free.

Batalov · 2012-06-20, 03:56

Well, yes, but debugging hardware is a maze of twisty little passages, all alike, so you don't want to take the wrong turn just because there was a sign on the wall. And surely Prime95 also can haz ~~cheeseburgers~~ bugs.

axn · 2012-06-20, 04:03

Quote:

Originally Posted by Batalov

And surely Prime95 also can haz ~~cheeseburgers~~ bugs.

Yeah. OTOH, both of them having simultaneous, heretofore unknown, bugs, both manifesting under the exact same conditions? As Mr Spock would say, "Fascinating!".

Batalov · 2012-06-20, 04:12

Why simultaneous and why unknown? the author of memtest writes himself - "The error in test#5 at 0x13CF0 & 0x13CF8 is a bug in the code. It will be solved in the next beta. Did you get an error at another address ? It will help to get a screenshot." (and the following posts show a variety of low addresses) this makes sense, because memtest relocates itself to test; so, he missed something an offset or a relocation size (hardcoded from a previous version? whatever). Happens to anyone.

kracker · 2012-06-20, 19:04

Quote:

Originally Posted by x3r

passes 1 and 2 gave no error whereas pass 3 started giving error. attaching pic for detailed info.

There ya go.

(Sorry Batalov, I just HAD to say it... haha)

x3r · 2012-06-21, 20:49

Quote:

Originally Posted by Dubslow

Edit: Posted before pic.

To add to what Batalov said, to help narrow it down, try testing one stick at a time by removing the rest. If all but one pass, then it's probably a bad stick. If they all individually fail, then it's either the mem bus or mem controller as Batalov said.

alrighty, checking 1 stick at a time. how long should i be running the memtest for...?

2012-06-20, 02:59	#14
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3×29×83 Posts	Edit: Posted before pic. To add to what Batalov said, to help narrow it down, try testing one stick at a time by removing the rest. If all but one pass, then it's probably a bad stick. If they all individually fail, then it's either the mem bus or mem controller as Batalov said. Last fiddled with by Dubslow on 2012-06-20 at 03:18

2012-06-20, 03:49	#16
Batalov "Serge" Mar 2008 Phi(4,2^7658614+1)/2 2·47·101 Posts	don't despair too early P.S. Could be a bug of the memtest, too! (don't laugh) Here (though the addresses are not exactly the same, post #29; errors in very low addresses in test #5)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Prime95 crashes everytime on same core	chiro	Software	18	2018-04-12 12:41
Computer crashes	robert44444uk	Hardware	8	2017-01-19 11:18
Memtest86+ shows no errors but computer crashes with Prime95	TObject	Hardware	11	2013-05-09 11:43
Everything crashes my computer	Unregistered	Hardware	6	2004-08-09 19:28
Upgrade and XP now crashes!!!!	johnymccarthy	Software	13	2002-09-26 05:08

2012-06-20, 03:56	#18
Batalov "Serge" Mar 2008 Phi(4,2^7658614+1)/2 2·47·101 Posts	Well, yes, but debugging hardware is a maze of twisty little passages, all alike, so you don't want to take the wrong turn just because there was a sign on the wall. And surely Prime95 also can haz ~~cheeseburgers~~ bugs.

2012-06-20, 04:12	#20
Batalov "Serge" Mar 2008 Phi(4,2^7658614+1)/2 2×47×101 Posts	Why simultaneous and why unknown? the author of memtest writes himself - "The error in test#5 at 0x13CF0 & 0x13CF8 is a bug in the code. It will be solved in the next beta. Did you get an error at another address ? It will help to get a screenshot." (and the following posts show a variety of low addresses) this makes sense, because memtest relocates itself to test; so, he missed something an offset or a relocation size (hardcoded from a previous version? whatever). Happens to anyone.