BSOD: A clock interrupt was not received on a secondary processor - Windows 7 x64

A

Acry

New member
Joined
Apr 9, 2014
Posts
4
Hello, I just installed Windows 7 today, started to play a game (League of Legends) and within an hour of play got this BSOD. I'm somewhat savvy on bsods, and solving them but this is one I've never gotten before and I'm not too good at interpreting dump files. I have attach everything needed I believe!

Thanks for any help :)

· x64
· Win 7 (installed today)
· Ultimate x64 legitimate
· 1 week
· Nope

· AMD FX-6350
· Nvidia GTX 770
· Asus m5a97 le r2.0
· Corsair 600MX

· Manu: Me

· Desktop


 

Attachments

Hi,

There are no minidumps located in your Jcgriff2 output folder, and the kernel-dump is corrupt. With this said, you may not have your dump settings correct. Please check everything here is correct:

1. 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'.

2. 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'.

3. 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
 
Patrick said:
Hi,

There are no minidumps located in your Jcgriff2 output folder, and the kernel-dump is corrupt. With this said, you may not have your dump settings correct. Please check everything here is correct:

1. 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'.

2. 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'.

3. 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
Click to expand...
That's weird - but I've done all as you said. Everything was already checked and as you stated they should be, except the WERS service that was on manual. That's now on automatic start.

Thanks for the help :)

Should I just wait for the next crash then and come back if it occurs? If I remember correctly, it was an 0x1 bug check that was on screen when it occurred, if this helps any.
My cpu was running hot (140 F) then I replaced the heatsink and I'm now down to 100-110F if this means that its was possible it was overheating (but I don't think it got much higher than 150F if at all)
When I check the debug file myself in windbg this is what I get on the only place I can click "analyze"

http://puu.sh/82H7t.png

Hopefully this info can help instead of just waiting for another crash :s
 
Thanks for the information. 140F is around 60c, which is not too hot. It's a bit warm for idle operation temperatures, so as long as you were able to bring that down, that's good.

Unfortunately, that is of no help given that's what I already know. It's indicating there's a corrupt modulelist (drivers, etc) due to the dump process not completing gracefully. This can be due to one of many things, such as the pagefile not being set up properly, improper dump settings (which we've checked now), hardware failure (RAM, CPU, etc). We'll find out what the problem is accordingly, don't worry.

Keep me updated when the next crash occurs.

Regards,

Patrick
 
Patrick said:
Thanks for the information. 140F is around 60c, which is not too hot. It's a bit warm for idle operation temperatures, so as long as you were able to bring that down, that's good.

Unfortunately, that is of no help given that's what I already know. It's indicating there's a corrupt modulelist (drivers, etc) due to the dump process not completing gracefully. This can be due to one of many things, such as the pagefile not being set up properly, improper dump settings (which we've checked now), hardware failure (RAM, CPU, etc). We'll find out what the problem is accordingly, don't worry.

Keep me updated when the next crash occurs.

Regards,

Patrick
Click to expand...
Alright, thanks for the help Patrick. I'll make sure to come back asap when it happens.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top