Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1197286" data-attributes="member: 82144">Okay.This possibility was something that crossed my mind. Unfortunately your Windows system and application event logs (which contain Windows update logging) have been cleared since August, so I can't check which updates have been installed since then. Perhaps you could find a way to do that independently?I don't think you can maintain the plugins, but you can definitely maintain settings and databases. As documented in the wiki, a &quot;standard uninstall&quot; removes the program without removing the settings and databases:<a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/1_Getting_Started/12_Installing_MediaPortal/Uninstalling_MediaPortal" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/1_Getting_Started/12_Installing_MediaPortal/Uninstalling_MediaPortal</a>After uninstalling MP 1.15 you can reinstall MP 1.14.Having said this, you may want to hold off after you read the info below...The thing that is so attractive about the GPU driver explanation is that in addition to all the D3D/DirectX-related messages/errors in the MediaPortal log files, your Windows system event log shows:&quot;10/3/2016 8:47:05 AM&quot;;&quot;Display&quot;;&quot;(0)&quot;;&quot;Warning&quot;;&quot;Display driver igfx stopped responding and has successfully recovered.&quot;;&quot;4101&quot;&quot;10/3/2016 8:47:04 AM&quot;;&quot;Microsoft-Windows-Power-Troubleshooter&quot;;&quot;(0)&quot;;&quot;Information&quot;;&quot;The system has returned from a low power state.&nbsp; Sleep Time: 2016-10-02T21:46:10.655875200Z Wake Time: 2016-10-02T21:47:02.989968500Z&nbsp; Wake Source: 0&quot;;&quot;1&quot;...and the Windows application event log shows:&quot;10/3/2016 8:47:21 AM&quot;;&quot;Windows Error Reporting&quot;;&quot;(0)&quot;;&quot;Information&quot;;&quot;Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_igdkmd32.sys_GEN5.75_DX10_DISPLAY, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 57546305-c358-43ac-bbf9-9bbe24805306&nbsp; Problem signature: P1: 117 P2: f9ba21c0 P3: 8fc849d0 P4: 0 P5: 1b8c P6: 10_0_14393 P7: 0_0 P8: 256_1 P9:&nbsp; P10:&nbsp; Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161003-0847.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-165208171-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF367.tmp.WERInternalMetadata.xml&nbsp; These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_a62127c09bca18d7ceb8f9a1a76b0c8529e309d_00000000_cab_08791e7e&nbsp; Analysis symbol:&nbsp; Rechecking for solution: 0 Report Id: c2324adb-88e9-11e6-85d7-20cf30906730 Report Status: 0 Hashed bucket: &quot;;&quot;1001&quot;(In earlier log files the application event log shows even more errors:[collapse]&quot;10/2/2016 2:50:54 PM&quot;;&quot;Application Error&quot;;&quot;Application Crashing Events&quot;;&quot;Error&quot;;&quot;Faulting application name: LogonUI.exe, version: 10.0.14393.0, time stamp: 0x5789917a Faulting module name: Windows.UI.Xaml.dll, version: 10.0.14393.187, time stamp: 0x57cf9c3e Exception code: 0xc000027b Fault offset: 0x008b7a98 Faulting process id: 0x2238 Faulting application start time: 0x01d21c6014557a33 Faulting application path: C:\WINDOWS\system32\LogonUI.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: d6662021-fec5-4227-8ade-dfafbcaa6b0b Faulting package full name:&nbsp; Faulting package-relative application ID: &quot;;&quot;1000&quot;&quot;10/2/2016 2:51:00 PM&quot;;&quot;Windows Error Reporting&quot;;&quot;(0)&quot;;&quot;Information&quot;;&quot;Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0&nbsp; Problem signature: P1: 117 P2: f9b93008 P3: 8fc849d0 P4: 0 P5: 2674 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9:&nbsp; P10:&nbsp; Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161002-1450.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-100637062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0A8.tmp.WERInternalMetadata.xml&nbsp; These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_bd452fa269c0765eef9952e6d8ac46c9983964_00000000_cab_2063b0b8&nbsp; Analysis symbol:&nbsp; Rechecking for solution: 0 Report Id: 6acf0d1d-8853-11e6-85d7-20cf30906730 Report Status: 4 Hashed bucket: &quot;;&quot;1001&quot;&quot;10/2/2016 2:51:02 PM&quot;;&quot;Windows Error Reporting&quot;;&quot;(0)&quot;;&quot;Information&quot;;&quot;Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0&nbsp; Problem signature: P1: LogonUI.exe P2: 10.0.14393.0 P3: 5789917a P4: StackHash12_2bf P5: 0.0.0.0 P6: 00000000 P7: 8007000e P8: 0 P9:&nbsp; P10:&nbsp; Attached files: \\?\C:\Windows\Temp\WER9A52.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8C.tmp.WERInternalMetadata.xml C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\memory.hdmp C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\triagedump.dmp&nbsp; These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9&nbsp; Analysis symbol:&nbsp; Rechecking for solution: 0 Report Id: d6662021-fec5-4227-8ade-dfafbcaa6b0b Report Status: 4 Hashed bucket: &quot;;&quot;1001&quot;&quot;10/2/2016 2:51:03 PM&quot;;&quot;Dwminit&quot;;&quot;(0)&quot;;&quot;Warning&quot;;&quot;The Desktop Window Manager process has exited. (Process exit code: 0x0000042b, Restart count: 1, Primary display device ID: Intel(R) HD Graphics)&quot;;&quot;2147614720&quot;&quot;10/2/2016 2:51:03 PM&quot;;&quot;Desktop Window Manager&quot;;&quot;(0)&quot;;&quot;Information&quot;;&quot;The Desktop Window Manager has registered the session port.&quot;;&quot;1073750851&quot;&quot;10/2/2016 2:51:08 PM&quot;;&quot;Windows Error Reporting&quot;;&quot;(0)&quot;;&quot;Information&quot;;&quot;Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_igdkmd32.sys_GEN5.75_0_DISPLAY, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: cdbbf8b8-f473-4d9c-8497-869bca1b36af&nbsp; Problem signature: P1: 117 P2: de1504e0 P3: 8fc849d0 P4: 0 P5: 1b14 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9:&nbsp; P10:&nbsp; Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161002-1444.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-100224937-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68A0.tmp.WERInternalMetadata.xml&nbsp; These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_c9168054591465e4a352e8f2dc2219e7b159f8_00000000_cab_0127d055&nbsp; Analysis symbol:&nbsp; Rechecking for solution: 0 Report Id: 752b8c40-8852-11e6-85d7-20cf30906730 Report Status: 0 Hashed bucket: &quot;;&quot;1001&quot;&quot;10/2/2016 2:51:10 PM&quot;;&quot;Windows Error Reporting&quot;;&quot;(0)&quot;;&quot;Information&quot;;&quot;Fault bucket 108401657857, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0&nbsp; Problem signature: P1: LogonUI.exe P2: 10.0.14393.0 P3: 5789917a P4: StackHash12_2bf P5: 0.0.0.0 P6: 00000000 P7: 8007000e P8: 0 P9:&nbsp; P10:&nbsp; Attached files: \\?\C:\Windows\Temp\WER9A52.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8C.tmp.WERInternalMetadata.xml C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\memory.hdmp C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\triagedump.dmp&nbsp; These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_0127d71c&nbsp; Analysis symbol:&nbsp; Rechecking for solution: 0 Report Id: d6662021-fec5-4227-8ade-dfafbcaa6b0b Report Status: 0 Hashed bucket: 704281f1ca13f7a271922de1ba37194e&quot;;&quot;1001&quot;&quot;10/2/2016 2:51:15 PM&quot;;&quot;Windows Error Reporting&quot;;&quot;(0)&quot;;&quot;Information&quot;;&quot;Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_igdkmd32.sys_GEN5.75_0_DISPLAY, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: e53f31b1-86ad-4f44-aa0d-a53d12a25dbd&nbsp; Problem signature: P1: 117 P2: f9b93008 P3: 8fc849d0 P4: 0 P5: 2674 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9:&nbsp; P10:&nbsp; Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161002-1450.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-100637062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0A8.tmp.WERInternalMetadata.xml&nbsp; These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_bd452fa269c0765eef9952e6d8ac46c9983964_00000000_cab_0127eb40&nbsp; Analysis symbol:&nbsp; Rechecking for solution: 0 Report Id: 6acf0d1d-8853-11e6-85d7-20cf30906730 Report Status: 0 Hashed bucket: &quot;;&quot;1001&quot;[/collapse]These references to &quot;ig...&quot; are references to components of the Intel Graphics/GPU driver and associated software.Of course the ultimate question is: do the Intel GPU error precede (and therefore presumably trigger) the MediaPortal problems, or is it the other way around?I can't answer that with absolute certainty, but it sure looks like the answer is yes [the GPU driver errors are prior and cause the subsequent problems].P.S. Interestingly, your Windows system event log also shows:&quot;10/3/2016 8:47:01 AM&quot;;&quot;Microsoft-Windows-Kernel-General&quot;;&quot;(5)&quot;;&quot;Information&quot;;&quot;Possible detection of CVE: 2016-10-02T21:47:01.500000000Z Additional Information: 2016-10-02T21:46:12.707306500Z&nbsp; This Event is generated when an attempt to exploit a known vulnerability (2016-10-02T21:47:01.500000000Z) is detected. This Event is raised by a User mode process. &quot;;&quot;1&quot;...right around the time that the system resumes from hibernate. Exploitation of a vulnerability sure doesn't sound good. I have no idea what to make of this message as it's the first time I've ever seen it, and official MP releases would never knowingly attempt to exploit security holes.</blockquote>

[QUOTE="mm1352000, post: 1197286, member: 82144"] Okay. This possibility was something that crossed my mind. Unfortunately your Windows system and application event logs (which contain Windows update logging) have been cleared since August, so I can't check which updates have been installed since then. Perhaps you could find a way to do that independently? I don't think you can maintain the plugins, but you can definitely maintain settings and databases. As documented in the wiki, a "standard uninstall" removes the program without removing the settings and databases: [URL]http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/1_Getting_Started/12_Installing_MediaPortal/Uninstalling_MediaPortal[/URL] After uninstalling MP 1.15 you can reinstall MP 1.14. Having said this, you may want to hold off after you read the info below... The thing that is so attractive about the GPU driver explanation is that in addition to all the D3D/DirectX-related messages/errors in the MediaPortal log files, your Windows system event log shows: "10/3/2016 8:47:05 AM";"Display";"(0)";"Warning";"Display driver [B]igfx[/B] stopped responding and has successfully recovered.";"4101" "10/3/2016 8:47:04 AM";"Microsoft-Windows-Power-Troubleshooter";"(0)";"Information";"The system has returned from a low power state. Sleep Time: 2016-10-02T21:46:10.655875200Z Wake Time: 2016-10-02T21:47:02.989968500Z Wake Source: 0";"1" ...and the Windows application event log shows: "10/3/2016 8:47:21 AM";"Windows Error Reporting";"(0)";"Information";"Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_[B]igdkmd32.sys[/B]_GEN5.75_[B]DX10_DISPLAY[/B], type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 57546305-c358-43ac-bbf9-9bbe24805306 Problem signature: P1: 117 P2: f9ba21c0 P3: 8fc849d0 P4: 0 P5: 1b8c P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161003-0847.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-165208171-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF367.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_a62127c09bca18d7ceb8f9a1a76b0c8529e309d_00000000_cab_08791e7e Analysis symbol: Rechecking for solution: 0 Report Id: c2324adb-88e9-11e6-85d7-20cf30906730 Report Status: 0 Hashed bucket: ";"1001" (In earlier log files the application event log shows even more errors: [collapse] "10/2/2016 2:50:54 PM";"Application Error";"Application Crashing Events";"Error";"Faulting application name: LogonUI.exe, version: 10.0.14393.0, time stamp: 0x5789917a Faulting module name: Windows.UI.Xaml.dll, version: 10.0.14393.187, time stamp: 0x57cf9c3e Exception code: 0xc000027b Fault offset: 0x008b7a98 Faulting process id: 0x2238 Faulting application start time: 0x01d21c6014557a33 Faulting application path: C:\WINDOWS\system32\LogonUI.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: d6662021-fec5-4227-8ade-dfafbcaa6b0b Faulting package full name: Faulting package-relative application ID: ";"1000" "10/2/2016 2:51:00 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 117 P2: f9b93008 P3: 8fc849d0 P4: 0 P5: 2674 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161002-1450.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-100637062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0A8.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_bd452fa269c0765eef9952e6d8ac46c9983964_00000000_cab_2063b0b8 Analysis symbol: Rechecking for solution: 0 Report Id: 6acf0d1d-8853-11e6-85d7-20cf30906730 Report Status: 4 Hashed bucket: ";"1001" "10/2/2016 2:51:02 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: LogonUI.exe P2: 10.0.14393.0 P3: 5789917a P4: StackHash12_2bf P5: 0.0.0.0 P6: 00000000 P7: 8007000e P8: 0 P9: P10: Attached files: \\?\C:\Windows\Temp\WER9A52.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8C.tmp.WERInternalMetadata.xml C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\memory.hdmp C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\triagedump.dmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9 Analysis symbol: Rechecking for solution: 0 Report Id: d6662021-fec5-4227-8ade-dfafbcaa6b0b Report Status: 4 Hashed bucket: ";"1001" "10/2/2016 2:51:03 PM";"Dwminit";"(0)";"Warning";"The Desktop Window Manager process has exited. (Process exit code: 0x0000042b, Restart count: 1, Primary display device ID: Intel(R) HD Graphics)";"2147614720" "10/2/2016 2:51:03 PM";"Desktop Window Manager";"(0)";"Information";"The Desktop Window Manager has registered the session port.";"1073750851" "10/2/2016 2:51:08 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_igdkmd32.sys_GEN5.75_0_DISPLAY, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: cdbbf8b8-f473-4d9c-8497-869bca1b36af Problem signature: P1: 117 P2: de1504e0 P3: 8fc849d0 P4: 0 P5: 1b14 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161002-1444.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-100224937-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68A0.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_c9168054591465e4a352e8f2dc2219e7b159f8_00000000_cab_0127d055 Analysis symbol: Rechecking for solution: 0 Report Id: 752b8c40-8852-11e6-85d7-20cf30906730 Report Status: 0 Hashed bucket: ";"1001" "10/2/2016 2:51:10 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket 108401657857, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: LogonUI.exe P2: 10.0.14393.0 P3: 5789917a P4: StackHash12_2bf P5: 0.0.0.0 P6: 00000000 P7: 8007000e P8: 0 P9: P10: Attached files: \\?\C:\Windows\Temp\WER9A52.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B8C.tmp.WERInternalMetadata.xml C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\memory.hdmp C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_cab_04ab9ba9\triagedump.dmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LogonUI.exe_bfee84a072322a575072dcbd4a6553cacfa5b78b_a384bf35_0127d71c Analysis symbol: Rechecking for solution: 0 Report Id: d6662021-fec5-4227-8ade-dfafbcaa6b0b Report Status: 0 Hashed bucket: 704281f1ca13f7a271922de1ba37194e";"1001" "10/2/2016 2:51:15 PM";"Windows Error Reporting";"(0)";"Information";"Fault bucket LKD_0x117_Tdr:3_TdrVTR:14_IMAGE_igdkmd32.sys_GEN5.75_0_DISPLAY, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: e53f31b1-86ad-4f44-aa0d-a53d12a25dbd Problem signature: P1: 117 P2: f9b93008 P3: 8fc849d0 P4: 0 P5: 2674 P6: 10_0_14393 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20161002-1450.dmp \\?\C:\Users\default.HomeTheatre\AppData\Local\Temp\WER-100637062-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB0A8.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_bd452fa269c0765eef9952e6d8ac46c9983964_00000000_cab_0127eb40 Analysis symbol: Rechecking for solution: 0 Report Id: 6acf0d1d-8853-11e6-85d7-20cf30906730 Report Status: 0 Hashed bucket: ";"1001"[/collapse] These references to "ig..." are references to components of the Intel Graphics/GPU driver and associated software. Of course the ultimate question is: do the Intel GPU error precede (and therefore presumably trigger) the MediaPortal problems, or is it the other way around? I can't answer that with absolute certainty, but it sure looks like the answer is yes [the GPU driver errors are prior and cause the subsequent problems]. P.S. Interestingly, your Windows system event log also shows: "10/3/2016 8:47:01 AM";"Microsoft-Windows-Kernel-General";"(5)";"Information";"Possible detection of CVE: 2016-10-02T21:47:01.500000000Z Additional Information: 2016-10-02T21:46:12.707306500Z This Event is generated when an attempt to exploit a known vulnerability (2016-10-02T21:47:01.500000000Z) is detected. This Event is raised by a User mode process. ";"1" ...right around the time that the system resumes from hibernate. Exploitation of a vulnerability sure doesn't sound good. I have no idea what to make of this message as it's the first time I've ever seen it, and official MP releases would never knowingly attempt to exploit security holes. [/QUOTE]

Verification