A7V133/A7V and Mosel/Mushkin Rev2... warning of a problem.

[Dulanic]

I wanted to put out a warning, there is a problem with the latest BIOS 1002A for the A7V133. This new BIOS enables some memory feature that Mosel/Mushkin do NOT like, you will find random amounts of memory will showup at POST... usually 128MB will show as 64MB sometimes even 32MB. So far the only known memory to have this problem is Mosel Rev2 or Mushkin Rev2.

To fix the problem just revert back to BIOS 1001D instead. Unfortunely right now we can't get the extra memory performance 1002A offers if you own this memory.

The new A7V 1006 BIOS also seems to enable these memory features that cause this problem... I have confirmed the problem with the A7V133 1002A BIOS, I will do some more testing with the A7V 1006 BIOS to be double sure.

Also this problem only happens with Cas2 settings, with Cas3 it is fine.

 

[Nu2PC]

Dulanic,

Thanks for the rapid reply to my earlier post. Actually, I just tried flashing back to the earlier bios and this too sees my ram as only 64 instead of 128. I hope that there is a solution soon.

My fault I flashed to 1001c not 1001a.

 

[Nu2PC]

Damn. I can't find 1001d at the asus site and all of the sites that have links, all link to dead pages. Anyone know where I can get this bios version?

 

[nealh]

Are you sure about the bios 1.001D ...can not find this anywhere

 

[Spook]

I've never had a problem with it reporting incorrectly... Does it cause any kind of instability problems?

Where did you get this information?

 

[Spook]

I'm using Mushkin 256Meg Rev 2 Dimms x2... 512Meg... I just booted, and rebooted about 10 times, all cold boots... And I came up with the proper amount every time...

 

[SaturnX]

Spook: What BIOS version you running?

This is not good.. I just bought some Musking Rev 1.5 when it was on sale during xmas and I plan on picking up an A7V133... oh great.. I guess I'll have to run it at CAS3 if I get the above.

--Mark

[Edit]
Is there any officially released info about this? Or is it just from experience?
[/Edit]

 

[Spook]

I'm running the bios he's talking about... 1002a... in CAS 2, at 133Mhz..


I hear you, I'm thinking the same thing... I wanted stability, So I went with the more expensive Mushkin, over Crucial... I don't want to think I just pissed $370 away...

 

[Dulanic]

Its not a big deal, it really seems to be mostly Mosel, Ive talked to a half dozen people who had this problem, and reverting to an older BIOS worked for all. It just seems Asus turned on some option that some Mosel RAM doesn't like. Why it only seems to effect Mosel I'm not sure. BTW Im not 100% sure on Muskin.... only known 2 people with this problem with Mushkin. It really seems to be luck of the draw on the RAM.... some people it works fine, some others it doesnt.

EDIT: I uploaded the 1001D BIOS.
1001D BIOS

 

[Dulanic]

BTW I did find that the RAM it did detect was 100% stable, so if all your RAM is detected don't worry about it, youll be fine. And if you find it doesnt detect all your RAM just go to the 1001D BIOS (For A7V133... or 1005 for A7V)

 

[Nu2PC]

Dulanic,

I used your 1001d bios file and I still have the same issue.:|

 

[Dulanic]

You may have a different problem, maybe some of your RAM is bad. Try the RAM in a different board if possible? Or try different RAM if possible? Or even try moving it to a different slot on the board.

 

[Technonut]

I had the same problem with 2 256MB sticks of Infineon PC133 when I flashed to the new BIOS on an A7V133 that I was trying out. Almost everytime I rebooted, it would come up with an incorrect amount of RAM. So it appears that the issue is not isolated to Mosel chips. The RAM was CAS3, but the same Infineon chip #'s that Mushkin uses on their Rev. 3. I of course was running it at CAS2. The Infineon works great in my KT7AR, and I have run it at 150MHz just fine, but had to up the I/O voltage to 3.6 to have it stable, and run at 1350MHz, so I am back to a smooth 1400MHz with the Infineon at 140MHz CAS2 Turbo, 3.5V.

I have a few 128MB sticks of CAS2 PC133 Crucial around, and may test it out in the A7V133 to see what it does.

 

[Dulanic]

I guess the issue is with Mosel it even happens at 133 CLS2 for some people, that shouldnt happen since its PC143 Cas2. Ive tested my RAM up to 155 Cas2 and its fine, but with the 1002A BIOS even at 133 Cas2 it only shows some of the RAM. You where OCing your RAM so that could be that your RAM just couldnt take the better settings 1002A uses.

 

[nealh]

Is the bios 1.001D better than 1.001C and is it an official bios file or a hacK????

Neal

 

[Dulanic]

It is an offical BIOS.

 

[lundog22]

Hmm thats interesting guys. I am runing the 1002a BIOS too.
But I got no problem with my 2 128MB KingMax PC150. I run them @ 143Mhz Cas2.

Weird

 

[delray]

I have a similiar problem on my Iwill KK266--have 2x128MB's Mushkins Rev2 sticks--when overclocking at Cas2 at 150 bus and everything set to turbo in memory, I get a reading of only 128MB'S---when I change it to Cas3 and Turbo, all 256MB's appears---only slightly lower in memory scores---try this and see if it changes anything for you!

Delray

 

[tpetre4322]

maybe reseat ram, vacuum out dust bunnies, i know the a7v133 takes alot of force to seat the ram, my findings with my ram pc133 micron generic 2x128, it will run 143 7ns setting up to 8.5x143 this is a 1gig penciled, above 143 i have to switch to cas 3,2,2 and iam stable to 152x8 this is 1.75 vcore for both.

 

[BayouL]

To add my two cents. I have the 1002a BIOS on my A7V-133 with 512mb RAM, 2x256 Mushkin Rev 2, and have not experienced any problems.

BayouL

 

[Dulanic]

<< maybe reseat ram, vacuum out dust bunnies, i know the a7v133 takes alot of force to seat the ram, my findings with my ram pc133 micron generic 2x128, it will run 143 7ns setting up to 8.5x143 this is a 1gig penciled, above 143 i have to switch to cas 3,2,2 and iam stable to 152x8 this is 1.75 vcore for both. >>



Not the problem.... like I said Im not alone.... about a half dozen people with Mosel I have personally talked to.... if they are using 1001D all is fine even past 150 FSB.... use 1002A and even 133 2-2-2 wont work right.

Anyways Im about to try the new BIOS 1003.

 

[BayouL]

Forgot to add that my sticks have the Infineon chips, so it may not pertain to the current situation. Sorry.

BayouL

 

[Dulanic]

From first testing 1003 seems to fix it somewhat. I was fine all the way up to 147, but for now Ill keep 1001D and 150FSB, and just use WPCRSET to get the performance of 1002 and 1003.