Non-random BSOD "Clock Interrupt was not received..."

[MindBlown]

So I just built my first computer. Everything went good for about 3 hours. I installed the OS, updated drivers, installed basic programs, ran the Windows Experience Index thingy, booted Anno 1404 and tested a variety of high graphics settings,so on and so forth, and everything was good.

Until on one of my reboots, I went into the BIOS and changed the setting from Normal to Performance mode (I'm running a Asus Sabertooth 990FX motherboard). Then I booted and ran the Experience Index program again to see if anything would change. This time, when it was checking CPU performance, it BSOD'ed. "Clock Interrupt was not received on a secondary processor within the allocated time interval".

I went into the BIOS and changed the setting back to Normal mode and then tried the WEI again. BSOD. I tried 1404 again and it crashed. I ran OCCT for my CPU and everything was good. Ran it on my GPU and it was good. I ran FurMark for my GPU, fine. But if I use OCCT to stress my CPU and FurMark to stress my GPU at the same time: "Clock Interrupt was not received on a secondary processor within the allocated time interval".

So far, I've come up with 2 theories.

1. My GT440 graphics card is trying to pull too much power from my motherboard and crashing (the GT440 doesn't have external power), or

2. My processor is bad

I'll run more tests tomorrow to see if any alternate configurations have a different effect. Until then, I'll leave you with my specs and thank you in advance for any help.


AMD FX-8150
Asus Sabertooth 990FX
EVGA GT 440 (x2)
Cooler Master GX 750W
Windows 7 Professional 64-bit

P.S.: I've ordered a graphics card that draws its power from the PSU to test my first theory, (EVGA GTX 460) but I won't get it for 5 to 8 days.

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[MindBlown]

Here are the dump files. There was originally just the first one so I changed the settings like you said and then used the stress tests to crash the system. The moment I start the second test, everything freezes but I didn't get the BSOD this time, it just never recovered.

And just to clarify, I don't overclock. Ever.


EDIT: New info. I setup and started OCCT to do a 24 hour burn in for my processor, nothing else running. It crashed within 5 seconds of starting. I've done it 3 times and the first 2 it didn't give me a BSOD or a dump file, it just froze and never recovered. The 3rd gave me a dump.

 

[zigzag3143]

Here are the dump files. There was originally just the first one so I changed the settings like you said and then used the stress tests to crash the system. The moment I start the second test, everything freezes but I didn't get the BSOD this time, it just never recovered.

And just to clarify, I don't overclock. Ever.


EDIT: New info. I setup and started OCCT to do a 24 hour burn in for my processor, nothing else running. It crashed within 5 seconds of starting. I've done it 3 times and the first 2 it didn't give me a BSOD or a dump file, it just froze and never recovered. The 3rd gave me a dump.

Results 1-124, 2-101, 3-124. All hardware, all CPU.

http://www.sevenforums.com/crash-lo..._watchdog_timeout-troubleshtg.html#post567135


Stop 0x124 is a hardware error.... if you are overclocking try resetting your processor to standard settings and see if that helps ... if you continue to get BSOD here are some more things you may want to consider ..

Stop 0x124 - what it means and what to try
Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled. If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. It is good practice to run the latest drivers anyway.

4) Update the motherboard BIOS according to the manufacturer's instructions. Their website should provide detailed instructions as to the brand and model-specific procedure.

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially. The most obvious examples are the RAM and HDD(s). For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing. For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors". Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc. Should that fail to mitigate the 0x124 problem, jump to the next steps. Otherwise, if you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes. Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine. Reseat all connectors and memory modules. Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.htm

 

[Vir Gnarus]

Just to add to zigzag's diagnosis:

6: kd> !errrec fffffa800d4fd8f8
===============================================================================
Common Platform Error Record @ fffffa800d4fd8f8
-------------------------------------------------------------------------------
Record Id     : 01cd1852e1e1f80a
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/12/2012 2:20:53 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800d4fd978
Section       @ fffffa800d4fda50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=Red]Error Type    : BUS error
Operation     : Generic[/COLOR]
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f12
Processor ID  : 0x0000000000000005

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800d4fd9c0
Section       @ fffffa800d4fdb10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000005
CPU Id        : 12 0f 60 00 00 08 08 05 - 0b 22 98 1e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800d4fdb10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800d4fda08
Section       @ fffffa800d4fdb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR=Red]Error         : BUSLG_GENERIC_ERR_*_NOTIMEOUT_ERR (Proc 5 Bank 5)[/COLOR]
  Status      : 0xf480000000020e0f
  Address     : 0x0000000000000009
  Misc.       : 0x0000000000000000

