XP-M and Hyper-X not playing nicely together, memtest86+ v1.20 errors

[F@TMAN]

Attempting to o/c my setup (see sig), but I'm getting errors in memtest86+ v1.20 (test #5 in particular) @ 166x12 (2.0Ghz), from 1.45v up to 1.7v vcore (PC will not post @ 1.7v), memory in SC with 6:6 ratio, from 2.6v to 2.9v vdimm, 2.5-3-3-8 timings.

Not much else to say, really, but this FSB and multi combination is well within the limits of both my CPU and RAM, errors in test #5 imply memory-related issues, but to my knowledge there aren't any (133x15, no errors in test #5), and the fact that my PC won't post @ 1.7v vcore is not encouraging to say the least! Using D21 BIOS, was thinking of flashing to a modded BIOS with L12 mod, but I doubt that'll fix anything at this point. Any suggestions much appreciated, cheers
:confused:

[mluckey]

Your CPU should post at any voltage over the minimum rated voltage at it's rated speed unless it is not being cooled properly or the PSU is unstable. Remove the HS and reseat it. Then try again. Also, if your OS was loaded with APIC enabled, you will have a much greater chance of errors than if the the OS was loaded without APIC enabled in BIOS. Also check the PSU voltages under load.

FWIW Memtest picks up more than just RAM errors. It also picks up CPU and chipset errors, though it primarily stresses the RAM.

