Constant Clock Interrupt BSODs

Bump for dump :wave:

Update: The bootable memtest did not reveal any problems. I cleaned up the system as best as I could. After 2 days without a crash, I again experienced a BSOD this morning.
I don't know if there is anything left to do (test/cleanup ...) on my side, so our IT department will contact the seller.

This error is incredibly frustrating ...
 
Initial diagnosis:

The hung-up processor cores are holding threads that are talking to each other, both involving some form of network activity. The 3rd-party drivers involved are your Intel Wifi and Gigabit Ethernet drivers, both of which are rather outdated, dating Jan 11 and June 3, respectively. Check updates on those, as well as BIOS and mobo chipset driver updates since those can be involved.

This is just an initial diagnosis. I'll be working through it some more to see what I can pull out. I hypothesize we're dealing with some sort of resource contention where both threads involving the wifi and LAN adapters are not playing well with each other.
 
Vir Gnarus said:
Initial diagnosis:

The hung-up processor cores are holding threads that are talking to each other, both involving some form of network activity. The 3rd-party drivers involved are your Intel Wifi and Gigabit Ethernet drivers, both of which are rather outdated, dating Jan 11 and June 3, respectively. Check updates on those, as well as BIOS and mobo chipset driver updates since those can be involved.

This is just an initial diagnosis. I'll be working through it some more to see what I can pull out. I hypothesize we're dealing with some sort of resource contention where both threads involving the wifi and LAN adapters are not playing well with each other.
Click to expand...

I have checked, and it seems indeed that these are the latest versions of the respective drivers. The Wifi driver is the latest from Intel, and the Gigabit Ethernet driver is the latest from Lenovo (this is an OEM-specific driver?!). Chipset and BIOS are also up to date ...
 
Be careful about mixing OEM-based drivers with manufacturer counterparts. There could be compatibility problems that can arise from em. Either have them both from Intel or both from the OEM (preferably the OEM), even if this means rolling back one of them to an older version.

I might not be able to continue analysis today, but I should have some time tomorrow unless something comes up.
 
Quick update: no new crashes last week, but I had stretches of 7-10 days of stable system execution without BSODs before, interrupted by more frequent crashes (a couple of times daily in the stretch that prompted the OP).

Vir Gnarus said:
.
I might not be able to continue analysis today, but I should have some time tomorrow unless something comes up.
Click to expand...

Did you find anything, Vir?

Best regards,
S
 
I was just re-reading this topic and found this ethernet driver for you: http://downloadcenter.intel.com/Det...sion=Windows 7 (64-bit)*&DownloadType=Drivers It dates from Aug 2012

Lateralus said:
Vir Gnarus said:
Initial diagnosis:

The hung-up processor cores are holding threads that are talking to each other, both involving some form of network activity. The 3rd-party drivers involved are your Intel Wifi and Gigabit Ethernet drivers, both of which are rather outdated, dating Jan 11 and June 3, respectively. Check updates on those, as well as BIOS and mobo chipset driver updates since those can be involved.

This is just an initial diagnosis. I'll be working through it some more to see what I can pull out. I hypothesize we're dealing with some sort of resource contention where both threads involving the wifi and LAN adapters are not playing well with each other.
Click to expand...

I have checked, and it seems indeed that these are the latest versions of the respective drivers. The Wifi driver is the latest from Intel, and the Gigabit Ethernet driver is the latest from Lenovo (this is an OEM-specific driver?!). Chipset and BIOS are also up to date ...
Click to expand...
 
Sorry, yes, evidently stuff has come up, lol. I've been busy with several projects. I still have your memory dump file, and will try to get to it at earliest convenience. This should not stop you from pursuing Lenovo support on this problem, as it may end up coming to that.

The pattern though of having large bouts of BSODs for a couple day period followed by no symptoms for several days is pretty odd. Is there anything different going on with your PC during those moments, such as a program you run temporarily or some other activity?
 
Vir Gnarus said:
Sorry, yes, evidently stuff has come up, lol. I've been busy with several projects. I still have your memory dump file, and will try to get to it at earliest convenience. This should not stop you from pursuing Lenovo support on this problem, as it may end up coming to that.

The pattern though of having large bouts of BSODs for a couple day period followed by no symptoms for several days is pretty odd. Is there anything different going on with your PC during those moments, such as a program you run temporarily or some other activity?
Click to expand...

Update: Got first BSOD in a week just a couple of minutes ago. I can't correlate this to any particular activity, as I did not use my machine differently than in the previous days. It crashed while using a web browser (Firefox), and only having MS Outlook open as the other manually started application. I anticipated the crash (freezing of mouse for ~5-7 seconds before BSOD), and did not unplug adapter in order to see if it would actually happen.

@usasma: Thanks for pointing out the ethernet driver, but I had already installed it (in early September, I guess, when I was first trying to troubleshoot the issue).

Vir Gnarus said:
This should not stop you from pursuing Lenovo support on this problem, as it may end up coming to that.
Click to expand...
We are also doing that, but the customer service is not exactly the fastest on earth ....
 

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

Back
Top