I'm running Windows 2k with SP 4 on a gigabyte 7NNXP Pro with a XP 2800,
gb of Mushkin ddr 400 dual channel, BFG 6800 Ultra, Maxtor SATA 120's on Sil
in base, a set of Maxtor IDE 40's on gigaraid in RAID, IDE master DVDR
slave DVD IDE Sec master CDRW/DVD slave Zip 250, Sound blaster Audigy
Platinum on board LAN and GigaLAN. I have tried two different AMD XP3200
(BIOS ID) CPU's one will not boot as a 3200 but will run as a 2500. The
other boots as a 3200 and runs as a 3200 by Win 2K will BSOD on start up. I
can put the 2800 back in and reset the BIOS to my normal settings and it
will start right up.
1- I should not have to reload the system just for changing the CPU?
2- Clear the BIOS install the new CPU reset the BIOS and start the
computer. Right?
3 -Are there forged CPU's the numbers break down to the AMD OPN?
4- What the $#&& am I doing wrong?

JD
(E-Mail Removed)am

bigdawg wrote:
> I'm running Windows 2k with SP 4 on a gigabyte 7NNXP Pro with a XP 2800,
> gb of Mushkin ddr 400 dual channel, BFG 6800 Ultra, Maxtor SATA 120's on Sil
> in base, a set of Maxtor IDE 40's on gigaraid in RAID, IDE master DVDR
> slave DVD IDE Sec master CDRW/DVD slave Zip 250, Sound blaster Audigy
> Platinum on board LAN and GigaLAN. I have tried two different AMD XP3200
> (BIOS ID) CPU's one will not boot as a 3200 but will run as a 2500. The
> other boots as a 3200 and runs as a 3200 by Win 2K will BSOD on start up. I
> can put the 2800 back in and reset the BIOS to my normal settings and it
> will start right up.
> 1- I should not have to reload the system just for changing the CPU?
> 2- Clear the BIOS install the new CPU reset the BIOS and start the
> computer. Right?
> 3 -Are there forged CPU's the numbers break down to the AMD OPN?
> 4- What the $#&& am I doing wrong?
>
> JD
> (E-Mail Removed)am

Looking at this motherboard, there seem to be some booting issues when
the FSB is at 200. Which it is with the 3200+ but not the 2800+.

I recommend updating the BIOS to the latest revision.

Most of the time you don't run into bios bugs, but when you do it
REALLY sucks.

http://www.gigabyte.com.tw/Support/m...tName=GA-7NNXP

Let us know whether that cures it

Already running the F20 BIOS Second thing I tried.. Also forgot to mention
in the other post that I have 2
of these boards. what I have not done is rob the CPU to test the other
board its a 3200. same BIOS
same board different memory and hard drive set up but 1 will run the 3200
and one will not.

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> bigdawg wrote:
>> I'm running Windows 2k with SP 4 on a gigabyte 7NNXP Pro with a XP 2800,
>> gb of Mushkin ddr 400 dual channel, BFG 6800 Ultra, Maxtor SATA 120's on
>> Sil
>> in base, a set of Maxtor IDE 40's on gigaraid in RAID, IDE master DVDR
>> slave DVD IDE Sec master CDRW/DVD slave Zip 250, Sound blaster Audigy
>> Platinum on board LAN and GigaLAN. I have tried two different AMD XP3200
>> (BIOS ID) CPU's one will not boot as a 3200 but will run as a 2500. The
>> other boots as a 3200 and runs as a 3200 by Win 2K will BSOD on start up.
>> I
>> can put the 2800 back in and reset the BIOS to my normal settings and it
>> will start right up.
>> 1- I should not have to reload the system just for changing the CPU?
>> 2- Clear the BIOS install the new CPU reset the BIOS and start the
>> computer. Right?
>> 3 -Are there forged CPU's the numbers break down to the AMD OPN?
>> 4- What the $#&& am I doing wrong?
>>
>> JD
>> (E-Mail Removed)am
>
> Looking at this motherboard, there seem to be some booting issues when
> the FSB is at 200. Which it is with the 3200+ but not the 2800+.
>
> I recommend updating the BIOS to the latest revision.
>
> Most of the time you don't run into bios bugs, but when you do it
> REALLY sucks.
>
> http://www.gigabyte.com.tw/Support/m...tName=GA-7NNXP
>
> Let us know whether that cures it
>

Tried with only a single memory stick?

