ubuysa
The BSOD Doctor
That BSOD was a KMODE_EXCEPTION_NOT_HANDLED which happens when an exception occurs in the kernel which the error handlers cannot resolve. In this case the failing driver was volmgr.sys which is the Windows volume manager driver - the driver that manages disk volumes. The exception code was 0xc0000005 which is a memory (RAM) access violation - and that's pointing once again at RAM. In the stack trace you can see a page fault immediately after volmgr.sys, that means that the RAM page the driver was trying to read was either not in RAM (which should never happen) or the page couldn't be read properly (which the exception code shows was the case). The owning process is (unsurprisingly) the system process.
This BSOD is screaming RAM error, though if your Windows system is corrupted (which it might be - that's why a reinstall is so important now) that could also be the cause. Since Memtest ran clean, a corrupt Windows system is much more likely - although Memtest can never prove that your RAM is good, it's just the best test we have.
In troubleshooting it's very important to handle only one thing at a time, so I suggest you park the RAM suspicions for now and concentrate on getting Windows reinstalled. You need a stable and reliable software platform before you can start investigating potential hardware problems.
I no longer trust that PC and I strongly suggest that you don't use it to run the Media Creation Tool - you'll never be able to fully trust the installation files that are written to it by your flaky PC. Find another laptop or PC and run the Media Creation Tool on there so that you can have confidence in the install USB you make.
This BSOD is screaming RAM error, though if your Windows system is corrupted (which it might be - that's why a reinstall is so important now) that could also be the cause. Since Memtest ran clean, a corrupt Windows system is much more likely - although Memtest can never prove that your RAM is good, it's just the best test we have.
In troubleshooting it's very important to handle only one thing at a time, so I suggest you park the RAM suspicions for now and concentrate on getting Windows reinstalled. You need a stable and reliable software platform before you can start investigating potential hardware problems.
I no longer trust that PC and I strongly suggest that you don't use it to run the Media Creation Tool - you'll never be able to fully trust the installation files that are written to it by your flaky PC. Find another laptop or PC and run the Media Creation Tool on there so that you can have confidence in the install USB you make.
