[CaptainHaplo]

Ok - IRQ is old school stuff - it means interrupt request. Originally (back in the dos days) you would have a piece of equipment that would use an IRQ address and a DMA range. (DMA being Direct Memory Access) Its old school because it goes back to how things interact direct with hardware. It was usually dealt with in regards to things like sound cards.

Nowadays almost all the hardware access stuff is handled by HAL - or the Hardware Access Layer (and not the sentient insane computer).

This helps only so much - as windows doesnt give you a really good way to see IRQ settings except thru the MMC, and thats not going to really show us the problem. For some reason, the picture doesnt display anymore on your thread, though if I recall the msg was IRQ not less than or equal (or something similiar).

Its important that you noted it happens when you browse files - but seems to run fine in safe mode.

SAFE MODE USES THE SAME MEMORY AS NORMAL WINDOWS - so this is a big pointer away from it being a ram issue. If it was memory - you would see the same issue in safe mode.

You didn't say anything about adding new hardware - so we can rule it out being a hardware install issue. Again - since it works in safe mode - failing hardware would fail regardless of the OS mode. You mentioned overheating concerns - but is your box going to overheat browsing files in normal windows and not do so in safe mode? No - so we can toss that idea.

That leads us to ask the question of what is different between safe mode and normal windows operation. The biggest answer - DRIVERS!

It may or may not be SP3. I would suggest the following steps:

Roll back drivers for most major components.

You mentioned having a RAID array/controller - make sure you go to the manufacturer's website and get a driver for it and install it. Since your having this issue with drive access - check with the mb manufacturer and install their driver - SP3 or another windows update may have overwritten the working driver. Even without a raid array, make sure your HDD controller has a driver that was made for it - and not a default microsoft one.

Same with your video and audio cards - update the drivers from the manufacturers.

Also check to see if your mb uses something like a via bridge - if so - install the latest via 4n1 driver. Bridge driver errors can cause some weird stuff man.

Doublecheck the network driver, and any other peripherals you have - and don't forget stuff like printers and scanners - they can make wonky stuff happen as well.

Do this and then let us know if you still see the funkyness. My bet is the Raid Array Driver got "updated" either by SP3 or by a windows update.