Starting the new year off with a bad cough - sort of grumpy. Relaxed and tried several more searches - no problems. Possibly was a fluke BSOD.

Might get the xp64 in the mail tomorrow - just going to bite the bullet and do the new install and go from there.

question for Nick -  should I leave all settings at auto until after the install or put in some manual basic settings - no clocking yet.

fwiw, cpu-z says 450x7.5 and Corsair ram at 1800 8-8-8-24-2t

No prob - still haven't rec'd xp64 - maybe tomorrow. Just want to have a stable platform for the initial install - then will do the clocking. Since my earlier post, with everything still on auto - have had no problems  but still can't pass OCCT at stock speeds.

Trying to get my head around this - so running the 1800 Corsair at rated speeds w/o clocking the cpu will still require some tweaking right out of the box.

I guess that's why they call it plug n pray. 

DOH!  I've been looking at the CPUz screen over and over - finally *see* the 450x7.5. So, by putting in the normal 1800 sticks, the auto settings applied a fsb clock on their own to get the 1800.

Learned something today, always thought that when the multiplier was 'fixed' it meant it couldn't be changed. Now  see that it means that the user can't change it but the system can as necessary.

As I said, fighting a bad cough - brain cells aren't hitting all the notes.

OK, so I'll set the voltages a bit but keep it at 3Ghz until I do the XP64 install. Then I'll get back to clocking.

Happy New Year

did you disable al the CPU advanced crap? CE1, TM Speedstep and anything else on that list?

Did you set the memory timing manually and not Auto?

Assuming you did all that, after getting this error did you do what IU said and import the NB and CPU GTL numbers we worked out for the VTT?

What about running 1600? Last I heard you were getting errors at 1800 and 1600 ... What about 1600 7-7-7 20? @ 400MHZ?



Yep.. you may have a defective CPU.. not sure but the bottom line is you do need to work this and we know the Mushkin Memory was stable at 1600 in which you posted it would not run either before you RMA'd the board

what about that? .. go back to the thread where we worked out the Mushkin clock and make sure you are using the same settings.. the GTL numbers as I recall were posted in the last 2 pages somewhere.

If the mushies are still unstable then sumthin aint right

setup the mush at 400x9  1600 7-7-7-20 1T PL6 - super pi fine

currently running OCCT and it didn't reboot or bsod instantly as before.

Maybe the HW is fine - user error as usual. 

In the old days you could just slam the parts together and if you didn't have a short - everything worked out of the box. I think that's where my mindset was at. Forgot that with the pro type boards there's not really a "default" setting - gotta do it manually.

Assuming this setup is stable, I'l use it for the xp64 install - make sure that's set up properly. Then try the Corsair 1800 at 450x9.

Who says you're to old to learn

BTW Nick - with all the other accolades you have gotten for your work, I hope someone has lauded your patience.

I would love to be a fly on the wall and hear your comments when reading messages.

HAH! you ought to hear the things  say to myself after you nicely reply to yet another off the wall comment!

So far OCCT has been stable for about 1 hour so I think I might have that base to start with for the xp64 install.

Now, when the time comes -  can I set up the 1800 corsair at 1600 7-7-7-20  400x9 just to establish a reference or will I run into different issues by doing it that way.

well, the xp64 didn't come in the mail so it'll probably be Monday night before I can get to it. Couple of days off - time to double check all my serials and preps are in order.