Phenom 9500 w/ MSI K9A2 Platinum

Quote:

---

Originally Posted by jesteronyer6

I flashed to the POH BIOS last night all went well it seemed I setup AOD to run at startup to disable TLB and then this morning my wife booted into Windows and it froze and gave a high pitched noise. I was sleeping so I told her to just turn it off and I went down stairs later and it is in a continuous post loop go's through the drive check my 2900XT red light flashes then it starts over I tried clearing the BIOS with the jumper I even took a stick of RAM out but it is stuck in this loop. I pulled the battery out of the board and unplugged the PSU and came to work any ideas?

---

You did set BIOS defaults before you flashed, right?

When did you get this problem, running stock or overclocked?

What did you type to flash the P0H BIOS?

If it froze on booting after Windows basic libraries, then maybe you have something starting up which is causing this, i.e. AOD Assistant. I never leave this running as it usually causes me this problem (freezing).

This BIOS is the most stable so far. A BIOS doesn't cause such a problem, the rebooting and whatever caused the freezing is what will cause no subsequent bootup. You might also have had a power surge/spike. Can you verify if you generally experience electrical problems at your house?

Can you check your power supply voltages idle/load?

Leave it off yet. The reboot loop will mean BIOS isn't clearing. You will have to only try one DIMM after clearing for over 30 minutes and shutting down power whilst doping so with minimal peripherals connected to get into the BIOS, set everything up at stock and then reboot.

EDIT:
Dave I've just seen a 0749[mxxw] and it's so far hitting 3.0-3.1GHz at 1.3-1.312V stable stock cooler. Test your CPU fully, yours is the closest batch. ;)

Quote:

---

Originally Posted by KTE

The problem with disabling only one core specific is this:

How does Windows label core0/1/2/3? In which rotation and manner? (diagram)

If we can find out how then we can disable the same core2 always. When Windows usually disables a core, it will do it in numerical order only, rather than picking a core in-between to disable (i.e. core 3/4). That's a limitation I've not yet surpassed yet but maybe I have and don't know how to test up on it. :shrug:

---

The downcore control located on the Phenom NorthBridge
Bus:0h
Device:24h
Function:3h
Offset:BEh
Bit:3,2,1,0 = 0000000000000000b (All 4 core enable)

Bit 0 = Core0
Bit 1 = Core1
Bit 2 = Core2
Bit 3 = Core3

Register Definition:
0b = Enable Core
1b = Disable Core

Example: Toliman :hehe: Tricore
I want to disable core3 = 1000b
I want to disable core2 = 0100b
I want to disable core1 = 0010b
I want to disable core0 = 0001b

Code:

---

Host Bridge
bus 0 (0x00), device 24 (0x18), function 3 (0x03)
Common header
Vendor ID 0x1022
Model ID 0x1203
Revision ID 0x00
PI 0x00
SubClass 0x00
BaseClass 0x06
Cache Line 0x00
Latency 0x00
Header 0x80
PCI header
Subvendor ID 0x0000
Subsystem ID 0x0000
Int. Line 0x00
Int. Pin 0x00
Capabilities
Secure Device Capability
Offset F0h
Dump
0 1 2 3 4 5 6 7 8 9 A B C D E F
00 22 10 03 12 00 00 10 00 00 00 00 06 00 00 80 00
10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30 00 00 00 00 F0 00 00 00 00 00 00 00 00 00 00 00
40 FF FF FF 3F 44 00 90 0A 00 00 00 00 00 00 00 00
50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60 00 00 00 00 04 00 7F 12 00 00 00 10 52 80 01 00
70 53 11 04 00 01 01 18 00 14 0C 20 00 14 09 09 00
80 81 83 00 E6 E6 41 E6 00 08 00 00 00 00 40 40 00
90 00 00 00 00 0B 6C 00 00 00 46 81 B5 00 00 00 00
A0 00 29 0A 80 80 98 1C 10 00 00 00 00 00 00 00 00
B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D0 00 00 00 00 29 0F 81 C8 16 18 00 03 28 51 00 00
E0 00 00 00 00 30 12 00 00 99 3F 07 02 00 00 00 00
F0 0F 00 10 00 00 00 00 00 00 00 00 00 22 0F 10 00

---

Edit the register with WPCRedit or Read&Write tool then RESTART.
Good Luck :up:

Thanks Cutie :D

I'll try it in a moment.

Make sure Offset:BEh using 16bit access mode ;)
or Offset BCh using 32bit access mode
or Offset BFh using 8bit access mode

make no mistake ok :nono:

Quote:

---

Originally Posted by KTE

You did set BIOS defaults before you flashed, right?

When did you get this problem, running stock or overclocked?

What did you type to flash the P0H BIOS?

If it froze on booting after Windows basic libraries, then maybe you have something starting up which is causing this, i.e. AOD Assistant. I never leave this running as it usually causes me this problem (freezing).

This BIOS is the most stable so far. A BIOS doesn't cause such a problem, the rebooting and whatever caused the freezing is what will cause no subsequent bootup. You might also have had a power surge/spike. Can you verify if you generally experience electrical problems at your house?

Can you check your power supply voltages idle/load?

Leave it off yet. The reboot loop will mean BIOS isn't clearing. You will have to only try one DIMM after clearing for over 30 minutes and shutting down power whilst doping so with minimal peripherals connected to get into the BIOS, set everything up at stock and then reboot.

EDIT:
Dave I've just seen a 0749[mxxw] and it's so far hitting 3.0-3.1GHz at 1.3-1.312V stable stock cooler. Test your CPU fully, yours is the closest batch. ;)

---

I did not set the BIOS to defaults. :(
I was not overclocked I have given up on that I was running stock.
I have the computer plugged into a battery backup system so I dont think it was a surge.
I used the USB Flash program to flash the BIOS.

Edit: I just called NewEgg for an RMA I am sending this board back now which board should I get the DFi or ASUS with the 790FX chipset?

I read about the core2 issue some people are having.

Question: will disabling core2 grant stability and/or higher oc?

Quote:

---

Originally Posted by tictac

Make sure Offset:BEh using 16bit access mode ;)
or Offset BCh using 32bit access mode
or Offset BFh using 8bit access mode

make no mistake ok :nono:

---

It didn't work tictac :(

When I restarted, the 1b went back to 0b. I set 1b for core2 (0100b) and restarted. This is what I got after restart:

Attachment 72720

If I use Windows to disable a core would that not change this register?

Quote:

---

Originally Posted by jesteronyer6

