E
Ethan--
After running one of my dmp files through WinDBG I found the image_name to be "memory_corruption" I did some research into that and found it to commonly be a driver problem. I reset my PC yesterday and am still having BSOD so if resetting fixed any drivers, it didn't fix the right one. but just last night I got another BSOD and this time the dmp file comes back as "hardware" under image and module name. What are my options for fixing this/finding the driver responsible? (this has been happening since November when I initially built my pc)
I have run memtest for 3 passes and found nothing.
I tried Driver Verifier but that just threw my pc into more consistent BSOD with driver_verifier
Since resetting my PC I've only installed essentials such as spotify, discord, just things I'd need and use often.
If it matters my ram is Corsair Vengeance 16gb Pro RGB ( 2x 8gb)
Continue reading...
I have run memtest for 3 passes and found nothing.
I tried Driver Verifier but that just threw my pc into more consistent BSOD with driver_verifier
Since resetting my PC I've only installed essentials such as spotify, discord, just things I'd need and use often.
If it matters my ram is Corsair Vengeance 16gb Pro RGB ( 2x 8gb)
Continue reading...