https://forge.codesys.com/forge/talk/Runtime/thread/7155b1e106/2022-10-18T16:40:49.321000ZRecent posts to CODESYS Control RTE V3 (version 3.5.7) unable to start PLC, computer rebooting, target information not available2022-10-18T16:40:49.321000Z2022-10-18T16:40:49.321000Zman2002https://forge.codesys.com/u/man2002/https://forge.codesys.com25b5169d761d9631a13373c0afd91b5b8316d3bf

<div class="markdown_content"><p>I am currently investigating this problem as I have tried all the above to no success yet.</p></div>

2022-10-18T16:40:46.067000Z2022-10-18T16:40:46.067000Zman2002https://forge.codesys.com/u/man2002/https://forge.codesys.com9b5c6071c66f1152089eda49f8a692fb14b86a95

<div class="markdown_content"><p>I am currently investigating this problem as I have tried all the above to no success yet.</p></div>

2022-10-15T03:39:46.198000Z2022-10-15T03:39:46.198000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com2c22e49ae0bf80884768e6f111ecbd6dcb275337

<div class="markdown_content"><p>use latest version, disable hyperthrading check amout of real cores. If this does not solve it - it is a bug need to investigated - use my question in the CODESYS store</p></div>

2022-10-14T19:16:22.329000Z2022-10-14T19:16:22.329000Zman2002https://forge.codesys.com/u/man2002/https://forge.codesys.com982fc859edb405c6fe1b69fa7a236231c82b3069

<div class="markdown_content"><p>Eschwellinger, </p> <p>what is the work around if "net start CmpDrvSchedulerAMP" returns the details below?:</p> <p>Stop Code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED<br/> What failed: CmpDrvSchedulerAMP.</p> <p>This is after the steps 1 and 2 you mentioned above were successful. </p> <p>Thanks.</p></div>

2022-03-01T15:35:26.681000Z2022-03-01T15:35:26.681000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comd85a027e2aea498c09354235ed5aab2e541c88e2

<div class="markdown_content"><p>I would suggest the follwoing:<br/> 1. check if the drivers are loaded:open Command line with admin rights and then "net start 3srte3".<br/> Expected response: Successfully loaded. <br/> If signature error occurs: Secure Boot active. No way, must be deactivated in BIOS.<br/> <br/> <br/> 2 Check if with numproc at least 1 core is reserved for RTE:<br/> Same command line : "bcdedit".<br/> Check in "current" if the setup has set numproc. If not, (e.g. it is a real 4 core) with<br/> bcdedit /set numproc 3<br/> reserve a core for RTE ( this is usually done by the setup)<br/> <br/> 3. check if CmpDrvSchedulerAMP starts correctly. with (also same command line) "net start CmpDrvSchedulerAMP".<br/> This takes about 20 seconds the first time, because of the measurements.</p></div>

2022-03-01T12:57:01.209000Z2022-03-01T12:57:01.209000Zplcdroidhttps://forge.codesys.com/u/plcdroid/https://forge.codesys.com851016018e7a687b1c5996dbac164ecdc6525b11

<div class="markdown_content"><p>Hi,I've installed CODESYS Control RTE 64 3.5.16.50. But still no information is displayed in diagnostics. PLC not starting even after clicking on start from system tray icon. But system reboot issue when trying start PLC is not there now.</p> <p>I've disabled secure boot and hyperv launch also. Still no luck.</p></div>

2022-02-27T14:53:54.772000Z2022-02-27T14:53:54.772000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comc79f844f6bf30b614cedfe5ce2c086e6d5c53f43

<div class="markdown_content"><p>..this happens since a Windows Update,<br/> you need to upate the Control RTE version.<br/> (Keep in mind it is always possible just to update the runtime and keep CODESYS and your Project in exact you testet/proved and runnning version).<br/> So I would chose latest SP16 RTE or SP17 - both is possible.</p></div>

2022-02-27T12:57:18.984000Z2022-02-27T12:57:18.984000Zplcdroidhttps://forge.codesys.com/u/plcdroid/https://forge.codesys.coma7af2750668aaad3da69753e34b4a960b55df525

<div class="markdown_content"><p>Hi,</p> <p>PC with CODESYS Control RTE V3 (version 3.5.7) is restarting whenever I try to start PLC. </p> <p>Target name, address, type, ID are n/a and version is 0.0.0.0 in diagnostics.</p> <p>Windows OS: Windows Server 2019<br/> Processor: Intel Xeon E3-1505M Quad Core</p> <p>Hyper-threading, SpeedStep and C-State are disabled in BIOS.</p> <p>What would be the reason behind system reboot when starting Control RTE V3 PLC? Also, why no information is displayed in diagnostics of PLC?</p> <p>Screenshot of diagnostics is attached for reference.</p></div>