2009 is NOT my year

[NickN]

You got my number...

The flu meds knocked me on my arse last night. I swear a good blast of night time flu meds are a better drunk than a 1/2 a bottle of Disaronno Amaretto when your head is swolen from the flu

does not take much

I am feeling better this morning though. finally



Remove the bufferpool entry and try this again

[vgbaron]

will do when I get home tonight.

Glad you're on the mend!

[vgbaron]

Removed BP - in DSX fullscreen mode - flying LA basin at dusk with lots of lights, etc - about 15 min into flight approaching LAX I saw a few large white tiles - as I turned out toward the west and the ocean I suddenly got pic 1 - hard to tell but I am straight and level, ocean below and sky above with part of coast on right.

Immediately hit Alt Enter and pic2 is the result. Flew for another 5 mjin or so with no issues.

Think there'd be any benefit is switching memory sticks? Same stix, white slots just swap a&b? I ask mainly because if not an issue I'd like to keep my hands out of the box.

[NickN]

LOL!


I have never seen any error like that before


When you back the memory down do you get any of this?

Drop the FSB down to 420 and see if this still shows up

[vgbaron]

Still with BP deleted - FSB 420 -

[NickN]

Strange

I have seen a lot of errors in FSX but those are a first for me


Looking something up here....

[NickN]

Vic

I dont want you to go any higher on VTT. Consider 1.35 your max

I want you to set the system to 400FSB and the memory back down to 1600 7-7-7 1T PL6 and check this again with everything else the same.

If you see this error at that speed there is something wrong and it is not memory

[NickN]

Set VTT back down to 1.3 and CPU GTL's back up to -40 too

If you see the error again @ 1600 could try swapping the Corsairs with the mushies since the settings are exactly the same @ 1600 and check it again

but if that error comes back I think there is something else afoot here

[vgbaron]

reset to 400 - the GTL's were at auto in this profile. VTT 1.28. Memory 1600 7-7-7-20 2T PL7

Flew FSX dusk LA basin for over 40 minutes w/o a hiccup.

[NickN]

reset to 400 - the GTL's were at auto in this profile. VTT 1.28. Memory 1600 7-7-7-20 2T PL7

Flew FSX dusk LA basin for over 40 minutes w/o a hiccup.

Alright

Something just does not jive

Im going to throw out a wild card

Crank it back up to 430 and 8-8-8-24 1T PL6 (I thinks that is what you had)

VTT 1.10/ Also try 1.20

CPU GTL

[vgbaron]

What did you put in that Bacardi??

Set it up at 430 1721 8-8-8-24-1T pl7 ( thought I'd sneak up on 6) with GTL's at +70 nb GTL +60 CHa&B +25 Vtt 1.10

3DMark ran fine score 14943 - about 4500less than PL6

Flew dusk LAX as before about 1/2 hour - not a problem!

Did they change the BIOS again???

[NickN]

I dont know Vic but thats why I shifted numbers back to the old math because this was just off the wall and not making sense

Leave everything else the same and pump it back up to 450

1800 8-8-8-24 1T PL7 (PL6 wont be possible at 1800)

on VTT you can go as high as 1.30 but start at 1.1, 1.2, 1.28

[vgbaron]

will give it a try tonight.

They must have reset the bios or something. Some of the clocking forums had the low Vtt and +70 GTL but that was on the 0501 bios.

Whatever - we seem to be on the right track.

Just as a fyi - still was getting about 26fps(30 lock) at night around LAX. Using Gexn, special AG, UTX, ASA weather, etc - that's amazing to me.

For now, unless you think differently, I'll leave the BPools out until we reach a stopping point.

Off the wall though - couls *whatever* this is have affected the other issue re the secondary IDE?

[NickN]

+70 represents .63x in any other BIOS with VTT 1.10 (1.10v x.63= .693) if the BIOS math is using the standard method of calc and then does the rest behind the scenes.

[vgbaron]

LOL - I was just beginning to get a little paranoid. I know I'm not an expert but I'm not a total klutz either and I've been searching through my memory as to what steps I might have taken to screw it up. Couldn't really find anything I did that wasn't documented.

I often wonder about BIOS and driver programmers - the way they pop these things out frequently....do they just take the last one and apply a fix, or start from scratch (doubtful) or whatever method.

Fix one thing, break ten, that's job security.