The situation appears to be critical. Six BSODs today, with six different Bugcheck code. Depending on the situation, I think it is better to proceed slow and step by step.
What is most important information that you have SPTD installed, and as usual it is crashing.
Code:
fffff880`0aaea458 fffff880`01113adcUnable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
sptd+0xb4adc
Keeping SPTD present in the system, no troubleshooting is meaningful.
Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :
- Double click to open it.
- Click this button only:
- If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
Next, Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept then restart.
Your C drive is substantially filled up? Copy the documents to the other partitions which is having enough free space.
Let us know the situation after doing these three. Depending on the situation we will decide our next steps.
______________________________________________________________________________________
BSOD ANALYSIS:
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff88004220cee, fffff880077ea568, fffff880077e9dc0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
Followup: MachineOwner
------------------------------------------------------------------------------------------------
BugCheck A, {fffff38006bfb778, 2, 1, fffff8000473bc8f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
Followup: MachineOwner
-------------------------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff88001b8fdaa, fffff880039b6b60, 0}
Probably caused by : afd.sys ( afd!AfdBReceive+10a )
Followup: MachineOwner
-------------------------------------------------------------------------------------------------
BugCheck 1, {741c2e09, 0, f700, fffff8800a877b60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
-------------------------------------------------------------------------------------------------
BugCheck 1E, {ffffffffc0000005, fffff800047be9bc, 0, ffffffffffffffff}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
Followup: Pool_corruption
-------------------------------------------------------------------------------------------------
BugCheck 50, {fffff1a000004700, 1, fffff800049dfe3d, 7}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+884a )
Followup: MachineOwner
---------