AMD CPU's and an ASUS Board.


Recommended Posts

I got an AMD Athlon XP 2600+ on an ASUS A7N8X-X.

And it will/would run at 1250Mhz... Anything above that, and it doesn't want to know, I just get BSOD's. (BSOD's trying to run Windows or even install Windows :x :angry:)

I just rung up the place I bought it and they said that the FSB should be 166Mhz and the Multiplier 12.5x but it still only runs at 1250Mhz...

I've flashed the BIOS to the latest version.

Could anyone point me in the right direction, coz I don't really wanna send it back !!!

Thanks,

Ferret !

Link to comment
https://www.neowin.net/forum/topic/101934-amd-cpus-and-an-asus-board/
Share on other sites

Yes...

I've just figured something though, I originally bought a DDR266 stick of RAM just to get the machine up and running...

266 / 2 = 133

133 x 12.5 (Multiplier) = 1.6Ghz.

But when I had that DDR266 stick, it would still only run at 1.2Ghz.

100 x 12.5 = 1250Mhz (1.2Ghz)

That seems to suggest that since I got the board, it was ALWAYS running at a 100Mhz FSB.

I've set the FSB in the BIOS to 100Mhz, 133Mhz, 166Mhz and 200Mhz.

Even played with the jumper on the board it's self, but to no avail.

But whats getting me, is even with the original DDR266 and my current DDR400, why won't the FSB lift above 100Mhz ?!?

Is it really damaged, there can't be anything thing else, i've read the manual from front to back and theres only ONE jumper for the FSB/CPU and that didn't do jack**** !

Thanks,

Ferret !

There is a solution but I don't have time this morn to go step by step.

The problem you are having is due to automatic configuration done by the Asus BIOS. I don't agree with the amount of control that certain vague settings give the BIOS as far as setting timings and stuff, I have fourd that even when it seems that basically you are defining the settings the BIOS can sometimes still override you.

I recommend playing with the BIOS until it seems you have EVERYTHING defined manually.

If you can't figure out good settings I'll check back later and help ya out a bit.

G

I've tried both RAM sticks, resetting the BIOS... Just about everything I could think to do...

Garrett Socling: I've set EVERYTHING (To the best extent I could) in Advanced Chipset Features to Manual settings -- And guess what, 1.2Ghz, supprise supprise.

So that walkthrough would be greatly appreciated please mate !!!

Thanks alot mate,

Ferret !

I did that mate - Upda\ted with the latest BIOS, but that didnr't work...

ANYWAY, goooooooooooood news, after trying to set ALL the options to manual, then that didn't work, I set them back to AUTO and guess what..

I got a working AMD Athlon XP2600+ :D:D:D:D

Why this has done the trick I don't know, But i'm never gonna enter the BIOS again incase it goes again.

Thanks for all your help,

Ferret !

i know mate.. i read through the thread, and i'm sure you're very computer literate, but I still think something was set wrong somewhere because things don't just not work and then all of a sudden start working.

but hey thats just my opinion :) again, glad its working!

That sounds very typical compared to what I have experienced with this BIOS.

A setting that would not work one try would work at a different date.

As far as setting stuff to manual and it not working, I'd say 95% of the settings I tried didn't work. Even dumb things like lowering the multipler from 10.5 to 10.0 as the inital step of overclocking prevented posting.

Then, when I tried to raise the FSB, if I did it in too great of steps it wouldn't post. I had to do it in like 3Mhz increments to reach 155. Then, it wouldn't go above that for a while. Now it is at 160Mhz/160Mhz...Wierd.

Finally, I think the board has issues with memory. I have Crucial PC2700 (2x256). Some relaxed settings would not post.

