https://forge.codesys.com/forge/talk/Runtime/thread/0e6e33c7fb/2022-10-20T10:29:04.357000ZRecent posts to Bluescreen When RTE PLC Start2022-10-20T10:29:04.357000Z2022-10-20T10:29:04.357000Zmondinmrhttps://forge.codesys.com/u/mondinmr/https://forge.codesys.combc4620ede2fa37c0c5131a5f4fb516618076e84e

<div class="markdown_content"><p>I found this problem in many RTE devices.<br/> RTE work in kernel space, so some division by 0, some index out of bound in arrays and things like that in IEC tasks, bring sometime in this situations.</p> <p>To find that exceptions I use a runtime Linux SL (Working great in user space) in a kernel RT installed on my PC or in a RPi 4.<br/> I connect my PC or RPi to fieldBUS, download the application and test.</p> <p>When error bring me to stack exception, I fix it than I download everything in RTE and I reconnect fieldBUS to RTE.</p></div>

2022-10-02T08:17:49.667000Z2022-10-02T08:17:49.667000Zwajdiyounishttps://forge.codesys.com/u/wajdiyounis/https://forge.codesys.comf503faab3c1c8b48584275ab376bf585a6e9509a

<div class="markdown_content"><p>I've the same exact problem. All was working good and suddenly the PLC is not loading any more and windows crashes at shutdown. reinstalling solved the issue, but I would like to know the cause.</p></div>

2022-07-01T00:03:44.164000Z2022-07-01T00:03:44.164000Zangelyuchuhttps://forge.codesys.com/u/angelyuchu/https://forge.codesys.com2bc86c0784c6d6f93ab666e8decb25bddcc06d99

<div class="markdown_content"><p>I've tried everything besides hyperthreading disabled. It seems for my BIOs setting, it is greyed out and I could not change the settings for hyperthreading. Other than hyperthreading, are there other things might cause the problem I encountered?</p></div>

2022-06-29T07:30:04.796000Z2022-06-29T07:30:04.796000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comfe7a06bc9aed3d76195a39971b93776cb2288850

<div class="markdown_content"><ol> <li> <p>switch hyperthreading off in the BIOS + check how many real cores your CPU has - (google it).</p> <ol> <li>check if the drivers are loaded: Command line with admin rights and then: <br/> "net start 3srte3".Expected answer: Successfully loaded. If signature error comes: Secure Boot active. No way, must be deactivated in BIOS. 3.</li> </ol> </li> </ol> <p>Check if at least 1 core is reserved for RTE with numproc:<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 us.</p> <ol> <li>check if CmpDrvSchedulerAMP starts correctly. with (also same command line) "net start CmpDrvSchedulerAMP".<br/> This takes about 20 seconds the first time on first start, because of the measurements.</li> </ol></div>

2022-06-28T17:24:00.509000Z2022-06-28T17:24:00.509000Zangelyuchuhttps://forge.codesys.com/u/angelyuchu/https://forge.codesys.com058b0383e61269c813918508130783931227af0d

<div class="markdown_content"><p>I have installed the CoDeSys RTE 3.5.17.20 and when I start the PLC I get a blue screen from Windows. Then I tried uninstall it and install the most recent version 3.5.18.20. It still gives the same result with blue screen. I have an Intel CPU with 4 cores. I have been following the Installation and Getting Started.</p></div>