I did not set the BIOS to defaults. :(

---

Ah well, there you go. :(

Quote:

---

Edit: I just called NewEgg for an RMA I am sending this board back now which board should I get the DFi or ASUS with the 790FX chipset?

---

If they check the BIOS you had flashed (a BETA) you'll get the board back again since you weren't warrantied to do that. :(

I also doubt very much the board is dead, they don't die like this. It looks like your old settings causing problems. They can put an X2 into it and have it started up IMO.
Between those two I would chose the ASUS, but I'm not saying it's worth it or you'll get miracles with it over this board at all. It's very similar, better BIOS though.

i will check back later. thx

Quote:

---

Originally Posted by jesteronyer6

I did not set the BIOS to defaults. :(
I was not overclocked I have given up on that I was running stock.
I have the computer plugged into a battery backup system so I dont think it was a surge.
I used the USB Flash program to flash the BIOS.

Edit: I just called NewEgg for an RMA I am sending this board back now which board should I get the DFi or ASUS with the 790FX chipset?

---

Before you do that(RMA),please try this:
http://www.msicomputer.com/support/B...I_Recovery.asp

Quote:

---

BIOS Recovery Feature

For AMI BIOS

1. Rename the desired AMI BIOS file to AMIBOOT.ROM and save it on a floppy disk. e.g. Rename A569MS23.ROM to AMIBOOT.ROM
2. Insert this floppy disk in the floppy drive. Turn On the system and press and hold Ctrl-Home to force update. It will read the AMIBOOT.ROM file and recover the BIOS from the A drive.
3. When 4 beeps are heard you may remove the floppy disk and restart the computer.

---

Quote:

---

BIOS Recovery Feature

For Award BIOS

1. Make a bootable floopy disk
2. Copy the Award flash utility & BIOS file to the said floppy disk.
3. Create an autoexec.bat with "awdfl535 biosfilename" in the content e.g. awadfl535 a619mj21.bin
4. Boot up system with the said floppy (it will take less than 2 minutes before screen comes out)
5. Re-flash the BIOS & reboot.

---

If this doesn't work out,try it again but before doing this time remove the battery and clear cmos.Leave the system 30 minutes,then put back the battery and try the procedure described in the Quote above .

Hope it helps,good luck!

Does anyone know what the extra set of pins next to the CMOS reset jumper is? I couldn't find any docs on it. I was really hoping you guys were going to tell me it was a static/backup bios... :(

I pulled one stick of ram, still no post (monitor doesn't even light), so I pulled the battery, unplugged it and left the jumper in the reset positon till I get home from work tonight.

KTE: Yes, I reset to stock speeds/no OC before I flashed, but I didn't use those switches... The wierd thing is I used the same method to flash as Jesterone (USB drive). Oh well, guess I'll find out tonight if it worked.

Jon: Unfortunately I don't have a PCI VidCard so thats not an option. But thanks for the suggestion.

Quote:

---

MSI Tech. 02/21/2008 The answer is no... Will there be an official release bios that allows you to enable and disable the TLB fix? No, since it need to have it enable all the time.

---

:down:

Quote:

---

Originally Posted by KTE

I've tried nearly all the ways to clock Phenom and found the best, quickest and most accurate understanding giver is by working your way up slowly moving from one perfectly stable setting to another. :yepp:
I usually try max valid and max benchable before this though, but after this too.

---

Was an easy go up to 2.5GHz by just increasing vcore and the multi. Normaly I oc the same way you do.

Quote:

---

Originally Posted by KTE

AFAIK the multipliers and PLLs are separate, hence the no effect. Otherwise, there certainly would be.

---

I thought about the tlb bug. He occures in an timeframe whom is affected by both frequencies cuz the core and the l3 cache are involved.

Quote:

---

Originally Posted by KTE

Check out these articles.

1. The following AMD CPU's compared for power efficiency: http://www.tomshardware.co.uk/proces...iew-30178.html


Unfortunately, they made a crucial mistake. They used BIOS P0F which disables the TLB Fix only on the first core and not on the other three (unless done manually). Pity, it would've been useful.

---

Very interesting together with the comparison of intel cpu's. Got an qx6850 ES today, rest of the system arrives tomorrow. Will have that stuff for about two weeks. During all my ocing I ran cinebench 10's opengl and multi-cpu benchmark and noted points/time used and temps and power consumption during the cpu benchmark, so i can do a similar comparison between my be9600 and that qx6850.
BTW: Also an 5000be arrived here today, so much to play with. :)

Quote:

---

Originally Posted by KTE

2. X2 K8 and X4 K10h compared throughout the clock ranges: http://209.85.135.104/translate_c?hl...-phenom-22756/


Very useful IMO as they tried to show the max possible for Phenom by 2008 compared to what we can already have with X2 (and more really). I'm not sure about the NB though as I'm pretty sure unless they manually clocked it down, it would be 2000MHz which is 200MHz more than retail Phenoms so far. Not a large difference generally if any at all, but in memory sensitive applications, it can very well be.

Happy reading. :)

---

Not yet finished.

Quote:

---

Originally Posted by informal

Before you do that(RMA),please try this:
http://www.msicomputer.com/support/B...I_Recovery.asp

Hope it helps,good luck!

---

INFORMAL: I know your post was directed toward Jester, but I'm experiencing a very similar problem and that looked promising. Unfortunately it didn't work on my machine... Thanks for the link though, may come in handy in the future.

JESTER: Just curious if you flashed the same version of "P0H" that aGeoM linked back on page 50? Thats the one I used and I'm having similar problems. Although mine never even posted after the flash...

aGeoM: Did you get your version from that link, and did it work OK? I'm certainly not accusing you of anything malicious, but If it's a bad file I'd hate to see someone else flash a bad bios.

I've looked all over and still can't figure out what the jumper right next to CMOS reset does (JCI1), but I'm assuming it's not the backup bios I was hopeing for...

Not sure what I'm going to do now.... :zombie:

Thanks Informal. :)

You don't happen to play Urban Terror 4.1, do you? :D

Quote:

---

Originally Posted by Oc-Ghost

I read about the core2 issue some people are having.

Question: will disabling core2 grant stability and/or higher oc?

---

It really depends from chip to chip. I definitely agree there is a weak-er core within Phenoms compared to the other three, but it's not always core2, it's been core1 and core3 aswell.

Disabling it should allow higher MHz, higher MHz benchable, higher stable MHz, high MHz at lower volts or a combination of these if it really is the setback. It's up to the user to test and find out whether it is.

The problem is, with Phenoms each core has a separate PLL, they are independent clockers. You can use AOD to keep one poor clocker at stock when oc'ing and you can see very clearly if you will get more MHz (etc) on the other ones. With most users there isn't much increase at all. The ASUS RD790 already has users doing this with their oc's.

Quote:

---

Originally Posted by Daveburt714

Does anyone know what the extra set of pins next to the CMOS reset jumper is? I couldn't find any docs on it. I was really hoping you guys were going to tell me it was a static/backup bios... :(

---

Not sure really. Don't have the board here to check either and from memory, I think you're referring to two pins? I haven't seen any documentation on them that I recall. Will checkup later when I get back to flat. It won't be a BIOS backup though.

You guys all flashed the same file it seems, because others haven't had this problem yet (many I know who have flashed it). I've flashed/re-flashed it at least 8/9 times. I flash the files on my disk (originals) and I've had zero problems with P0H but you will get these problems with many BIOSes on all boards if you don't set defaults before flashing, if you don't use the switches and if you don't CMOS clear and then power down after flashing (for BETA's) before starting up. You're all encountering pretty much the same problem here.

Let me know if you've both flashed the file aGeoM linked and I'll hunt him down.
I'm kidding. :D
I'll flash the file myself and see if it's the file that's corrupt.

Also, clear CMOS and then power down, i.e. switch the power supply off or disconnect it. Leave it like that for an hour. Then connect again and restart with a minimal build. Does it POST (keep pressing Del)?

Quote:

---

KTE: Yes, I reset to stock speeds/no OC before I flashed, but I didn't use those switches... The wierd thing is I used the same method to flash as Jesterone (USB drive).

---

I always use the failsafe and established stable method and through good [nightmare] experience across boards too. :yepp:
Many boards react differently but FDD flash is always set to work right. You should always use the pbnc switches or you're setting yourself up for error, especially with BETA's. The good thing about FDD's is that you can access them on all systems in all ways.

Behind the scenes the amount of troubleshooting I do is really ridiculously tedious when dealing with a new platform, like this. It comes part and parcel of "BETA testing" though.

Quote:

---

Originally Posted by jonspd

Quote:

---

Originally Posted by MSI

MSI Tech. 02/21/2008 The answer is no... Will there be an official release bios that allows you to enable and disable the TLB fix? No, since it need to have it enable all the time.

---

:down:

---

I strongly hope he was talking out of his rear there. :mad:

I'm now planning on getting rid of the board actually and maybe swapping to see if other boards have made any progress.

BTW, those replies are pretty poor. Maybe you should tell him that we pay not the other way round. :down:

Quote:

---

Originally Posted by justapost

Very interesting together with the comparison of intel cpu's. Got an qx6850 ES today, rest of the system arrives tomorrow. Will have that stuff for about two weeks. During all my ocing I ran cinebench 10's opengl and multi-cpu benchmark and noted points/time used and temps and power consumption during the cpu benchmark, so i can do a similar comparison between my be9600 and that qx6850.
BTW: Also an 5000be arrived here today, so much to play with. :)

---

Nice, looking forward to it. :)

The QX6850 is hot though, you'll need a good cooler or it'll start throttling under loads as it reaches plus 85C with many aftermarket air coolers. So results might be less than accurate if it does.

@KTE
Not playing UrbanT. (not really a Quake mods player :) ),but will DL it later today and see if i can hit someone :D.
I do play Americas Army ;).

@KTE
Scrap the MSI board and get a DFI and learn us how to tweak the phenom with it:bows:

informal: I play it to check my system at times. Only game I still play randomly (or HL2:LC), dropped gaming since my studies started. :(

Jaivan: If only I knew how. :D
I can't find the DFI board here anymore, I am after it though. :(

Can you tell me which BIOS you're running and how stable it is? (any major issues)

Official BIOS 1.3

change log

- Support AM2+ CPU.
- Update CPU Module.
- Update SATA ROM version.
- Update Promise ROM version.
- Support memory EPP mode

Quote:

---

Originally Posted by KTE

I strongly hope he was talking out of his rear there. :mad:

I'm now planning on getting rid of the board actually and maybe swapping to see if other boards have made any progress.

BTW, those replies are pretty poor. Maybe you should tell him that we pay not the other way round. :down:
Nice, looking forward to it. :)

---

we shall see soon enough I would also make a move to another board but at this time when b3 comes I will give it a go and if I'm still not happy then I quess I will be off to intel land :D:ROTF:

Quote:

---

Originally Posted by Jaivan

@KTE
Scrap the MSI board and get a DFI and learn us how to tweak the phenom with it:bows:

---

I have been playing around with the MSI 790FX board since release, while I am not completely impressed with it, for me alteast it feels like a waste of money to replace it with another motherboard with the SB600. I will happly replace the K9A2 when the SB710 790FX motherboards are released.

