Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1156853" data-attributes="member: 82144">In my opinion the fact that a restart doesn't clear/toggle the problem is another sign that you have a hardware, power or network (eg. address conflict) problem, as I previously said. After all, a system restart mostly restarts the operating system. It doesn't fully reinitialise the hardware (because the power is never completely removed).Yes, as above: a proper/complete shutdown and boot reinitialises the hardware. When shutdown has an effect but restart does not, it should tell you that the problem is likely to be hardware, power or network related. I did not say anything about a reboot hardware issue.There's been a misunderstanding here. I [wrongly] assumed that you would've been using the fast startup mode (since it appears to be enabled by default). I was trying to recommend to disable it. If it's already disabled then that's fine, and please leave it that way. Please do not enable it.You can read the system event log (which I already pointed to). <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />The Windows system event log entries that I posted already told you that Windows is not attempting to start MySQL or TV Server due to whatever is causing the problem, so there will be no logs from either MySQL or TV Server.The first errors in the system event log for the boot cycle on the 16th seem to be:[collapse]&quot;16.10.2015 09:46:14&quot;;&quot;Microsoft-Windows-DriverFrameworks-UserMode&quot;;&quot;(101)&quot;;&quot;Information&quot;;&quot;WUDFPf (part of UMDF) did not load yet. After it does, Windows will start the device again.&quot;;&quot;10114&quot;&quot;16.10.2015 09:46:14&quot;;&quot;Microsoft-Windows-Kernel-PnP&quot;;&quot;(212)&quot;;&quot;Warning&quot;;&quot;The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&amp;Ven_Canon&amp;Prod_MG6300_series&amp;Rev_0201#7&amp;6f2971f&amp;0&amp;11FF72&amp;0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.&quot;;&quot;219&quot;&quot;16.10.2015 09:46:14&quot;;&quot;Microsoft-Windows-DriverFrameworks-UserMode&quot;;&quot;(101)&quot;;&quot;Information&quot;;&quot;WUDFSvc (part of UMDF) did not load yet. After it does, Windows will start the device again.&quot;;&quot;10114&quot;&quot;16.10.2015 09:46:14&quot;;&quot;Microsoft-Windows-Kernel-PnP&quot;;&quot;(212)&quot;;&quot;Warning&quot;;&quot;The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&amp;Ven_Generic-&amp;Prod_SD#MMC&amp;Rev_1.00#8&amp;bc7c096&amp;0&amp;058F63646476&amp;0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.&quot;;&quot;219&quot;&quot;16.10.2015 09:46:14&quot;;&quot;Microsoft-Windows-DriverFrameworks-UserMode&quot;;&quot;(101)&quot;;&quot;Information&quot;;&quot;WUDFSvc (part of UMDF) did not load yet. After it does, Windows will start the device again.&quot;;&quot;10114&quot;&quot;16.10.2015 09:46:14&quot;;&quot;Microsoft-Windows-Kernel-PnP&quot;;&quot;(212)&quot;;&quot;Warning&quot;;&quot;The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&amp;Ven_Generic-&amp;Prod_Compact_Flash&amp;Rev_1.01#8&amp;bc7c096&amp;0&amp;058F63646476&amp;1#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.&quot;;&quot;219&quot;[/collapse]I'm ignoring them. They appear to be related to SD/flash card storage and/or printer, and I don't think an SD/flash card or printer error could cause this problem. Maybe I'm wrong.The next error is:&quot;16.10.2015 09:46:15&quot;;&quot;Service Control Manager&quot;;&quot;(0)&quot;;&quot;Error&quot;;&quot;The Net.Tcp Listener Adapter service depends on the Net.Tcp Port Sharing Service service which failed to start because of the following error:&nbsp; %%1058&quot;;&quot;3221232473&quot;That Net.Tcp Port Sharing Service relates to networking, which is why I've been saying that the problem could be network related.Earlier in the log (15th) you can also see:[collapse]&quot;15.10.2015 15:26:20&quot;;&quot;NetBT&quot;;&quot;(0)&quot;;&quot;Error&quot;;&quot;A duplicate name has been detected on the TCP network.&nbsp; The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.&quot;;&quot;3221229791&quot;&quot;15.10.2015 16:50:05&quot;;&quot;NetBT&quot;;&quot;(0)&quot;;&quot;Error&quot;;&quot;A duplicate name has been detected on the TCP network.&nbsp; The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.&quot;;&quot;3221229791&quot;&quot;15.10.2015 16:50:05&quot;;&quot;NetBT&quot;;&quot;(0)&quot;;&quot;Error&quot;;&quot;A duplicate name has been detected on the TCP network.&nbsp; The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.&quot;;&quot;3221229791&quot;&quot;15.10.2015 18:57:55&quot;;&quot;NetBT&quot;;&quot;(0)&quot;;&quot;Error&quot;;&quot;A duplicate name has been detected on the TCP network.&nbsp; The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.&quot;;&quot;3221229791&quot;&quot;15.10.2015 18:57:55&quot;;&quot;NetBT&quot;;&quot;(0)&quot;;&quot;Error&quot;;&quot;A duplicate name has been detected on the TCP network.&nbsp; The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.&quot;;&quot;3221229791&quot;&quot;15.10.2015 19:09:01&quot;;&quot;NetBT&quot;;&quot;(0)&quot;;&quot;Error&quot;;&quot;A duplicate name has been detected on the TCP network.&nbsp; The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.&quot;;&quot;3221229791&quot;&quot;15.10.2015 19:09:03&quot;;&quot;NetBT&quot;;&quot;(0)&quot;;&quot;Error&quot;;&quot;A duplicate name has been detected on the TCP network.&nbsp; The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.&quot;;&quot;3221229791&quot;[/collapse]Those entries another reason why I've been mentioning networking...</blockquote>

