vwilly

I have an odd problem. Currently, when I initially turn on my machine and boot into XP it just locks up for not reason. Keyboard does not function and mouse stops moving. After a cold Restart everything runs fine. There does not appear to be any conflicts in device Manager. Has anyone else encountered this at all? I read something about the Intellimouse Explorer and the USB Hub on the boards and that happens on one of my other boxes so it sits on a PS2 port now with no problems. This sort of bothers me a little bit since everything is brand new. Any Ideas? My Setup: SuperMicro p3-dde 1 gig of Ram 2 P3 1 gig Intellimouse Explorer Visiontek GF3 400 watt PS SBlive 3c905tx Nic 3com Adaptec 2940uw SCSI Card 2 Hard drives 1 Cdrom 1 Burner

Well, it started after the install. Win2k worked fine without any problems. I have 3 dimms out of the four slots. I will give that a shot though, but I thought that was because of the Via Apollo pro 133A Chipsets. The geforce is not overclocked. As a matter of fact I am looking for a program that does that to try it out. Is that NVMax? Thanks!

This also has something to do with the MPS version control if you use an smp box. This thing threw me for a loop for the past few weeks. Pain in the arse it was.

System Specs Tyan Tiger 133 (1834) 2 P3-933 786 mb Ram V5-5500 AGP 3Com 3C905TX NIC AHA-2940u/UW Scsi Card SBLive When I load up Win2k (Computer Management)I look at the IRQ settings and the Periperhals listed above take on an IRQ: Nic = IRQ 68 SBLive = 71 V5 = 76 Scsi = 73 These are not valid IRQ's. However, they look fine during the BIOS post with no conflicts and there is no IRQ sharing going on. I have ACPI turned on in the BIOS and the numbers change to the late teens. Nic = 19 and so on. Is there anything that anyone knows of that can help me out? The reason for this is that when I play online games I notice alot of spikes in my connection which were never there before I switched to a 133 FSB machine. I am speculating that since the NIC has a valid IRQ in the post screen and not in Win2k that the IRQ assignment could be the culprit. Any ideas?? Thanks!

Thanks for the response! I have since worked out the issues. One thing that I found interesting is that during the post the devices that had the high IRQ number were really the device numbers listed in the post screen. Win2k looks at the device Numbers and thinks that they are the IRQ's. hehehe took me awhile but I think that this is a pretty safe assumption. Thanks again!!