The issues we are having with the first round of 790FX motherboards are very similiar to the issues that around with the first 754 socket motherboards where released. Bios fixes where promised and in the end the only solution was to buy the latest motherboard with the fixed features.

Thanks madfaze. :)

Quote:

---

Originally Posted by madfaze

Official BIOS 1.3

---

CRAP! :mad:

Recommendation: Stay away!!

Includes TLB Fix by default with no options to turn it off. No more options than the last official BIOS, only CPU/HT multiplier and voltage controls in BIOS for oc, nothing else. Abysmal BIOS for oc and performance.

It may offer good compatibility and support issues for others but not any for me that P0H doesn't. It also allows running all memory dividers.

Look at the performance, this is worse than a single core P4 at 3.3GHz. Who the heck does MSI think will buy a Phenom+MB for this performance? :down:

Attachment 72753


Obviously I can mod it to have proper performance but that's my own (and others) painful research and testing, MSI didn't allow. I am now seriously looking at modding one of these BIOSes because I'm getting fed up.

I think msi might have there head in the wrong place :D

nice performance gain lol

Quote:

---

Originally Posted by Daveburt714

INFORMAL: I know your post was directed toward Jester, but I'm experiencing a very similar problem and that looked promising. Unfortunately it didn't work on my machine... Thanks for the link though, may come in handy in the future.

JESTER: Just curious if you flashed the same version of "P0H" that aGeoM linked back on page 50? Thats the one I used and I'm having similar problems. Although mine never even posted after the flash...

---

Yep that is where I got it and I couldnt recover the BIOS the board is shipped back to the etailer.

@KTE
Well I find that the DFI is more stable and can overclock the HTT higher, but my Phenom is the problem it won't do more than 2.42ghz stable.
I had a Gigabyte DS5 before the DFI and i couldn't reach 245 HTT stable on it while with the DFI I'm currently running at 255 HTT stable haven't really tested to see if it could go higher since I'm pretty happy at this speed for now.
Compared to the Gigabyte the DFI has better features and for me a more stable BIOS. There were lots of freezing in the BIOS on the Gigabyte and I think that it didn't like my RAM since sometimes it wouldn't even post and I would have to remove two sticks to get it started. I get none of those problems on the DFI.
I'm Currently running the 01/30/2008 BIOS which is the latest non beta.
Oh BTW this is where I got my board from:
http://www.ncix.com/products/index.p...anufacture=DFI

Quote:

---

Originally Posted by jesteronyer6

Yep that is where I got it and I couldnt recover the BIOS the board is shipped back to the etailer.

---

Thanks Jester, I thought that may have been the one you used too.

I've done everything I know to do and followed the instructions per Informal & KTE... Mobo is just bricked... :mad:

KTE: Did you get a chance to DL that version of P0H? Personally, I wouldn't flash it just in case! But you may be able to run a checksum comparison with your known good copy.

The only other thing I can think of is that we both used a USB drive to flash the bios. Thats the first time I've ever used that method, but everything seemed to go as it should, ie: ran all the steps and completed as expected.

I'll get back to you all in a bit, just found some free time.

I heard midday today that there is a Phenom FX CPU yet to release within the next 3 months. FX-82 it was dubbed. Have yet to check online on it yet, will do after I start-up Phenom and flash the P0H you guys flashed.

[EDIT]

Yep, I'm sure there was such a model. Whether it'll still release or not, I'm not sure. No motherboard manufacturer lists Phenom FX compatible until they've fully tested and verified samples of this product. Infact, check out what I found listed on MSI site for our board:

Attachment 72816

Bit of a giveaway that. ;)


Guys, the BIOS file P0H aGeoM attached is fine, checksum is also perfect. I've flashed it without even setting defaults although I did follow the safe known procedure and did use the flash parameters.

http://img167.imageshack.us/img167/9486/poh2bz6.png

Heck, look at my lowest voltage 2700MHz boot so far... (no crashes)

Attachment 72815

It is safe and working. Looks like the method being the root error. :(
1.30 official release is based off P0H fully.

Jaivan: no DFI in this country, one I briefly tested is gone back to DFI for some reason so I have to get the Sapphire instead. I can get hold of the Sapphire, which is DFI half rebadged.

Quote:

---

Originally Posted by informal

@KTE
Not playing UrbanT. (not really a Quake mods player :) ),but will DL it later today and see if i can hit someone :D.
I do play Americas Army ;).

---

Does Phenom work with AA and PBuster,, I havnt tried to play it in several months..

P.S. KTE ,AA is a pretty decent shooter game.lots of maps to run on.
82 info will be interesting.

)x(ElitejArHead)x(

Quote:

---

Originally Posted by gOtVoltage

P.S. KTE ,AA is a pretty decent shooter game.lots of maps to run on.
)x(ElitejArHead)x(

---

Yea I know, the military would feed us it day and night. I trained with the military in 3 countries from '99-02 and then in '04 and we would play it very often. Haven't played it since late 2004 now, and I don't have it here either. There's no US military recruitment sites to give it away free here. :)

I can check it out if I could get it free to test somewhere, maybe even a playable demo. Did want to play v3.0 when it comes out though.

Quote:

---

Originally Posted by KTE

Guys, the BIOS file P0H aGeoM attached is fine, checksum is also perfect. I've flashed it without even setting defaults although I did follow the safe known procedure and did use the flash parameters.

---

Thats really strange... Must have been the USB flash procedure then, have you ever Flashed a BIOS like that KTE?

Now the even stranger thing is, I swapped out the PSU and the VC. Same results and they both work fine in other machines. I went and got a new board today, same results... I'll put the 9600Std back in tommorow, about the only thing left would be the 9600BE went bad... :(

Thanks Much for all your help Man... :up:
And sorry about muddying your thread with my problems...

hmm i updated to v1.3 how come i cant find those auto express option?!

@KTE
Well the only difference with the DFI and the Sapphire is that the Sapphire has an odd color scheme lol.

Quote:

---

Originally Posted by Daveburt714

Thats really strange... Must have been the USB flash procedure then, have you ever Flashed a BIOS like that KTE?

---

Never, not BETA's. Known to give random issues and be a problem causer IME. ;)

Quote:

---

Now the even stranger thing is, I swapped out the PSU and the VC. Same results and they both work fine in other machines. I went and got a new board today, same results... I'll put the 9600Std back in tommorow, about the only thing left would be the 9600BE went bad... :(

---

It won't have become naft but it looks exactly like the problem I've had many times after a CMOS clear or flash. The CMOS doesn't clear and keeps a mix of old and new values but throws the VCore too low and that results in no boot, maybe for many days.. until you go subzero with the chip.

Quote:

---

Thanks Much for all your help Man... :up:
And sorry about muddying your thread with my problems...

---

You're welcome. No need to apologize, I'm still alive. :D

Quote:

---

Originally Posted by madfaze

hmm i updated to v1.3 how come i cant find those auto express option?!

---

It doesn't have it, P0H does.

Quote:

---

Originally Posted by Daveburt714

JESTER: Just curious if you flashed the same version of "P0H" that aGeoM linked back on page 50? Thats the one I used and I'm having similar problems. Although mine never even posted after the flash...

aGeoM: Did you get your version from that link, and did it work OK? I'm certainly not accusing you of anything malicious, but If it's a bad file I'd hate to see someone else flash a bad bios.

I've looked all over and still can't figure out what the jumper right next to CMOS reset does (JCI1), but I'm assuming it's not the backup bios I was hopeing for...

Not sure what I'm going to do now.... :zombie:

---

Hi

The link it's just the upload from the bios posted in MSI beta bios. I had used no problems found worked with same settings used in 1.131 beta.

Quote:

---

Originally Posted by Daveburt714

Thanks Jester, I thought that may have been the one you used too.

I've done everything I know to do and followed the instructions per Informal & KTE... Mobo is just bricked... :mad:

KTE: Did you get a chance to DL that version of P0H? Personally, I wouldn't flash it just in case! But you may be able to run a checksum comparison with your known good copy.

The only other thing I can think of is that we both used a USB drive to flash the bios. Thats the first time I've ever used that method, but everything seemed to go as it should, ie: ran all the steps and completed as expected.

---

I use bootable USB pen, and run afud4184 BIOS.NAME normally.

I only use commands /n /pbnc for reverting to previous version eg. 1.P0H to 1.P0D.

Sorry if the file I uploaded make your boards brick, but it was to help you guys to have it without register in the German site just to download.:shrug:

@Informal I play AA mainly in Interdiction Map, but not playing ATM.

Quote:

---

Originally Posted by aGeoM

Hi

The link it's just the upload from the bios posted in MSI beta bios. I had used no problems found worked with same settings used in 1.131 beta.

---

Thanks aGeoM, no offense intended, it just seemed odd that Jester and I both had similar problems.. ;)

I put the 9600Std back in last night (on the new board) and did finally get it to post, but it's still acting strange... Looks like it may be a PSU problem after all.

BTW, aGeoM: I do appreciate you putting the file up for us!! :)