If you under-clock the memory, the board automatically increases the aggressiveness of the memory settings, even in full-auto mode. Hence, when I set the board to full auto, and it gave me 133/166, and I changed it to 133/133, it would not post (lowering the CL didn't go over well with the memory?). After bringing the mem and FSB in synch, I had to raise the FSB high enough to raise the CL to get the board to post. Then, it was fine and dandy.

Very very complicated. If the board is going to make assumptions as to what is optimal, it should at least do a basic quick-test/post routine to find out what 'optimal' settings are valid. I dunno...I just didn't like the 'I know what is good for you' attitude of the board, especially when its know-it-all configs wouldn't post...

I think I am going to reboot and go for 166/166...all this talkin about it has me interested.

I'll get a pic of my current BIOS settings while I am there...

G

I apologize for the poor pictures...I wasn't planning on taking so many and wasn't really planning ahead...

BIOS Default -

biosdefault.jpg

This is what I have been running at as my default setup. It is stable and has decent performance. Basically, the initial bootup settings overclocked from 133Mhz to 160Mhz. This is what I stepped up 3Mhz at a time when I was overclocking. It would not accept jumps of more than 3 or 5Mhz at a time, but if I went slow it went up without a problem. At 166Mhz, the system is not 100% stable, and I believe the problem is my ancient Palamino. Shame I can't drop the multiplier...

Full Auto -

fullauto.jpg

This is completely what the BIOS chooses when it first boots up, except for choosing 133Mhz over the initial bootup of 100Mhz. Note the incorrect CL settings (considering that it is running the memory at 166Mhz, this stick of Crucial ram is not rated for 2 at 166, and the Active Precharge Delay set to 6. Not that the BIOS says its is gonna run the memory at 166Mhz...all you see is the vague 'auto'...What happens if you aren't really BIOS tweaking inclined and you can't install Win XP because when set to full auto the mobo pushes your memory to the point it isn't stable? Memory Timings, notice, are set to Optimal.

Auto SPD -

autospd.jpg

This is what happens when you change the BIOS default from 'Mem Freq - Auto' to 'Mem Freq - By SPD'. Basically, when you enable SPD the mobo realizes that it was running the memory too agressively and backs the CL off to 2.5 and the Active Precharge Delay to 7. Memory Timings are still set at Optimal...the previous settings weren't so Optimal after all...

Auto Agressive -

autoagressive.jpg

This is simply 133Mhz with all of the auto-config settings set to agressive. Please note that I set Mem Freq to 100% to take that oddness out of the loop... All it shows on the surface are 'across-the-board' agressive memory timings, but it claims to also increase 'System Performance' - whatever that really is, it isn't obvious from the BIOS. I wasn't blown away with the increased performance when changing this to Agressive, but it does have a marginal effect. Probably decreases stabilty a hair too. Memory Timings set at Agressive have some of the same effects as changing the Memory Frequency from 'Auto' to 'By SPD'...Why is this so complicated?

Auto Optimal/Agressive -

autooptaggro.jpg

With this schitzophrenic setup, the end result is basically what you get at 'Full Auto' - of course, I have Mem Freq set to 100%, so who knows what you'd get with Mem Freq set to 'Auto' or 'By SPD'...though I bet that Auto and 100% are exactly the same thing - as far as memory timings go. It still recognizes that the memory is 166Mhz, and runs it accordingly when set to Auto. If this doesn't seem excessively obtuse to you yet, I hear they don't have a solid theory on gravity and probably could use your help...

Auto 166Mhz -

auto166.jpg

With this setup, which is simply full Auto and Optimal with the CPU memory forced at 166Mhz, everything starts making sense again :

Even though the BIOS doesn't recognize the memory as 166Mhz memory under all circumstances when it comes to Memory Timings, and yet will run it at 166Mhz when set to Auto, it obviously is doing some sort of guess-work as to how to run the memory when set to Auto. Notice here that even though Auto results at 166Mhz when the CPU freq is set at 133Mhz or 166Mhz, with the CPU overclocked the Memory Timings are relaxed...

To wit : There is a lot more going on here than is at first obvious.

1750 -

1750.jpg

She booted and ran for a few hours at 166Mhz, but Hot CPU Tester revealed that the CPU was not 100% stable. A short while later the computer spontaneously rebooted (but did not generate a BSOD error). When she did that I reduced the FSB/CPU to 160Mhz, set the System Performance and Memory Timings to Agressive, and have been running on that since. Hot CPU Tester says these settings are stable...Unfortunately I forgot to get a new pic of these settings...which are not represented above...doh...

Ok. Thats it. Draw your own conclusions, but I say the BIOS is poor. I don't like it very much, I don't like the way it acts, or reacts to changes, I don't like the way it is hiding all of the important decisions it is making, I just don't like it. It shouldn't be so hard. Oh...and this doesn't even include the fact that I can't lower my multiplier...

Please note that I did not actually try to boot any of the above settings except for the first and last. I know that most of them won't boot, because the first day I got this board I spent about two hours trying all sorts of combinations to find something that simply worked...much less work well...

I have been threatening to write a review of this board...if I do, I'll be sure to get SiSoft Sandra CPU & Memory, 3DMark 2001, 3DMark 2003 and AquaMark3 results for all of the combinations that I manage to get to boot...of course I'll probably never get around to it...I'll have to review the board, compile test results, include the above text on the BIOS...take more and better pics...oofa...

G

Correction : Changing the settings from Optimal to Aggressive made a signifigant difference in performance.

Now, my 1600+ is running like an 2000+ :

Aquamark3 - 16810

3DMark01 - 10924

3DMark03 - 1565

SiSoft CPU - 6284/2528

SiSoft Mem - 2400/2244

I decided to benchmark the system since it was stable and I didn't feel like changing the BIOS settings back...

I'll try to pin down exactly what increased the performance (I suspect the vague 'System Performance ;)) and quantify the improvement...

