Facing BSOD(Page fault Non page area/Clock interrupt not recd) + hangs

Guys..

I been facing some issues with my relatively new CPU.
I have an Intel i5 2400 cpu, combined with 4GB DDR3 memory.
Mobo is DH67BL - revision 3. No GPU installed.
Power supply is via Corsair VX450.

Problem i been facing:

1) BSOD saying that A clock interrupt wasnt recd.

Screenshot:-
http://i42.tinypic.com/262lbhc.jpg


2) BSOD saying: Page fault in non paging area.
Couldnt grab a screenshot for this.

3) Display randomly goes off for a split second and reappears.. but the color of the panes go blue (i havent chosen blue. My setting is for clear pane.)

Screenshot:-
http://i40.tinypic.com/o94vfs.png

This error solves itself after random number of hours/mins

4) Display vanishes for a split second and reappears, and a small balloon at the bottom right corner prompts that the display driver had stopped working.

5) System plain hangs/stops responding. Randomly happens.. but more so while on youtube, or after hrs of it idling, i come back to the comp and try to scroll the content onscreen.
Sometime it revives from the stuck state as if nothing happened, sometimes i have to give it a cold boot.


6) While reading forums with blue bands.. the blue bands kinda form blurry bars which stretch till the end of the screen. I tried to grab a screenshot but the screenshots were clean. The bands moved as i dragged the image about.

7) Also, my comp's display went off one day and within a second came back with a blue-ish hue. It restored itself but again has gone back to blue-ish.



I never have overclocked my processor.

What can be the reason for this ? Pls help me out here..



Other relevant information:
Windows 7 x64
No other OS resides/installed on system
Full Retail Version
OS was installed in July.

The cpu+mobo were purchased in July
I had Dynet RAM, 3 x 1GB each.. now using Corsair (2x2GB). Purchased in Aug i think.
The issue of hanging etc was faced with the Dynet RAM as well.

RAM info:
http://i41.tinypic.com/20hrolw.png
http://i44.tinypic.com/neuxzk.png

33 of 44 crashes were related (as you surmised ) to a Bugcheck of 101. The rest were various hardware complaints. Please read below for what to try.

STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg


You should also update to SP-1 when you resolve this issue.

Many thanks zigzag.
Its a relief to see that i have a start on this. My proccy's warranty period expires by june end. So i need to check and get this resolved asap.

Btw, is there a possibility that a proccy which hasnt seated in its slot properly may be causing this..?
(that is what a friend of mine came up with)

I ll try to glean as much info from the thread mentioned above in the meantime. :)

trackblazer said:

Many thanks zigzag.
Its a relief to see that i have a start on this. My proccy's warranty period expires by june end. So i need to check and get this resolved asap.

Btw, is there a possibility that a proccy which hasnt seated in its slot properly may be causing this..?
(that is what a friend of mine came up with)

I ll try to glean as much info from the thread mentioned above in the meantime. :)

Anything is possible, but it isnt likely unless you have had these probs from day one, or have physically moved the computer.

It could also be BIOS, heat, and very rarely software.

The system runs fine for days (2.5 days tbh when i ran it 24 x 7) and then it got stuck as i tried to read a page and scrolled the content. I have experienced hanging issues 3-4 times in a day as well.. So its that random.

And yes, i remember the BSOD issue cropping up within 2 weeks of the assembling of this rig.
I even discussed the hanging issue with friends who cudnt understand why a newly built system will behave like this.

trackblazer said:

The system runs fine for days (2.5 days tbh when i ran it 24 x 7) and then it got stuck as i tried to read a page and scrolled the content. I have experienced hanging issues 3-4 times in a day as well.. So its that random.

And yes, i remember the BSOD issue cropping up within 2 weeks of the assembling of this rig.
I even discussed the hanging issue with friends who cudnt understand why a newly built system will behave like this.

Could simply be either a failing CPU, or perhaps a second run cpu. Have you run stress tests on it?

No.
I am a total noob in these test/running of tests. Hence why it took me so long to come out here :|

If you mean the stress test mentioned in the post #2, then i am going to run them shortly.
It ll help me if you can pin point which stress test you are pointing at cuz the link leads to a page where many test are listed. So it ll help me if you can specify which ones i need to run specifically according to my rig's config as not all may be warranted.

trackblazer said:

No.
I am a total noob in these test/running of tests. Hence why it took me so long to come out here :|

If you mean the stress test mentioned in the post #2, then i am going to run them shortly.
It ll help me if you can pin point which stress test you are pointing at cuz the link leads to a page where many test are listed. So it ll help me if you can specify which ones i need to run specifically according to my rig's config as not all may be warranted.

Unfortunately it may take all of these tests to provide a comprehensive answer.