Got tired with phenom.
I just got new 9600BE with main giga 790FX DQ6, can not stable with 2.5ghz.
Changed to Asus M3A32 MVP, can not pass 2.5ghz too.
I tried near all options about volt. Sad about my phenom.

Apologies to all but I'm on holiday and so been too busy to get back with all I wanted. Brought the stuff with me here (car, not far) so I can speak details and reply to PM's later on but things will be very slow until after March 8.

Quickly speaking=>

aGeoM: we don't doubt you. As I said, I tested it and it's fine, it's the original file. The problem could only be with the method and functions used.

Jaivan: will get it as soon as I have office access. Need permission from uncle first and he's out of country yet.

linhvndiy: The 790Fx board you wanted to maximize Phenom is either the DFI or the Sapphire.

OK. Well been testing Phenom for many days now, +25 days rigorous. Here are my findings and trends. :(

Firstly, I went from 2.55GHz all the way up to 2.832GHz testing stability. My purpose wasn't to bench or take screenshots of Prime but to avoid the freeze/lockup after 2-3 and then 5 days.

*Moving up stability test/benchmark pass I reached 2.754GHz @ 1.3572V Prime 95/EVEREST/OCCT/Memtest fully stable. 20 hours for P95.
*No matter what cooling (air), ratio, volts was used, not a single MHz more was stable with stability testers.
*But when I tested real long term stability incl. freezing, the best +5 day stable was 2.7GHz @ 1.352V idle and 1.336V loaded. Fully perfect for over 7 days.
*I then moved to oc on various settings and didn't find any better again. So I reverted back after 5 days to trying to find stability with my most stable known, Last Known Good Conf in other words.
*However, now, 2.691GHz @ 1.512/1.506V was the max I could get stable. Yep, it really did require this voltage, 1.32V at 2.69GHz would reboot on load. More stability was possible below 2704MHz but yet to be explored.
*I then went ahead and tried higher than 2704MHz. All of them rebooted at any volts whilst I was idling, randomly and different periods ranging from 10 minutes to 11 hours. I could boot 2.832GHz maximum and benchmark it.
*However, when I now tried oc again to a lower spot in between 2704 and 2691 I found another phenomena. 2691MHz all the way to 2639MHz was not stable and was now rebooting randomly with an Ati VGA driver BSoD. Typical BSoD of instability (I analyzed the files). I dropped down to 1.456V and after 33 hours it froze again randomly while starting a YetiSport game (one of my tests).
*Trying anything from 2.618GHz to 2.639GHz with 1.56V to 1.3V was repeatedly calling the freeze.
*So for the past 11 hours since I got here I set it up and booted 2.613GHz at 1.408V and have been seeing if it froze. It still hasn't shown the freeze yet and is looking like the most stable setting so far... but for how long?
*In each case I tried all the voltage ranges, CPU/NB/RAM dividers, HT ref., and even with and without the TLB patch and with and without any videoing, stress, gaming and Firefox usage.

This is what I mean by not made to oc, look at the volts as well. Stability over 2.6GHz is just plain out random and hardly exists. ATM I'm at 2613MHz 1.392V idle/1.376V load, I had this setting stable for over 14 days at only 1.252V before and am not happy with the amount of MHz I'm losing day by day even with higher voltage. :yawn:

Has anyone else experienced similar happenings?
All my chips have reacted this way at top after one solid month.

BTW I'll have the Sapphire and the Abit boards soon to test but this MSI is also giving me a "USB device not recognized" random error very consistently where my mouse/keyboard stop working. Really does wind me up! :mad:

Hey KTE,

I've only had this board for a couple days (Gigabyte DS5), but if you get a chance you should check it out!

Flash the F3/F4f bios. Like I said, I'm still a noob on it, but the bios features work (pretty much) the way you would expect them to work, the one bad thing is that you can't control the NB v's but it actually seems like their TLB disable works! ;)

I like MSI, and I've been a fan for a few years, but it seems like they've given up on the K9A2 bios...

So far, I like this board MUCH better than the MSI offering... :up:

I have previously checked it out Dave. :p:
TBH I'm not fond if it, it clocks worse than the MSI and has less oc options than the 113 BETA. :(
The only one of GBT's lineup that is better in oc/stability is the DQ6.

BTW the MSI board has dropped in value a lot around places here I'm seeing while the DQ6 retains it's value.

Thanks a lot KTE.:D
I will try DFI. I think AMD need a lot of tweak for phenom.

Quote:

---

Originally Posted by KTE

BTW the MSI board has dropped in value a lot around places here I'm seeing while the DQ6 retains it's value.

---

hmm that's odd, does this mean that MSI is loosing its reputation as a good mobo? :(

Hehe... I want to show you all what ERRATA actually means. http://www.lazyforums.net/images/smilies/pukedesk.gif

Attachment 72998

Attachment 72999

Attachment 73000


DON'T BE FOOLED! That's just the clock generator going whacko, actual speed does not change from what we know and the core performance will show it clearly. The actual NB clock there is same as HT clock (1809/1809). That's not the maximum either, I've seen 4650x35 (162,750MHz NB) and 4650x2.66 (12,369MHz RAM) in those apps stock NB/RAM volts :lol2: :D

AMD has some very serious clock generator problems.

:rofl: :clap:

Quote:

---

Originally Posted by KTE

Hehe... I want to show you all what ERRATA actually
DON'T BE FOOLED! That's just the clock generator going whacko, actual speed does not change from what we know and the core performance will show it clearly. The actual NB clock there is same as HT clock (1809/1809). That's not the maximum either, I've seen 4650x35 (162,750MHz NB) and 4650x2.66 (12,369MHz RAM) in those apps stock NB/RAM volts :lol2: :D
AMD has some very serious clock generator problems.

---

You did all modifications with bar/wpcredit on a running system without a reboot i assume.

Hmm changing the nb multi requires a warm start says the bkdg. Can be the clock generator might need some sort of refresh command to display correct values if the multi is changed on a runnin system.
Polygon's bios-mod modifies MSR registers via the lan-boot module. This one should be loaded after the prozessor and stuff got initialized so the nb-multi change only confuses the clockgenerator.
If the nb multi is locked upward on the cpu the symptom is more obvious as the ref HT changes, with no nb-multi lock things look different.

Quote:

---

Originally Posted by justapost

If the nb multi is locked upward on the cpu the symptom is more obvious as the ref HT changes, with no nb-multi lock things look different.

---

not neccesary so. See here : http://img257.imageshack.us/img257/7...0tlbuj4.th.jpg

9500 nb multi x10 wich is not supposed to be possible. edited with BAR EDIT on the fly.

I already know that, I've been doing it since December. No Achim, it booted like that and it can get worse. It's like that since I booted for over 8 hours now. ;)

If I modify NB registers on the BE and try to boot, it won't boot because I need NB voltage which the P0H BIOS doesn't allow (stock voltage, see above). And my NB is downward locked, no POST with anything below 9x.

CPUZ Dump attached [worthless for this since this is a CPU error].

Quote:

---

Originally Posted by justapost

You did all modifications with bar/wpcredit on a running system without a reboot i assume.

Hmm changing the nb multi requires a warm start says the bkdg. Can be the clock generator might need some sort of refresh command to display correct values if the multi is changed on a runnin system.
Polygon's bios-mod modifies MSR registers via the lan-boot module. This one should be loaded after the prozessor and stuff got initialized so the nb-multi change only confuses the clockgenerator.
If the nb multi is locked upward on the cpu the symptom is more obvious as the ref HT changes, with no nb-multi lock things look different.

---

I am with justapost... I already state it back in barcelona :yepp:
http://www.xtremesystems.org/forums/...8&postcount=83

These processors can't be taking electron path dmg that quickly already can they? (forgot the technical term) Maybe that would be why Intel said native quad at 65nm wasn't practical... Granted AMD chips have never been spectacular OCers. But.... I can't see how that could happen if you're not running above stock volts, I was running 2.4ghz NB/IMC at stock nb voltage without issues, on 1.1b3. I've been considering going to P0H but don't want to if I can't do the nb thing. My luck with OCing nb on my phenom has either been stable at a voltage or no boot. For example I can do 2ghz nb at 1.1v VID stable, probably a bit lower too, never tried lowering it below that.

I was running 2.6ghz Core at 1.262VID 1.248v Actual for a long time, with the NB running at 2.4ghz 1.25v VID (according to AMD Power monitor). Had to lower back to stock recently to eliminate all possible issues trying to figure out if I was having a video card problem. Ended up having to RMA the 3870, wouldn't run graphics intensive games even with everything else at stock. Though I run perfectly stable with the 2600xt installed, granted it doesn't root out a possible PSU issue.

Don't really know, I can only speak on what we experience.
I have a problem where high MHz and overclock makes the VGA unstable, not load up of give BSoD's too. Even though the oc be Prime95 stable.

Quote:

---

Originally Posted by KTE

