BSOD in games and random, Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)

My system has BSOD twice today, used to do it many time a day before i re-installed windows. I have no idea what causes it and would really like to know. Most recent WhoCrashed said "This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)" and the other says "This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xCBB40)" which is related to nvida drivers but i have most recent one installed. If some genius could help it would be appreciated but if you cant, thats ok.

Hello and welcome to Sevenforums!

The problem is caused by your graphics driver. Run Display Driver Uninstaller(DDU)
Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again and you should be good to go! This is the guide for DDU: Drivers - Clean Left over Files after Uninstalling

Update DirectX.

Run sfc /scannow and chkdsk /r.
Install the latest updates from Windows Update.

Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

SFC /SCANNOW Command - System File Checker

Thanks for the welcome, i did what you suggested and i will report back in a few days to see if it comes about again.

On Thu 4/30/2015 1:19:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042915-5226-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA6622)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EF5622, 0xFFFFF880033E06D8, 0xFFFFF880033DFF30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

That just happened :/

Hm, run Driver Verifier for 24 hours.
Driver Verifier - Enable and Disable

What will this help with? I see it says it may cause more BSOD events, is this not what i want to avoid?

If Driver Verifier BSODs than it means it has found the driver which is bad.

Well is BSOD plenty of times after turning that on, like 1 minute after booting and logging into my account. Also I thought about turning on prime95 to best simulate like thirty minutes of gaming on the cpu but every time I got to the point where I actually had start the test it BSOD on me. After BSOD happens a few times do I need to send another collection zip like I initially posted?

Yup, post the new dumps and disable Driver Verifier.

Alright, I will do that as soon as I get home. Hopefully