BSOD - Clock Interrupt was not received - Windows 7 x64

M

matambanadzo

Active member
Joined
Nov 28, 2013
Posts
26
A clock interrupt was not received on a secondary processor within the allocated time interval

Followed BSOD post instructions. Driver verifier BSOD'd again claiming a device driver attempting to corrupt the system has been caught.
nvlddmkm.sys - Quick Google search to show that NVIDIA is the culprit.

OS : Windows 7 SP1
· x64
· As above
· full retail version
· Age of system (hardware) : 2-3 years
· Age of OS installation : under 1 year

· CPU - Core i7 920 (not overclocked)
· Video Card - Palit GTX 480
· MotherBoard - ASUS P6T Deluxe V2
· Power Supply - Corsair HX620W - 620W

· System Manufacturer - NA
· Exact model number - NA

Drives & RAM tested OK.
Everything attached.
 

Attachments

Hi,

We have three dumps, two of the same bug check and one different.

We'll start with the latest, which is of the DRIVER_VERIFIER_DETECTED_VIOLATION (c4) bug check.

This is the general bug check code for fatal errors found by Driver Verifier.

Very simple stack and dump....

Code: 
2: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0897c9c8 fffff800`039674ec : 00000000`000000c4 00000000`000000f6 00000000`000000b0 fffffa80`0d7e2b30 : nt!KeBugCheckEx
fffff880`0897c9d0 fffff800`0397cbf4 : 00000000`000000b0 fffffa80`0d7e2b30 00000000`00000004 fffff880`0897e000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0897ca10 fffff800`03734010 : fffff8a0`00001550 fffff880`0897cc60 fffff880`0897ce00 fffff880`0897cff0 : nt!VfCheckUserHandle+0x1b4
fffff880`0897caf0 fffff800`037a9e85 : 00000000`00000000 fffff880`00000001 fffffa80`09da43b0 fffff8a0`03bae100 : nt! ?? ::NNGAKEGL::`string'+0x1fa3e
fffff880`0897cbc0 fffff800`034d67d3 : fffffa80`0d88cb50 fffff880`0897cf78 00000000`00000002 00000000`00000000 : nt!NtQueryValueKey+0x115
fffff880`0897cd50 fffff800`034d2d90 : fffff800`0396bd96 fffff880`1014e879 fffff880`0897cff0 fffff880`0897cfe8 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0897cdc0)
fffff880`0897cf58 fffff800`0396bd96 : fffff880`1014e879 fffff880`0897cff0 fffff880`0897cfe8 fffff800`034d2d90 : nt!KiServiceLinkage
fffff880`0897cf60 fffff880`1014e879 : fffff880`0897da0a fffff880`0897d030 fffff880`0897d9f8 fffffa80`0a5adf18 : nt!VfZwQueryValueKey+0x76
fffff880`0897cfb0 fffff880`0897da0a : fffff880`0897d030 fffff880`0897d9f8 fffffa80`0a5adf18 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm+0x9a879[/B][/I][/COLOR]
fffff880`0897cfb8 fffff880`0897d030 : fffff880`0897d9f8 fffffa80`0a5adf18 00000000`00000000 fffff880`0897cfe0 : 0xfffff880`0897da0a
fffff880`0897cfc0 fffff880`0897d9f8 : fffffa80`0a5adf18 00000000`00000000 fffff880`0897cfe0 fffff980`00000000 : 0xfffff880`0897d030
fffff880`0897cfc8 fffffa80`0a5adf18 : 00000000`00000000 fffff880`0897cfe0 fffff980`00000000 00000000`000000b0 : 0xfffff880`0897d9f8
fffff880`0897cfd0 00000000`00000000 : fffff880`0897cfe0 fffff980`00000000 00000000`000000b0 fffffa80`00280026 : 0xfffffa80`0a5adf18

FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_nvlddmkm+9a879

The device driver in violation is nvlddmkm.sys which is the nVidia video driver.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

------------------------------------------------------------------------------------------

The other two dumps however are of the WHEA_UNCORRECTABLE_ERROR (124) bugcheck.

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:

Code: 
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800a950578
Section       @ fffffa800a950700
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR=#ff0000][I][B]Error         : Internal timer (Proc 0 Bank 5)[/B][/I][/COLOR]
  Status      : 0xfe00000000800400
  Address     : 0x00003880051db720
  Misc.       : 0x0000000000007fff

We have an internal CPU timer error in both dumps consistent with Processor 0 (primary CPU core) and Cache Bank 5.

If after you update the video card drivers you're still crashing:

There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick
 
Unfortunately, with a Stop 0x101, a Kernel Memory dump is needed to carry out proper analysis of the crash.

Please compress the Kernel Memory Dump, which is stored at:

Code: 
C:\Windows\MEMORY.DMP

Upload the compressed file to a free file hosting service such as Skydrive or Dropbox, and then post the URL of the file in your next post.

