J
JosephBerida
I have a Lenovo IdeaPad L340 Gaming Laptop that I just got at the last weekend of November this year. The specs should allow it to run modern games, at least on Low to Medium graphics settings.
I was able to play The Outer Worlds from start to finish for 30 hours on mostly High settings, with the game only crashing once.
Now I'm playing Control with all the settings bumped down to the lowest, and I've been able to play about 8 hours, but not without getting BSOD crashes. The laptop boots right back up just fine.
I'm thinking it's got to do with the CPU, GPU, or RAM. I know Control is one of the most graphically intensive games out right now, but it actually runs well on the lowest settings with a pretty solid framerate.... until the laptop just decides to crash.
I've been monitoring my laptop's CPU and GPU temperatures. It only gets really high when I bump up the graphics (going past 90 degrees celsius!), so I've settled on playing it at the lowest settings to keep the temperatures around 45 to 65 degrees celsius. I've done some undervolting as well to help with that.
It's just been inconsistent, because I was able to play for hours in one session without crashing, and then for another session it just crashed not even 30 minutes in.
I wouldn't be sweating it and posting here though if it was just the game crashing and kicking me back to the desktop. It's the BSODs that worry me.
I've updated all my drivers using Windows Update.
I've uninstalled the antivirus software that came with the laptop, which were McAfee and Avast.
I've run chkdsk before and it didn't fix this issue.
Windows Troubleshoot isn't recommending any BSOD fixes.
Specs:
OS: Windows 10 Home
CPU: Intel Core i5-9300 @ 2.40GHz
RAM: 8GB
Motherboard: LENOVO LNVNB161216 (U3E1)
GPU: 4095MV NVIDIA GeForce GTX 1650 (Lenovo)
Storage: 1TB WD HDD, 500GB SSD
Link to msinfo: Joseph msinfo.nfo
Link to latest crash minidump: 122219-9109-01.dmp
I'm ready to accept the most obvious solution that I just shouldn't play Control anymore because my computer can't handle it, but I'd like to hear from people who can actually analyze BSOD crash dumps to point out if there might be a bigger underlying problem with my relatively new computer.
Continue reading...
I was able to play The Outer Worlds from start to finish for 30 hours on mostly High settings, with the game only crashing once.
Now I'm playing Control with all the settings bumped down to the lowest, and I've been able to play about 8 hours, but not without getting BSOD crashes. The laptop boots right back up just fine.
I'm thinking it's got to do with the CPU, GPU, or RAM. I know Control is one of the most graphically intensive games out right now, but it actually runs well on the lowest settings with a pretty solid framerate.... until the laptop just decides to crash.
I've been monitoring my laptop's CPU and GPU temperatures. It only gets really high when I bump up the graphics (going past 90 degrees celsius!), so I've settled on playing it at the lowest settings to keep the temperatures around 45 to 65 degrees celsius. I've done some undervolting as well to help with that.
It's just been inconsistent, because I was able to play for hours in one session without crashing, and then for another session it just crashed not even 30 minutes in.
I wouldn't be sweating it and posting here though if it was just the game crashing and kicking me back to the desktop. It's the BSODs that worry me.
I've updated all my drivers using Windows Update.
I've uninstalled the antivirus software that came with the laptop, which were McAfee and Avast.
I've run chkdsk before and it didn't fix this issue.
Windows Troubleshoot isn't recommending any BSOD fixes.
Specs:
OS: Windows 10 Home
CPU: Intel Core i5-9300 @ 2.40GHz
RAM: 8GB
Motherboard: LENOVO LNVNB161216 (U3E1)
GPU: 4095MV NVIDIA GeForce GTX 1650 (Lenovo)
Storage: 1TB WD HDD, 500GB SSD
Link to msinfo: Joseph msinfo.nfo
Link to latest crash minidump: 122219-9109-01.dmp
I'm ready to accept the most obvious solution that I just shouldn't play Control anymore because my computer can't handle it, but I'd like to hear from people who can actually analyze BSOD crash dumps to point out if there might be a bigger underlying problem with my relatively new computer.
Continue reading...