Solved A clock interrupt was not received on a secondary processor within the

[paulpies84]

So a friend asked me to have a look at his laptop because of constant blue screens.

HP Pavilion dv6 running win 7 64 bit.

The BSOD happens regularly (about 10-15 mins) with the main one being clock interrupt, but also some random ones.

After much reading I decided to re-install windows 7 as a clean install but I am still getting the same BSOD. I am therefore assuming hardware issue.

I cannot update the current install because the laptop keeps blue screening me.

The attached was from the previous install but in safe mode.

The blue screens started about 45 minutes after windows had finished installing so updates or drivers had been installed.

Any help appreciated but personally think terminal as it is quite an old laptop.

Thanks in advance.

Paul

 

[wither 2]

The problem seems to be CPU related but, is the BIOS up to date?

In regards to the CPU, I would check that the vents to the system are clean and, if possible, if the CPU fan is running. You might download HWMonitor to check the CPU temperatures.

 

[paulpies84]

The BIOS is the latest version.

All air vents and fan seem to be fine but I will attempt to use HWMonitor if I can get it to run long enough.

Will let you know.

Thanks

Paul

 

[wither 2]

I got looking further into the various .dmp files and found a case in which the problem is rapportcerberus_..........

What I found about this is that it is malware. If you can, download the free malwarebytes and run it in either safe mode or normal mode (if you can get it to run long enough).

 

[paulpies84]

As I have done a clean install of seven I would assume that the rapport thing is gone so not sure that is the issue.

HWMonitor finally installed and it has sat running for about 15 mins now, shortly after two BSODs. temps currently sat at 50 degrees C.

I have attached the last two minidumps and HWMonitor data. Not sure what to go at next

 

[wither 2]

I don't know what the CPU is, but that seems to be a reasonable temperature. However, most of the other dump files you previously posted point to a CPU problem. However, that virus might have had an effect.

The latest mini-dumps didn't get attached to your last post. Would you try again?

Also, would you go to Device Manager and check to see if there's any black on yellow exclamation points which indicate a problem with a device?

 

[MrPepka]

Update (or uninstall) IBM Security trusteer rapport (check updates in program)

 

[paulpies84]

Mr Pepka, the laptop now has a clean install of windows so the rapport program is not now on their.

The processor is an AMD Phenom II P960.

Hopefully this time the minidumps will attach. I am trying to run the DM Log collector but the damn thing has blue screened twice in 15 minutes.

Got the latest info from it using DM log collector, hopefully attached.

There is one item in device manager which I think is the webcam, just trying to find drivers.

I know windows needs updates but I can't run it for long enough to update but will try it

 

[wither 2]

One of the problem devices isn't installed-

This is a fix- Solved: unknown device on PCI bus ACPI\HPQ0004 driver for hp elite ... - HP Support Community - 5307614

The other is the Security Processor Loader Driver is missing. I'm unable to find a general fix. It may be corrected if you can get Win 7 updated. I would disable automatic installation of updates and install a few at a time.

There's one BSOD caused by netio.sys which is related to network devices such as a Wi-Fi adapter. The driver should be obtained HP support website and installed.

However, the predominate indication of the BSODs is a CPU clock timeout because of an unhandled exception. The cause of the exception is not shown. It could be a corrupt file, old driver, etc. Until you can get Win 7 fully updated, I think further troubleshooting would not be beneficial unless you want to do things like a memory test or disk check just to make sure there's not problem there.

 

[paulpies84]

Quick update. Used your fix above and now device manager does not show anything as unknown. Downloaded some of the windows updates and tried to install but only managed to get one to install after about 2 hours due to constant BSODs.

Decided to put the HDD into an old laptop of mine to try and update it but it is taking a while. I did try the HDD from my old laptop in this one and still got the same BSOD so I assume the issue is the CPU as you said. Wondering if it is worth taking the motherboard out and removing/reseating the processor and giving everything a good clean. Other than that I have no idea, short of replacing the CPU but not sure if it is worth the risk.

 

[wither 2]

Well, at least one issue got resolved.

The big issue is that the CPU is being timed out by an unhandled exception but, there's no indication of what's causing it. There's also this type of problem- System Service Exception caused by a STATUS_ACCESS_VIOLATION but I don't know how to interpret what specifically is causing it. That stuff is for the big boys. I'm just a user like you. The descriptions for all these bug check codes always mention drivers but I don't know if that's an issue here. Once you get Windows updated, then we can see where you're at.

 

[paulpies84]

Latest

So I put the HDD into another laptop and updated 7 until it comes back with no more updates. Installed it back into the original laptop and get the BSOD again.

