I love this board personally. Try setting the ck ratio switch to >= 12.5 and keep the other at 133 and see if that helps. If that doesnt, i have no other suggestions. If it boots in 100 mode and auto settings, then i dont know. If it doesnt, (I cant remember if you said it did) try reinstalling the actual cpu again and make sure it is in fully and locked in. Good luck man.
I had this same problem a few months ago. It's almost always caused by a driver problem. However, it's difficult to determine which driver is causing the problem because when you get the infamous blue screen you don't get any specific information indicating a driver name. Have you updated any drivers recently? If so, try uninstalling them and restoring the original ones.
Anyway, it's simple to use. Open an MS-DOS prompt window and type "verifier". Then set it up to check every driver for IRQL_LESS_THAN_OR_EQUAL errors and restart your PC. It will restart extremely slow because it's doing its verifying work on every driver. Proceed to run the application that hangs up your PC. Then, when you get the blue screen, it will tell you the name of the driver that's causing the problem. In my case it was due to an "updated' audio driver I downloaded from the Microsoft webpage. I uninstalled it and restored the original driver that came with my motherboard and the problem was solved.
From this experience I learned that if my drivers are working correcly, I should never download "updated" drivers from Microsoft.
I had the same problem last night, I've got a Gigabyte 8IEXP board, I''m running a single stick of 512MB 2700 DDRAM, yep I know the board only supports 2100 RAM, but this should not be a problem ?? or should it.. Vendor wanted me to do a straight swap for the ram without giving me any credit !!!!, after I found out my hardware would not support the faster speed RAM.
I've only encounted this problem once (so far), but my PC now has automatically commenced a system shutdown 3 times in the last few days, at least it gives me a minute warning, so that I can abort it by typing "shutdown /a"at a command prompt. The shutdown is iniated by the NT System Authority, is all that it tells me, I'm wondering if the two issues are related, I'm running XP SP1