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.