I think me and Patrick posted at the same time, please follow Patrick's advice.
 
x BlueRobot said:
Unfortunately, with a Stop 0x101, a Kernel Memory dump is needed to carry out proper analysis of the crash.

Please compress the Kernel Memory Dump, which is stored at:

Code: 
C:\Windows\MEMORY.DMP

Upload the compressed file to a free file hosting service such as Skydrive or Dropbox, and then post the URL of the file in your next post.
Click to expand...

I was going to note the same thing, but none of the attached DMP's are *101. Kernel from this point on would certainly benefit, though.
 
A Stop 0x101 and a Stop 0x124 with a error record pointing to the internal timer, most likely does indicate a faulty processor.
 
I'm around BSOD's quite a bit so a lot is common :grin1:

*124's and *101's are far less frequent than let's say DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) or IRQL_NOT_LESS_OR_EQUAL (a).

As far as the dump you've attached in your prior post, it's a *C4 again faulting nVidia's video driver. Have you followed my recommendation in regards to the video card drivers yet?

Regards,

Patrick
 
No problem! I've never seen an nVidia video driver cause internal CPU timer issues, so I doubt it's the root of the crash... but stranger things have happened.
 
Aha, that's ironic! I mentioned it and here it is : )

You are right, this dump is of the IRQL_NOT_LESS_OR_EQUAL (a) bug check.

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

It is a verifier enabled dump:

Code: 
4: kd> !verifier

Verify Level 92b ... enabled options are:
    Special pool
    Special irql
    All pool allocations checked on unload
    Deadlock detection enabled
    Security checks enabled
    Miscellaneous checks enabled

Another simple call stack:

Code: 
STACK_TEXT:  
fffff880`09ad5548 fffff800`03481ae9 : 00000000`0000000a fffff980`17242f80 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09ad5550 fffff800`03480760 : 00000000`00000010 00000000`00000450 fffff880`009b68e4 fffffa80`0c07a060 : nt!KiBugCheckDispatch+0x69
fffff880`09ad5690 fffff800`0354ebe8 : fffffa80`0c07a060 00000000`00000000 fffff980`17242f80 fffff880`09ad58c0 : nt!KiPageFault+0x260
fffff880`09ad5820 fffff880`05606289 : 00000000`00000000 fffffa80`0d049d80 fffff980`17242f80 fffffa80`0bfaf010 : nt!IoEnumerateDeviceObjectList+0x68
fffff880`09ad5860 00000000`00000000 : fffffa80`0d049d80 fffff980`17242f80 fffffa80`0bfaf010 fffffa80`0ce2b060 : [COLOR=#ff0000][I][B]hcmon+0x6289[/B][/I][/COLOR]

FAILURE_BUCKET_ID: X64_0xA_VRF_hcmon+6289

^^ Verifier flagged hcmon.sys which is the VMware USB monitor driver. I am going to recommend uninstalling VMware for troubleshooting purposes at this time.

-----------------------------------------------------------------------------------------------

While we're here, let's tackle a few other software related things that may be causing potential conflicts:

1. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

2.

Code: 
[I]fttxr5_O.sys - Thu Feb 15 03:15:03 [COLOR=#ff0000][B]2007[/B][/COLOR][/I]

^^ Promise FastTRAK TX4200/TX4300 driver. Try and find updates - PROMISE Technology

If not, I'd recommend removing the device using this driver or the software for troubleshooting purposes.

Code: 
[I]Lachesis.sys - Fri Aug 17 03:48:44 [B][COLOR=#ff0000]2007[/COLOR][/B][/I]

^^ Razer Lachesis driver. Razer's drivers are unfortunately pretty awful now (even though they always have been) because they are all streamlined through an AIO software called Synapse which is horribly buggy. I would actually recommend in this case uninstalling your Razer drivers and allowing Windows on next restart to install the generic mouse drivers. As long as your Razer mouse has DPI switching built onto the mouse itself rather than relying on software you aren't missing out on much if not all functionality whatsoever.

Regards,

Patrick
 
Windows couldn't re-install my Razor mouse so had to re-install using their software. No newer version unfortunately.
Uninstalled Avast & Vmware Workstation. Installed Security Essentials. No newer version for the FastTrak controller. Cant unplug it as I require the hard drives connected for programs to run.

Try another verifier run?
 
Do you have a TP Link wireless USB modem? If so, can you work without it temporarily?

Remove Razer drivers and the Razer mouse.
Use a regular mouse while testing - DO NOT reinstall the Razer until you're certain that the system BSOD's without it.

MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install it immediately!

If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

I've seen issues with SABnxbd software (and USB sound devices) in the past. Can you remove this software (and any USB sound devices) in order to test?
 
Sorry for the delay.
Dang. I use MSI Afterburner & SABnzbd. Not uninstalling SAB though. No USB sound devices either. No USB wifi as well. Will remove razer mouse and software.

Then driver verifier run. Thanks
 

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

Back
Top