Hi!

My laptop has never had issues, I've been very satisfied with it in the years I've had it. Doesn't even seem to slow down over time!
Since a few days, I have been getting BSOD's for no apparent reason. All of them occur during intensive graphic demands. The error in event viewer is as follows:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80397e8c18e, 0xffff828260d8a1e8, 0xffff828260d89a20). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: eb1e0a36-eaac-4a5c-810b-4c15e8527df0.

I cannot access the dump though. I am currently doing an sfc /scannow in the cmd prompt, have set my laptop to do a chckdsk /f /r upon restarting and will run some anti-malware things to see if there's a problem there.
All my drivers are up-to-date.

My suspicion is that I have obtained a faulty video driver update of sorts? But I cannot read the bugcheck file and I was hoping someone knew where to find which code means what to further identify the problem and allow me to find a solution.


Hardware
IdeaPad L340-15IRH Gaming
Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz
RAM 8gb (7,88 GB usable)
Display 1 Intel(R) UHD Graphics 630, 4164 MB total memory
Display 2 NVIDIA GeForce GTX 1650, 8000 MB total memory

what nvidia geforce driver version are you using?

Driver Version: 27.21.14.5749, by NVIDIA.

I don't suppose it specifies the failing module under that?

when this started, are there any changes you made to your machine that correlate with that? this includes drivers/windows updates (check), installing software.. etc. if there comes a time when you need something to do overnight, run a memtest.. but this is usually a driver issue.

0x0000007e = SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

0xffffffffc0000005 = access code violation = your system tried to read from an invalid address in memory

0xfffff80397e8c18e, 0xffff828260d8a1e8, 0xffff828260d89a20 = where the error occurred, and then addresses for the exception and context records.

as an FYI, the best method of doing the corruption-seeking tasks is the following:

hardware test on storage first (people skip this because its usually fine until it's not)

once you know the drive is good you're safe to do a chkdsk. you don't want things being put where they aren't actually going due to a physical fault. if you don't have any data to lose this is less important I suppose.

then you should run this: dism /online /cleanup-image /restorehealth -- this will ensure the component store that SFC calls on is healthy.

then run the sfc /scannow