[QUOTE="mm1352000, post: 1156853, member: 82144"] In my opinion the fact that a restart doesn't clear/toggle the problem is another sign that you have a hardware, power or network (eg. address conflict) problem, as I previously said. After all, a system restart mostly restarts the operating system. It doesn't fully reinitialise the hardware (because the power is never completely removed). Yes, as above: a proper/complete shutdown and boot reinitialises the hardware. When shutdown has an effect but restart does not, it should tell you that the problem is likely to be hardware, power or network related. I did not say anything about a reboot hardware issue. There's been a misunderstanding here. I [wrongly] assumed that you would've been using the fast startup mode (since it appears to be enabled by default). I was trying to recommend to [B]disable[/B] it. If it's already disabled then that's fine, and please leave it that way. Please do [B]not[/B] enable it. You can read the system event log (which I already pointed to). ;) The Windows system event log entries that I posted already told you that Windows is not attempting to start MySQL or TV Server due to whatever is causing the problem, so there will be no logs from either MySQL or TV Server. The first errors in the system event log for the boot cycle on the 16th seem to be: [collapse] "16.10.2015 09:46:14";"Microsoft-Windows-DriverFrameworks-UserMode";"(101)";"Information";"WUDFPf (part of UMDF) did not load yet. After it does, Windows will start the device again.";"10114" "16.10.2015 09:46:14";"Microsoft-Windows-Kernel-PnP";"(212)";"Warning";"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Canon&Prod_MG6300_series&Rev_0201#7&6f2971f&0&11FF72&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.";"219" "16.10.2015 09:46:14";"Microsoft-Windows-DriverFrameworks-UserMode";"(101)";"Information";"WUDFSvc (part of UMDF) did not load yet. After it does, Windows will start the device again.";"10114" "16.10.2015 09:46:14";"Microsoft-Windows-Kernel-PnP";"(212)";"Warning";"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_SD#MMC&Rev_1.00#8&bc7c096&0&058F63646476&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.";"219" "16.10.2015 09:46:14";"Microsoft-Windows-DriverFrameworks-UserMode";"(101)";"Information";"WUDFSvc (part of UMDF) did not load yet. After it does, Windows will start the device again.";"10114" "16.10.2015 09:46:14";"Microsoft-Windows-Kernel-PnP";"(212)";"Warning";"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_Compact_Flash&Rev_1.01#8&bc7c096&0&058F63646476&1#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.";"219"[/collapse] I'm ignoring them. They appear to be related to SD/flash card storage and/or printer, and I don't think an SD/flash card or printer error could cause this problem. Maybe I'm wrong. The next error is: "16.10.2015 09:46:15";"Service Control Manager";"(0)";"Error";"The Net.Tcp Listener Adapter service depends on the Net.Tcp Port Sharing Service service which failed to start because of the following error: %%1058";"3221232473" That Net.Tcp Port Sharing Service relates to networking, which is why I've been saying that the problem could be network related. Earlier in the log (15th) you can also see: [collapse] "15.10.2015 15:26:20";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791" "15.10.2015 16:50:05";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791" "15.10.2015 16:50:05";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791" "15.10.2015 18:57:55";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791" "15.10.2015 18:57:55";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791" "15.10.2015 19:09:01";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791" "15.10.2015 19:09:03";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791"[/collapse] Those entries another reason why I've been mentioning networking... [/QUOTE]

Verification