"bigdawg" <(E-Mail Removed)> wrote in message
news:uTPGZ$(E-Mail Removed)...
> Already running the F20 BIOS Second thing I tried.. Also forgot to
mention
> in the other post that I have 2
> of these boards. what I have not done is rob the CPU to test the other
> board its a 3200. same BIOS
> same board different memory and hard drive set up but 1 will run the 3200
> and one will not.
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> >
> > bigdawg wrote:
> >> I'm running Windows 2k with SP 4 on a gigabyte 7NNXP Pro with a XP
2800,
> >> gb of Mushkin ddr 400 dual channel, BFG 6800 Ultra, Maxtor SATA 120's
on
> >> Sil
> >> in base, a set of Maxtor IDE 40's on gigaraid in RAID, IDE master DVDR
> >> slave DVD IDE Sec master CDRW/DVD slave Zip 250, Sound blaster Audigy
> >> Platinum on board LAN and GigaLAN. I have tried two different AMD
XP3200
> >> (BIOS ID) CPU's one will not boot as a 3200 but will run as a 2500.
The
> >> other boots as a 3200 and runs as a 3200 by Win 2K will BSOD on start
up.
> >> I
> >> can put the 2800 back in and reset the BIOS to my normal settings and
it
> >> will start right up.
> >> 1- I should not have to reload the system just for changing the CPU?
> >> 2- Clear the BIOS install the new CPU reset the BIOS and start the
> >> computer. Right?
> >> 3 -Are there forged CPU's the numbers break down to the AMD OPN?
> >> 4- What the $#&& am I doing wrong?
> >>
> >> JD
> >> (E-Mail Removed)am
> >
> > Looking at this motherboard, there seem to be some booting issues when
> > the FSB is at 200. Which it is with the 3200+ but not the 2800+.
> >
> > I recommend updating the BIOS to the latest revision.
> >
> > Most of the time you don't run into bios bugs, but when you do it
> > REALLY sucks.
> >
> >
http://www.gigabyte.com.tw/Support/m...tName=GA-7NNXP
> >
> > Let us know whether that cures it
> >
>
>

bigdawg wrote:
> Already running the F20 BIOS Second thing I tried.. Also forgot to mention
> in the other post that I have 2
> of these boards. what I have not done is rob the CPU to test the other
> board its a 3200. same BIOS
> same board different memory and hard drive set up but 1 will run the 3200
> and one will not.
>

Rats. Your troubleshooting life has just gotten a lot less fun.

Try stealing the memory from the board that boots, and see what
happens.

Swapping proccessors will do no harm, may as well try.

THere is also the possiblity that your RAM is marginal, works at 166
FSB but not at 200.

Run memtest86 with both settings.

Good luck.

tried with a single stick of the Mushkin and Corsair XMS. Both are dual
channel sets and tried both single and dual. Now get this I put the 3200 in
a Soyo KT600 Dragon board reset the bios and the board jumper to 200 and it
works just fine with either set of memory. but it is not dual channel and
only has the IDE's in use the SATA are disabled in the BIOS onboard sound
and 10/100 so the only thing in use is a AGP card. go figure
"DL" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Tried with only a single memory stick?
>
> "bigdawg" <(E-Mail Removed)> wrote in message
> news:uTPGZ$(E-Mail Removed)...
>> Already running the F20 BIOS Second thing I tried.. Also forgot to
> mention
>> in the other post that I have 2
>> of these boards. what I have not done is rob the CPU to test the other
>> board its a 3200. same BIOS
>> same board different memory and hard drive set up but 1 will run the 3200
>> and one will not.
>>
>> <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> >
>> > bigdawg wrote:
>> >> I'm running Windows 2k with SP 4 on a gigabyte 7NNXP Pro with a XP
> 2800,
>> >> gb of Mushkin ddr 400 dual channel, BFG 6800 Ultra, Maxtor SATA 120's
> on
>> >> Sil
>> >> in base, a set of Maxtor IDE 40's on gigaraid in RAID, IDE master
>> >> DVDR
>> >> slave DVD IDE Sec master CDRW/DVD slave Zip 250, Sound blaster Audigy
>> >> Platinum on board LAN and GigaLAN. I have tried two different AMD
> XP3200
>> >> (BIOS ID) CPU's one will not boot as a 3200 but will run as a 2500.
> The
>> >> other boots as a 3200 and runs as a 3200 by Win 2K will BSOD on start
> up.
>> >> I
>> >> can put the 2800 back in and reset the BIOS to my normal settings and
> it
>> >> will start right up.
>> >> 1- I should not have to reload the system just for changing the CPU?
>> >> 2- Clear the BIOS install the new CPU reset the BIOS and start the
>> >> computer. Right?
>> >> 3 -Are there forged CPU's the numbers break down to the AMD OPN?
>> >> 4- What the $#&& am I doing wrong?
>> >>
>> >> JD
>> >> (E-Mail Removed)am
>> >
>> > Looking at this motherboard, there seem to be some booting issues when
>> > the FSB is at 200. Which it is with the 3200+ but not the 2800+.
>> >
>> > I recommend updating the BIOS to the latest revision.
>> >
>> > Most of the time you don't run into bios bugs, but when you do it
>> > REALLY sucks.
>> >
>> >
> http://www.gigabyte.com.tw/Support/m...tName=GA-7NNXP
>> >
>> > Let us know whether that cures it
>> >
>>
>>
>
>

