Vic

I just dont get it

Everything in GTL's both CPU and NB should be correct along with VTT and NB voltage @ 1.55 also seems right

SPREAD SPECTRUMS in the BIOS also must be disabled too but I can not see those causeing 3D glitches

If OCCT is remaining stable and this it only tied to 3D something strange is going on. I know stability in 3D can be borked during use (like crashes in FSX but it flys for a  few mintes) but the errors you are getting are really strange

Do you have your old video card still?

The only other thing I can think of is to get the system back to the original stable settings in OCCT.. all the GTLs, Vcore, NB voltage 1.55, everything as we know stable with OCCT @ 450.. verify

Once stable.... hmmmm...    try DISABLE the memory remap feature first... if still unstable, then I have to suggest uninstalling the drivers and pulling the card completely out.. put your old card in and try that one

if you still see the same exact problem then there is something wrong in hardware elsewhere... if it runs clean then uninstall the video driver and put the new card back in and try it again on the same exact settings.

If it borks then you either have a card that does not like this clock or a driver that does not play well with a clock.. you may need to take a look at Nvidia for older 280 drivers and try a few

If still no go and this all works fine @ 1600 and it worked fine at 1800 in x32 I really have nothing else to add other than a BIOS problem. 0801 worked great for you in the past

On a hunch - I dropped back to 400x9 and redownloaded the DX9.0c update. Ran 3DM and still got a few clicks from the monitor but it completed without problem and the score was 18520 as opposed to 14917 before the update. Framerates were in the 100's as opposed to 60's.

Raised clock back to 450x9 - 3DM locked up.

I'll try your other suggestions and see what happens.

flashed down to 0901 - same problem - does NOT like 3d at the 450 clock.

400 clock - all seems fine.

The card is clocked by the mfgr - I made no changes.

The clicking from the monitor is puzzling - I have never heard that before.

If it stays stable at 3.6 I'll bite the bulklket and leave it alone unless I get a brilliant idea. Don't want to throw more $$ at the problem. Might as well save the cash for the I7's down the road.

IIRC, you mentioned that the first releases of XP64 that had sp2 applied after the fact had 3D issues. This was a MS disk with sp2 on it already but the similarity bothers me.

If I get creative in the next few days, I may pop the 280 out and the 8800 in and see if the problem continues. Too pooped to do that tonight.

vgbaron wrote on Jan 11^th, 2009 at 11:07pm:



alright

I will think it over and post if I get any bright ideas but this just does not make sense.. x64 is more stable than x32, always has been

Im really at a loss

I do know there were a few of these boards reported to have a defect where the heatsink rail lifted off the NB due to a cap placement

http://forums.overclockers.co.uk/showpost.php?s=7bf8dd90e51008da8688580afd14cba1...



memory goes in the white slots and I am sure that is where it is..

It just does not ring right.. the voltage are right and with the exception of NB you should not need to set anything different

I have never seen a Q9650 need a VTT of more than 1.30, 1.28 is the norm but I have seen a few clockers claim they had to raise it to 1.35. If you did that, the 4 CPU GTL's would need to be -43.199mv (rounded to the highest value the BIOS allows, probably -45mv

If there was no change I just can not see that being the target area of the problem


Im just about farting in the wind at this point

lol

yup - pll is 1.51106

going to call it a night and unwind. getting brain cramps   

Make sure your PL is not too low too


and to be quite honest..  if you were not seeing any of this in x32, and, you are sure you were set up with no clock and on the right BIOS settings and 100% stable when the OS installed, meaning you are not fighting a bad system file problem from a corrupt OS install, if nothing comes of what I posted in suggestions above I think you should go back to x32 and run the clock you want stable and use the 3GB USERVA edit in the boot file to avoid any OOM errors.

At this point the numbers have all been right and they were stable in x32, and, x64 is more stable than x32! So what ever this is it appears to be either OS corruption related or something in that system simply does not play well with x64


If you wish to stay on x64 and run 1600 7-7-7-20 1T PL6-if possible (DRAM STATIC READ DISABLED) thats up to you.

Going over this in my head I just do not see anything in a wild-card here and if none of the items I suggested above has any effect then I really do think this is either a bad OS install or something in the hardware not playing nice on 64

NickN wrote on Jan 12^th, 2009 at 12:01am:


Will do.