[$0m#0n#]

Originally posted by mluckey
Your CPU should post at any voltage over the minimum rated voltage at it's rated speed unless it is not being cooled properly or the PSU is unstable. Remove the HS and reseat it. Then try again. Also, if your OS was loaded with APIC enabled, you will have a much greater chance of errors than if the the OS was loaded without APIC enabled in BIOS. Also check the PSU voltages under load.

FWIW Memtest picks up more than just RAM errors. It also picks up CPU and chipset errors, though it primarily stresses the RAM. hey, man I am almost sure its not the CPU it's the memory, it doesnt mean the memory is bad, it;s just imcompatible, the easiest way is 2 try another memory.

[spaceman]

Or try switching to different DIMMs. I don't know about the NF7s but my AN7 is kinda picky about that.

[mluckey]

I run Hyper-X BH-5 and BH-6 on my NF7-S V2.0 without issues, so do many others on these forums.

It could be the DIMM slots as suggested, or that your RAM isn't matched. If that is the case, try swapping dimm slots as suggested. It helped me a while back when I was running BH-5 and BH-6 mixed a the same time.

I still find it odd that your CPU doesn't post at anything over 1.7 volts. That normally is PSU or insufficient cooling talking.

[Ol!ver]

Originally posted by F@TMAN
Attempting to o/c my setup (see sig), but I'm getting errors in memtest86+ v1.20 (test #5 in particular) @ 166x12 (2.0Ghz), from 1.45v up to 1.7v vcore (PC will not post @ 1.7v), memory in SC with 6:6 ratio, from 2.6v to 2.9v vdimm, 2.5-3-3-8 timings.

Not much else to say, really, but this FSB and multi combination is well within the limits of both my CPU and RAM, errors in test #5 imply memory-related issues, but to my knowledge there aren't any (133x15, no errors in test #5), and the fact that my PC won't post @ 1.7v vcore is not encouraging to say the least! Using D21 BIOS, was thinking of flashing to a modded BIOS with L12 mod, but I doubt that'll fix anything at this point. Any suggestions much appreciated, cheers
:confused:


What slots do you have the RAM in? I was struggling with my OC, and it turned out the NF7-S didnt like me having one of the sticks in slot 1. Moved it to slot 2 and it's been fine since.


HTH

Oli

[F@TMAN]

Thanks for your replies, everyone, I'll try and answer all your Q's. I'm currently running Prime95 torture test @ Large FFT's to check the voltages while under load, will post a pic if it lasts a decent amount of time. As for my cooling, using h2o, but I guess the block might be seating incorrectly, that's something I could check. My ram is a matched DC-kit, currently in DIMMS 1 and 2 (SC), because I was having trouble getting my PC to post @ 200mhz fsb while in DC (ie DIMMS 1 and 3, or 2 and 3).

As for APIC, I remember I read a lot about that topic, and atm its enabled, and I'm in no hurry to change that!

[mluckey]

Good luck!

I spent the better part of the week working to hit 216 x 11.5 with stability. I had APIC issues, bad RAM, incorrectly seated HS/Fan, two bad mobos, and a graphic card death. I finally made it though. so my next logical goal is 220 x 11.

The only thing still original is the CPU.

[F@TMAN]

lol @ mluckey, cheers mate! You're a motivation to us all!
=p

Been priming for about 7hrs now, here's a pic of the readouts from MBM if anyone cares to comment (ignore CPU temp, I cold-booted hehe)
http://users.tpg.com.au/adsla5yk/images/MBM%20readout.JPG

I'm pretty certain my m/b can handle this setting, I used to have a 2500+ which I ran @ 3200+ (200x11) with air, and 200x12 @ 1.93v vcore (1.86v real) on h2o. With some BH-5 memory, I managed to get the fsb to 225mhz as well, that's why I'm more inclined to think it's the PSU, CPU or RAM.

[$0m#0n#]

I think it must be the ram, the imcompatibility is the biggest - on nf2 chipsets! U may have even the best ram, but the motherboard doesn't like it, the easiest way 2 know if it's ram is try another or try only one stick.

[F@TMAN]

I think I should clarify the Vcore issue - when I would change it in BIOS to 1.7v, my PC would then "stall" so-to-speak once I would exit (ie. at the point when the PC restarts, there's a lot of hdd activity, but the PC never reboots, no beeping etc.). As such, I simply turn it off and reset the CMOS. I never attempted to boot up without first resetting the CMOS battery, and hence saying that it didn't post is not entirely correct!

[F@TMAN]

*UPDATE* I've managed to get some better results in DC (slots 2 and 3), but I want to gauge your opinion on a suggestion I received from another forum:

Also, make sure CPU interface is enabled (or maybe it needs to be disabled, can't remember) in bios. My previous XP-M setup wouldn't post above 190fsb unless I had this on/off (can't remember which)

comments?! I believe mine's been disabled (BIOS default)...

[a0chicken]

There's a series of tweaks on the NF7 that you may want to look through, in this topic: http://www.xtremesystems.org/forums/showthread.php?s=&threadid=37761

[SAE]

Pal, please do the L12 mod first.

Then try to ENable the cpu interface as it's not really a difference in stability but you are losing too much performance with it disabled.

[F@TMAN]

Cheers, SAE, thanks to you and others I decided to take the plunge and try that 3Dfire BIOS, read more about it here (http://s6.invisionfree.com/underclock/index.php?showtopic=9).

I'm memtesting now @ 200mhz FSB, memory in DC, 2.5-3-3-8 (wouldn't post @ CAS2), vdimm @ 2.9v - I'm happy, considering it's CH-5 memory (also, I enabled cpu interface). Here's hoping I continue to have some good luck with the multi!
:D

[a0chicken]

Heeeeeey.....
So did you do any of those tweaks I linked you to?

[F@TMAN]

Originally posted by a0chicken
Heeeeeey.....
So did you do any of those tweaks I linked you to?
Well, you can count enabling CPU interface as one of them! hehe
:)

My rigs been testing for 16hrs, did about 30-odd loops of the standard tests this morning, I'll wait until 24hrs has elapsed, then I'll boot into win and start priming. Any recommendations as to which stress-test will best help determine my cpu's stability?

[a0chicken]

Prime95, If memory serves me right.

[saaya]

prime+timedemo loop or 3dmarkloop has always worked best for me...

[F@TMAN]

200mhz FSB went well with the ram (23hrs, 50-odd loops of standard tests), atm I'm using Prime95 to get some stability @ 2.6ghz (atm, sitting on 1.75v vcore, 1.68v actual) before I make the big move up to 2.8ghz. Thanks again, everyone, will keep you posted!
:D

[F@TMAN]

*UPDATE* At this point, I'm priming @ 200x13.5 (1.85v vcore BIOS, 1.77v real), although I managed to boot up @ 200x14 (http://users.tpg.com.au/adsla5yk/images/2800mhz%20cpu-z.JPG) , but wasn't much good for anything other than web-browsing (even up to 1.975v vcore, but that undervolted to somewhere just above 1.9v). I believe it's my PSU holding me back, that +12v rail is hovering around 11.73v at load, and vcore atm is undervolting as much as 0.11v! But, if things go well, I will be happy with the current results. If I can be bothered, I might try upping the FSB 5-10mhz, but then again I've always liked round numbers, ie 200mhz :p Finally up there, w00t!