Can any1 confirm if my irqs are ok??

[Clunk]

One thing has just struck me.....

I see your ram is at ddr800, Im guessing that the cpu is at stock and youre using the divider to up the ram? If so, this could well be the problem, and my board also has similar problems to you when I use certain dividers at certain a fsb. If you can set it to 1:1 and try orthos again.

I'm having a similar problem to you with ram dividers, but I didnt realise that you were using one, thats why I havent mentioned it. DOH.

Let me know how you get on with 1:1

[Supershanks]

800 is what the bios selects on auto.
9x267 = 2440 @2:3 = 400 ddr2 = 800 yes??

will give it a whirl.

[Clunk]

I dont use auto, I just select the first one in the drop down box for 1:1 and it should be 266 = 533 ram.

I think this could potentially be the problem. orthos 1:1 ftw

Edit: Ill set mine to 266cpu and 800mhz ram and set orthos going and see how long it lasts.

[Supershanks]

Just starting to feel quiet cocky running as u say at:-
Stock1-1 probably around 30min in when i've been hit by 2xbsods. 1st running 2nd on reboot. It could be that write to precharge delay which we slackened to 12 or vdimm needing tweaking at 1.90v. have left pci-e on 205 which seems good, pci locked at 33.3 & spectrum off.

These ex amd newbies
Have been looking at oc reports & thinking well yea 1:1 is fine when your running 9x400 or 8x500

[Clunk]

Bugger, only 30 mins? you sure its 205 for the pcie? mines 100, 101, 102 etc? but auto should be fine at stock. Could try setting the ram by spd as well, just so everything is bog standard.

[Supershanks]

lol 205 was a typo 105

Could try setting the ram by spd as well, just so everything is bog standard

That's waht i did sorry piccy didn't show will edit it. went auto with sdpd as i said, the vdimm scales rto 1.90v on auto & the write to precharge delay is at 11 from spd. thought 1 or the other needed lifting. tried 12 but got another bsod(3rd). So have now upped both. vdimm a notch 1.925v & 12.

Am now at 33min Orthos i'm running blend now thought i'd changed but previos test was small ffts.

[Clunk]

What voltage are they meant to run at? 2.1?

[Supershanks]

2.2~2.3 at 1000.
nearly got the hour up when it bsod with page fault, this is usually a memory errror, have not had any 4 a cuople of days. so upped vdimm again 2 1.95. Bsod again just after restart up again now at 1.975v which is pretty well where i started when 1st got the 1st mobo

will keep going & see where it gets. i'ts just raelly getting the right memory settings for 1-1, which should be capable of being tighter/lower vdimm than running 800 i guess.

[Clunk]

Maybe yours need the full 2.3v even for lower mhz? give it some welly Are they D9s? These ive got need 2.35v

[Supershanks]

Have just had 3 bsods in a row the gfx 8e is back. This is a pattern im all to familiar with. Cleared cmos & get f1 to enter setup f2 load defaults. try loading defaults it hangs. retry use f1 save & exit. Try again won't post power light for reset & power button on mobo are on but the clear cmos button which is also lit when operating is off. Only way round this is to pull batteryloded back in the stable (well for this rig ) i've been running earlier today.

This after 1 more bsod has settled back to howw it was running @800 Here's one i made earlier 2:3 800 Now i just confirmed that Dram frequency was set to auto & did result in the shots you see in the link

As you can see from the piccy i've had stable ram at 2.15

so will try that as a 1:1 voltage.start point .

See DDR2 full specs D9GKX chips.

I've had bios corruption/issues b4 but that's when pushing a heavy oc, not when jjust changing voltage up a notch, running at stock.

[Clunk]

Dont forget about the vdroop

Did you try the other ram slots yet?

[Supershanks]

not bothered about vdroop as vcore is just on auto.vdroop is anbout 0.03 going to about .05 over 1.3v. On my 1st board when temps were high i'd oc on auto vcore then find i could get stable by dropping vcore a notch. At this speed i hope vcore isn't an issue.

Did you try the other ram slots yet

no not yet results i'd had earlier in the day made me think i was fairly close to getting there so was the thing to try next if tonights orthos failed.

Going from the settings i'd saved & loaded back, just dropping the dram frequency back to feels reasonably stable again. 2.15 vdimm is what i used for the memtest run hve been running today at 2.175v so am at that now.

Will see how it goes.

Edit Hey clunk fancy doing a tv programme (no not on the buses)

[Supershanks]

Got 1:40hr that run vdimm to 2.2v am going to switch orthos to largr ffts as atm all i'm seeing ia blue screen so unsure wether it's failing on small fft (cpu) or large fft(memory).

[Clunk]

Edit Hey clunk fancy doing a tv programme (no not on the buses)

Haha, can you imagine the french viewers trying to understand a Salford accented video review? SORTED!

[Clunk]

oops, sorry double post.

[Supershanks]

Haha, can you imagine the french viewers trying to understand a Salford accented video review? SORTED!

Hehe Nay problem

Had a run of just over 4hrs @2.25 auto(spd) timings except for write to precharge delay is at 11 in spd but needs to be 12. Brginning to think Orthos doesn't actually report errors just bsods. I just keep the log running in tat so i can see what cpu temps where & when failure occurs.

In effect i'm running exactly as i was set up at 800 just with a higher vdimm.