BSOD CLock interrupt was not recieved on a secondary processor - Windows 7 x64

S

schwalbe24

Member
Joined
Jul 30, 2014
Posts
9
hey guys i have been getting bsod's for a long time now and various types of them. But usually it is the one mentioned in the title and they have amped up recently. usually i would bsod maybe once every few days but today i've had 4 :( i am almsot certain it is a drriver issue somehwere. Also it has been happening today usually when i am playing Aces High. i am also new to what info i need to post so any help would be appreicated.

system info:

Operating system- Windows 7 ultimate 64bit
Processor- Amd Fx 6200 @stock
Installed ram- 8.0gb
Gpu- Nvidia Gtx 580
motherboard- gigabyte 970A-d3
 

Attachments

Hi,

We need a kernel-dump for this type of bug check.

Please upload the MEMORY.DMP located in C:\Windows to Mediafire, and then paste the link here.

Regards,

Patrick
 
Patrick said:
Hi,

We need a kernel-dump for this type of bug check.

Please upload the MEMORY.DMP located in C:\Windows to Mediafire, and then paste the link here.

Regards,

Patrick
Click to expand...

i cant seem to find the memory.dmp file only the minidump is there..any ideas. also i see that is is configured or is it?
 

Attachments

  • 68127165395242a8efa9504621aedc39.png
    68127165395242a8efa9504621aedc39.png
    312.4 KB · Views: 3
Everything looks good there, is there no MEMORY.DMP file (not folder) in C:\Windows?

If not, check:

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

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

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.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick
 
Patrick said:
Everything looks good there, is there no MEMORY.DMP file (not folder) in C:\Windows?

If not, check:

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

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

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.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick
Click to expand...

ok i had to change it to small memory dump i am trying to recreate the Bsod now,will get back to you asap with the files
 
Sorry, that's not what I wanted. I wanted you to keep it on kernel dump, but I pasted the wrong one.

Please change it back and ensure all of other settings are in place.

Regards,

Patrick
 
As I said above, I need the kernel-dump.

Check C:\Windows for a MEMORY.DMP file.

Regards,

Patrick
 
yea sorry patrick i found my mistake, i misread one of the instructions you gave me and messed up the memory dump path,sorry about that..i will send you the dump when it bluescreens. Again thank you for being patient and helpful
 
hey man i followed all of your instruction on how to set it up, but no luck. i dont see file that says memory.dmp and now after bsods its doesnt even create a file in the minidump,any help? i also tried setting the kernal dump setting through a registry file found here Dump Files - Configure Windows to Create on BSOD - Windows 7 Help Forums

but yea its bsods maybe 2-3 times since our last messages and still no memory.dmp file

*update ima wait one more time for it to bsod and see wat happens ill post back here.
 
If it doesn't generate a crash dump again, run Memtest for no less than 8 passes:

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works (you don't need to read, it's only for those interested in the specifics):

Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.

The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.

The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.

Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 
I agree, not only has the same bugcheck stayed through another install we can see two null processor cores.

Code: 
Child-SP          RetAddr           Call Site
[COLOR="#FF0000"]00000000`00000000 00000000`00000000 0x0[/COLOR]

  4    fffff880009b3180  fffff880009be040 ( 0)                       fffff880009be040  ................

Child-SP          RetAddr           Call Site
[COLOR="#FF0000"]00000000`00000000 00000000`00000000 0x0[/COLOR]

Processor 3 being the problematic one with a zeroed stack it's never a good sign.

I see a DPC still waiting one the 3rd core.

Code: 
[COLOR="#0000FF"]3[/COLOR]: kd> [COLOR="#008000"]!dpcs[/COLOR]
CPU Type      KDPC       Function
 3: Normal  : 0xfffff88002fdb9e8 0xfffff80002ff3a70 [COLOR="#FF0000"]nt!PpmPerfAction[/COLOR]

Never good having DPCs laying around like that.
Especially given it's a processor device driver routine I wouldn't put it past a bad CPU.

Run memtest86 as patrick has suggested first.

Are you overclocking?
 
Jared said:
I agree, not only has the same bugcheck stayed through another install we can see two null processor cores.

Code: 
Child-SP          RetAddr           Call Site
[COLOR=#FF0000]00000000`00000000 00000000`00000000 0x0[/COLOR]

  4    fffff880009b3180  fffff880009be040 ( 0)                       fffff880009be040  ................

Child-SP          RetAddr           Call Site
[COLOR=#FF0000]00000000`00000000 00000000`00000000 0x0[/COLOR]

Processor 3 being the problematic one with a zeroed stack it's never a good sign.

I see a DPC still waiting one the 3rd core.

Code: 
[COLOR=#0000FF]3[/COLOR]: kd> [COLOR=#008000]!dpcs[/COLOR]
CPU Type      KDPC       Function
 3: Normal  : 0xfffff88002fdb9e8 0xfffff80002ff3a70 [COLOR=#FF0000]nt!PpmPerfAction[/COLOR]

Never good having DPCs laying around like that.
Especially given it's a processor device driver routine I wouldn't put it past a bad CPU.

Run memtest86 as patrick has suggested first.

Are you overclocking?
Click to expand...

i will run memtest to make sure, but i guess this means new cpu. exactly what i was trying to avoid :(
 

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

Back
Top