BSOD Clock interrupt was not received on a secondary processor

Specials · Oct 15, 2013

Hi,

I've been getting a BSOD "Clock interrupt was not received on a secondary processor" lately and I can't identify what caused it. I've tried cleaning the system a bit, updating drivers, and checking OS and disk for errors with no luck.

I've followed the jcgriff2 instructions for a BSOD post from here so here goes! When collecting data, it got stuck at "Waiting for System Info" !?!

Answers:

OS - Windows 7 Pro
32/64 bit - 64 bit
Original OS - Windows 7 Pro
OS Version - OEM
Age of System - From Dec. 14 2010
Age of OS install - From Dec. 14 2010 - Original
CPU - Intel Core i7 Q 740 @ 1.73GHz
Video Card - NVIDIA GeForce GTX 460M
MotherBoard - AlienWare M15x - see attached screen shots
Power Supply - Skipped since system is a laptop
System Manufacturer - AlienWare - Dell
Model Number - M15x MLK

I've attached the required files with some additional CPU-Z info. Let me know if there is anything else you need.

I really hope you can help me out here - I'm lost!

Regards
Jones

jcgriff2 · Oct 15, 2013

Hi -

Thread title "BSOD Clock interrupt was not received on a secondary processor" is bugcheck 0x101 and is a CPU hang. Hardware failure is usually the cause, but not always.

I don't see any BSOD memory dump files in the attached zip files. Please check \windows\minidump

I do see recent entries related to video in msinfo32, specifically "Live Kernel Events" and 0x117 Video TDR Timeout (video driver was unable to reset in 30 secs, but ultimately did recover) & "Live Kernel Events" - which are usually 0x117 bugchecks (but NOT BSODs) -

Code:

14-10-2013 09:14	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131014-1114.dmp
C:\Windows\Temp\WER-254608077-0.sysdata.xml
C:\Windows\Temp\WER6A4.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_243506b3

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:016ba72c-34b1-11e3-be17-842b2b826643
Rapportstatus: 4
14-10-2013 10:00	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-03.dmp
C:\Windows\Temp\WER-339722722-0.sysdata.xml
C:\Windows\Temp\WERC2BC.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_21ffc2bc

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:6aba18a8-3257-11e3-b782-842b2b826643
Rapportstatus: 0
14-10-2013 10:01	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131014-1114.dmp
C:\Windows\Temp\WER-254608077-0.sysdata.xml
C:\Windows\Temp\WER6A4.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_243506b3

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:016ba72c-34b1-11e3-be17-842b2b826643
Rapportstatus: 0
14-10-2013 10:01	Windows Error Reporting	Fejl-bucket X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys, Type 0
Hændelsesnavn: LiveKernelEvent
Svar: http://wer.microsoft.com/responses/resredir.aspx?sid=19501&Bucket=X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys&ID=4ef03671-0baf-413d-9dcc-9201506183ac
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127.dmp
C:\Windows\Temp\WER-339708057-0.sysdata.xml
C:\Windows\Temp\WER9095.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_21963a8f

