Board or processor Failure?

[JacksonPerez]

The system was operating alright up till last night. My brother and I were playing SC2 side by side when abruptly the system simply nose dived and failed with a BSOD.

Upon undertaking to reboot I could not acquire any type of signal to the monitor. I switched out to my backup HD with XP on it and I handled to acquire it too boot however when I tried a Prime95 Run on it it BSOD's right after Test 1 with IRQ_LESS_THAN_OR_EQUAL.

Now normally I figured this has to be the RAM. So I drew out the G.SKills and simply put in some essential Sticks that I had kicking around. This permitted me to at least boot back into Win 7 thus I figured the problem was solved.

[ThompsonHarris]

Run memory test on experienced good sticks to stress the NB. Likely the board giving up.

[GonzalezBrown]

Can you attempt in safe mode and then work prime? Also attempt disabling on board sound and nic etc. and work in safe mode. Confirm your bios are updated too to perhaps help with IRQ appointment issues.

[LewisClark]

When I ran Memory test for win7 and the G.Skills were in the computer it failed at 55% and locked the computer. When changed over to the essential sticks it BSOD'd twice where I couldn't see what it said.

Those two Failures are simply ones I manged to catch its done the total memory dump thing on both sets of RAM that I have run but the error has been dissimilar each time. And to top it off like I said 3 of 4 workers failed with Hardware occurrence in several TXT file that I couldn't situate.

[WalkerCook]

Are you functioning this on thine table out the case later checking in heat sinks disliking everything and what not?

[PerezMorris]

I am belief more like the RAM was defective and it screwed something up in windows when it went south namely because while I acquired a some BSOD's later the first set I have not had one since running with my essential on board. BIOS is up to date before this occurred, as well as new drivers so I cannot for check why that might have been an issue.

While both 3.0 and Chisk are right with that one error I believe that was caused by the memory behaving something bad in the system.

[HallMiller]

Unless the G skills surely died and in the procedure may have imperfect Windows therefore the IRQL error. A re-install may be required.