Charmed Quark Systems, Ltd. - Support Forums and Community
Editing Triggered Events Possibly Causing Kernel Panic/Crash - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=3)
+--- Forum: CQC Support (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=9)
+--- Thread: Editing Triggered Events Possibly Causing Kernel Panic/Crash (/showthread.php?tid=10949)



Editing Triggered Events Possibly Causing Kernel Panic/Crash - gReatAutomation - 11-01-2019

Not sure if this is CQC causing this but the coincidence is too much. Both yesterday and today, when I am editing actions inside a triggered event, my Windows 10 system crashes. I thought it may be an OS issue however, after it happened yesterday, I powered off/on the system and left it alone for the remainder of the day and everything worked as normal.

Today, I tried editing actions in a triggered event and it happened again.

Both times, I was editing the actions of a triggered event that was not Pause mode (i.e., the triggered event was running).


RE: Editing Triggered Events Possibly Causing Kernel Panic/Crash - Dean Roddey - 11-02-2019

That would be pretty difficult for CQC to do. It might do it indirectly of course if there was an OS issue and that activity just happened to tickle the OS in the right way to bring it out or something.

About the only way CQC would have any likelihood of killing windows would be to eat up all available memory. But when that happens it almost always first gets kind of slow and then slower and slower and finally becomes unusualble. And, even then, CQC is 32 bit so worst case a CQC program can only eat about 3.5GB, and most modern systems have considerably more than that, so at worst that should just whack the program or make it unusuable and require you to kill it.

I guess I should ask, do you mean like blue of screen of death type crash? If so, it should show you an error code on the blue screen, so if happens again not that down since it will provide useful hints.


RE: Editing Triggered Events Possibly Causing Kernel Panic/Crash - gReatAutomation - 11-07-2019

Issue resolved. I was RDP'ing in to my CQC server to access the admin console. Randomly, Windows 10 would give me a Blue Screen of Death (BSOD).

Because the only time I was RDP'ing in to the machine was when I was accessing CQC, I mistakenly associated the issue to CQC.

Turns out, the issue is related to ntoskrnl.exe and the display driver while RDP'd in to a Windows 10 machine.


RE: Editing Triggered Events Possibly Causing Kernel Panic/Crash - kblagron - 11-08-2019

I used to always RDP into my CQC Server for admin duties, but found that adding Admin services to the computer I use in my office on install, I can do 95% of what I need on the Admin Console from my office with no noticed delay.  You can add drivers, change interfaces/triggers/images without ever going to the main server.  Has worked great for me.

If I am doing any driver development work, I will then log into the server, but probably even that isn't necessary, just never have done it.


RE: Editing Triggered Events Possibly Causing Kernel Panic/Crash - gReatAutomation - 11-08-2019

Thanks, I never thought about doing that and will give it a try!


RE: Editing Triggered Events Possibly Causing Kernel Panic/Crash - gReatAutomation - 11-08-2019

Wow.. I should have done this ages ago. Thanks kblagron.


RE: Editing Triggered Events Possibly Causing Kernel Panic/Crash - Dean Roddey - 11-08-2019

You don't need to log into the server for driver development either. Unless the device is connected to it and you need to mess with it for some reason.