Don't really know, I can only speak on what we experience.
I have a problem where high MHz and overclock makes the VGA unstable, not load up of give BSoD's too. Even though the oc be Prime95 stable.

---

See thats the thing I don't get with mine. I was completely stable at 2.7ghz 1.262v VID 1.248v actual on the cores 2.0ghz 1.1v VID on the NB. Then after upgrading from the 2600XT to the HD3870, suddenly I'd get a machine check BSOD in games like Civ IV with the graphics set to high on 1680x1050 res. I'd get graphic corruption, then either that machine check bsod, or I'd lose video and have to reset the computer twice. Some times when it would come back up after the first reset, the windows splash screen would be way dark and not load beyond that, but after a second reset it would be fine, until putting a heavy graphics load on it, and that continued to happen even with everything at stock. Now I'm back on the 2600XT with no problems at all, had to RMA the 3870.

The bad thing about the machine checks was it never mentioned the video card. It always listed Processor, Power supply, Memory, or system board, even though I knew for a fact that the bsod's didn't start till after putting the 3870 in. I probably could of got a dud vid card, but like I said, it still doesn't rule out a weak psu. Won't be able to fix that part till either my quarterly bonus from work, or the $110 in rebates comes back from Raidmax.

You know something, my BSoD's relating to the GPU I only figured out after lengthy troubleshooting, the stacktrace and analysis logs didn't show anything but the CPU or RAM at error. Typically I had to uninstall and reinstall GPU driver many times to figure this out.
I was stable 1.28V 2.7GHz at the beginning as I've shown, which was then moved up to 1.344V for 2.754GHz. But now that is impossible without those dreaded freezes. The max I've had without freezes was 2613MHz. It's now at 1.28V idle at 2613MHz stable for many hours even benchmarking, priming and gaming without the random freezes. Still far off from 1.232V 2.6GHz stable as beginning.

I don't want to spread unsubstantiated FUD but I will tell you the honest facts to keep in mind. The TLB errata doesn't have to crash your system alone.. it can make you lose hard drive data, cause drive fragmentations, loss of files and corrupt files especially those held in system memory i.e. VGA SYS and DLL files included. :yepp:

But you really shouldn't rely on that PSU. It's not even a PSU, honestly advising you, it's a total rip off for what it's doing to your components.

Whats the stepping on that 60Ghz Phenom KTE!! :rofl:

That is wierd man! You think it's a software problem? Seems like if it was an actual problem with the clocks it would have crashed long before that....

It's the CPU MSR's and/or PLL feedbacks and any software which depends on them. Actual clocks do not change with these bugs, core limitations are well known by now. :D

Once I opened up Crystal CPUID to check my MSR values and a lot of them were totally blank (0's) where they shouldn't be at all. :confused:
It's the same with BarEdit/WPCREDIT access of NB registers, they totally whack out many times. The last time I checked that also was reading 0b for everything in the NB FID D4 register, whereas it should not be and was still running 9x multi as it showed. At those instances L3 performance and access becomes very bad and slower than stock.

If I could capture it, I'd show you some much higher MHz to show you the scale of the problem. Dilemma is, when the [fake] high MHz show up in all software the system freezes for 2-3 seconds at a time and so the PrntScrn is never saved until after it restores from freezing. The way to test the bug is to test the system on multiple boards really.

BTW what config are you now running on the GBT? Any more oc on HT, NB or CPU?

Quote:

---

Originally Posted by KTE

BTW what config are you now running on the GBT? Any more oc on HT, NB or CPU?

---

The best I've gotten so far with any stability (not really stressed) was 2.76Ghz (240x11.5x8x8) using AOD, those setting would not boot windows when set in Bios though... :( Looks like 2.7 may wind up being doable, while my best stable on the MSI board was 2.5...

So far it looks much better than K9A2, I can boot at 13x multi now.
To be fair to the MSI board, I never really got a chance to play with it much using XP, most of my testing was done using Vista 64....

A short story of how I wound up with the DS5:
I have a 9600std and a 9600be, when my K9A2 died I thought I'd be shady :shakes: and go buy another one switch them out, return it, then I'd have 2 boards right?
Well, the board I bought actually WAS bad!! When I went back to the store they were out of K9A2's and all they had were DS5/DQ6 and the Asus boards, so it wound up costing me an extra $45!!

Poetic Justice I guess.. :yepp:
I'm just not good at being bad..

Your chip looked 2.7G doable pretty easily to me as I stated once before. You looked limited by Vista on the MSI. ;)

The DS5 doesn't clock better than the MSI IME, it doesn't have the BIOS options to, not if you use all we have made clear regarding VID/FID/DID or the 1.13 BETA. The DQ6 will. You can't oc the NB/RAM with the DS5 much. Try plus 600 on RAM and plus 2.4G on NB for instance.

So you're telling me that you tried to do some fraud? :p:

Quote:

---

Originally Posted by Daveburt714

I have a 9600std and a 9600be, when my K9A2 died I thought I'd be shady :shakes: and go buy another one switch them out, return it, then I'd have 2 boards right?
Well, the board I bought actually WAS bad!! When I went back to the store they were out of K9A2's and all they had were DS5/DQ6 and the Asus boards, so it wound up costing me an extra $45!!

---

What goes around comes around :yepp:

I got my new ASUS board and couldnt get video so I installed a 5000 and she fired right up so my Phenom is dead as well RMA-ing it tommorow :(

Quote:

---

Originally Posted by KTE

So you're telling me that you tried to do some fraud? :p:

---

Fraud is a pretty harsh word, I NEVER do that kind of stuff. But I had bought both chips from there plus the board and a cheapo CoolerMaster PSU which I thought had caused the problem (apparently not). Plus the fact that the board was only a couple weeks past thier normal return policy and I bought another board, a decent PSU and another set of RAM...
Oh well, just trying to justify it in my own mind, guess I got what I deserved. ;)

As far as the DS5 goes, I think the BIOS may have gotten alot better since you tested it. I'm running the F4f version and they seem very solid. Here are the pros & Cons so far:

