Cronic BSOD when playing- A clock interrupt was not received on a secondary processor

Hofer · Aug 9, 2014

Hello Everyone,

I am having a regular BSOD, half the times I play a very graphic intensive game, like Battlefield 4 I ran in the "A clock interrupt was not received...".
It started happening a year ago, but now it's much more frequent, I am even able to reproduce it (which is good for troubleshooting) since half the times I play a game, it happens.

It may have something to do with the Logitech G930 driver, since before the crash, the sound of the wireless headphone starts to sound "metalized" and have some interruptions. Or maybe it's just a consequence because a minute or two before the actual crash all USB devices start acting strange, the headset simply stops playing audio, the mouse becames very slow and when I type the keyboard just outputs 70% of the keystrokes. Since the headset needs a higher bandwidth, it's the first one to suffer (I think).

Maybe something else is doing this to the USB bus or maybe the USB bus is causing the problem.

I've already run a Memtest86+ for 22 hours and no errors were detected. The CPU has no overclock and is not overheating.

Here are my specs:

· OS: Windows 7 x64
· CPU: Core i7 920
· RAM: 3xCorsair XMS 1600Mhz (running at 1066)
· MotherBoard: Asus P6T
· Video Card: NVIDIA GeForce GTX 275
· Power Supply: Akasa 650W
jcgriff2 is annexed.

Patrick · Aug 9, 2014

Re: Cronic BSOD when playing - A clock interrupt was not received on a secondary proc

Hi,

We'll need a kernel-dump to properly debug this type of bug check as not information lies within the minidump.

Kernel-dumps are located at C:\Windows and named MEMORY.DMP. If there is nothing there, you may need to enable generation of them - Creating a Kernel-Mode Dump File (Windows Debuggers)

It'll be too large to upload here, so use Onedrive, Mediafire, etc. Please don't use DropBox, my ISP hates DropBox.

Regards,

Patrick

Hofer · Aug 9, 2014

Re: Cronic BSOD when playing - A clock interrupt was not received on a secondary proc

Sure Patrick, here's a link to it: https://drive.google.com/file/d/0BzFyB88ayVkNbnFMeDVnOUlzM2c/edit?usp=sharing

Patrick · Aug 9, 2014

Re: Cronic BSOD when playing - A clock interrupt was not received on a secondary proc

Would you mind changing the permissions, please? I need to request access with the way it's currently set. If you're uncomfortable with a public link, you can PM me.

Regards,

Patrick

Hofer · Aug 9, 2014

Re: Cronic BSOD when playing - A clock interrupt was not received on a secondary proc

I've changed it, please try again.

If there's any problem I will upload to another server.

Patrick · Aug 9, 2014

Re: Cronic BSOD when playing - A clock interrupt was not received on a secondary proc

Thanks very much.

It's a corrupt dump:

Code:

0: kd> ~1
WARNING: Unable to reset page directories
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

Please make sure all of the following settings are in place:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Regards,

Patrick

Hofer · Aug 10, 2014

Re: Cronic BSOD when playing - A clock interrupt was not received on a secondary proc

I did what you said, the only configuration that wasn't already what you said was the WERS, since it was disabled.

So I need to create a crash again and upload the next dump?

Patrick · Aug 10, 2014

Re: Cronic BSOD when playing - A clock interrupt was not received on a secondary proc

Correct, good work.

It'll need to be a kernel-dump from this point on (MEMORY.DMP).

Regards,

Patrick

Hofer · Aug 11, 2014

Re: Cronic BSOD when playing - A clock interrupt was not received on a secondary proc

Hello Patrick,

I did what you said but at the same time I tried some things to stop the BSOD's.

I was researching about this BSOD and it happens sometimes when people try to overclock the Core i7 920 and it becomes unstable.
So I went to the BIOS and disabled Hyper Threading, Speedstep, Turbo Boost, Clock Spread Spectrum and I set all voltages of the CPU manually (they were "auto").
I set them to a higher value than the default, for example: vcore is at 1.3V instead of the default 1.2V.

After that, I played for 8 hours and my computer was solid stable, I felt no performace hit on gaming because I disabled HT or Turbo Boost.

For some reason, my CPU was unstable at stock conditions. I will now re-enable HT and see what happens.
Them I will start lowering the voltage until the PC becomes "barely stable".

Do you know any tools to verify the "stability" of the CPU?
Prime95 was not good since I've already runned it for ours before the tweaking and my PC didn't crash.
Maybe the Logitech Driver generated a particular kind of load that triggered the CPU fail more easily.

Patrick · Aug 11, 2014

Re: Cronic BSOD when playing - A clock interrupt was not received on a secondary proc

Sounds like a faulty CPU to me.

Sometimes you get a really bad batch that made it through testing. It'll require more voltage as time goes on (as it'll hit levels of degradation faster than a normal CPU).

I would definitely re-enable HT, yes. HT is pretty important outside of game scenarios as you can carry out more instructions and such. It's certainly not the reason you're crashing, and if it is, then you have a faulty CPU anyway.

Regards,

Patrick

Search

Search

Cronic BSOD when playing- A clock interrupt was not received on a secondary processor

Hofer

Member

Attachments

Patrick

Sysnative Staff

Hofer

Member

Patrick

Sysnative Staff

Hofer

Member

Patrick

Sysnative Staff

Hofer

Member

Patrick

Sysnative Staff

Hofer

Member

Patrick

Sysnative Staff