BSOD A clock interrupt was not received on a secondary processor

G

Gus Erlangga

New member
Joined
Nov 27, 2013
Posts
4
Good morning, everyone. I have a persisting BOSD that has been plaguing my computer since last week.
Since last week, I have been playing a relatively low CPU-intensive video game called "Euro Truck Simulator 2". However, a BSOD saying "A clock interrupt was not received on a secondary processor" ever since I've been playing that game.

When I went around and ask for help on "Euro Truck Simulator 2"'s website, members have been telling me to stop playing that game for the sake of avoiding the BSOD, but I want to fix this problem, not running away from it.

Anyway, I have read there was already an existing thread regarding this BSOD, but his problem surfaced under a different condition. I have filled out some information to help some of you help me solve this problem. Any help will be greatly appreciated.

· OS: Windows 7.
· Bit: x64.
· Original OS was Windows Vista.
· The current OS is full retail version.
· Age of system is approximately 6 years, however the motherboard is 4 years, power supply is 4 years, and graphics card is 3 years.
· Age of OS installation 3 years, as the Windows 7.

· CPU: AMD Phenom 9550 Quad-Core 2.2 GHz
· Video Card: NVIDIA GeForce GTX 550 Ti
· MotherBoard: Not sure how I can find this information.
· Power Supply: Logisys 550W

· System Manufacturer: Gateway
· Exact model number: DX4200-US001A

I ran the jcgriff2 BSOD File Collection app, but it keeps saying "Waiting for Autoruns to complete". I have launched the attached autoruns.exe, but I have no idea what to do with it once it is loaded. So I only have the Perfmon.html (attached) completed.

Please, help me how to first use the jcgriff2 BSOD File Collection app and autoruns.exe because I have no idea how to work it.

As for the BSOD, any help is greatly appreciated. :smile9:

Here is the Perfmon.html file attached as a .zip file down here.
View attachment 6029
 