I managed to collect the files again and had a quick look at the minidump and it has the same problems. I am not used to working with minidumps (software I can do and strip/rebuild but this isn't my strong point but am learning). The minidumps all mention driver fault but I can't pin it down and with everything I have done it points to a hardware issue but again, I can't pin it down. Yesterday while I was updating the drive I stripped the laptop, going as far as removing the heatsink and re-assembling (with thermal paste) just to make sure everything was seated correctly. The HDD I think is fine as I had no issue in the second laptop and I got the BSOD when I put the other laptop HDD into it. I thought about running Prime95 but doubt it will run long enough to be of any use.

I think I may have to admit defeat on this one but, just in case you can spot anything in the latest minidumps I have attached them and will see if you have any ideas. I really need to learn how to interpret these so If you have any links to good sites to help it would be much appreciated.

Finally, even if we don't fix this thank you for your time and help, it is much appreciated.

 

[MrPepka]

Update:
Graphics driver (https://www.amd.com/en/support/grap...on-hd-4000-series/ati-mobility-radeon-hd-4200)

 

[wither 2]

Back in Post 9, I suggested that he go to the HP support website and download/install the driver for the wi-fi adapter. I don't know if he did that.

I have to agree installing the HD 4200 driver is warranted as is installing the driver for the HD 6470m.

I think he should go to the HP support website and download/install all the drivers for this system.

 

[paulpies84]

Yep totally agree, the problem was that all the drivers I installed came from the HP website, which as you have said are all out of date. This laptop was bought in 2011 so there have been no updated drivers since around 2013 and , because the damn thing kept crashing, it wouldn't run long enough to get them all on.

Anyway windows is now as up to date as it can be, I have manged to go through each item in device manager and updated some that popped up. the link you sent I ended up having to play about with because as soon as it started to install it would cause a blue screen. I did manage to get them installed but still got the BSOD.

And then I had a thought, in the minidump there was an entry which said FAULTING PROCESSOR: 2, CPU_COUNT 4, so I went into msconfig and under BOOT advanced options set the number of processors to 1 and, lo and behold, it ran for over an hour with no issue, when I then reset it to normal, BSOD in 15 minutes. I now have it set on 2 processors and it has been running for over an hour again.

So it seems to fall over when running on all four cores which, once again points to some kind of CPU issue. I am going to give it a bit longer then try 3 cores and see what happens. Think it may have been just luck that I decided to try it.

So just tried with three cores and BSOD so turned it back to two and will see how long it lasts.

 

[wither 2]

Would you try disabling or removing the HD 4200 graphics driver/card? Too many AMD problems popping up in your most recent dumps.

Does that help with the core count behavior?

 

[paulpies84]

So disabled HD4200, set start-up to normal (all 4 cores) and BSOD within 5 minutes of restart. Set back to 2 cores and runs fine with and without HD 4200 enabled or disabled.

I know there seems to be issues with the graphics driver but it seems the issue is with the processor. I had it running last night for about 7 hours with no issues whilst running on 2 cores.

The only thing I can think is that Core 3 has an issue of some kind, whether it is/has failed I don't know but as soon as I go to 3 cores I get the same BSOD.

 

[paulpies84]

Well, at least one issue got resolved.

The big issue is that the CPU is being timed out by an unhandled exception but, there's no indication of what's causing it. There's also this type of problem- System Service Exception caused by a STATUS_ACCESS_VIOLATION but I don't know how to interpret what specifically is causing it. That stuff is for the big boys. I'm just a user like you. The descriptions for all these bug check codes always mention drivers but I don't know if that's an issue here. Once you get Windows updated, then we can see where you're at.

On this comment you mentioned about there being no indication of what is causing it. If it is the CPU failing could that be why there is no indication?

 

[wither 2]

Here's an over-view of the problem-

A clock interrupt was not received on a secondary processor within the allocated time interval.

Since the system has only one processor, it's hard to figure out why one would get that error.

In the event log, the problem core is ID'd as 2.

Here's one of the errors-



The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.

The embedded controller could be in either a device or the mobo. I'm not familiar with it.

You could run prime95 to test the CPU-

Prime95 28.7 (64-bit) - Download

However, would you run eventvwr.exe? In Windows logs, System find the last crash. Open it and then open the Details section. Post a screen shot.

 

[paulpies84]

I haven't tried running prime 95 as haven,t had time but I did force a BSOD by setting to normal start up (happened within about 2 mins) 2 screen shots attached. I can confirm that it runs perfectly with only two cores selected in selective start-up.