Funky recent P4 build problems

VirtualLarry

No Lifer
Aug 25, 2001
56,587
10,227
126
Ok, a while back, I got a P4 Mobile 2.0Ghz CPU from a friend for nothing. I bought a P4P800 from Computer Geeks, but the system didn't get built for months because I was looking for a cheap retail Intel HSF. Having found one, I put the system together, and installed using a slipstreamed XP SP2 CD that I made.

I started using a single 256MB DIMM, Apex brand with Elpida DRAM. Stick is marked as PC2100 in the SPD, but sold and tested working find at PC2700.

The mobo is an i845P-based board, which supports 200Mhz FSB, which isn't officially supported by Intel for the chipset. No CPU or DRAM voltage adjustment in BIOS though.

Mobile P4 CPUs default to a 12x multi when used in desktop S478 mobos - without SpeedStep support in mobo/chipset/bios, no way to kick in the "AC power speed" multi, which on this CPU is 20x. But the good news is that @ 200Mhz FSB, the CPU will run at 2.4Ghz.

With just the PC2700 DIMM, I could cold-boot @ 200Mhz FSB about 80% of the time. Otherwise a C-A-D soft reboot would get the video to come up. But I had trouble installing XP SP2 with that setup, got occasional errors about unable to read files off of the CD, and setup hung at the second stage, and there was video corruption. There were also a few pixels that appeared out of place on the screen using Partition Commander to partition initially, which worried me.

So I instead installed a 512MB double-sided DIMM (KVR -C3A), intending to use it since it was PC3200. But I cannot easily cold-boot at all with that DIMM installed! Sometimes I get a single long beep (identical to if I pull all DIMMs completely out), and sometimes just nothing. C-A-D doesn't help.

Two things come to mind: vDIMM = 2.6v for this, and there is no BIOS adjustment, and also, the chipset only offers manual CAS settings of 1.5/2.0/2.5, no 3.0 setting, but this DIMM is rated CAS 3.0 @ 200Mhz.

I only pulled the PC2700, as it failed Memtest86+ testing first pass @ 200Mhz, which is understandable.

I fiddled with things, and managed to get it to boot fine @ 166Mhz FSB / PC2700, and PC Health shows vCore = 1.53v - 1.55v, which is I assume standard desktop CPU voltage, which should be enough to take a Mobile P4 CPU quite some ways in OC'ing, enough for 2.4Ghz stable I think.

So I install XP SP2 again, after re-formatting/partitioning, and this time, no glitches or hangs during setup.

But after setup completed, and I start configuring Windows, it hard-hangs!

No C-A-D, no hitting the Power button (ACPI soft-off settings), nothing helps but Reset.

This happens several times, and I'm not sure what to think. A few times, the video display screwed up royally as it hung, and then went to a black-screen a couple of seconds after.

Interestingly enough, I couldn't reproduce any hang when booting into Safe Mode. The video driver used in S.M. is "VGA.SYS" I think, so perhaps it is a video card/driver issue.

So I'm thinking, either it's the video card, or the drivers for it, the default XP SP2 native drivers for a 2MB PCI S3 Virge DX/GX video card. It almost feels like there's some sort of address-decode error, or some other kernel-mode something is scribbling over the S3's MMIO mappings, but perhaps I'm reading way too much into this.

I went back and Googled the known issues with XP SP2 and Dell laptops - all seemed to be a Prescott/microcode-stepping issue. Mine's a Northwood CPU, but it did come out of a Dell laptop.

I'm just hoping that the CPU and mobo are kosher, since before I acquired an Intel HSF, I tried doing some BIOS-level boot-testing without any significant heatsink, and the chip hit 80C and shutdown in no short order. Not to mention, I don't know if the CPU got damaged before it got to me.

I also have the 300W generic PSU in this case, taken from a Codegen case+PSU combo, although it was powering my AMD XP2000+ rig with multiple HDs/opticals just fine. It has the extra 4-pin square 12v molex, and is plugged in to the mobo.