PROS: TLB disable works across all 4 cores (fully disables)
Temps report much more accurately than the MSI
HTT/HTR voltage settings (although it doesn't seem to offer much)
SB Voltage control
Voltages seem alot more stable (Less fluctuation)

CONS: No voltage option for the IMC (NB Vid)
Looks like max HTT Ref is around 235 (250 was stable on the MSI)
Voltage options are a little more limited (idiot proof), which may be a good thing in my case... :ROTF:
If you want to see some BIOS pics let me know.

Quote:

---

Originally Posted by jesteronyer6

I got my new ASUS board and couldnt get video so I installed a 5000 and she fired right up so my Phenom is dead as well RMA-ing it tommorow :(

---

Sorry to hear about your Phenom Jest... My CPU is fine, guess it was just some weird coincidence...

oh yeah, my phenom's batch number is:
CAAWB AA 0747MPMW

Decided to reseat my HSF since when I had originally installed it, the thumb push down latch was right up against the sercupipe on my board, so I switched the mounting latch around to the opposite direction.

Quote:

---

Originally Posted by KTE

Guys, the BIOS file P0H aGeoM attached is fine, checksum is also perfect. I've flashed it without even setting defaults although I did follow the safe known procedure and did use the flash parameters.

---

what parameters did you used during update of bios?what does this do?:confused:

Quote:

---

Originally Posted by Daveburt714

Fraud is a pretty harsh word, I NEVER do that kind of stuff. But I had bought both chips from there plus the board and a cheapo CoolerMaster PSU which I thought had caused the problem (apparently not). Plus the fact that the board was only a couple weeks past thier normal return policy and I bought another board, a decent PSU and another set of RAM...
Oh well, just trying to justify it in my own mind, guess I got what I deserved. ;)

---

:stick: :fact: :D

Quote:

---

As far as the DS5 goes, I think the BIOS may have gotten alot better since you tested it. I'm running the F4f version and they seem very solid. Here are the pros & Cons so far:

PROS: TLB disable works across all 4 cores (fully disables)
Temps report much more accurately than the MSI
HTT/HTR voltage settings (although it doesn't seem to offer much)
SB Voltage control
Voltages seem alot more stable (Less fluctuation)

---

The first thing is awesome! Nope that wasn't in the earlier BIOS I tried. The rest of the volts aren't important as we know, only NB VID/Volts is the main importance after CPU. What are your idle/load temps now, any test ss?

Quote:

---

CONS: No voltage option for the IMC (NB Vid)
Voltage options are a little more limited (idiot proof), which may be a good thing in my case... :ROTF:

---

This is what made me stay away from it frankly. NB is central to control for a good oc here.

Quote:

---

If you want to see some BIOS pics let me know.

---

Yes please (just don't make them huge) :D

Quote:

---

Originally Posted by madfaze

what parameters did you used during update of bios?what does this do?:confused:

---

Example for Flash Utility 418 with P0H:

Code:

---

afud418.exe a7376ams.p0h /p /b /n /c

---

Some type /pbnc instead, it's best to clear everything properly when flashing.

basically what it does with those parameters?

i mean even without those parameters can you still update the bios normally like i do...

Parameters flash over the boot-strap of your BIOS.

As I've said before, I would never flash without those using a BETA, you are going to end up with random problems many times and even unbootable systems.

geez... now i have second thoughts on flashing BETA bios ... dont wanna end up a brick mobo...

but when the bios is official release is it still good to run it without those parameters?right?

It's always best to do that, always... always. :yepp:

Well that is what BETA is about, you know. :p:

how about the command "/reboot" will it work too?

KTE: Here some Bios/Temp shots from the DS5.

http://i30.photobucket.com/albums/c3...Temps_0228.jpg

As you can see those temps look much more realistic than what I was getting from the K9A2. Alot of times the MSI board would show temps below ambient, and never went over 32c. One thing I never noticed on the MSI board was the somewhat broad Voltage swing when you put the CPU under load. CPU V's are set at 1.3v's but when I load the processor it jumps to 1.36 as shown in the ss, as soon as I turn off Prime4 it drops back down to 1.296v. Seems a little odd but it does seem to help stability... :)
(BTW, Ambient is around 71f right now)

http://i30.photobucket.com/albums/c3...h_DSCN0194.jpg

We don't need no stinking TLB Patch! Sweet... :D

http://i30.photobucket.com/albums/c3...h_DSCN0197.jpg

Haven't had a chance to play with the AutoExpress thing yet, but it looks interesting. I'm just looking for stability right now...

http://i30.photobucket.com/albums/c3...h_DSCN0199.jpg

The only thing I really miss in this Bios is the ability to adjust NB v's. I wonder if they just didn't feel the need to include it, or if they cheaped out on the power section of the board (I doubt that)...

KTE, If you and Achim can figure out a way to adjust that setting through registers let me know. If it's not too scary I might try it... ;)

Quote:

---

Originally Posted by madfaze

how about the command "/reboot" will it work too?

---

I don't recall what that's for or if it works. Load the flash utility and type /? or /help and you should get a list of parameters which do work and what they do.

Quote:

---

Originally Posted by Daveburt714

KTE: Here some Bios/Temp shots from the DS5.

---

Thank you! :)

Quote:

---

As you can see those temps look much more realistic than what I was getting from the K9A2. Alot of times the MSI board would show temps below ambient, and never went over 32c.

---

I'm working through this but the temperatures reported by all software including the BIOS are TCONTROL, and TCONTROL is not a temperature value but an arbitrary value in decimals to allow better control of thermal management. It is designed to read sub-ambient values and even negative values whilst ambient is plus 10C as it does not literally show temperature values in degrees but shows a TCONTROL value that is set to always stay below TCONTROL max; which is calibrated to be consistent with the actual processors TCASE max. ;)

The TCONTROL correlating to the TCASE can be found in the thermal management guide.

My 9500 and last 9600BE didn't read this value as this but once or twice. They were reading the same temp as the TCASE with software and a thermocouple. My current one and 9600s reacted different though and often read sub-ambient. This is by design. ;)

The values for temps you have above are also not real temp values (they are very low for real values, lower than my 9600BE is at stock).

Here's the pertinent explanation of AMD K10h temperature workings:

http://img132.imageshack.us/img132/8700/amdtempev2.png

Quote:

---

One thing I never noticed on the MSI board was the somewhat broad Voltage swing when you put the CPU under load. CPU V's are set at 1.3v's but when I load the processor it jumps to 1.36 as shown in the ss, as soon as I turn off Prime4 it drops back down to 1.296v. Seems a little odd but it does seem to help stability... :)
(BTW, Ambient is around 71f right now)

---

That's good and bad actually.

Good, as in no Vdroop as on MSI which causes mass instability many times, especially if more than 0.02V.
Bad as in you'll have higher load power/temps and current going to your chip, which is not healthy for it. The Vdroop is actually by design a feature for the CPU safety. :yepp:

Very good options in BIOS though, just a trimmed version of the DQ6 one.

Quote:

---

The only thing I really miss in this Bios is the ability to adjust NB v's. I wonder if they just didn't feel the need to include it, or if they cheaped out on the power section of the board (I doubt that)...

KTE, If you and Achim can figure out a way to adjust that setting through registers let me know. If it's not too scary I might try it... ;)

---

You can do it on the fly in Windows, yup. But it will revert after restart.

Check mine and Achim's posts out towards the end of the DFI RD790 thread, they'll help. The register that controls the current processor state is this following and you need to change and write the following value to whatever you want using Crystal CPUID:

Attachment 73166

The 48h control NB VID.
The 340h controls CPU VID.

48h = 1.100V
340h = 1.225V

i.e.

Attachment 73167

I had to put load on it to show you the specs because I'm running CnQ. Check what we're idling with CnQ in the DFI thread. ;)

Just posting some K10h related roadmaps I was about to a day ago but was delayed. Don't mind me... :D

BTW, Phenom FX maybe mentioned there you know. :p:

http://img352.imageshack.us/img352/5728/17888812pg4.png

http://img84.imageshack.us/img84/937...4026kb3.th.png http://img352.imageshack.us/img352/6...0689bi3.th.jpg http://img213.imageshack.us/img213/4...0875cj0.th.png http://img206.imageshack.us/img206/3715/25fp9.th.png

http://img207.imageshack.us/img207/5616/53549237wh7.png

Hmm....2 version of 9750 with diff TBD?

I wonder if the availability of the FX82 will lead to a FX70/72/74 style dual CPU socked motherboard. If there is a chance AMD will get a dual socket motherboard for the Phenom FX series before September I'll put off my computer build.

Quote:

---

Originally Posted by ragnarok95

Hmm....2 version of 9750 with diff TBD?

---

Probably one with L3 cahce and one with out the L3 cache.

Quote:

---

Originally Posted by ragnarok95

Hmm....2 version of 9750 with diff TBD?

---

Different TDP's (2.4GHz).

Quote:

---

Originally Posted by spicypixel

I wonder if the availability of the FX82 will lead to a FX70/72/74 style dual CPU socked motherboard.

---

Don't count on it, believe me, there won't be. Not until after Deneb 2009 anyway. 1P you will get though. :yepp:

http://www.lavalys.com:8081/beta/eve...l9xdsv2crt.zip

Just gets better and better. ;)

Any of you miss Barcelona benchmarked with Xeon (Core 2 and Penryn)?

Independent world famous professional research found a while ago, that due to FBDIMMs Intel uses, Barcelona servers beat similarly configured Xeons based on Core 2 and Penryn in power usage and performance efficiency: http://www.worlds-fastest.com/wfz986.html

Test were conducted far better than SPEC_CPU 2006 or TPC can, these saturate each RAM module, network, disk and core far more. These are also not configured by separate entities, flags or components, but are purely apple to apple comparisons.

Full details of the testing:
Power Usage at various transaction levels: http://www.worlds-fastest.com/wf3400.html
Throughput: http://www.worlds-fastest.com/wf2400.html

That's basically why Penryn was rushed and released as Intel knew, and as any market analyst would tell you. In the major server market with strong loads, Woodcrest would get trumped for power/cost/efficiency/performance by Barcelona. Let alone that, even 2.33GHz Harpertown vs. 2.0GHz Barcelona get beat overall when you weight the overall cost:performance down. That's also why someone would take Barcelona over them for supercomputers.

Never would have thought that was the case, Barcelona on par with Penryn. :cool:

I´d like to say that I have seen that before somewhere, but I´m not sure where.... maybe in the news section..

which of those phenoms are tri-core?

Toliman.

Yes, test data is obvious as to why firms jump on products.. but for lunatics. Obviously that doesn't account for all work-types, just a major few.

are they schedule to be out on 2Q?

Just got my 9600 on my K9A2 plat. Happy with it. Zero problems so far.

madfaze: late this month first samples AFAIK and mainly to OEMs in Q2 in B3 step.

ragnarok95: nice. So any testing details yet? Max HT, Max NB, Max MHz, Max stable MHz, Max benchable MHz? :confused:

BTW another myth debunked which I told you about before very clearly.

I asked AMD why they had asked MB manufacturers to definitely put the TLB Fix on by default and they said no we haven't done any such thing. What the MB manufacturer chooses is their choice entirely.

So there you have it, just as I had told you around 4 weeks back now. :)

My K9A2 refuses to boot twice in a row. I've got a 3600X2 on it, 2GB Dominator 6400C4, ATM 1 3850, and it's powered by a PCP&C Silencer 750 Quad. Is it BIOS related (IE, fixable) or would it sound more like a bad board?

Kayin which BIOS are you using?

Was 1.2, now 1.3. I'm still not booting every time, but at least now I can get it into windows if I grit my teeth and try hard.

