VOGONS


First post, by ubiq

User metadata
Rank Member
Rank
Member

My P2B-DS system was unstable and had some bad caps, so I recapped all of the same 16v 1000uf caps on the board to see if that would fix it. Well, it fixed the instability, but apparently introduced a new problem. The system works perfectly when running with one CPU, but as as soon as I put a second CPU in, it starts hitching up, especially when running 3d accelerated applications like Q3A or 3dMark. Roughly once a second, but it varies.

I've tried everything I can think of to troubleshoot this, and have come up empty:

  • Swapped CPUs around
  • Tried different CPUs
  • Tried Katmai instead of Coppermine CPUs
  • Tried swapping out every other bit of hardware: PSU, GPU, RAM, HD, ide cables
  • Reinstalled Win2k
  • Tried WinXP
  • Visually inspected and reflowed the caps I replaced
  • Messed around with BIOS settings (not many to play with though)

At one point I thought it might be undervolting the second CPU because it was dipping down to 1.68V or so, but when I put the Katmai CPUs in, the second CPU actually showed slightly higher than CPU1 at 2.05v and still had the stuttering issue.

It wasn't doing this before the recap, and the only other thing that changed was the CMOS got wiped during the recap. Did I break my board?

At this point I'm out of ideas and about to give up on this one. Last thing I can think of is I'm going to try reflashing the BIOS and see if that does anything .

Anyone have any other ideas?

Last edited by ubiq on 2024-10-24, 00:00. Edited 1 time in total.

Reply 1 of 8, by soggi

User metadata
Rank Member
Rank
Member

I guess you have the latest BIOS 1013, respectively latest beta 1014.003, flashed?

kind regards
soggi

Vintage BIOSes, firmware, drivers, tools, manuals and (3dfx) game patches -> soggi's BIOS & Firmware Page

soggi.org on Twitter - inactive at the moment

Reply 2 of 8, by ubiq

User metadata
Rank Member
Rank
Member

Oh my godddd. I just reflashed the BIOS and that immediately fixed it. I feel like an idiot - I've been fighting with this for three days!!

I didn't suspect the bios because I knew that I'd recently (earlier this year) flashed it with yes, the 1014.003 Beta BIOS.

Well, if anyone reads this, feel free to chime in - should I have checked the BIOS sooner, instead of leaving it for my hail mary?

Reply 3 of 8, by ubiq

User metadata
Rank Member
Rank
Member

Well, since this thread ended up being a waste of time, why stop now - impromptu build log!

At this point, I'm just going to go full-send and throw everything back in the case and install Win2k from scratch. Here goes!

The attachment IMG_1918.jpeg is no longer available

Reply 4 of 8, by ubiq

User metadata
Rank Member
Rank
Member

Dare I say, I think we're in business?

The attachment IMG_1923.jpeg is no longer available

(I haven't even loaded any specific drivers - just shotgunning 3Dmark dry, with whatever Win2k comes with!)

Reply 5 of 8, by ubiq

User metadata
Rank Member
Rank
Member

Bring thy EAX unto me...

Reply 6 of 8, by ubiq

User metadata
Rank Member
Rank
Member

We

The attachment IMG_1930.jpeg is no longer available

Are so

The attachment IMG_1939.jpeg is no longer available

Back

The attachment IMG_1943.jpeg is no longer available

RIght, think we're done here... g'night all!

Reply 7 of 8, by darry

User metadata
Rank l33t++
Rank
l33t++

That's a nice mix of old and new.

Reply 8 of 8, by soggi

User metadata
Rank Member
Rank
Member
ubiq wrote on 2024-10-23, 22:43:

Oh my godddd. I just reflashed the BIOS and that immediately fixed it. I feel like an idiot - I've been fighting with this for three days!!

Haha...see it as a positive thing and be happy it was that easy - don't be an idiot, but the lucky one! 😀

kind regards
soggi

Vintage BIOSes, firmware, drivers, tools, manuals and (3dfx) game patches -> soggi's BIOS & Firmware Page

soggi.org on Twitter - inactive at the moment