Windows 7: BSOD errors, Machine check Exception, Clock interrupt not rec 9C

dirtbag · 06 Nov 2012

Hi all im new here,Grab yourself a coffee / tea this is a long one !

For the last 2 weeks my computer which is circa 3 years old is starting to crash quite abit. I am due an upgrade and was going to sell off some bits, but I am having trouble working out which peice of my hardware is causing problems, thus not wanting to buy new kit when the old kit is not faulty.

The i7 920 is overclocked to 3.5ghz alkas nero cooler, v core is 1.26v, cpu temp on idle is 39 - 45 degrees, running Arma 2 it moves up to circa 56 degrees. Motherboard is an Asus P6T6WS revolution with the latest bios. Graphics card is XFX 295 GTX, with latest drivers.

Then :
The problem started when the computer used to randomly freeze (Mainly just as the welcome screen comes up) Then apon reboot id notice my Graphics card drivers disappered and that I had to reisntall them.

I decided to do a format, and after about 3 installation attempts (One attempt ended in my screen going RED tint colour) to get a fresh installation.
I opened up the computer and gave everthing a real clean, this seemed to cure the Red screen issue. As well as a bios reflash

Now :
Most of the time everying runs fine including games, HD video rendering with Sony vegas pro 9 etc.
Then suddenly I get a BSOD crash, normally Machine check exception error, sometomes the clock interrupt not recieved. When I restart the computer and load back into windows I notice the sound is jittery as if there is a loose wire. Loading up a game is also laggy as well as video playing / rendering. I also get this with all overclocking off and everything left stock
Then as the computer is left on for a while on OR restarted the issue is gone. Weird !

I have included (which I hope is correct following the guide) the dmp file of the latest crash as well as a picture , along with my pc probe readings.

Thanks for taking the time to read this, and I hope you can help

Thanks

DB

These are the errors that I have recorded.

roblem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800B6B5038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\110512-30747-01.dmp
C:\Users\****\AppData\Local\Temp\WER-41870-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 9c
BCP1: 0000000000000000
BCP2: FFFFF880009FBC70
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\110612-28407-01.dmp
C:\Users\****\AppData\Local\Temp\WER-39546-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Arc · 07 Nov 2012

Hello dirtbag.

upgrade the network driver: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC. It goes back to Thu Feb 26 14:34:13 2009. And most of the error entries are associated with it.

Download the network card driver from manufactuer's website Realtek
Then reinstall the driver:

Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
Double click to expand "Network adaptors".
Right click your network card and click Uninstall.
Check "Delete driver software for this device" check box, click OK.
Restart the computer
If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

Anyway, your dump says:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff880009fbc70, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c )

Followup: MachineOwner
---------

It is a hardware error. You need to test your hardware components.

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

► Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

► Stress test the CPU.
Hardware - Stress Test With Prime95

But, as long as the Service Pack 1 and other updates are installed, there is a chance of instability in software's side.

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Let us know the results.

dirtbag · 07 Nov 2012

Hi thanks for the in depth reply. I forgot to mention that sometimes my nic fails (connection drops) but my router shows that i have connectivity. I will do all of the above and report back. Thanks again

dirtbag · 07 Nov 2012

Let us know the results.

Hi okay so far I have tested my gcard and had furmark running at 1900 x 1200 (my native res) for 10 minutes, max temp 91 and no higher, no artifacts.
Is it safe to say the Gcard is in the clear ?

Ran Prime 95 on the CPU, had probe 2 running at same time. Within 3 minutes the temp raised to 80 and alarm went off so I stopped the test. I have (what I think) a good cooler alkas nero and with my machine oced it keeps it idle under 40 sometimes. Have I found my problem, the cpu ?

I also had a clock interupt crash just now so I've added the file for you to look at

Need to test the ram next and report back
Thanks again

Arc · 08 Nov 2012

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880030f9180, 6}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880030f9180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.

Follow it: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

dirtbag · 08 Nov 2012

Many thanks, and here is more. This is the result from last nights test on all 12g of my ram.

Arc · 08 Nov 2012

So you got the result. Now Test the modules individually, to rule out the faulty one.

dirtbag · 08 Nov 2012

Many thanks again for taking the time to read through my logs. Is it possible that the dodgey ram could be causing all these issues?

Arc · 08 Nov 2012

Most possible. A corrupted RAM can make all the troubles.

dirtbag · 09 Nov 2012

Quote: Originally Posted by Arc

Most possible. A corrupted RAM can make all the troubles.

Hi, I found the bad stick with first attempt and removed it. Ran memtest over night no errors. Ran Prime95 and worked fine, furmark again fine. So lets see if i get any more errors. Once again thanks very much for your help

Windows 7: BSOD errors, Machine check Exception, Clock interrupt not rec 9C

BSOD errors, Machine check Exception, Clock interrupt not rec 9C problems?