OK I think I have it figured out. the gigabyte board, Mushkin memory and
the XP3200 conflict (DUH). I started a fresh install reformatted 1 drive and
tried to load Win2K kept getting random errors datestamp Win32K etc as I
said both sets of memory are dual channel but the Mushkin is Hi Prem CAS2
and the corsair is CL2 (which I thought was the same) but the CAS rCas
timing with the Mushkin was 2 2 2 6 and the corsair is 2.5 3 3 8. but after
installing the Corsair I have not had 1 problem reloaded and am doing
updates right now.
a beer to anyone who can figure out why?

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> bigdawg wrote:
>> Already running the F20 BIOS Second thing I tried.. Also forgot to
>> mention
>> in the other post that I have 2
>> of these boards. what I have not done is rob the CPU to test the other
>> board its a 3200. same BIOS
>> same board different memory and hard drive set up but 1 will run the 3200
>> and one will not.
>>
>
> Rats. Your troubleshooting life has just gotten a lot less fun.
>
> Try stealing the memory from the board that boots, and see what
> happens.
>
> Swapping proccessors will do no harm, may as well try.
>
> THere is also the possiblity that your RAM is marginal, works at 166
> FSB but not at 200.
>
> Run memtest86 with both settings.
>
> Good luck.
>

memory can be picky with some mobo / cpu configerations

"bigdawg" <(E-Mail Removed)> wrote in message
news:e$(E-Mail Removed)...
> OK I think I have it figured out. the gigabyte board, Mushkin memory and
> the XP3200 conflict (DUH). I started a fresh install reformatted 1 drive
and
> tried to load Win2K kept getting random errors datestamp Win32K etc as I
> said both sets of memory are dual channel but the Mushkin is Hi Prem CAS2
> and the corsair is CL2 (which I thought was the same) but the CAS rCas
> timing with the Mushkin was 2 2 2 6 and the corsair is 2.5 3 3 8. but
after
> installing the Corsair I have not had 1 problem reloaded and am doing
> updates right now.
> a beer to anyone who can figure out why?
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> >
> > bigdawg wrote:
> >> Already running the F20 BIOS Second thing I tried.. Also forgot to
> >> mention
> >> in the other post that I have 2
> >> of these boards. what I have not done is rob the CPU to test the
other
> >> board its a 3200. same BIOS
> >> same board different memory and hard drive set up but 1 will run the
3200
> >> and one will not.
> >>
> >
> > Rats. Your troubleshooting life has just gotten a lot less fun.
> >
> > Try stealing the memory from the board that boots, and see what
> > happens.
> >
> > Swapping proccessors will do no harm, may as well try.
> >
> > THere is also the possiblity that your RAM is marginal, works at 166
> > FSB but not at 200.
> >
> > Run memtest86 with both settings.
> >
> > Good luck.
> >
>
>

bigdawg wrote:
> OK I think I have it figured out. the gigabyte board, Mushkin memory and
> the XP3200 conflict (DUH). I started a fresh install reformatted 1 drive and
> tried to load Win2K kept getting random errors datestamp Win32K etc as I
> said both sets of memory are dual channel but the Mushkin is Hi Prem CAS2
> and the corsair is CL2 (which I thought was the same) but the CAS rCas
> timing with the Mushkin was 2 2 2 6 and the corsair is 2.5 3 3 8. but after
> installing the Corsair I have not had 1 problem reloaded and am doing
> updates right now.
> a beer to anyone who can figure out why?

I think if you can get Gigabyte to confirm this, then they may release
bios revision f21. I wouldn't hold my breath, but you may want to send
an email their way.