the big problem of the micrsoft error messages is that they tell you almost nothing about what is really happening
the error can tell you that it's a driver but it can be almost anything of the damn windows
i had 17 similar pcs after one weekend almost all got the same bluescreen every boot, some few days later, but we didn't change anything with them, they've been running for many weeks/month.
the error was PAGE_FAULT_IN_NONPAGED_AREA
all pcs were protected with hdd sherrif a pci card that restores the previous state when booting so changing anything on the hd is impossible, every boot the same windows.
then we noticed that during that weekend there was the change from daylight saving time to normal time, i don't know what the error message has to do with that but it's the only explanation.
after booting one time in nonprotected mode everything worked fine again
crazy windows ...
the only way to find out the cause of your bluescreen is (because windows isn't open source
), to create a complete memory dump and then debug this with the debugging tools and symbols, there are a few sites on the net that can explain how to do but you should know a bit about assembler and how the memory, drivers, ... are managed in windows.
all these tools are available at the microsoft page.
and i don't think it is a motherboard issue... i got a bluescreen everytime when i tried to install of win2k and i removed all components except video card too, resetting to bios default solved the problem. but i don't remember what the errormessage was.
FortiTude