2: kd> !errrec fffffa800ced48f8
===============================================================================
Common Platform Error Record @ fffffa800ced48f8
-------------------------------------------------------------------------------
Record Id     : 01cd18bb49bb7f68
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/12/2012 14:48:15 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800ced4978
Section       @ fffffa800ced4a50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=Red]Error Type    : BUS error
Operation     : Generic[/COLOR]
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f12
Processor ID  : 0x0000000000000005

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800ced49c0
Section       @ fffffa800ced4b10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000005
CPU Id        : 12 0f 60 00 00 08 08 05 - 0b 22 98 1e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800ced4b10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800ced4a08
Section       @ fffffa800ced4b90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR=Red]Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 5 Bank 0)[/COLOR]
  Status      : 0xb880000000020f0f

These are from the two 0x124 bugcheck minidumps. It may very well be core 5 (6th core) that's causing the fault. Bus errors do typically come from memory failure (check with Memtest86+ for 7+ passes) or motherboard northbridge chipset failure, but the 0x101 bugchecks hint more towards CPU failure as zigzag suspects. Also, I've seen that most software that comes installed with motherboards have bugs that actually show these problems, even if these types of bugchecks are hardware-based. Make sure to uninstall any and all software that came with your motherboard (including monitoring software) and only leave the drivers (chipset, audio, etc.) intact (update them too while yer at it). I've seen video card failure do this as well (albeit very rare), and BIOS problems also, make sure to update video card drivers and your BIOS.

 

[MindBlown]

Thanks to both of you. I also came to the conclusion that it was CPU failure. Most of the possible fixes mentioned by Zigzag were tried either actively or passively due to the fact that it was a new build and install and those are the kinds of things that I do with a new install. I'll be sure to specifically try all of your suggestions ASAP, but it will be a few days.

After I came to the conclusion that my CPU was to blame, I pulled (just about) everything out of the case. I'm having the motherboard and CPU replaced and changing the video card. I'm pretty sure that the problem isn't heat related since I could use basic programs indefinitely but it crashed within 3 seconds of the start of a CPU test. Also, I am using a Cooler Master High Air Flow case with a Cooler Master 212 EVO CPU cooler. Last night, when I successfully ran the CPU stress test for an hour, my infrared thermometer said that the base of my cooler never got above 40c and my case fans, which are controlled by the motherboard, never sped up. I'm not a tech guru but it doesn't sound like overheating to me. And, as I said, I never overclock.

It looks like I'll get my replacements about next Wednesday and I'll have an update within a few hours of then. Thanks again for the help.

 

[zigzag3143]

Thanks to both of you. I also came to the conclusion that it was CPU failure. Most of the possible fixes mentioned by Zigzag were tried either actively or passively due to the fact that it was a new build and install and those are the kinds of things that I do with a new install. I'll be sure to specifically try all of your suggestions ASAP, but it will be a few days.

After I came to the conclusion that my CPU was to blame, I pulled (just about) everything out of the case. I'm having the motherboard and CPU replaced and changing the video card. I'm pretty sure that the problem isn't heat related since I could use basic programs indefinitely but it crashed within 3 seconds of the start of a CPU test. Also, I am using a Cooler Master High Air Flow case with a Cooler Master 212 EVO CPU cooler. Last night, when I successfully ran the CPU stress test for an hour, my infrared thermometer said that the base of my cooler never got above 40c and my case fans, which are controlled by the motherboard, never sped up. I'm not a tech guru but it doesn't sound like overheating to me. And, as I said, I never overclock.

It looks like I'll get my replacements about next Wednesday and I'll have an update within a few hours of then. Thanks again for the help.

Well good luck and let us know if we can help. Infrared thermometer, I like. {grin}

 

[Vir Gnarus]

Remember that infrared therms only record surface temperature. While the cooler is designed to attempt to distribute the heat evenly as much as possible, point of contact with the CPU die will always be the hottest compared to the rest of the cooler.

Me and zigzag both had a feeling it was going to end up being CPU related, but it is always best to make sure any other potential candidates - which are easier and cheaper to address - are taken care of before resorting to something more time and resource-consuming as swapping hardware with a replacement. That's just common sense.