Code: 
0: kd> [COLOR=#008000]vertarget[/COLOR]
Windows 7 Kernel Version [COLOR=#ff0000]7600[/COLOR] MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0365f000 PsLoadedModuleList = 0xfffff800`0389be70
Debug session time: Wed Nov 27 06:30:32.613 2013 (UTC + 0:00)
System Uptime: 0 days 4:19:04.860

No Service Pack 1 installed? Please install Service Pack 1, since it has many security updates and patches.

Code: 
[COLOR=#ff0000]BugCheck 101[/COLOR], {31, 0, [COLOR=#008000]fffff88002f64180[/COLOR], [COLOR=#0000ff]2[/COLOR]}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

The hung processor is processor number 2. It's currently running a thread of level 11 priority, which would fall within the Above Normal prioirty range.

Code: 
0: kd> [COLOR=#008000]!ipi[/COLOR]
IPI State for Processor 0

    [COLOR=#ff0000]As a sender, awaiting IPI completion from processor(s) 2.[/COLOR]

    TargetCount          1  PacketBarrier        1  IpiFrozen     0 [Running]


IPI State for Processor 1
    TargetCount          0  PacketBarrier        0  IpiFrozen     2 [Frozen]


[COLOR=#ff0000]IPI State for Processor 2[/COLOR]

    As a receiver, unhandled requests are pending from processor(s) 0, 3.

    TargetCount          0  PacketBarrier        0  IpiFrozen     5 [Target Freeze]

    From processor 0, active request of type: flush all
    From processor 3, active request of type: packet ready
        WorkerRoutine fffff800036acbe0 (nt!FsRtlpNopStackOverflowRoutine)
        Parameter[0] 0  Parameter[1] 0  Parameter[2] 0

IPI State for Processor 3

    As a sender, awaiting IPI completion from processor(s) 2.

    TargetCount          1  PacketBarrier        1  IpiFrozen     2 [Frozen]

Code: 
2: kd> [COLOR=#008000]!running -ti[/COLOR]

System Processors:  (000000000000000f)
  Idle Processors:  (0000000000000000) (0000000000000000) (0000000000000000) (0000000000000000)

       Prcbs             Current         (pri) Next            (pri) Idle
  0    fffff80003848e80  fffffa8005e18b60 ( 1) fffffa80095f2a10 (15) fffff80003856c40  ................

 # Child-SP          RetAddr           Call Site
00 fffff880`009a9768 fffff800`0367c993 nt!KeBugCheckEx
01 fffff880`009a9770 fffff800`036d7677 nt! ?? ::FNODOBFM::`string'+0x4d8e
02 fffff880`009a9800 fffff800`03620895 nt!KeUpdateSystemTime+0x377
03 fffff880`009a9900 fffff800`036cb533 hal!HalpHpetClockInterrupt+0x8d
04 fffff880`009a9930 fffff800`037041b1 nt!KiInterruptDispatchNoLock+0x163
05 fffff880`009a9ac0 fffff800`036dceac nt!KxFlushEntireTb+0x79
06 fffff880`009a9b00 fffff800`03715f79 nt!KeFlushMultipleRangeTb+0x28c
07 fffff880`009a9bd0 fffff800`03715b4f nt!MiZeroPageChain+0x14e
08 fffff880`009a9c10 fffff800`0396e6e6 nt!MmZeroPageThread+0x7da
09 fffff880`009a9d40 fffff800`036ad566 nt!PspSystemThreadStartup+0x5a
0a fffff880`009a9d80 00000000`00000000 nt!KxStartSystemThread+0x16

  1    fffff880009e6180  fffffa800928cb60 ( 8)                       fffff880009f0fc0  ................

 # Child-SP          RetAddr           Call Site
00 00000000`2975ff18 00000000`00000000 0x83dd3c

  2    [COLOR=#008000]fffff88002f64180[/COLOR]  [COLOR=#ff0000]fffffa8008d2c4d0[/COLOR] (11) fffffa8005e3d040 (23) fffff88002f6efc0  ................

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

  3    fffff88002fd5180  fffffa8006e1fb60 (27)                       fffff88002fdffc0  ................

 # Child-SP          RetAddr           Call Site
00 fffff880`03ad07d0 fffff800`039c76a8 nt!KeFlushProcessWriteBuffers+0x6b
01 fffff880`03ad0840 fffff800`039c8325 nt!ExpQuerySystemInformation+0x1368
02 fffff880`03ad0be0 fffff800`036ce293 nt!NtQuerySystemInformation+0x4d
03 fffff880`03ad0c20 00000000`778bfa1a nt!KiSystemServiceCopyEnd+0x13
04 00000000`02dff668 00000000`00000000 0x778bfa1a

Code: 
2: kd> [COLOR=#008000]!thread fffffa8008d2c4d0[/COLOR]
THREAD fffffa8008d2c4d0  Cid 1644.1204  Teb: 00000000fffdb000 Win32Thread: fffff900c284d010 RUNNING on processor 2
Not impersonating
DeviceMap                 fffff8a002797e50
Owning Process            fffffa8006697060       Image:         [COLOR=#ff0000]eurotrucks2.exe[/COLOR]
Attached Process          N/A            Image:         N/A
Wait Start TickCount      995743         Ticks: 716 (0:00:00:11.169)
Context Switch Count      4451230        IdealProcessor: 0                 LargeStack
UserTime                  02:15:21.287
KernelTime                00:01:03.476
Win32 Start Address 0x0000000000c612ee
Stack Init fffff88007fbbdb0 Current fffff88007fbba90
Base fffff88007fbc000 Limit fffff88007fb1000 Call 0
Priority 11 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

Code: 
2: kd> [COLOR=#008000]!dpcs[/COLOR]
CPU Type      KDPC       Function
 2: Normal  : 0xfffff88002f689e8 0xfffff800037ef190 nt!PpmPerfAction

When the Clock Interrupt was sent as a IPI, then the activity which was currently running on this processor, was deferred and then queued as a DPC. The processor obivously didn't respond properly to the Clock Interrupt, and therefore lead to a crash.

Code: 
fffff880`07fbbc08  fffff800`03718513 [COLOR=#ff0000]nt!KiDpcInterruptBypass+0x13[/COLOR]
fffff880`07fbbc10  fffff800`036dbc2c nt!KiSecondaryClockInterrupt+0x13c
fffff880`07fbbc18  fffff800`036dbc98 nt!KiSecondaryClockInterrupt+0x1a8

nt!KiDpcInterruptBypass is used to ignore any DPCs.

I noticed a few drivers in the raw stack of the thread of the hung processor, these may or may not be causing the processor to get hung up on other things.

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

start             end                 module name
fffff880`11e2f000 fffff880`12a66000   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]Wed Oct 23 07:21:50 2013[/COLOR] (52676AFE)
    CheckSum:         00C0CF0F
    ImageSize:        00C37000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update to the latest WHQL version of your nVidia graphics card driver, the current latest version is the 19th November 2013.

Code: 
2: kd> [COLOR=#008000]lmvm aswSnx[/COLOR]

start             end                 module name
fffff880`03e5d000 fffff880`03f5d000   aswSnx     (no symbols)           
    Loaded symbol image file: aswSnx.SYS
    Image path: \SystemRoot\System32\Drivers\aswSnx.SYS
    Image name: aswSnx.SYS
    Timestamp:        [COLOR=#ff0000]Fri Aug 30 08:38:17 2013[/COLOR] (52204BE9)
    CheckSum:         00106AAB
    ImageSize:        00100000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I'll advise removing avast! with the avast! Removal Tool for at least troubleshooting purposes. In the meantime, you could install another program like Microsoft Security Essentials.
 
I was looking at this dump file again, and it does seem a Clock Interrupt was received, but at the same wrong time. IPI's have a higher IRQL Level than Clock Interrupts, and therefore will have higher priority, I believe the processor was waiting upon the IPI completion, which seemed to have never completed, and then a Clock Interrupt was issued within the wrong interval.
 
I have updated drivers, but BSOD still happens only when I play Euro Truck Simulator 2. I am confused! I recently have downloaded a game called Skyrim from Steam. When I play that game for hours on end, I did not get the BSOD. Both games are not illegally obtained, as they were purchased from Steam. I un-installed the truck simulator game and re-installed it to see if it would stop the BSOD. Two hours into the game, it blue screened again.

Any suggestions?
 
It may just be random, as most BSOD's are, especially *101's depending on the true culprit. I would advise not playing the Euro Simulator at all for a few days and see if the crashes cease to exist. If after a few days you get no crashes, try and play the game again and see if you crash. If you do, there may be a bug in the game somewhere that is causing conflicts and you may need to contact the developers.

I would also attach the latest dump file, please.

Regards,

Patrick
 
As said by Patrick, it may be bug in the game if it only occurs with that game. Please also upload the dump file using the same method as before.
 

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

Back
Top