Random BSOD "Clock interrupt not received on a secondary processor"

[Naflannel]

Random BSOD "Clock interrupt not received on a secondary processor"

Hey guys! About a month ago I began receiving this bsod. "A clock interrupt was not received on a secondary processor"
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003364180, 0x2)
My System Specs:
Laptop. Clevo p170hm
Mobo: Clevo p170hm
CPU: Intel Core i7-2820QM Processor (8M Cache, @2.30 GHz)
RAM: 8GB DDR3 1600mhz
GPU: nVidia geforce gtx 560m
(As per the BSOD Instruction thread)
- Windows 7 x64
- Original installed OS
- Its OEM
- The system was purchased brand new in August 2011
- The OS was also installed in August 2011, by the manufacturer.

Anyway I have been having frequent bsod's for about a month with the same error listed above. For absolutely no reason, It would occur while I was watching a youtube video or typing on Word with the cpu under 4% load. At first I assumed that it was my i7 going south so I stress tested my cpu using Intel Burn Test at the maximum settings for 10 runs (did so twice) and got no errors. Then I ran OCCT Linpack for an entire hour at the maximum settings. Since that caused absolutely no instability I turned to ram.. I removed a stick and tested the other using Memtest x86 then switched. Which is why in my dump files I have only 4gb of ram listed. However 5 passes on each stick revealed no errors. So now I have turned to drivers and upon running "verifier.exe" I got a bsod on startup because driver verifier found a faulty driver and crashed the system.

I come as yes, a new user, because frankly I have no where else to turn. A friend reccomended you guys because you offer great crash analysis and I leaped at the oppurtunity.. I am frustrated and tired of my system hanging roughly once for every hour of run time. I will cruise around on the forums and try to help here and try to be active.
If you guys would help me I would be forever grateful
Thank you So much!

 

[JMH]

Your crash may have been caused by stop-0x101-clock_watchdog_timeout
Please read the link below carefully...

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[Naflannel]

Your crash may have been caused by stop-0x101-clock_watchdog_timeout
Please read the link below carefully...

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

Thank you for the response but yes I already knew that my blue screen was a "0x101 clock_watchdog_timeout" And thank you for linking the post I had already read as well.. lol
Im not an idiot.. I know that this bluescreen is being caused by a driver.. I have read countless posts, run ample hardware tests and with "Whocrashed" and "Bluescreenview" have found that my system hangs, due to a core on my i7 locking, from this driver in the windows kernel, "ntoskrnl.exe" however I figure this is caused by a third party driver unless of course you guys find out it is caused solely by the windows kernel driver. In which case I will ask what I should do.
What I desire help with is analyzing my dump files and hopefully getting a fix on the faulty driver.. And while I am not an idiot I have no experience reading crash dump files.

Thank you for your time JMH and I am attaching the dump files as I am typing this.
Again I have no idea how to analyze the dump files so I really appreciate you folks!

 

[zigzag3143]

I am a big fan of Nir Sofer's work, BUT blueScreen View more often than not doesn't point out the correct causes. Similarly Who crashed is even worse.

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

We would be happy to help diagnose what turns up in verifier as soon as we get one thats verified.

Your BCC101's are not and the most recent is a one off pointing elsewhere.

We treat no-one like an idiot, nor do we like to be called condescending.

 

[JMH]

You said
!.

I have read countless posts, run ample hardware tests and with "Whocrashed" and "Bluescreenview" have found that my system hangs, due to a core on my i7 locking, from this driver in the windows kernel, "ntoskrnl.exe"

You may indeed be correct.
I think not.
Yet to be determined.
"Whocrashed" and "Bluescreenview" are not our primary source of information.

2.

Im not an idiot...

3.

What I desire help with is analyzing my dump files and hopefully getting a fix on the faulty driver.. And while I am not an idiot I have no experience reading crash dump files.

We make no assumption as to the intelligence or otherwise of the people seeking help.
{Perhaps we should!}

****
Note we are all volunteers here from various parts of the world who donate our free time to assisting others.
Our expectation from those we endevour to help is politeness.
****