My K9A2 is doing the same thing. I have a 5000+ BE @ 3150 w/ crucial ballistix and a 3870x2. The thing rarely boots the first time. Usually I will have to hit the reset button then it boots fine. I have prime95'd the system for over 10 hours continuously, plus there are no errors in windows, games, or any other app. The only problem is cold boot. Is it possible that the board doesn't up the voltages soon enough at cold boot? I am also using Bios 1.3

Try BIOS P0H (BETA, but better than 1.3): http://www.box.net/shared/gsn4mgt6o4

Load defaults and then flash with parameters /p /b /n /c

Let me know if you get the same problem. It looks like memory to me.
Also check your PSU voltages on all rails at boot.

If you still get it, can you describe exactly what happens and at what stages?

What memory would you recommend then? 8 GB worth, if possible-this machine does rendering duty on occasion...

I flashed the bios to P0H and my problem has disappeared. I applied the same overclock settings in this bios and it boots everytime. Also, it boots faster, and XP loads noticeably quicker as well. Also shutting down in Xp is quicker as well. Before it seemed like windows locked up while shutting down as it took a long time. Now it shutsdown in about 8 to 10 secs. Clearly there is something wrong with the 130 bios. Also, does anyone happen to know what the Auto Xpress feature is, and what it does? I currently have it disabled.

My board just flat died (open circuit, no beeps) and I've gotten an RMA number for it. I'm sending it off tomorrow, will post back when the new one gets here.

Mine was not just a warm boot. I had trouble coaxing it to do anything at all, including post. BIOS settings could not be changed, etc.

Quote:

---

Originally Posted by KTE

Try BIOS P0H (BETA, but better than 1.3): http://www.box.net/shared/gsn4mgt6o4

Load defaults and then flash with parameters /p /b /n /c

Let me know if you get the same problem. It looks like memory to me.
Also check your PSU voltages on all rails at boot.

If you still get it, can you describe exactly what happens and at what stages?

---

M9K2 Plat.. 9600BE
I tryed this bios, and it causes a BSOD (nvidia driver) on boot :
I think it's nvd3dumx.dll
OS is x64 vista
i have flashed with 1.33/1.30, and no issues, but i cannot get over 208 HHT...
no biggie really, not trying to do what KTE does.