Analysesymbol: X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys
Søger efter løsning igen: 0
Rapport-id:61fd2eb7-3257-11e3-b782-842b2b826643
Rapportstatus: 0
14-10-2013 10:02	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1128.dmp
C:\Windows\Temp\WER-339728026-0.sysdata.xml
C:\Windows\Temp\WERD784.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_548fd784

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:6de48976-3257-11e3-b782-842b2b826643
Rapportstatus: 0
14-10-2013 10:02	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-01.dmp
C:\Windows\Temp\WER-339712628-0.sysdata.xml
C:\Windows\Temp\WER9B4F.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_572b9b4f

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:64b6175c-3257-11e3-b782-842b2b826643
Rapportstatus: 0
14-10-2013 10:52	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131014-1114.dmp
C:\Windows\Temp\WER-254608077-0.sysdata.xml
C:\Windows\Temp\WER6A4.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_243506b3

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:016ba72c-34b1-11e3-be17-842b2b826643
Rapportstatus: 0
14-10-2013 10:51	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-03.dmp
C:\Windows\Temp\WER-339722722-0.sysdata.xml
C:\Windows\Temp\WERC2BC.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_21ffc2bc

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:6aba18a8-3257-11e3-b782-842b2b826643
Rapportstatus: 0
14-10-2013 10:38	Windows Error Reporting	Fejl-bucket X64_0x117_Tdr:3_TdrBug:575504_TdrVTR:13_IMAGE_nvlddmkm.sys, Type 0
Hændelsesnavn: LiveKernelEvent
Svar: http://wer.microsoft.com/responses/resredir.aspx?sid=1&Bucket=X64_0x117_Tdr:3_TdrBug:575504_TdrVTR:13_IMAGE_nvlddmkm.sys&ID=7f0ec525-75b4-4e11-9c0a-b959f491cdf4
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-02.dmp
C:\Windows\Temp\WER-339718088-0.sysdata.xml
C:\Windows\Temp\WERB0A3.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:


Analysesymbol: X64_0x117_Tdr:3_TdrBug:575504_TdrVTR:13_IMAGE_nvlddmkm.sys
Søger efter løsning igen: 1
Rapport-id:67f87d53-3257-11e3-b782-842b2b826643
Rapportstatus: 0
11-10-2013 09:27	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-02.dmp
C:\Windows\Temp\WER-339718088-0.sysdata.xml
C:\Windows\Temp\WERB0A3.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_2b6bb0a3

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:67f87d53-3257-11e3-b782-842b2b826643
Rapportstatus: 4
11-10-2013 09:27	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127.dmp
C:\Windows\Temp\WER-339708057-0.sysdata.xml
C:\Windows\Temp\WER9095.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_2be39095

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:61fd2eb7-3257-11e3-b782-842b2b826643
Rapportstatus: 4
11-10-2013 09:27	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-01.dmp
C:\Windows\Temp\WER-339712628-0.sysdata.xml
C:\Windows\Temp\WER9B4F.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_572b9b4f

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:64b6175c-3257-11e3-b782-842b2b826643
Rapportstatus: 4
11-10-2013 09:27	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-03.dmp
C:\Windows\Temp\WER-339722722-0.sysdata.xml
C:\Windows\Temp\WERC2BC.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_21ffc2bc

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:6aba18a8-3257-11e3-b782-842b2b826643
Rapportstatus: 4
11-10-2013 09:28	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1128.dmp
C:\Windows\Temp\WER-339728026-0.sysdata.xml
C:\Windows\Temp\WERD784.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_548fd784

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:6de48976-3257-11e3-b782-842b2b826643
Rapportstatus: 4
11-10-2013 09:44	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-03.dmp
C:\Windows\Temp\WER-339722722-0.sysdata.xml
C:\Windows\Temp\WERC2BC.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_21ffc2bc

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:6aba18a8-3257-11e3-b782-842b2b826643
Rapportstatus: 0
11-10-2013 09:44	Windows Error Reporting	Fejl-bucket X64_0x117_Tdr:3_TdrBug:575504_TdrVTR:13_IMAGE_nvlddmkm.sys, Type 0
Hændelsesnavn: LiveKernelEvent
Svar: http://wer.microsoft.com/responses/resredir.aspx?sid=1&Bucket=X64_0x117_Tdr:3_TdrBug:575504_TdrVTR:13_IMAGE_nvlddmkm.sys&ID=7f0ec525-75b4-4e11-9c0a-b959f491cdf4
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-02.dmp
C:\Windows\Temp\WER-339718088-0.sysdata.xml
C:\Windows\Temp\WERB0A3.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_27f9cd6c

