XP Home or the new hardware

[systempat]

Did a new build over the weekend. Not going to post all the hardware now as I have to take off. It's based on a 1800+ Athlon and an EPOX 8k5a2+ which is a kt333 chipset. All other hardware is new.
It went together nicely and booted up first time. Got all the hardware configured and XP home installed.
I am getting an occasional error message which requires a reboot. It seems to be the XP version of the BSOD.
Message is IRQL-NOT-LESS-LESS-THAN-OR-EQUAL.

What the hell is that? Other than sounding like an IRQ is involved I have no clue.

[systempat]

Here's the particulars on the system build:
EPOX 8k5a2+ motherboard VIA kt333
AMD Athlon 1800+ XP
Maxtor 40 gb hard drive
256 MB Kingston valueRam pc2100
Abit Siluro Geforce4-420 video
Lite-On CDRW 40x-12-48
The motherboard - CPU - and memory are a Multiwave combo, included their choice of a cooler for the Athlon
And an InWin mid-tower case with a 300-wt "Powerman" PSU and 1 case fan

With WinXP, should I be installing the VIA 4-in-1 drivers and the video card drivers from the retail box?? I was a little confused about this. XP seemed to have already installed things as all the devices said they had Microsoft drivers.

---->>> Pat

[cuffs007]

Hi

straight from the MS site....To troubleshoot hardware failure stop errors

Check that the devices on your computer have drivers that are signed and certified by Windows Hardware Quality Labs (WHQL). Run Sigverif.exe to check for unsigned drivers.
Check the manufacturer for driver updates that may be available for your hardware.
Update any software that uses filter drivers (for example, antivirus, disk defragmentation, remote control, firewall, or backup programs).
Uninstall any non–critical hardware and software to help isolate the item that may be causing the problem.
Install Windows XP in a new folder. Add drivers and restart as you proceed, to isolate the driver that is causing the problem.
Run Recovery Console, and allow the system to repair any errors that it detects.

or, just click:
http://www.microsoft.com/windowsxp/p...eshoot.asp#TSE

Good luck

[systempat]

Thanks for the info, Cuffs
The sigverif.exe really helped. I knew I had loaded some drivers that had warned about being "signed", but assumed that since they came from the manufacturer's CD they were right. Went thru removing & adding to re-install drivers and let WinXP do its thing to find the drivers. This took care of all the exceptions, but I have no valid driver for USB 2.0. I suspect that I have to go to EPOX website.
Ran for about two hours after update and had no error screens. That doesn't prove it's fixed yet, but it looks good !!!