G

Setting system performance to aggressive bumps your vcore .05v. It won't show it in the advanced chipset features but you will notice it in asus probe or mbm5. I suspect if you check the model #'s on your crucial ram that you'll find they are from the batch that were having compatibility problems with the A7N8X but I could be wrong since you have an -x board and the problems were with rev 1.x versions.

I don't think there's any way to access lower multi's without doing an L3 bridge mod and I think AMD made that pretty difficult with the 1600+ by perforating the space between the cut.

Anyway, good luck and thanks for the interesting read.

Thanks for the heads up on the compatibility issues...I suspected that there were issues (I thought I remembered reading something about it a while ago). I don't know why I didn't before, but I googled for a7n8x crucial problem and got a pile of results to read throug, so I can check it out. As far as the L3 mod, I had thought that the A7N8X automatically unlocked them, but if it doesn't...well, that explains that problem! Hafta break out the old pencil...

I think that this Palamino is a good overclocker, but I have no frame of reference. I guess some people are used to massive overclocks, but with my K7S5A all I ever had was like a 50Mhz overclock, so anything seems good to me in comparision ;)

Again, thanks for the info!

G

Garrett Socling - Thats one hell of a read...

I notice you said you got your CPU from 1600+ to 2000+ - All I can say is thats wicked, but I ain't touching bugger all after that experience of mine...

I personally wouldn't recommend this board to anyone, it's nice, but the BIOS is crap !!!

You know that 'Uber' BIOS I was on about, it's actually working alot better than the Offical BIOS, so I may have an attempt to overclock and see what happens ;)

Thanks again,

