Windows BSOD when all cpu cores enabled

2

1

I'm getting a blue screen "A clock interrupt was not received on a secondary processor within the allocated time interval", just a few seconds after the Windows desktop is loaded. (For reference, this is BugCheck 0x101: CLOCK_WATCHDOG_TIMEOUT.)

  • My CPU is a Core i7 Extreme 975 and the BIOS is up to date.
  • My motherboard is a Gigabyte EX58-UD5.
  • My OS is Windows Server 2008 R2 (which I'm using as a Workstation).

For the moment, I disabled one core (out of four) on the BIOS settings and my computer is working well. But I would like to use all the cores available in my CPU, with Windows.

I think it is not related to an hardware problem, because Ubuntu (Live CD) is working on my computer with all cores enabled.

I'm NOT using Hyper-V or any other roles.

anonymous

Posted 2012-01-01T21:21:55.433

Reputation: 21

Did this EVER work? You mention your BIOS twice, but what kind of motherboard? – Ƭᴇcʜιᴇ007 – 2012-01-01T22:23:14.137

I'm always getting a BSOD. My motherboard is a Gigabyte EX58-UD5. – anonymous – 2012-01-01T23:31:44.160

2Has Windows ever worked? Is this a new install or an old install that has suddenly broken? – Mokubai – 2012-01-02T00:33:49.307

Windows works only with 3 cores. It always crashes with 4 cores. It is a new install. Before I updated my BIOS, Windows (with all the 4 cores enabled) was crashing before loading the desktop. – anonymous – 2012-01-02T01:17:50.040

Hardware problems sometimes only exhibit for particular operating systems. Can you select which core is disabled? – Harry Johnston – 2012-01-02T01:48:14.427

Is it at all possible to test the CPU in another computer, or test your computer with an alternate CPU? I know you tried Ubuntu, but I would make 100% sure that it's not the CPU first (it's possible Ubuntu doesn't use a specific hardware feature that may be damaged in that particular core). So long as your BIOS is up to date, and you experience no other hardware issues, keep your primary focus on the CPU. You may also be able to bring it to a local computer shop and have them test the processor for you, if you don't have any pin-compatible ones. – Breakthrough – 2012-01-02T02:11:00.667

Another thing to doublecheck, particularly if this is a home build, is that the motherboard supports that particular CPU model. – Harry Johnston – 2012-01-02T03:21:32.277

Can you select which core is disabled? No, I can't. Unfortunately, on the BIOS settings, it is only possible to select the number of core enabled. is that the motherboard supports that particular CPU model. The motherboard was designed specifically for Core i7. In this forum, they recommend to set the page file size manually for those who have this trouble. I have tested this method. In fact, before I tested this method, when the page file size was defined automatically, Windows was crashing during the startup (just after the loading screen)

– None – 2012-01-02T17:39:23.823

I did not install Hyper-V or any other roles, as I'm using Windows Server 2008 R2 as a Workstation OS. – None – 2012-01-03T18:31:11.170

It might still be worth trying the hotfix JdeBP refers to. It isn't clear whether or not it will install on a non hyper-V system, but it won't do any harm. – Harry Johnston – 2012-01-04T23:55:30.507

Answers

4

You have a "Nehalem" microarchitecture Intel CPU, you have Windows Server 2008 R2, and you haven't installed the hotfix.

Further reading

Microsoft blames Intel.

Intel blames Microsoft.

Always check the doco provided by the manufacturer before coming to SuperUser.

JdeBP

Posted 2012-01-01T21:21:55.433

Reputation: 23 855

The Hyper-V role is not installed by default. Anonymous, did you install Hyper-V? – Harry Johnston – 2012-01-03T01:22:00.947

The second MS link above says this in the workaround section: "You can disable the Advance Configuration and Power Interface (ACPI) C-states by using a BIOS firmware option on the computer. If the firmware does not include this option, a software workaround is available. You can disable the ACPI C2-state and C3-state by setting a registry key." Though everything is in the context of hyper-v, this appears to be a ACPI power save issue (?) – horatio – 2012-01-04T16:40:47.303

Also this linux bug listing might be old news, but possibly relevant: "This bug has not been visible until Nehalem, which advertises a CPU-C2 worst case exit latency on servers of 205usec. That (incorrect) figure is being used by BIOS writers on mobile Nehalem systems for the AC configuration. Thus, Linux ignores C2 leaving just C1, which is saves less power, and also impacts performance by preventing the use of turbo mode." ( see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/516325 )

– horatio – 2012-01-04T16:44:44.957