• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New AXP-M build problems + UPDATE2

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Hi mooojojojo


Sorry if I haven't read everything in this thread. But have you looked for some modded BIOS for your mobo which include a built-in L-12 mod? There are many versions around for my mobo, perhaps some as well for yours. Proly easier than doing it manually.

Fern
 
Fern: yes I did find a modded BIOS, but I'm not sure I want to install it.. did you experience any issues with your modded BIOS? Or did things go smoothly? What if the BIOS file is corrupt? I'll end up with a dead motherboard! I wish more companies would implement the DualBIOS Gigabyte has...

0roo0roo: the PSU is a Fortron 300W.

CZroe: I ran Memtest, and it was running all night (~8h 30mins), completed the test 32 times without a single error...

EDIT: Forgot to mention, Memtest was completed with the CPU at 11x200MHz, 1.600V, RAM at 3-3-3-11 timings and Default voltage.
 
0roo0roo, it runs stable as it is now (11x200), it's just that Prime won't comlpete the Blend test (no restarts since Sunday). Haven't tried it yet at stock speeds. Will do today / tomorrow.

EDIT: Ok, I see how this sounds.. no restarts since Sunday, but it's been bahaving lately 😉
 
Yeah.. right.. stable my arse. Blue screen, the error being in something called WATCHDOG.SYS. Can't get any more random than that. Will try stock speeds now, and if it doesn't work it better be strong enough to withstand a 9-story fall.. 😉
 
Now this is getting very stupid..

I couldn't run the CPU at 13.5 x 133MHz.. it would keep saying 'Bad overclock' and put it at 6x100MHz. So I put it at 9 x 200MHZ (still 1800MHz), and that worked, but Prime again bombed after 1h 6mins (it would give an error much quicker previously).

Now what can it be? Is the chipset getting too hot (haven't checked)? Why can it complete Memtest with no problem, but not Prime?
And why the heck won't it run at 13.5 x 133MHz?!

I need help!!! 🙂
 
Any ideas on how I can run the CPU at the default CPU clock?

And is the L12 mod still a viable solution? I'm beginning to doubt anything will help it...

And 3rd: if I decide to switch this combo (AXP-M + NF2) with a NF3 + Sempron 754 combo, which is the CPU I should get (i.e. which Sempron) and what is a good mobo for that. Thanks!
 
Originally posted by: mooojojojo
Fern: yes I did find a modded BIOS, but I'm not sure I want to install it.. did you experience any issues with your modded BIOS? Or did things go smoothly? What if the BIOS file is corrupt? I'll end up with a dead motherboard! I wish more companies would implement the DualBIOS Gigabyte has...
Click to expand...

Sorry for the delay in responding: My OC went fine, haven't bothered with the BIOS yet. I was looking at them only to try and get my FSB stable above 220mhz (a mobo limitation it seems).

Re: 13.5 x 133mhz. Diff mobo's have problems some multi's. I'm not familair with your borad. You may ned to check around. Keep in mind which BIOS you are running now. I have seen that impact which multi's work on Asus NF2 mobo's.

Fern
 
Originally posted by: mooojojojo
Originally posted by: Excelsior
If prime bombs..it isnt stable.
Click to expand...
Yeah.. thanks for that insight, but I'm aware of that 😉
Click to expand...


Then why...why..bother having it set that high? Do like others suggested, and run it at default speed, then run prime and increase until it bombs.


And you said "I'm not very concerned about Prime 95 as long as I don't get any automatic restarts, but I think that somehow the two problems are connected and I'd like to fix them somehow. Thanks in advance for your replies and ideas!"

Why the hell arent you concerned? If p95 fails within 10minutes, you should be concerened. Even if you don't have random restarts.
 
Ok, I tried with the CPU at 8x200MHz and the RAM at 100MHz (200DDR) to rule them out as a possible cause for the failures and just to test how the FSB behaves at 200MHz (400DDR). Prime ran for 8hours before I aborted it - it's pretty obvious it doesn't have any problems with that FSB speed I guess, right?

Next I will try the CPU at 11x200MHz and the RAM still at 100MHz to see if it's the CPU and I have a feeling it will be fine again. If it indeed has no problem with the CPU at 2200MHz and the FSB at 200MHz (400DDR), then that would leave the RAM, right? But why then Memtest completed successfully 32runs with no errors, before I aborted it at the 8th hour of running?
Click to expand...

I could be wrong here. Hopefully others can chime in. But I'm thinking if you're running a divider to keep the ram @ 100/200 FSB (instead of 200/400) you haven't ruled out the mobo (North Bridge). The mem controler in the NB may be having probs at 200/400.

If the cpu operates fine at 11 x 200, I think you can rule it out as the prob.

Fern
 
Originally posted by: Excelsior
Originally posted by: mooojojojo
Originally posted by: Excelsior
If prime bombs..it isnt stable.
Click to expand...
Yeah.. thanks for that insight, but I'm aware of that 😉
Click to expand...


Then why...why..bother having it set that high? Do like others suggested, and run it at default speed, then run prime and increase until it bombs.


And you said "I'm not very concerned about Prime 95 as long as I don't get any automatic restarts, but I think that somehow the two problems are connected and I'd like to fix them somehow. Thanks in advance for your replies and ideas!"

Why the hell arent you concerned? If p95 fails within 10minutes, you should be concerened. Even if you don't have random restarts.
Click to expand...
Excelsior, you have a point. I'm doing this right now.. testing the RAM and FSB without pushing the CPU to see whether they work to rule them out individually as problems.

And I was wrong by not being concerned with Prime.. obviously it's a good indicator that somethings wrong and that sooner or later the system will BSOD. So.. thanks, you're right, and if you can give me a good advice or opinion as to what is the matter with my system, that will be greatly appreciated! 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top