Ferret !

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft releases PowerToys v0.100.1, fixes a bug that made remapped keys misbehave by Ivan Jenic Microsoft just released PowerToys v0.100.1, a patch update that addresses several stability and behavior issues found in v0.100.0. The v0.100.0 patch was a significant update for PowerToys, as it introduced all sorts of new features and additions, such as a rebuilt Shortcut Guide, a Command Palette Extension Gallery, webcam overlay support in ZoomIt, and more. However, the v0.100.0 version also introduced some bugs and stability issues. And now, Microsoft is addressing these issues in the new patch. The most impactful fix in this release perhaps is in Keyboard Manager, where remapped modifier keys were being delivered as system-key events, causing unexpected behavior in apps. The clearest example of this was Alt-to-Backspace remaps, deleting whole words instead of a single character. So, if you thought there was an issue with your keyboard, Microsoft just confirmed that it was PowerToys. Beyond the Keyboard Manager fix, v0.100.1 also addresses several other issues. It fixes a bug with Power Display that was preventing monitors from waking from standby correctly. Additionally, the new update patches Quick Access crashes on launch, and resolves a Shortcut Guide crash that occurred when switching between sidebar sections. Here’s the full changelog: Color Picker Fixed a bug where the main Color Picker window could appear inside the zoomed-in picker view Command Palette Fixed Run history initialization in AOT builds Fixed a bug where the Performance Monitor dock item could show ??? after restart Fixed the Hibernate command using the Sleep icon Limited the "pin to dock" dialog to displays where the dock is enabled Keyboard Manager Fixed modifier keys remapped to non-modifier keys being delivered as system-key events, which caused unexpected behavior in apps such as Alt-to-Backspace deleting whole words Power Display Fixed a bug where selecting On in the monitor power-state control did not wake a monitor from standby Fixed built-in display detection and brightness control on dual-GPU laptops where the internal panel is driven by the discrete GPU PowerToys Run Fixed VS Code Workspaces discovery after VS Code moved recently opened workspace data to shared storage Quick Access Fixed Quick Access flyout crashes caused by unhandled XAML exceptions during launch or page navigation Shortcut Guide Fixed a crash when navigating between Shortcut Guide sidebar sections Fixed number-key rendering in shortcut manifests and added a Postman shortcut manifest Updated bundled shortcut manifests to use the literal number-key token so number keys render correctly across apps ZoomIt Fixed a race condition in audio initialization for ZoomIt video recording You can download PowerToys v0.100.1 from the official GitHub releases page.
    • OBS Studio 32.2.0 Beta 2 by Razvan Serea OBS Studio is software designed for capturing, compositing, encoding, recording, and streaming video content, efficiently. It is the re-write of the widely used Open Broadcaster Software, to allow even more features and multi-platform support. OBS Studio supports multiple sources, including media files, games, web pages, application windows, webcams, your desktop, microphone and more. OBS Studio Features: High performance real time video/audio capturing and mixing, with unlimited scenes you can switch between seamlessly via custom transitions. Live streaming to Twitch, YouTube, Periscope, Mixer, GoodGame, DailyMotion, Hitbox, VK and any other RTMP server Filters for video sources such as image masking, color correction, chroma/color keying, and more. x264, H.264 and AAC for your live streams and video recordings Intel Quick Sync Video (QSV) and NVIDIA NVENC support Intuitive audio mixer with per-source filters such as noise gate, noise suppression, and gain. Take full control with VST plugin support. GPU-based game capture for high performance game streaming Unlimited number of scenes and sources Number of different and customizable transitions for when you switch between scenes Hotkeys for almost any action such as start or stop your stream or recording, push-to-talk, fast mute of any audio source, show or hide any video source, switch between scenes,and much more Live preview of any changes on your scenes and sources using Studio Mode before pushing them to your stream where your viewers will see those changes DirectShow capture device support (webcams, capture cards, etc) Powerful and easy to use configuration options. Add new Sources, duplicate existing ones, and adjust their properties effortlessly. Streamlined Settings panel for quickly configuring your broadcasts and recordings. Switch between different profiles with ease. Light and dark themes available to fit your environment. …and many other features. For free. At all. OBS Studio 32.2.0 Beta 2 changelog: Beta 2 Changes Fixed a CI deployment issue. There are no application changes since Beta 1. 32.2 New Features Replaced add source dropdown with new dialog [Warchamp7] Improved FPS selector UX [jcm93] Added missing file support for filters [exeldro] Added ability for plugins to set custom icons for new source types [cg2121] Included .webp files when adding a directory to Image Slide Show source [TarunCore] Added copy paste functions to frontend API [exeldro] Added filter to compose SDR into HDR [jpark37] Added delete as a hotkey to delete sources on macOS [PatTheMav] Added dynamic bitrate support to multitrack video [lexano-ivs] 32.2 Changes Forced Intel-based installations to update to Apple Silicon version on macOS [PatTheMav] This change means that OBS Studio versions built for Intel-based Macs but running on Apple Silicon Macs will automatically update to OBS Studio built for Apple Silicon Macs. If an installation was using third-party plugins, those plugins will no longer load until replaced with Apple Silicon versions. Fixed audio mixer state getting out of sync when changing settings via websockets or plugins [Warchamp7] Added theming for checked QToolButtons [glikely] Improved OpenGL performance slightly on low-end machines [kkartaltepe] Set minimum size for color source to 1 pixel [exeldro] Added minimum width to spinboxes [Warchamp7] Disallowed overwriting the crash handler [sebastian-s-beckmann] Applied process mitigation policies for Windows [notr1ch] Adjusted description of multitrack video [jhnbwrs] Changed new capture devices to use fallback frame rate by default [PatTheMav] Improved DLL loading behavior on Windows [notr1ch] Limited multitrack video config to Custom service [PatTheMav] 32.2 Bug Fixes Fixed OAuth and dock state save corruption [PatTheMav] Fixed group bounds not resizing when removing items [howellrl] Fixed canvas mixes not being restored after video reset [dsaedtler] Fixed some erroneous crashes during shutdown [Warchamp7] Fixed display capture sometimes capturing black after a duplicator failure [ThrowTop] Fixed color of controls dock output buttons in System theme [shiina424] Fixed virtual camera reset failures [stephematician] Fixed potential crash when user discards changes in the settings window [suogesi] Fixed incorrect return value in virtualcam filter [xtfo] Fixed source toolbar buttons not working after dragging a source into a group [Warchamp7] Fixed properties hint icon spacing [Warchamp7] Fixed potential crash when a video device reconnects on macOS [jcm93] Fixed an issue where PipeWire could fail on NVIDIA GPUs [hoshinolina] Fixed obs_canvas_get_video_info returning incorrect framerate [dsaedtler] 32.2 Deprecations Deprecated obs_properties_add_button [sebastian-s-beckmann] Download: OBS Studio 32.2.0 Beta 2 | Portable | ARM64 | ~200.0 MB (Open Source) View: OBS Studio Homepage | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Is a fast food restaurant a good metric to compare against?
    • Grand Theft Auto VI pricing revealed alongside Ultimate Edition and pre-loading details by Pulasthi Ariyasinghe Last week, Rockstar revealed Grand Theft Auto VI pre-orders will be starting soon, and just a day ahead of that, now the studio has announced the official pricing for the highly anticipated game. This has been a hotly debated topic among fans and industry veterans for a long time, considering the game is expected to be the biggest entertainment product launch ever. The confirmed pricing for the Grand Theft Auto VI standard edition is $79.99, which Rockstar says gives access to the "single-player experience set in the biggest, most immersive evolution of the series yet." This follows what most of our readers thought would happen with the pricing too. At the same time, a $99.99 Grand Theft Auto VI: Ultimate Edition has been confirmed as well, which lands with "an exclusive collection of premium vehicles, weapons, apparel, and action threaded across all aspects of Jason and Lucia’s story." Pre-ordering will also give fans extra bonuses, including a Vintage Vice City Pack of cosmetic items as well as a free month of GTA+. Head to the official website of the game here to check out all the cosmetic rewards the Ultimate Edition and pre-orders bring. Interestingly, the studio does not mention Grand Theft Auto VI multiplayer at all in today's announcement. Perhaps this will arrive later, following the campaign launch, or the studio is keeping that reveal for a later date. Digital pre-orders for Grand Theft Auto VI will begin on June 25, 2026, at midnight local time across regions for Xbox Series X|S and PlayStation 5. The title is slated to launch on November 19 on those same platforms. Pre-loading for Grand Theft Auto VI will kick off on November 12, giving players a week to get the game ready on their consoles. As for the physical edition, Take-Two has confirmed that this will be available without a disc, with the box only containing a download code inside. This will be purchasable starting November 12, giving players who take this route time to pre-load the title as well.
  • Recent Achievements

    • One Year In
      OHI Accounting earned a badge
      One Year In
    • First Post
      Almohandis earned a badge
      First Post
    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      472
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      121
    4. 4
      Michael Scrip
      81
    5. 5
      Xenon
      70
  • Tell a friend

    Love Neowin? Tell a friend!