BF3 - BSOD "Clock interrupt was not received on a secondary processor" error & freeze

[campu0999]

BF3 - BSOD "Clock interrupt was not received on a secondary processor" error & freeze

While playing BF3 the other day i got aBSOD "Clock interrupt was not received on a secondary processor" error and now after about 30 mins of playing the screen locks up and the audio makes a high pitched noise. I managed to get a picture of the BSOD message but it hasn't returned since.

I have had this pc over-clocked previously to 4 GHz but have now reset everything to optimized defaults in bios, I also updated the bios at this time to the latest non beta update.
I have attempted to run the driver verifier as suggested but have been unable to get past the windows loading screen (ill see if I can get a picture of it, it goes all pixelates and out of line)

• OS - Windows 7 (This was the OS first installed and is the retail version)
  

I reinstalled windows when i got my SSD sometime around the beginning of this year

• Age - Brought this pc secondhand maybe 2 years ago so unsure about hardware age

• 32/64 bit - 64 bit
• CPU - i7 860
  
• Video Cards - 2x Radeon 5850 Sapphire toxic editions (firmware updated to latest)
  
• MotherBoard - Gigabyte P55A-UD6
  
• Power Supply - CoolerMaster silent pro gold 1000w
  
• Ram - 8gb Kingston HyperX

​
Let me know if you need any more information, the files asked for are atatched.
​I may not be able to try suggestions or reply till Monday (New Zealand Time).
Cheers Campbell

 

[Patrick]

Re: BF3 - BSOD "Clock interrupt was not received on a secondary processor" error & fr

Hi,

There are no attached DMP files in your output folder. Can you please manually navigate to C:\Windows\Minidump and attach any and all DMP files?

Regards,

Patrick

 

[campu0999]

Re: BF3 - BSOD "Clock interrupt was not received on a secondary processor" error & fr

Cheers for reply
no minidump files sorry i only enabled small memory dump today - i think

 

[Patrick]

Re: BF3 - BSOD "Clock interrupt was not received on a secondary processor" error & fr

For a clock interrupt BSOD (101) we need a Kernel, so change it from Small to Kernel please and enable Driver Verifier while waiting:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick

 

[campu0999]

Re: BF3 - BSOD "Clock interrupt was not received on a secondary processor" error & fr

Cheers I'll try this on monday

 

[Patrick]

Re: BF3 - BSOD "Clock interrupt was not received on a secondary processor" error & fr

My pleasure, I look forward to your update.

Regards,

Patrick

 

[campu0999]

Re: BF3 - BSOD "Clock interrupt was not received on a secondary processor" error & fr

I have tried what you have suggested and all I got was this before it loaded into windows.

Same as last time, I had to go into safe boot to remove the verifier - still no Minidump files.
I have also changed the dump file to a kernel

Cheers
Campbell

 

[Patrick]

Re: BF3 - BSOD "Clock interrupt was not received on a secondary processor" error & fr

Hi,

This could imply that verifier is catching a driver, but it's crashing so fast it doesn't have time to do its job. For now, let's disable verifier and keep the DMP type set to Kernel. When it crashes, upload it to Mediafire and paste the link here.

Regards,

Patrick