I don't have another PCI video card to test with at the moment, sadly. My S3 PCI *is* my test card, but I wonder if I've fried it with static at some point in the past.

Oh, one other thing, just before it froze the first time, or just after, something made a small noise in the machine. I inspected visually and smelled for anything that might have gone "pop" and didn't find anything, so I think it might just have been the HD's write-back cache getting flushed, but it did sound slightly wierd.

I'm going to run the Intel FID util to check microcode steppings, and perhaps flash to version 1.3 of the BIOS (currently 1.2), and try changing the video driver from S3 to standard VGA.

The fact that I can't cold-boot @ 200Mhz FSB, with the KVR PC3200 512MB DIMM still bothers me though. If the DRAM can't run @ 200Mhz / CAS2.5, then I should still be able to boot and get into BIOS setup, so there may be either a PSU or mobo vDIMM/vCore issue going on here still.
 

VirtualLarry

No Lifer
Aug 25, 2001
56,587
10,227
126
Ok, more testing. Setting the "Video Accelleration" slider down to one notch from left doesn't help, disabling "write combining" doesn't help. There doesn't seem to be any easy way in XP to install the "Standard VGA" driver over the in-box S3 driver.

Nearly all of the hangs appear to happen after I select something, or while something is drawing on-screen. About 25% of the time, the screen scrambles after the hang. Slowing the FSB down to 133Mhz (x12 = 1.6Ghz) doesn't help either. Switching the keyboard from PS/2 to USB doesn't help either. (Am using an IBM Trackpoint M13 keyboard.)

I noticed something though - the resource usage for the VGA card is A0000-AFFFF, not A0000-BFFFF, which is what I thought the standard was. Also E0000000-E3FFFFFF.
 

stevty2889

Diamond Member
Dec 13, 2003
7,036
8
81
I think this 2MB PCI S3 Virge DX/GX video card is your problem..I was trying to install winXP at one point using an old trident 2mb PCI video card that I keep as my test card while I was waiting for my 6600 to arrive. Everything seemed to install fine, and I could get in to safe mode fine, but windows would always crash before I could get all the way in. Windows XP would not run with the 2mb graphics card period. I'm am almost 100% sure that is your problem, the card is way too old to handle windows XP even if it has drivers that support it.
 

VirtualLarry

No Lifer
Aug 25, 2001
56,587
10,227
126
Thanks for the input. The card used to work fine, but I haven't had it in a machine in a year or so.

I re-partitioned and installed W2K SP4 (slipstreamed) from scratch - install went without a hitch, but again, it froze during the first normal bootup. Several times I tried and it froze, it seemed to happen mostly when I was messing with the MMC snap-ins, and twice happened when clicking "Removable Storage", after clicking on Logical Drives or Disk Defragmenter.

I then remembered - when I was first setting it up, without a HD connected - I accidentally had the IDE cable on the secondary port reversed. I'm really wondering if perhaps I fried the mobo's IDE controller, or at least port 2, or perhaps did something to my DVD drive. It defaulted to PIO mode after the W2K SP4 install, but that could be just because it's an old drive.

I set it to run the 3D OpenGL 'Pipes' screensaver, I figure that puts a decent amount of stress on the CPU and RAM and video card, I'm going to check it in a while and see if it has locked up or not. If it doesn't (@ 2Ghz), then the vCore and vDIMM and FSB should be fine, as should the VGA card.. it's just really strange that the screen got scrambled so many times with XP SP2 after it froze, and it hasn't shown any strange visual anomolies with W2K SP4.

The mobo's BIOS has ACPI permanently enabled, so I can't try turning that off. :(

Edit: I've hacked the Display.inf file to force-install the VGA.SYS driver instead of the S3 driver, and that seems to have stopped the freezing. Not sure if it's just a buggy S3 driver, or bad hardware, but I'm just going to pray that I didn't fry the IDE secondary port and hope things keep running. To my credit, the IDE cable I used, had the red pin1 stripe on the wrong side of the connector... "Made in China", of course. Guess they do things backwards over there, must be some communist plot or something. :p