BSOD -- Clock interrupt not received on a secondary processor

A

achkas

Member
Joined
Nov 29, 2013
Posts
5
Hi everyone, hopefully you can help. First, a problem that may or may not be related to the BSOD: I came back home last week to find that, when I tried to boot up my computer, it produced a black desktop with a white cursor but nothing else each time it reached the Window’s logo. Even safe mode did this. I had made no recent changes to my computer. System recovery was not affected though. So after a while failing to fix this, I wiped my system and reinstalled windows. Everything has been working fine apart from recent occasional random mouse hangs – some days nothing, some days a bit of it, where the cursor freezes but then moves on. The last two times this has happened I’ve received a BSOD error saying a clock interrupt was not received on a secondary processor. Each time, I've just been doing normal internet browsing or document editing. When playing games like the new Tomb Raider and Prison Architect, nothing whatsoever has occurred as a problem ,it's been fine.
I’ve attached my perfmon and other diagnostic file, and uploaded memory.dmp to my skydrive (I saw another thread with a similar problem -- very recent, actually https://www.sysnative.com/forums/bs...as-not-received-on-a-secondary-processor.html -- where the guy did it -- https://skydrive.live.com/redir?resid=262B307624FC9B2A!129&authkey=!ACN220oUzYc3aOE&ithint=file,.zip is the file I uploaded)

OS: Windows 7
Bit: x64
Original/Current OS: as above. OEM since system construction.
Age of system: almost exactly 3 years for every component. Same goes for OS.
CPU: Intel Core i5 760 2.80ghz
Video Card: NVidia GeForce GTX 460
Motherboard: Gigabyte P55M-UD2
Power Supply: 500W OCZ ModXStream Pro 80PLUS Modular Power Supply
I constructed the system myself – I’ve had no problems like this whatsoever for three years.

So perfmon and other stuff attached, and memory.dmp at -- https://skydrive.live.com/redir?resid=262B307624FC9B2A!129&authkey=!ACN220oUzYc3aOE&ithint=file,.zip
Thanks in advance for any help!
 

Attachments

Hi,

First, off in regards to the Perfmon:

[TABLE="class: block"]
[TR]
[TD="class: h4"]ymptom:[/TD]
[TD="class: info, align: center"]
error.gif

Device is disabled.[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"]Cause:[/TD]
[TD="class: info b2, align: center"]A device is disabled preventing it from working properly.[/TD]
[/TR]
[TR]
[TD="class: h4, width: 12%"]Details:[/TD]
[TD="class: info, align: center"]The device, Network Controller, is disabled. If this device is no longer used it may be intentionally disabled. The Plug and Play ID for this device is PCI\VEN_168C-DEV_002D-SUBSYS_0300168C-REV_01\4-F52DBAB-0-10F0.[/TD]
[/TR]
[/TABLE]

^^ Is this on purpose? If so, I presume it's due to having a 3rd party NIC installed?

In regards to the MEMORY.DMP, it's unfortunately corrupt:

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Click to expand...

Unable to get current machine context, NTSTATUS 0xC0000147

^^ Usually this appears in crash dumps when a page file is missing (or the dump is just corrupt). In addition to the Small memory dump change above, make sure of the following:

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'.
Click to expand...

In addition to checking the above, ensure all future dumps are set for Kernel - Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > change from Small to Kernel or ensure Kernel is set.

In addition to this, please also enable Driver Verifier so we'll gave a Kernel dump + verifier for as much info as possible:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick
 
Thanks! -- I checked all these things and these settings were already enabled. The disabled network thing is a wireless card I installed but do not need. I do have a minidump file from the other day if this would also be of help -- I think system.dmp may have failed as I switched it off in a panic (in retrospect, this was quite stupid). I'm enabling Driver Verifier now -- in the meantime, I've attached the other .dmp that's in that folder.
 

Attachments

Unfortunately, we cannot analyze *101 bug checks without a Kernel dump as not enough information is contained in Minidumps from the time of crash. With that said, when you crash next and the MEMORY.DMP is overwritten with the latest from the crash, post it here.

Regards,

Patrick
 
Patrick said:
Unfortunately, we cannot analyze *101 bug checks without a Kernel dump as not enough information is contained in Minidumps from the time of crash. With that said, when you crash next and the MEMORY.DMP is overwritten with the latest from the crash, post it here.

Regards,

Patrick
Click to expand...

Just did the Verifier -- immediate BSOD after I typed in my password into windows startup. Did a system restore and now compressing my memory.dmp for upload -- will post here in a few minutes
 
Did a system restore
Click to expand...

This may have deleted the DMP that generated because you restored to a point prior to the latest MEMORY.DMP being generated. If this is the case, crash again and rather than system restoring, boot into Safe Mode and disable it. Only system restore if you experience OS corruption.

Regards,

Patrick
 
Just downloading the file now, it seems to be very small for a Stop 0x101. Only 68.9MB?
 
Code: 
[COLOR=#ff0000]BugCheck C4[/COLOR], {f6, [COLOR=#0000cd]ac[/COLOR], [COLOR=#008000]fffffa80077c5670[/COLOR], [COLOR=#ff8c00]fffff8800f0b2879[/COLOR]}

Probably caused by : [COLOR=#ff0000]nvlddmkm.sys[/COLOR] ( nvlddmkm+9a879 )

It appears that a driver has attempted to use a User Mode handle in Kernel-Mode. Hopefully we can dump the handle table of the process, and see which object the handle was referencing.

I managed to find the handle, and it seems to reference a Registry Key object.

Code: 
[COLOR=#ff0000]00ac[/COLOR]: Object: fffff8a001efe940  GrantedAccess: 00020019 Entry: fffff8a001f002b0
Object: fffff8a001efe940  Type: (fffffa800371a390) Key
    ObjectHeader: fffff8a001efe910 (new version)
        HandleCount: [COLOR=#ff0000]1[/COLOR]  PointerCount: 1 <<< Reference Count = 2
        Directory Object: 00000000  Name: \REGISTRY\MACHINE\SYSTEM\CONTROLSET001\CONTROL\CLASS\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000\NVSPCAPS



Code: 
1: kd> [COLOR=#008000]dt nt!_OBJECT_HEADER fffff8a001efe910[/COLOR]
   +0x000 PointerCount     : 0n1
   +0x008 HandleCount      : 0n1
   +0x008 NextToFree       : 0x00000000`00000001 Void
   +0x010 Lock             : _EX_PUSH_LOCK
   +0x018 TypeIndex        : 0x23 '#'
   +0x019 TraceFlags       : 0 ''
   +0x01a InfoMask         : 0x8 ''
   +0x01b Flags            : 0x2 ''
   +0x020 ObjectCreateInfo : 0xfffffa80`06852400 _OBJECT_CREATE_INFORMATION
   +0x020 QuotaBlockCharged : 0xfffffa80`06852400 Void
   +0x028 SecurityDescriptor : (null) 
   +0x030 Body             : _QUAD

Code: 
1: kd>[COLOR=#008000] lmvm nvlddmkm[/COLOR]

start             end                 module name
fffff880`0f018000 fffff880`0fc59000   nvlddmkm   (export symbols)       nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR=#ff0000]Mon Nov 11 13:24:05 2013[/COLOR] (5280DA75)
    CheckSum:         00C10283
    ImageSize:        00C41000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update your nVidia graphics card driver to the latest WHQL version, which is 19th November or version 311.82.
 
Edit: BlueRobot and I always post at the same time, it's quite humorous! :lolg:

To further add onto his registry reference analysis:

Directory Object: 00000000 Name: \REGISTRY\MACHINE\SYSTEM\CONTROLSET001\CONTROL\CLASS\{4D36E968-E325-11CE-BFC1-08002BE10318}\0000\NVSPCAPS
Click to expand...

nvspcaps is an nVidia related .dll, so just more things to see nVidia at fault here.

achkas said:
Here you go -- https://skydrive.live.com/redir?resid=262B307624FC9B2A!130&authkey=!AK6xgoua2bx4eQM&ithint=file,.zip -- I don't think it did get deleted due to the modified time matching up with the crash, but let me know. Thanks for all your help!
Click to expand...

It's a DRIVER_VERIFIER_DETECTED_VIOLATION (c4) bug check.

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

Taking a look at the call stack:

Code: 
STACK_TEXT:  
fffff880`06bcb9c8 fffff800`0314f4ec : 00000000`000000c4 00000000`000000f6 00000000`000000ac fffffa80`077c5670 : nt!KeBugCheckEx
fffff880`06bcb9d0 fffff800`03164bf4 : 00000000`000000ac fffffa80`077c5670 00000000`00000004 fffff880`06bcd000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`06bcba10 fffff800`02f1c890 : fffff8a0`00000003 fffff880`06bcbc60 fffff880`06bcbe00 fffff880`06bcbff0 : nt!VfCheckUserHandle+0x1b4
fffff880`06bcbaf0 fffff800`02f926b5 : 00000000`00000000 fffff880`00000001 fffffa80`0371a390 fffff8a0`01607f00 : nt! ?? ::NNGAKEGL::`string'+0x2027e
fffff880`06bcbbc0 fffff800`02cc1e53 : fffffa80`077c7b50 fffff880`06bcbf78 00000000`00000002 00000000`00000000 : nt!NtQueryValueKey+0x115
fffff880`06bcbd50 fffff800`02cbe410 : fffff800`03153d96 fffff880`0f0b2879 fffff880`06bcbff0 fffff880`06bcbfe8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06bcbf58 fffff800`03153d96 : fffff880`0f0b2879 fffff880`06bcbff0 fffff880`06bcbfe8 fffff800`02cbe410 : nt!KiServiceLinkage
fffff880`06bcbf60 fffff880`0f0b2879 : fffff880`06bcca0a fffff880`06bcc030 fffff880`06bcc9f8 fffffa80`03bc7b98 : nt!VfZwQueryValueKey+0x76
fffff880`06bcbfb0 fffff880`0f0b20c2 : 00000000`00000000 00000000`00000000 fffff880`06bcc140 fffff880`06bcc140 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0x9a879
fffff880`06bcc060 fffff880`0f0fccbe : fffff880`0f0b2045 fffff980`01394bd0 fffffa80`060d8000 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0x9a0c2
fffff880`06bcc100 fffff880`0f0cb1d4 : fffff880`06bcc9c0 00000000`00000004 fffff880`06bccaf8 fffffa80`060d8000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0xe4cbe
fffff880`06bcc180 fffff880`0f0bde5c : fffff880`06bcc6c8 fffff880`0f9320e4 fffff880`06bcc2d0 fffffa80`077c7b50 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0xb31d4
fffff880`06bcc1d0 fffff880`0f9321c3 : 00000000`00000010 fffff880`0f9320e4 00000000`00000010 00000000`00010286 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0xa5e5c
fffff880`06bcc5e0 fffff880`0f0bd30b : fffff880`0f548b30 fffff880`06bcc6d9 fffffa80`060d8000 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]!nvDumpConfig+0x29fdeb
fffff880`06bcc620 fffff880`0f9149b9 : fffff880`06bcc950 fffff880`06bcc7a9 fffff880`06bcc950 fffff880`06bcc950 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0xa530b
fffff880`06bcc740 fffff880`0f9b2c05 : 00000000`00000000 00000000`00000000 00000000`4e562a2a 00000000`01000003 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]!nvDumpConfig+0x2825e1
fffff880`06bcc810 fffff880`0fc8df50 : 00000000`00000000 00000000`00000000 fffff880`06bcc950 00000000`00000018 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]!nvDumpConfig+0x32082d
fffff880`06bcc840 fffff880`0fc81093 : 00000000`00000000 00000000`00000000 fffff880`06bccca0 00000000`00000003 : [COLOR=#ff0000][I][B]dxgkrnl[/B][/I][/COLOR]!DXGADAPTER::DdiEscape+0x50
fffff880`06bcc870 fffff960`001b1b32 : 00000000`0027f0e8 fffffa80`077c7b50 00000000`003ce2b0 00000000`00000020 : [COLOR=#ff0000][I][B]dxgkrnl[/B][/I][/COLOR]!DxgkEscape+0x7af
fffff880`06bccbf0 fffff800`02cc1e53 : 00000000`00000008 000007fe`f8e2dc70 00000000`00000001 00000000`0000001c : win32k!NtGdiDdDDIEscape+0x12
fffff880`06bccc20 000007fe`fe5213ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0027ea98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe5213ea

FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_nvlddmkm+9a879

^^ We can see two Direct X Kernel calls into various nVidia video driver calls. We can also see verifier successfully detected a driver in violation which in fact is nVidia's 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.

Regards,

Patrick
 
Last edited:
We could have got more information about the registry key, by doing a !reg findkcb with the full path of the registry key, and then using the !reg kcb with the address provided by the !reg findkcb extension. I've demonstrated it in my latest blog post.
 

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

Back
Top