UH HUH!
Good ol' IRQL_NOT_LESS_OR_EQUAL. This one tells you with pretty good accuracy the problem is isolated at the CPU.
IRQL = Interrupt Request Level.
First parameter = Target Memory Address
Second parameter = IRQ Level At Time of Reference
Third parameter = Read/Write Bitmask
Fourth parameter = Source Memory Address
Basically first parameter isn't a valid memory address, and third parameter is neither a valid bitmask of 0 or 1.
So you have either not enough Vcc (Vcore), you have out of whack CPU Clock Skews, or you might need more Vtt voltage.
This tells you the problem lies on the CPU side of the IOH, but more than likely it is between the IMC and Processor. CPU is either corrupting the addressing/data, or IMC is.
CPU is more likely to trigger an IRQL Bugcheck though as IRQL is used for Kernel Mode scheduling/thread context.
Edit: If you ever get stuck you can reference MCE Bugcheck codes from here.
http://msdn.microsoft.com/en-us/library/ms789516.aspx




Reply With Quote

Bookmarks