Thanks for the answer.
Quick tests about ram using Windows Repair Tools were OK, but I can try that - I have less than 2 hour a day at home to test that, by 21:00 to 23:00 (on my timezone, it is 12:10 PM now).
The reason I did not investigate there is I wonder if a RAM issue would provoke that exact type of BSOD, and if I would never have experimented such BSOD during Win7 life of the computer, or in debug mode.
MiniDump files were left in my PC, because there was something like 20 of them. Exploitation of these through WhoCrash gave nothing. I set BSOD to generate kernel memory dumps, to analyse these with windbg. I will post minidump and the last memory dump tonigh, if the site permits that type of file.
My personnal suspect are :
- JMicron's chipset. It is desactivated in BIOS now, so driver shouldn't load. Device manger is clean from hidden devices, so it's not even remembered by windows. But there was a Win7 autorun name xInsIDE.exe. After desactivating it, the system was stable for 5 hours, which is an unique record. I suspect it to try to load IDE drivers for e-SATA ports on the front and back panels of the PC. I had to use advanced uninastaller pro to be able to find it - it isn't listed with windows tools.
I did that because of this IDE controler that keep coming back after each boot, because I suspect a driver try to instal or peek at a new IDE port that doesn't really exist (I suspect an external IDE drive).
- Sound card (A card that I read here that the official driver were not 1909 compatible)
- HyperX Cloud 2, that have issues with win10 that doesn't really work with 2 sound card computer : it have a deported sound card in the volume dongle).
- I have a lot of Wifi connect/disconnect issue that I did not investigate so far.
HyperX, Wifi, Mouse are on the front panel, and there is 1x e-SATA port on the front panel. The system crash even if reboot with no HyperX plugged there.
HyperX and JMicron drivers doesn't load in debug mode and debug mode is stable.
Other suspects :
- PEBCAK, because I tried lots of maintenance tools and actions, and I'm not a real specialist. I may have amplify an existing problem after a BSOD panic (not used to these in Win7).
- Maybe there was a rollback on a driver. I have to check why a driver upgrade tool detects it as obsolete.