Random crash.

Please run the DM Log Collector again and upload a new zip, the current uploaded one misses several logs.
You could check if there are

1. 18 .txt,
2. 1 .nfo,
3. 1 or more .dmp,

files present, if this is the case then all logs are present :)
If there are a few missing, no problem as we can get them manually if required :)

Run this command in an admin command prompt, it'll create some files on the desktop. Select the files, copy them to a zip file and upload the zip.

Code:

copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

Files that are created:

• *.dmp,
• dxdiag.txt,
• hosts.txt,
• systeminfo.txt,
• drivers.txt,
• msinfo32.nfo,
• eventlog.txt,
• uninstall.txt,
• installed.txt,
• services.txt,
• startup.txt

I would suggest that you make sure the suggestions provided are only applied to the system we deal with at that moment, I will only help with 1 problem at a time (per thread) to prevent confusion with the suggestions.

So, if you post logs from different systems and I have only posted a suggestion for 1 pc, use the suggestion on the mentioned system and not on the other system(s). Chance that I'm still analyzing the logs of the other system(s) is great, your patience is appreciated :)


Run the command I posted earlier on the new system, it misses a few logs.

Forget about the new system i have send before.

If you don't want me to pay attention to a system, that you ask me to do in the first place...., please take a breath and be sure of what you want me to do :)
No aggression please, I'm only a volunteer.

I tried the commands you posted before but i dont get the *.dmp, startup.txt and dxdiag.txt files again.

With 0x7A and 0xF4 this isn't surprising, these crashes are hard drive related.
If a BSOD occurs with these error codes, good chance that no dump can be saved.


The second parameter of the 0x7A is the one that identifies what the problem is

Code:

STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.

Diagnostics Test

 HDD TEST

   Note

Please run HDTune first, in the order posted!

Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log