Windows 10 Crashes on my laptop when on battery power while using Logos

I have a weird issue where Logos is trying to access video card resources that causes Windows 10 to crash while I'm on battery power. It does not happen with any other program and it doesn't happen when it is plugged in. It is a new computer with a Ryzen 5900HS processor, 40GB of RAM, and a RTX 3070. What I want to know is if anyone else is having the same or similar issue? With my last laptop I had a different issue where if I tried to use the keyboard shortcut to throw a window to another screen(Win+Shift+arrow) it would cause Windows to crash. However, this one is different as I only have to have the program open and without even doing anything the operating system will crash. Is it an issue with having essentially two graphics processors?(The CPU has integrated graphics much like all modern mobile cpus, or more accurately called APUs)

Find more posts tagged with

Desktop App

Comments

danwdoo

Don't have this issue but I would start with a video driver/Firmware update and see if that helps. If your PC manufacturer does not offer an update, you might try directly going to AMD and see if you can get one that way.

Jason Carwile

https://community.logos.com/discussion/comment/1174079#Comment_1174079

First I want to say I appreciate you do not know anything about me to know that I would have tried this first, but I did already make sure everything was up to date. I don't think it is a driver issue, and now I'm thinking it isn't even a Logos issue(or at least I may be able to resolve it without a patch from Logos). I haven't done a long test yet, but it seemed to be stable over a 10 minute period when I went into Nvidia Control Panel and made sure that the integrated graphics is specifically selected for Logos instead of the auto-select function. I think it was switching between graphics processors in the middle of running the program for some odd reason. So designating the correct graphics seems to have resolved the issue, though in the end it is somehow a quirk of how Logos makes video resource requests to the system that is causing this strange behavior. If you don't hear from me in 2 weeks time(time enough for our next Bible study where I'll be running it for at least an hour straight on battery) you can assume this was indeed the issue and this is how to resolve it for any forlorn soul that happens to experience the same issue. I suspect it is a rather rare issue as I doubt there are a whole lot of people running Logos on an expensive gaming laptop that has integrated graphics from AMD and a discrete GPU from Nvidia.