Good luck on the CPU replacement, let us know of any updates.

 

[MindBlown]

Well, I'm back. I received my parts Friday afternoon so I rebuilt and started running tests. 28 hours of Memtest86+ produced 8 passes and 0 errors. I did a 15 minute benchmark burn-in on my video card with no problems, and a 25 hour burn-in on my processor with no problem.

After that completed, I went into the BIOS and changed the manufacturer's setting from "Normal" mode to "Performance" mode and rebooted. The first thing I ran was the Windows Experience Index thing and it crashed twice. Furmark ran fine but OCCT caused a BSOD within 3 seconds, just like last time. I changed the setting back to normal and tried OCCT again. This time it said "Error detected on core #-1" and crashed the program. I tried again and it BSOD'ed. I'm attaching the dump files, if you would be so kind as to read them for me but I have a feeling that it's going to be a malfunctioning core again.

Assuming that is the case, the solution that comes to mind is to get the processor replaced but also to change to a different motherboard, since apparently clicking one wrong (and very large) button in the BIOS is all it takes to destroy the processor.

Any advice is welcome.



UPDATE: Just for the sake of being though, I went into by BIOS and reset it. Now I can run OCCT without crashing or BSODing.

 

[Vir Gnarus]

So you are no longer suffering any issues at all after you reset the BIOS to factory defaults? In that case, you may be overclocking it improperly ("Performance" settings on most mobo BIOSes are OCed settings) and/or you may have heating issues that could be caused by improper placement of the heatsink or improper paste application. Make sure to test your idle and high load temps with the BIOS and something like HWInfo to make sure that's not the case (make sure to check "Sensors only" at startup). If you wish, you can log an idle and high load session for us to look at as well.

 

[MindBlown]

Good idea. I'm doing that now. How long would you recommend that I log the results for each test?


UPDATE: I let my computer idle for a while and then did a short "shapshot" log at Idle. Then I ran OCCT for 45 min and FurMark for 15 min simultaneously. Here are the logs.


UPDATE: Before I start another thread let me ask if any of you have experience with the 'Windows Kernal Mode Display Adapter stopped Working And Has Recovered' problem?

 

[Vir Gnarus]

Those tests don't look problematic. The CPU looks very cool and stable, as well as the GPU, and the PSU rails look stable as well, so there's no evident signs of problems from the logs (evident being keyword here). I'm not personally familiar enough with OCing to be able to ascertain what's good vcore voltages or not, but if you have the BIOS set to factory defaults then it should be good.

Just to make sure, did you manage to update everything, like the chipset drivers and especially the BIOS? I don't recall you mentioning you ever did so in the conversation so far.

As for the error message you're getting, that's called a TDR. You can get plenty of details about it here. What I'm curious about is why it called it "Windows Kernel Mode Display Adapter". Often it should just say "Display adapter". Hmm. Can you send us one more BSOD report as previously? Thanks.

 

[MindBlown]

Sorry about the delayed response, I've been out of town. What kind of BSOD do you mean? If you mean a BSOD related to the video driver problem, it doesn't cause one. The screen goes black for a few seconds and then turns back on and the error is displayed in a balloon in the bottom right.

And you're right, I haven't updated my BIOS or chipset drivers. I'm doing that now.


UPDATE: I've finished updating BIOS, chipset drivers, etc. I've been thinking about how to replicate the video driver problem but haven't thought of anything yet. The good news is that it hasn't happened today, the bad news is that I have no idea why not.

 

[Vir Gnarus]

What I meant by BSOD report was the JCGriff Report as you provided in the past, mentioned here. I am aware what happens during a TDR. Of course, there are times when TDR triggers multiple times in quick succession, thereby having Windows be alerted something bigger is happening and will cause a TDR-triggered BSOD.

Keep us in touch on any updates if your system happens to BSOD or not. If it fails to BSOD again, it may have simply been a BIOS or chipset driver issue.

 

[MindBlown]

As I said I updated my drivers and so forth and I haven't had any trouble at all for the last two days. I'm going to wait just a little longer before I mark this thread as solved just in case but I think everything is good now. A huge thank you to both of you for the help.

 

[Vir Gnarus]

That's good to hear, mate. I think we might be able to write this off as being related to the BIOS or chipset drivers in need of some freshening up. You can mark solved at your discretion!