BSOD 0x1000007e at power on my PC with ntoskrnl.exe driver volsnap.sys

CABJ mate these two errors are often associated with memory and power problems ntoskrnl.exe and security volsnap.sys I know it says security essentials but this could mean anything

Do if you can get into safe mode try these first


https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

https://www.sevenforums.com/tutorials/433-disk-check.html

Hmm now I cannot advise you on the RAM voltages and if I were you I would leav them at that default.

Now it might be an idea to run a memtest

https://www.sevenforums.com/tutorials/105647-ram-test-memtest86.htmlthisone you will need to make a bootable disk set the BIOS to optical (or USB ifpreferred) boot the machine and let it run for at LEAST 8 passes unless theerrors come up straight away. Takes fair time to complete and some leave itrunning overnight.
But before you do that reseat all the cable sticks and cards and if you feel confident enough this is some thing else I do

SLOTCLEANING

Now as for the slots to clean them use astrip of old credit card about 1/2 inch wide nip the corners off one end - preferably round them offhold apiece of thin lint free cloth over the end dab on some form of alcohol - isopropyl alcohol (what we swab the skin with before an injection) is good and GENTLY swipe along the slots.

This can also be done for the GPU slot/s.

see pic

Do the chdsk and sfc scan that was requested. The Code 7E can be a corrupt OS file due to ocverclocking. Use the motherboard default settings. The volsnap.sys is Windows back up, try turning it off.

Hardware can fail at any time or be bad when new. It could also be due to your having mis-matched RAM modules. It's always best for them to be a matched set. even the same model from the same manufacturer can foul things up unless purchased as a set. Each module has up to 16 chips on it so they are carefully selected to work together.

It is hardware error.

Code:

BugCheck 3B, {c0000005, fffff80002efbf5b, fffff88009925ed0, 0}

Probably caused by : hardware ( nt!AlpcpSignalAndWait+8b )

Followup: MachineOwner
-----------------------------------------------------------------------
BugCheck 1000007E, {ffffffffc000001d, fffff80002ae299b, fffff88002e9ba28, fffff88002e9b280}

Probably caused by : hardware ( volsnap!VspWorkerThread+80 )

Followup: MachineOwner
---------

Start with some hardware tests ......

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

Do this too as suggested by ICit2lol.
SFC /SCANNOW Command - System File Checker