eh?if anyones interested
Try running the driver verifier, this will stress each driver in turn and if they bsod then the culprit will be named on the dump file.
If the driver verifier causes a bsod boot loop, you'll need to boot into safe mode and turn the verifier off. The resulting dump files should have the culprit named.
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 & Vista - Windows Crashes, BSOD, and Hangs Help and Support
There isn't one.kemical on Driver Verifier page wheres the download
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffffb0824f4dc028, be000000, 800400}
Probably caused by : GenuineIntel
Followup: MachineOwner
Can you check anyway?Also there are 4 fans so I don't think it will be the temperature .
How to Test Your Computer’s RAM for ProblemsIn Windows 7 you did a Windows Memory Diagnostic test where you restarted and checked for errors . Is there nothing like that in Windows 10 .
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {62, ffff968040740000, ffff96804074000c, b7}
*** WARNING: Unable to verify timestamp for iocbios2.sys
*** ERROR: Module load completed but symbols could not be loaded for iocbios2.sys
Probably caused by : memory_corruption
Followup: memory_corruption