but I noticed that BIOS 1.13 was reccomended, but i DO have
OCZ PC2-8000 ReaperX HPC 4GB Dual Channel for my ram...
could I place them in slots 1&3 (i know 1&2 are needed for dual channel, i got it like that now) and place the memory as unganged and get the same performance? only ask this because i could add some XMS2 ram then... and not feel weird with differnt in slots (don't ask lawl)

eather way, i'm thinking i should get a bit higher than :
(with AOD on red, and RWeverthing patch applyed)
http://www.imagehosting.com/out.php/i1609727_bench.jpg

I don't want to start messing around with bios, till i know i have one worth messing with. bear with me, havn't overclocked sence pencil mod on the athlons!

If you're buying 2GBx2 or 2GBx4 kits then please be very careful and ask before doing so. Many kits are not yet supported especially with Phenom and if you have Vista 64-bit!

I will repeat as I've mentioned many times before; Vista 64bit = hundreds of problems with Phenom!

Most well known problem = BSoD 'Clock interrupt not received on second processor within the allocated time permitted'

Source of problem = BIOS/Vista, nothing else!

Examples (multi-CPU):
http://forums.amd.com/forum/messagev...threadid=92110
http://forums.anandtech.com/messagev...readid=2122913
http://www.driverheaven.net/windows-...not-oc-ed.html
http://answers.yahoo.com/question/in...1225702AAUYnW2

AMD gave out their sample chips with quite some time for MFGs to troubleshoot but most MB MFGs did not have a clue of intricate understanding about Phenom functioning up until around January after user feedback and many users telling them word for word. First ones were in July 0723/0724/0725 B0 step AFAIK. Since then the BIOS/compatibility has got much better. Many many closed BETA testers of BIOSes had absolutely no idea what or how Phenom works and why and they were formulating wrong conclusions and opinions. Main reason being, it's a complex arch. and unlike K8 in it's functioning, which they now know. Just look at how long it took us to work it out and Me/Achim here are still finding important things starting non-stop from 15th Nov (latest in DFI RD790 thread).

For MSI K9A2 Plat., BIOS P0H has many major fixes and updates; apart from the lack of OC options for Phenom and the semi-enabled TLB fix, it is near flawless for me. Very stable as one should expect. I have tested them all, even some you haven't, and P0H is the most stable/hardware supporting out. :)

Quote:

---

Originally Posted by jeremydde

I flashed the bios to P0H and my problem has disappeared. I applied the same overclock settings in this bios and it boots everytime. Also, it boots faster, and XP loads noticeably quicker as well. Also shutting down in Xp is quicker as well. Before it seemed like windows locked up while shutting down as it took a long time. Now it shutsdown in about 8 to 10 secs. Clearly there is something wrong with the 130 bios. Also, does anyone happen to know what the Auto Xpress feature is, and what it does? I currently have it disabled.

---

Good to know. I told them not to use the old 1.32 code but use P0H but they didn't listen. :(

AutoXpress briefly: http://www.xtremesystems.org/forums/...postcount=1050

Boosts subsystem component performances. It's useful for systems with powerful PCIe 2.0 cards.

Quote:

---

Originally Posted by [XC] Kayin

My board just flat died (open circuit, no beeps) and I've gotten an RMA number for it. I'm sending it off tomorrow, will post back when the new one gets here.

Mine was not just a warm boot. I had trouble coaxing it to do anything at all, including post. BIOS settings could not be changed, etc.

---

Bad board then. :(

Quote:

---

Originally Posted by dr_drache

M9K2 Plat.. 9600BE
I tryed this bios, and it causes a BSOD (nvidia driver) on boot :
I think it's nvd3dumx.dll
OS is x64 vista

---

I'll get back to you about the RAM but I've emboldened the problem near enough every user has had with Phenom so far. :(

The BSoD at that stage makes me think you installed OS on a different board and didn't format/install it new here?

Quote:

---

(with AOD on red, and RWeverthing patch applyed)
http://www.imagehosting.com/out.php/i1609727_bench.jpg

---

That's very low, the patch is still applied to 3 cores there. :yepp:

What speeds were you at?

thanks for check on the ram,

Quote:

---

The BSoD at that stage makes me think you installed OS on a different board and didn't format/install it new here?

---

that right after OOBE, then install drivers, and reboot.
first install gave me no AREO, and acted like old xp/98 as in, REQUIRED
a reboot to detect new hardware.
2nd time, worked fine, but was getting that BSOD, then i thought,
what the heck, and flashed 1.30, and running pretty good right now
(it's a bit slower than my crosshair mobo though)
which also, weird enough had no issues with OC other than the lack of voltage control (bios 0905beta if you care)

Quote:

---

That's very low, the patch is still applied to 3 cores there. :yepp:

---

how would i make sure all 3 are applyed with RW? (version .29) i'll do it manually again see if i can "Fix it"

Quote:

---

What speeds were you at?

---

that's about as stock as it gets, ~2301 everything in bios on default.


EDIT : changed the 0xc0010015 from 0x0000018 to 0x0000010 in all 4 cores. same results. tryed with RED AOD and all 4 cores, same result. intrestingly enough, when i brought up AOD after the first change, it was set at "yellow". and then when i shut it off (black), and rechecked CrystalCPU, only core 1 was back at 18.

What RAM is safe to get in 2X2GB or 4X2GB?

Did some winrar benchmark tests with different BIOS versions. Phenom 9600 at stock, no optimizations, Vista 32-bit. I must say I was a bit surprised.

The scores are all "about" scores, I did not record the numbers, just noticed they were about the same all the time regardless of BIOS-version (apart from P0H).

BIOS 1.1 : around 400KB/s (varies between 380 and 430, mostly around 400-410) at stock, around 580KB/s (varies between 570 and 620, mostly at around 58x) with AOD at "red"
BIOS 1.3 : about the same
BIOS 1.0B1 TLB-fix enabled : about the same
BIOS 1.0B1 TLB-fix disabled : about the same
BIOS P0H TLB-fix disabled : around 400KB/s at stock, around 490KB/s with AOD at "red"

First: Are the numbers fine?
Second: Why does P0H have such poor performance compared to the other versions?

I am kinda amazed at how large a difference there is in this particular test between AOD at yellow/red and no AOD running...

UPDATE :

well, for S.A.G's sake (S**ts and giggles) I went into bios and reset to ganged mode (aka, 1x128bit, dual channel as we remeber it) (hopefully i am getting the terms right)
came into windows, opened AOD, set RED, open crystalCPU
went through and just checked the state of 0xc0010015, only core 4 was changed, (to 0x01000010), so it seems AOD for me is pretty much useless,
anyway, set the bits, and benchmarked :
http://www.imagehosting.com/out.php/i1611270_bench2.jpg

much better!!

now am i supposed to be doing something with this MSR? :
0xc0011023, it's in the RW file, but i don't know if it applys to me?

on a side note, my install may be buggered, the progress bar pauses 3 times while booting...

Quote:

---

Originally Posted by dr_drache

i have flashed with 1.33/1.30, and no issues, but i cannot get over 208 HHT...
no biggie really, not trying to do what KTE does.

---

Should get much more than that. You'll need to work at it and spend time on it if you wanted it. ;)

Quote:

---

but I noticed that BIOS 1.13 was reccomended, but i DO have
OCZ PC2-8000 ReaperX HPC 4GB Dual Channel for my ram...
could I place them in slots 1&3 (i know 1&2 are needed for dual channel, i got it like that now) and place the memory as unganged and get the same performance?

---

RAM should be wok fine IMO. Nope, you need it in 1&2 or no dual channel. Single channel is poor performance. Like this: http://www.xtremesystems.org/forums/...2&postcount=23

Quote:

---

I don't want to start messing around with bios, till i know i have one worth messing with. bear with me, havn't overclocked sence pencil mod on the athlons!

---

It's easy but just confusing. :D

Quote:

---

Originally Posted by dr_drache

that right after OOBE, then install drivers, and reboot.

---

For Phenom you may have to install OS fresh. Or it'll give too many problems unless you've deleted all the waste files and registries of old components manually. OOBE, out of body experience? :p:

Quote:

---

2nd time, worked fine, but was getting that BSOD, then i thought,
what the heck, and flashed 1.30, and running pretty good right now
(it's a bit slower than my crosshair mobo though)
which also, weird enough had no issues with OC other than the lack of voltage control (bios 0905beta if you care)

---

Hmm.. you should flash 1.13B if you want to oc through BIOS. Slower than your Crosshair, as in what way? Any benchmark comparisons?

Quote:

---

how would i make sure all 3 are applyed with RW? (version .29) i'll do it manually again see if i can "Fix it"

---

Like this: http://www.xtremesystems.org/forums/...0&postcount=39
CPU1, 2, 3 etc parameters write MSR for each core separately. RWE has never worked for me yet though so I don't use it, no time to troubleshoot. :(

Quote:

---

EDIT : changed the 0xc0010015 from 0x0000018 to 0x0000010 in all 4 cores. same results. tryed with RED AOD and all 4 cores, same result. intrestingly enough, when i brought up AOD after the first change, it was set at "yellow". and then when i shut it off (black), and rechecked CrystalCPU, only core 1 was back at 18.

---

It's because you need to write to all cores and two different MSR (AOD yellow will do fine). Like shown here: http://www.xtremesystems.org/forums/...postcount=1215

Try it. ;)

Quote:

---

Originally Posted by [XC] Kayin

What RAM is safe to get in 2X2GB or 4X2GB?

---

2x2GB, many incl. Crucial Ballistix/Tracer, Corsair Dominator (XMS2), Kingston HyperX (newer BIOSes), many OCZ such as ReaperX/Reaper, G.Skill such as F2-8500CL5D-4GBPK/F2-8000CL5D-4GBPQ and GeIL modules like the Black Dragon which can all boot 1.8V if need be. Higher, either 4x2GB or 4x1GB, it gets tricky and depends on the RAM latencies/volts itself. I have not seen or tested any where all four are populated with this board but two which worked with BIOS P0F and P0H: Corsair QUAD2X4096-8500C5DF (Twin2x 4x1GB) and GeIL Black Dragon GB24GB8500C5QC (4x1GB). YMMV as always, but the above are known to be working for others on this board. P0H is best to try them with especially since it can run all RAM dividers, all before P0E do not offer many 4x2GB, 4x1GB or 2x2GB RAM compatibility. The biggest problems are experienced by Vista users and especially Vista X64. Many will have no boot.

Quote:

---

Originally Posted by Suosaaski

Did some winrar benchmark tests with different BIOS versions. Phenom 9600 at stock, no optimizations, Vista 32-bit. I must say I was a bit surprised.

The scores are all "about" scores, I did not record the numbers, just noticed they were about the same all the time regardless of BIOS-version (apart from P0H).

BIOS 1.1 : around 400KB/s (varies between 380 and 430, mostly around 400-410) at stock, around 580KB/s (varies between 570 and 620, mostly at around 58x) with AOD at "red"
BIOS 1.3 : about the same
BIOS 1.0B1 TLB-fix enabled : about the same
BIOS 1.0B1 TLB-fix disabled : about the same
BIOS P0H TLB-fix disabled : around 400KB/s at stock, around 490KB/s with AOD at "red"

First: Are the numbers fine?
Second: Why does P0H have such poor performance compared to the other versions?

I am kinda amazed at how large a difference there is in this particular test between AOD at yellow/red and no AOD running...

---

There is definitely a performance difference across BIOSes, 1.13B is best I've tested in pure performance and P0H is second. But you need to disable the TLB errata patch first :D

Try this link method and then switch off all basic extra's, AOD yellow and rerun the WinRAR bench. Should be much higher: http://www.xtremesystems.org/forums/...postcount=1215

Quote:

---

Originally Posted by KTE

For Phenom you may have to install OS fresh. Or it'll give too many problems unless you've deleted all the waste files and registries of old components manually. OOBE, out of body experience? :p:

---

OOBE = Out of Box Experence, the wizard before you can first log-in

Quote:

---

Originally Posted by KTE

Hmm.. you should flash 1.13B if you want to oc through BIOS. Slower than your Crosshair, as in what way? Any benchmark comparisons?

---

no benchmarks that i can post, but i KNOW that i was getting near 1900 in the winrar test, it was stock running, no matter what i tryed. switched because I saw that a 790FX chipset may be better for me for tweaking (kinda irked about lack of SLI, but i'll live) love love this crosshair sitting on my desk :P

Quote:

---

Originally Posted by KTE

It's because you need to write to all cores and two different MSR (AOD yellow will do fine). Like shown here: http://www.xtremesystems.org/forums/...postcount=1215

Try it. ;)

---

ahhh, i've been doing only the 1/2 of it, i have not done the 0xc0011023 registers.
i'll give it a shot.

Quote:

---

Originally Posted by KTE

There is definitely a performance difference across BIOSes, 1.13B is best I've tested in pure performance and P0H is second. But you need to disable the TLB errata patch first :D

Try this link method and then switch off all basic extra's, AOD yellow and rerun the WinRAR bench. Should be much higher: http://www.xtremesystems.org/forums/...postcount=1215

---

i'll look into it, not really looking into formatting again, will if it needs it. will attempt to build a new iso with vlite, see if i can get a promise raid driver intagrated right this time. as soon as i decide on the format, i'll switch back to trying P0H.

UPDATE :
i think i may got an issue, my 0xc0011023 doesn't match

http://www.imagehosting.com/out.php/i1611432_bench3.png




UPDATE #2 : flashed 113, did BOTH register changes and got :

http://www.imagehosting.com/out.php/i1611527_bnc.jpg

Quote:

---

Originally Posted by Suosaaski

Did some winrar benchmark tests with different BIOS versions. Phenom 9600 at stock, no optimizations, Vista 32-bit. I must say I was a bit surprised.

The scores are all "about" scores, I did not record the numbers, just noticed they were about the same all the time regardless of BIOS-version (apart from P0H).

BIOS 1.1 : around 400KB/s (varies between 380 and 430, mostly around 400-410) at stock, around 580KB/s (varies between 570 and 620, mostly at around 58x) with AOD at "red"
BIOS 1.3 : about the same
BIOS 1.0B1 TLB-fix enabled : about the same
BIOS 1.0B1 TLB-fix disabled : about the same
BIOS P0H TLB-fix disabled : around 400KB/s at stock, around 490KB/s with AOD at "red"

First: Are the numbers fine?
Second: Why does P0H have such poor performance compared to the other versions?

I am kinda amazed at how large a difference there is in this particular test between AOD at yellow/red and no AOD running...

---

Funny, I did the winrar benchmark after I flashed to P0H and increased from 580 to 642 KB/s.

Sorry, didn't have the multithreaded box checked. I got 1306 kb/s , dunno what was before the flash.

Hmmm, so if I'm understanding this right, does P0H have the ability to disable the TLB fix? Or does it only disable it for one core?

Quote:

---

Originally Posted by KTE

There is definitely a performance difference across BIOSes, 1.13B is best I've tested in pure performance and P0H is second. But you need to disable the TLB errata patch first :D

Try this link method and then switch off all basic extra's, AOD yellow and rerun the WinRAR bench. Should be much higher: http://www.xtremesystems.org/forums/...postcount=1215

---

I might test that when I get back home.

By the way, do you happen to have any idea why AOD shows my memory is in single channel mode?

I have 4 * 1GB PC2-6400 and BIOS is set to unganged.

And I was to understand BIOS 1.1 would not have the TLB-fix, howcome it gets the same performance as the newer ones?