SN45g and AMD 3200+ problems

[chewdog316]

Well i searched and cannot find help so maybe yall can help. Im running a sn45g v2 with a amd3200+ and it will not recognize my processor. I flashed the bios with an upgrade and now it sees it as a 2500+. And whenever i go into the bios it resets the bios to the original bios and not the upgraded. weird isnt it. please help me out. th0ough my pc runs its not running as it should. i checked the processor and yes it is a 3200. thanks.

[Apex]

are you defo sure that the cpu you have is a 3200 and not a rebadged cpu ?

if it's a 3200 for sure then you could try setting the settings to run the cpu at 11 * 200 to give it 2.2ghz which is the correct speed for the cpu to be running at.

if the cpu is failing to work yada yada then it might be case that the chip is faulty in some ways.

it would help if you gave a bit more info on the setup.

Andrew

ps

i have a sn45g v2 with a 2500 xp-m @ 2.2ghz

[chewdog316]

Its not a repackged proccesor. I changed the fsb to 200 and it fixed that but now no matter what i set things too the memory still sets at 400 mhz and then i get that blue screen of deatch after post. It says win32k address bf somethin really long. Then it does a physical memory dump. What the heck man!

[Boris25]

Its not a repackged proccesor. I changed the fsb to 200 and it fixed that but now no matter what i set things too the memory still sets at 400 mhz and then i get that blue screen of deatch after post. It says win32k address bf somethin really long. Then it does a physical memory dump. What the heck man!

...what's the memory rated at? If it's not DDR400 or above then it won't be happy running a FSB of 2ooMHz.

[mrdata2003]

if not PC3200 then you will need to change the fsb/ram ratio in the bios

[chewdog316]

Well its 400mhz and its 3200 so im not sure whats going on. The guy at Frys said to mess with voltage settings. I dont see any voltage settings in the bios. Am i lookin in the right spot. Maybe i need to change some of the other settings too. What settings should i use there?

[yamangman]

It don't sound like a 3200+ to me. You get BSOD's and other weirdness when you overclock a CPU without increasing the vcore voltage.

[St3v3]

I got this too.... I think some batches of Nforce2 Ultras obviously can't cope with the 400mhz bus for some reason. My 3200 goes up to around 195mhz bus and anything above gives me a BSOD in windows when running benches. I have to up the multiplier and try to keep the bus as high as I can.

[cmaness]

I have a similar issue, with a fresh out of the box XP 3200, bios flashed to latest and greatest, yet it recognizes the chip as an Athlon 1100 mhz

If I make any adjustment in the bios and save, it won't reboot. I have to kill power, and clear CMOS just to get it to boot again. Recognizes my OCZ PC3200 (2x512mb, dual channel) just fine with proper cas, but the proc isn't recognized.

Before you say bad proc, it recognizes and runs fine in a second machine I have.

Any suggestions?

[schmunk]

cmaness: Make sure that the FSB is set to 200MHz (It's currently at 100MHz - 11x100 = 1100MHz for the CPU). Also make sure that the CPU voltage is set to 1.65v.

My shuttle resets as you describe when it's undervolted or overclocked - resetting back to 600MHz for mine (as it's a mobile CPU).

[cmaness]

cmaness: Make sure that the FSB is set to 200MHz (It's currently at 100MHz - 11x100 = 1100MHz for the CPU). Also make sure that the CPU voltage is set to 1.65v.

My shuttle resets as you describe when it's undervolted or overclocked - resetting back to 600MHz for mine (as it's a mobile CPU).

I have checked this. It's not even saving the bios changes. As for the 11x, that is what shuttle recommends for Barton +3200. I am in the midst of a conversation with them, but they don't wish to listen. The one thing I have noticed is after I have flashed the bios, my checksum value is 3EE0h, but once I reboot, the checksum is 0h, which means something is not holding in the memory on rebooot.

[schmunk]

Actually, I remember now - when my Shuttle first arrived it did similar things. I swapped in the CMOS battery from my old system and it worked fine. Give that a try...

[cmaness]

Actually, I remember now - when my Shuttle first arrived it did similar things. I swapped in the CMOS battery from my old system and it worked fine. Give that a try...

I have already tried that too. It gave the same results.

[DJWillis]

Well its 400mhz and its 3200 so im not sure whats going on. The guy at Frys said to mess with voltage settings. I dont see any voltage settings in the bios. Am i lookin in the right spot. Maybe i need to change some of the other settings too. What settings should i use there?

If you are talking about Memory Voltage settings?

Simple answer is that unless you know what you are doing DONT CHANGE anything regards mem. voltages as there are some faults with some of the SN45G's boards/BIOS combos that will kill the board (yep, a BIOS option that can kill an M/B, lovely). There are work arounds (of the solder variant) if you just have to push your luck .

As for your CPU speed problems, I can only agree.

I have got an SN45G that is confined to the scrap as it's the most unstable, poorly implemented board I have had in a long time (and I am a big Shuttle fan, got 6 ATM).

Early versions of the board seem to not like 3200+'s at all and there is nothing a BIOS update seems to do to solve the problem. There are loads of threads about with just this problem with constant CMOS resets and the CPU’s running well below stock if the Shuttle even POST’s at all.

[cmaness]

I haven't adjusted any voltage. I even took shuttle's advice on this and lowered the cas ratings in the bios, with no different outcome. When I forwarded shuttle the link for this forum, and let them know I wasn't the only one with this problem, I got one message:

"Thank you very much for this information as clue, and we'd info relate
department. Any update will release on our web site. Thanks again."

Their second response to the same e-mail was as follows:

"Actually, another chipset provider make FSB and memory clock to the
CMOS, then it can turn back to original BIOS setting by power off after
clear CMOS, but NForce not, they put memory clock to the CMOS and let the
FSB to the BIOS, so if want to clear CMOS to original BIOS setting, yes, but
it is not including clear FSB too, you need to do is:
1. unplug power code from supply.
2. clear COMS by jumper(JP1).
3. plugs power cable.
4. press and hold keyboard of insert key (Ins) while, then press power
button until system boot up.
Please kindly understand that we not this guide in .pdf form cause
this troubleshooting skill we released by nVIDIA. Thanks."

My response to this was as follows:

" Put the scripted guide down and actually offer some support. I work in a services related IT field, and if I gave scripted responses of this nature, I wouldn't have a job. I am thoroughly disappointed in your responsiveness to this problem.

I have loved Shuttle products from the first day you came on the IT scene, but this is really leaving a bad taste in my mouth.

I have owned three different shuttle SFF's, and always been amazed with their responsiveness. This is the first relavent issue I have ever had with one. I would hope there would be a better answer than clear CMOS and reboot.

As far as this being Nvidia's problem, and not yours: wrong answer! Nvidia provided the chipset for YOUR motherboard, but they didn't build it for you. Do you not have enough pride in the product you build to back it?"

I'll keep you updated on the answers I get. Keep in mind this is their branch in Tiawan sending these answers. The one in the US sent me a number to contact them with, but I haven't been home during their hours of operations. If I make any headway there, I will post it here as well.

[Gipo]

what brand of ram u running?