Multiple BSODS with different errors, caused by ntoskrnl.exe

Nothing new in the 2/25 dumps.

Looking through the event viewer again I just noticed that every time a BSOD occurs, it's immediately after this entry:

Code:

Event[10829]:
  Log Name: System
  Source: Service Control Manager
  Date: 2017-02-17T15:29:28.014
  Event ID: 7045
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-21-3151266363-2160262959-3254069687-1000
  User Name: ETHANHOME-PC\EthanHome
  Computer: EthanHome-PC
  Description: 
A service was installed in the system.

Service Name:  cpuz138
Service File Name:  C:\Users\ETHANH~1\AppData\Local\Temp\\cpuz138\cpuz138_x64.sys
Service Type:  kernel mode driver
Service Start Type:  demand start
Service Account:

Try uninstalling CPUZ, see if that helps.

In the msinfo32 under problem devices i found this entry

ATAPI iHAS120 X ATA Device IDE\CDROMATAPI_IHAS120___X_______________________FL02____\5&1EFB7D31&0&0.1.0 Failure using the VxD loader.

Do not know if it is related to the BSOding and/or freezes etc. But try to reinstall drivers or uninstall and reinstall the cdrom or even remove it from your systyem.

In the latest dumpfile

Code:

 BugCheck 1E, {ffffffffc0000005, fffff80368adb04f, 0, ffffffffffffffff}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80368adb04f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

In the stacktext 2 times mentioning of storport.sys

Code:

 TACK_TEXT:  
ffff9600`02c69478 fffff803`68bed572 : 00000000`0000001e ffffffff`c0000005 fffff803`68adb04f 00000000`00000000 : nt!KeBugCheckEx
ffff9600`02c69480 fffff803`68b6baed : fffff803`68d70000 fffff803`68a1b000 0004f530`00820000 80000000`00000000 : nt!KiFatalExceptionHandler+0x22
ffff9600`02c694c0 fffff803`68aae1b1 : ffff9600`02c6b000 00000000`00000000 ffff9600`02c65000 00000000`00000001 : nt!RtlpExecuteHandlerForException+0xd
ffff9600`02c694f0 fffff803`68aacf64 : ffff9600`02c69c20 ffff9600`02c6a120 ffff9600`02c69c20 ffff9600`02c6a3f8 : nt!RtlDispatchException+0x421
ffff9600`02c69bf0 fffff803`68b70902 : fffff803`69147940 fffff803`68a92b05 ffffd100`292463f0 fffff803`691280af : nt!KiDispatchException+0x144
ffff9600`02c6a2c0 fffff803`68b6ebbd : ffff9600`02c6a529 fffff803`6911bf71 ffffd100`29054280 ffff9600`02c6a529 : nt!KiExceptionDispatch+0xc2
ffff9600`02c6a4a0 fffff803`68adb04f : ffffd100`297491b0 ffff9600`03b12bc0 ffffd100`297491b0 ffff9600`03b12bc0 : nt!KiGeneralProtectionFault+0xfd
ffff9600`02c6a630 fffff80d`64445c9b : 00000000`00000001 ffff9600`02c6a760 ffffd100`297491b0 ffffd100`297491b0 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x1f
ffff9600`02c6a660 fffff80d`64457d6d : 00000000`00000000 ffff9600`03b12010 ffffd100`297261a0 00000000`00000000 : storport!RaidUnitCompleteRequest+0xfb
ffff9600`02c6a7f0 fffff803`68a7f281 : ffff9600`02c42f00 00002778`9792880d 00000000`00000000 ffff9600`02c40180 : storport!RaidpAdapterRedirectDpcRoutine+0x8d
ffff9600`02c6a890 fffff803`68a7e67f : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x2b1
ffff9600`02c6a9e0 fffff803`68b6877a : ffffffff`00000000 ffff9600`02c40180 ffff9600`02c4ccc0 ffffd100`281d1080 : nt!KiRetireDpcList+0x5df
ffff9600`02c6ac60 00000000`00000000 : ffff9600`02c6b000 ffff9600`02c65000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

Look into your storagedrivers, maybe corruption of the drivers, update or reinstalling?

Do you have the latest drivers and firmware installed for your SSD?
Is your SSD compatible with your mobo?

Your system has a few older drivers.
AODDriver2 Wed Nov 21 08:44:04 2012
Driver Description: AMD Overdrive; also in EasyTune6 for Gigabyte motherboard
Known BSOD issues in Win7 Update to the latest version.

HWiNFO64A Tue Mar 31 11:51:32 2015, hardwareinfo update to the latest version.

rt640x64 Tue May 05 18:21:03 2015 (5548EDEF)
fffff80d`67320000 fffff80d`677a7000 RTKVHD64 Tue Jul 07 13:13:02 2015
Realtek Lan and audio driver. Look for the latest version

Look if there are newer drivers for your Razer devices.

usbfilter Wed Aug 29 03:27:12 2012
Driver Description: AMD USB Filter Driver (likely part of the chipset drivers)
Driver Update Site: Support & Drivers
See if there are newer chipsetdrivers for your mobo avaliable.

This thread is getting long. Have you ever done a Clean Install of Windows 10? If not, might be a good time to do so. Just make sure you have all your data backed up, preferable an image backup to an external USB hard drive using a program like Macrium Reflect Free.

Something to think about at least.

I can't think of any CDs you would need. You download the latest ISO from Microsoft: Download Windows 10. That will give you 14393 which is the Anniversary update version. Windows update on top of that gives you the 1607 14393.693 version which is the latest.

The key is to have a good backup first.