Random & Several Blue Screens

[Shortland]

Hello all.
Recently i updated to the latest build of Windows,and since update,several and randoms BSoDs occurs almost every day. Three days ago, BSoDs was non stop,one after another,over 30 in a single day.I tried everything,even safe mode,system restore,etc,yet blue screening keep happens and i was unable to even try to fix OS. So,i un-install Windows,and installed again all new and fresh. Everything went well for two days,and then today BSoDs started again. This is happens only after latest build (10586.36) update. Thanks in advance.

*Here's my .dmp file,Windows info,and latest two BSoDs:

Edition: Windows 10 Pro
Version: 1511
OS Build: 10586.36
Cpu: AMD FX-4130
Ram: 8.00 Gb Crucial Balistix Sport 1866
Mobo: ASRock 970 Pro3 R2.0

"On Sat 19/12/2015 16:56:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121915-16156-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!HvpValidateLoadedBin+0x0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80122A8556C, 0xFFFFD000238C5B58, 0xFFFFD000238C5370)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.

On Sat 19/12/2015 16:56:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80122A8556C, 0xFFFFD000238C5B58, 0xFFFFD000238C5370)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time."

 

[Trouble]

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80122a8556c, The address that the exception occurred at
Arg3: ffffd000238c5b58, Exception Record Address
Arg4: ffffd000238c5370, Context Record Address

Although I don't see a particular driver called out in the stack trace

STACK_TEXT:
ffffd000`238c5d98 fffff801`22a84805 : ffffc000`a2228000 ffffd000`238c5e19 ffffc000`a2275000 00000000`00000082 : nt!HvpValidateLoadedBin
ffffd000`238c5da0 fffff801`22a3f77c : ffffc000`a2228000 ffffc000`00573000 00000000`00000000 00000000`00000000 : nt!HvpRemapAndEnlistHiveBins+0x91
ffffd000`238c5e80 fffff801`22a3ec99 : 00000f80`00000000 00000000`00000004 00000000`00000000 ffffc000`a2228000 : nt!HvLoadHive+0x1ac
ffffd000`238c5f80 fffff801`22a3e67c : 00000000`00000000 00000000`00000001 ffffd000`238c6071 00000000`00000001 : nt!HvInitializeHive+0x289
ffffd000`238c5fe0 fffff801`22b4d667 : ffffd000`238c61a8 ffffe001`00000001 ffffd000`00020000 00000000`00000002 : nt!CmpInitializeHive+0x4a4
ffffd000`238c60c0 fffff801`22aa6026 : ffffd000`6e664d43 fffff801`00000000 ffffe001`d14d8500 00000000`00000000 : nt!CmpInitHiveFromFile+0x3fb
ffffd000`238c62e0 fffff801`22acc073 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd000`0000010e : nt!CmpCmdHiveOpen+0xb2
ffffd000`238c64f0 fffff801`22b4c3b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmLoadKey+0x17f
ffffd000`238c65b0 fffff801`227cbfa3 : ffffe001`d08e4840 ffffd000`238c6a70 ffffe001`00000080 00000000`00000000 : nt!NtLoadKeyEx+0x880
ffffd000`238c67f0 fffff801`227c4650 : fffff801`22a31d31 ffffe001`cd83b3c0 00000000`00000060 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`238c69f8 fffff801`22a31d31 : ffffe001`cd83b3c0 00000000`00000060 00000000`00000001 fffff801`22981e40 : nt!KiServiceLinkage
ffffd000`238c6a00 fffff801`22a32406 : ffffe001`d08e4840 ffffe001`cd93a850 ffffe001`cd93a860 fffff801`226cf926 : nt!PiDrvDbLoadHive+0x81
ffffd000`238c6ab0 fffff801`226e9b79 : fffff801`00000000 ffffe001`00000001 ffffe001`00000000 00000000`00000000 : nt!PiDrvDbLoadNodeWorkerCallback+0x66
ffffd000`238c6b80 fffff801`22688125 : 00000204`acbb3dfe 00000000`00000080 ffffe001`cd8c4700 ffffe001`d08e4840 : nt!ExpWorkerThread+0xe9
ffffd000`238c6c10 fffff801`227c6906 : fffff801`2299c180 ffffe001`d08e4840 fffff801`226880e4 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffd000`238c6c60 00000000`00000000 : ffffd000`238c7000 ffffd000`238c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

There are a few older ones on your system that may need your attention.... Upgrade / Update or uninstall or break them.

ElcMouLFlt.sys     10/4/2010                       
ElcMouUFlt.sys    11/29/2010                       
dfx12x64.sys         8/28/2012                       
t_mouse.sys         12/3/2012                      
trufos.sys              3/6/2013                       
RtNdPt630.sys      9/26/2013                  
VClone.sys            5/3/2014                       
mbae64.sys          9/8/2014

Use Google and see if you can determine what options you may have regarding the above drivers.
AND
Make sure your BIOS is up to date and if BSODs persist test your system memory.
http://www.memtest.org/
Grab the ISO, burn it to a CD and boot your system from that and run Memtest86+ for at least 6 passes (over night is better).
Unless it starts throwing errors early on in the testing.

 

[Shortland]

Hello again sir,and thanks a lot for your attention.
Well,bios is up to date,at least as far as i can see,Asrock released latest firmware some months ago.Now,rest,yes i think time to update all the above programs. Trufos.sys,hm,it's kinda weird because it was from my BitDefender.I've total uninstalled it with revo,due to incombatibility/bsods,but why driver still exists?I delete is now.Also elcmoulft/t_mouse.sys,seems coming from my CM Storm mice. VClone,isn't using SPTD.So far,2h now not a single blue screen after: system restoration,disabling an HDD,switched power options from High to Balanced,and re-enabled some windows services,such as search indexing,printer,and ftp sharing,plus switched back to normal desktop theme,instead of performance one.So,my question is: any possibility blue screen's occurs due to high performance mode, and/or disabled services,desktop themes switching? I keep HDD out for awhile to check also.That's all for now and thank you very much again for your time.

Edit: i just installed/checked again RtNdPt630.sys, and inside /system32/drivers, showing up as 2015/07/29,and at Realtek's site latest version 10.006 as update time 2015/11/25.

 

[AceInfinity]

Reviewing the stack trace, you might even have a corrupt registry. -- In that case whether you were to view the corrupted section manually with regedit, or some program requests keys or values from that section, would cause the BSOD.

That's just what the stack trace tells me though, keep in mind a more accurate analysis can only be done by debugging the *.dmp file.