Analysesymbol: X64_0x117_Tdr:3_TdrBug:575504_TdrVTR:13_IMAGE_nvlddmkm.sys
Søger efter løsning igen: 0
Rapport-id:67f87d53-3257-11e3-b782-842b2b826643
Rapportstatus: 0
11-10-2013 09:45	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127.dmp
C:\Windows\Temp\WER-339708057-0.sysdata.xml
C:\Windows\Temp\WER9095.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_2be39095

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:61fd2eb7-3257-11e3-b782-842b2b826643
Rapportstatus: 0
11-10-2013 09:46	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1128.dmp
C:\Windows\Temp\WER-339728026-0.sysdata.xml
C:\Windows\Temp\WERD784.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_548fd784

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:6de48976-3257-11e3-b782-842b2b826643
Rapportstatus: 0
11-10-2013 09:47	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20131011-1127-01.dmp
C:\Windows\Temp\WER-339712628-0.sysdata.xml
C:\Windows\Temp\WER9B4F.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_572b9b4f

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:64b6175c-3257-11e3-b782-842b2b826643
Rapportstatus: 0
20-09-2013 08:25	Windows Error Reporting	Fejl-bucket X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys, Type 0
Hændelsesnavn: LiveKernelEvent
Svar: http://wer.microsoft.com/responses/resredir.aspx?sid=19501&Bucket=X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys&ID=42e7a977-8247-43fc-b5e1-6da75ebeb5a7
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20130919-1332.dmp
C:\Windows\Temp\WER-11730027-0.sysdata.xml
C:\Windows\Temp\WERFE8D.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1382d7e7

Analysesymbol: X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys
Søger efter løsning igen: 0
Rapport-id:3ac04c6e-211f-11e3-b8d6-a453e99ee71a
Rapportstatus: 0
19-09-2013 11:32	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20130919-1332.dmp
C:\Windows\Temp\WER-11730027-0.sysdata.xml
C:\Windows\Temp\WERFE8D.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_2a7afe8d

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:3ac04c6e-211f-11e3-b8d6-a453e99ee71a
Rapportstatus: 4
13-09-2013 20:17	Windows Error Reporting	Fejl-bucket X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys, Type 0
Hændelsesnavn: LiveKernelEvent
Svar: http://wer.microsoft.com/responses/resredir.aspx?sid=19501&Bucket=X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys&ID=624eefae-93cb-45e4-b308-688d6b4e3077
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20130912-1735.dmp
C:\Windows\Temp\WER-7955036-0.sysdata.xml
C:\Windows\Temp\WER6450.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_22b58970

Analysesymbol: X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys
Søger efter løsning igen: 0
Rapport-id:f02f4ad6-1bc0-11e3-b8fb-842b2b826643
Rapportstatus: 0
12-09-2013 15:35	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20130912-1735.dmp
C:\Windows\Temp\WER-7955036-0.sysdata.xml
C:\Windows\Temp\WER6450.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_1eb16450

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:f02f4ad6-1bc0-11e3-b8fb-842b2b826643
Rapportstatus: 4
27-05-2013 14:42	Windows Error Reporting	Fejl-bucket X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys, Type 0
Hændelsesnavn: LiveKernelEvent
Svar: http://wer.microsoft.com/responses/resredir.aspx?sid=19501&Bucket=X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys&ID=c9d75958-9e43-47bd-b4b6-7d102fd57583
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20130527-1624.dmp
C:\Windows\Temp\WER-884721060-0.sysdata.xml
C:\Windows\Temp\WERCA64.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1488b644

Analysesymbol: X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys
Søger efter løsning igen: 0
Rapport-id:31964bbc-c6d9-11e2-a384-863c71e2aa03
Rapportstatus: 0
27-05-2013 14:24	Windows Error Reporting	Fejl-bucket , Type 0
Hændelsesnavn: LiveKernelEvent
Svar: Ikke tilgængelig
Cab-id: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Tilknyttede filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20130527-1624.dmp
C:\Windows\Temp\WER-884721060-0.sysdata.xml
C:\Windows\Temp\WERCA64.tmp.WERInternalMetadata.xml

Disse filer er muligvis tilgængelige her:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_4b2bca74

