BSOD Clock interrupt was not receieved on a secondary processor

ea5t0n

Member
Joined
May 29, 2016
Posts
6
Hi!

I got BSOD Clock interrupt was not receieved on a secondary processor for the 4rd time in 2.5 weeks. All BOSDs happend while I was in game. Note that BSOD doesnt appear in all games. I would say mostly in games that are GPU "heavy".

View attachment 20975
View attachment PERFMON_system_health_report.zip

Bought this PC 8 months ago. Before BSODs I had no issues what so ever.
Windows 7 x64 Home Premium SP1 retail version
CPU Intel i7-6700
MB Gigabyte GA-Z170-D3H
GPU Gigabyte GeForce GTX970 Windforce
PSU NZXT Hale82 v2 550W
RAM 2x 4GB Kingston Fury DDR4-2666

I also included minidump as zip if it helps.

View attachment Minidump.zip
 
Moin,

Code:
Physical Memory Array Handle  0042h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM1
  Bank Locator                  BANK 3
  Memory Type                   1ah - Specification Reserved
  Type Detail                   0080h - Synchronous
  [COLOR=#ff0000]Speed                         2666MHz[/COLOR]
  Manufacturer                  Kingston
  Serial Number                         
  Asset Tag Number                        
  Part Number                   KHX2666C15D4/4G

if you're really running your Rams at this speed, anything can happen.

Intel says, DDR4-1866/2133, or DDR3L-1333/1600 @ 1.35V
 
Thank you for reply!

So basiclly my RAM is too fast or better to say, i have wrong RAM on my motherboard? I should switch to DDR4-1866/2133?
 
Please upload the dump file from C:\Windows\MEMORY.dmp to a third party hosting service, and paste the download link here.
 
I do apologise for the really late reply, I had a lot of work recently.
From the looks of it, the processor(s) which didn't respond to the IPI were all nulled, the call stack, currently instruction, everything.
This almost certainly identifies a failing processor, if it is under warranty, I recommend RMAing it.
 
Thank you for the reply! So it's bad news, huh! :( Thanks again for the update.

Indeed, Jared seems right (was on the Road explaining mobile Devices and Management like for X2 2011, 2012 & WiGig and so on)

my findings beside Jared:
Code:
System Processors:  (00000000000000ff)
  Idle Processors:  (0000000000000000) (0000000000000000) (0000000000000000) (0000000000000000)

       Prcbs             Current         (pri) Next            (pri) Idle
  0    fffff800031fae80  fffffa8007da9b50 ( 8) fffffa800c854a00 (22) fffff80003208cc0  ................

Child-SP          RetAddr           Call Site
fffff880`083d8048 fffff800`030d5b79 nt!KeBugCheckEx
fffff880`083d8050 fffff800`03085be7 nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`083d80e0 fffff800`035fc895 nt!KeUpdateSystemTime+0x377
fffff880`083d81e0 fffff800`03077953 hal!HalpHpetClockInterrupt+0x8d
fffff880`083d8210 fffff800`03080ee0 nt!KiInterruptDispatchNoLock+0x163
fffff880`083d83a0 fffff800`0309bd71 nt!KeFlushMultipleRangeTb+0x260
fffff880`083d8470 fffff800`0309e7e8 nt!MiFlushTbAsNeeded+0x1d1
fffff880`083d8580 fffff800`031b0f86 nt!MiAllocatePagedPoolPages+0x4cc
fffff880`083d86a0 fffff800`0309c4e0 nt!MiAllocatePoolPages+0x906
fffff880`083d87e0 fffff800`031b390e nt!ExpAllocateBigPool+0xb0
fffff880`083d88d0 fffff800`0308f485 nt!ExAllocatePoolWithTag+0x82e
fffff880`083d89c0 fffff800`032e3e16 nt!ExAllocatePoolWithQuotaTag+0x55
fffff880`083d8a10 fffff800`0333e31c nt!PiControlGetInterfaceDeviceList+0x92
fffff880`083d8a90 fffff800`0307a693 nt!NtPlugPlayControl+0x100
fffff880`083d8ae0 00000000`773acb8a nt!KiSystemServiceCopyEnd+0x13
00000000`0267ee48 00000000`00000000 0x773acb8a

  1    fffff88003500180  fffffa800d039b50 ( 8)                       fffff8800350b0c0  ................

Child-SP          RetAddr           Call Site
fffff880`08a3c530 fffff800`0333788f nt!KeFlushProcessWriteBuffers+0x6b
fffff880`08a3c5a0 fffff800`03388f96 nt!ExpGetProcessInformation+0x7f
fffff880`08a3c6f0 fffff800`033899e9 nt!ExpQuerySystemInformation+0xfb4
fffff880`08a3caa0 fffff800`0307a693 nt!NtQuerySystemInformation+0x4d
fffff880`08a3cae0 00000000`773abe9a nt!KiSystemServiceCopyEnd+0x13
00000000`01cce2b8 00000000`00000000 0x773abe9a

  2    fffff88003572180  fffff8800357d0c0 ( 0) fffffa800e213740 (11) fffff8800357d0c0  ................

Child-SP          RetAddr           Call Site
00000000`00000000 00000000`00000000 0x0

  3    fffff880035e4180  fffff880035ef0c0 ( 0) fffffa80078cd5f0 (11) fffff880035ef0c0  ................

Child-SP          RetAddr           Call Site
00000000`00000000 00000000`00000000 0x0

  4    fffff880009cf180  fffffa800879aa40 ( 8) fffffa800776d660 (23) fffff880009da0c0  ................

Child-SP          RetAddr           Call Site
fffff880`0a5cc100 fffff800`0309bd71 nt!KeFlushMultipleRangeTb+0x260
fffff880`0a5cc1d0 fffff800`0309e7e8 nt!MiFlushTbAsNeeded+0x1d1
fffff880`0a5cc2e0 fffff800`031b0f86 nt!MiAllocatePagedPoolPages+0x4cc
fffff880`0a5cc400 fffff800`0309c4e0 nt!MiAllocatePoolPages+0x906
fffff880`0a5cc540 fffff800`031b390e nt!ExpAllocateBigPool+0xb0
fffff880`0a5cc630 fffff880`05471b13 nt!ExAllocatePoolWithTag+0x82e
fffff880`0a5cc720 fffff960`0023ce86 dxgkrnl!DxgkEscape+0x22f
fffff880`0a5ccab0 fffff800`0307a693 win32k!NtGdiDdDDIEscape+0x12
fffff880`0a5ccae0 00000000`74e114ea nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2e8 00000000`00000000 0x74e114ea

  5    fffff880036a5180  fffffa800e478ac0 ( 8)                       fffff880036b00c0  ................

Child-SP          RetAddr           Call Site
00000000`0e5afe08 00000000`00000000 0x7755fda1

  6    fffff88003717180  fffff880037220c0 ( 0) fffffa800e00a600 (11) fffff880037220c0  ................

Child-SP          RetAddr           Call Site
00000000`00000000 00000000`00000000 0x0

  7    fffff88003789180  fffff880037940c0 ( 0) fffffa800d2c97e0 (11) fffff880037940c0  ................

More than one CPU seems active, unusual.

If not
EasyTuneEngine
or
MSIAfterburner
which are merely tuning tools are the cause, then it might be your CPU.

Regards
Michael
 
Thanks for the reply, MichaelB!

EasyTuneEngine, hmm? I unistalled it long ago so maybe that was causin' the problem if something was left behind. I'll try to reinstall that to see if it changes anything! Thanks for your feedback!
 

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

Back
Top