Analysesymbol: 
Søger efter løsning igen: 0
Rapport-id:31964bbc-c6d9-11e2-a384-863c71e2aa03
Rapportstatus: 4

0x117 events fall slightly short of becoming a 0x116 BSOD -- same TDR timeout, but the video driver does not recover and BSODs.

You should find dumps related to 0x117/Live Kernel Events in -

Code:

c:\windows\LiveKernelReports\WATCHDOG

They will simply tell us 0x117 + nvlddmkm.sys - NVIDIA video driver

Update NVIDIA video driver if you have not already done so -
http://www.sysnative.com/drivers/driver.php?id=nvlddmkm.sys

Regards. . .

jcgriff2

jcgriff2 · Oct 15, 2013

Hi again. . .

Somewhat of a language barrier in most of the reports, but some English and hex did come through. :)

I noticed APP hangs & crashes involving Windows Explorer, Intel Storage Manager and others.

Exception error codes were listed in the Event Viewer - 2 in particular -
0xc0000005 = memory access violation
0xc0000374 = heap corruption

RAM is certainly a candidate as is your SSD -

Code:

SAMSUNG SSD PM800 Series SCSI Disk Device

I found a link at Dell, but please double-check that it is in fact for your system/SSD -

http://www.dell.com/support/drivers...riverId=R276513&osCode=W764&fileId=2731113924

In fact, it would be best for you to enter your service tag - http://www.dell.com/support/drivers/us/en/19/DriversHome/ShowProductSelector?fkey=Drivers_PS

So far, I don't see any evidence in the system files of 0x101 BSODs.

Did you see 0x101 on the Blue Screen? Or. . .?

Regards. . .

jcgriff2

Specials · Oct 16, 2013

Hi jcgriff2,

Thanks for replying so quickly.

Yeah, there's bit of a language barrier there :) Sorry!

~~I'm not sure of the 0x101 on the Blue Screen! But when it comes next time, I'll pay attention.~~
[EDIT]Actually, I just found a picture of the BSOD I managed to take on 7/30/13 - I've attached it as well![/EDIT]

I've cleaned and cleaned as much as I could, as well as uninstalling and updating what I thought could possibly be the culprit. I think that's why there's no logs or minidumps or watchdog stuff about the crashes. I'll stop cleaning and let it gather some more evidence.

I upgraded the memory some 10 months back, but I think the BSODs first started some 4-6 months back! Maybe 1-3 times a month, so very sporadic! I've been seeing some video driver crashes/recoveries since I got the drivers containing the GeForce Experience program. But I've uninstalled and updated those a bunch of times, with no change in system stability.

In the same period, I've updated the drivers for the Samsung PM800 SSD a couple of times. I've noticed that the entire system hangs a bit when there's significant load on the SSD and when it's getting full. This corresponds to the fix in the firmware update that you linked to, but as you can see on the attached image, I'm pretty sure that I'm already running that firmware - even though it only says "VBM1AD1Q" and not "VBM1AD1Q,A00" right?

I'm running the latest version, 12.8.0.1016, of Intel Rapid Storage Technology - I've updated it after the issues began, but might have installed it before! I'm not sure if I should be using this Intel Matrix Storage Manager that Dell recommends instead? Could this be the cause? Or is Intel RST just a new name for the Intel MSM? I'm not even sure how I found the RST or if I chose to install it due to the issues I was experiencing!

There's also a BIOS update available! Think I'm gonna do that one and see if it helps.

What do you recommend I do now? Update BIOS, perform some memory checks, fiddle with the Intel Storage drivers? What program should I use to check the memory - Memory Diagnostics? Should I do this one as well - Hard Drive Diagnostic Procedure?

Thanks for helping me out. Much appreciated!
Jones

Search

Search

BSOD Clock interrupt was not received on a secondary processor

Specials

New member

Attachments

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Specials

New member

Attachments

BSOD Clock interrupt was not received on a secondary processor

Specials

New member

Attachments

jcgriff2

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

jcgriff2

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Specials

New member

Attachments

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)