satrow

http://www.hostingpics.net/viewer.php?id=688070IMG0192.jpg <--- Vérifier la Target CPU Frequency, BLCK et Multiplier.

Also, the BIOS CPU settings look incorrect for the i3 540, for stock settings: Target CPU Frequency 3.06Mhz, Bus Speed (BCLK) 133.?(.7/.8)Mhz, Multiplier x23 would be a better starting point.

Bienvenue, xst. Le ci-dessous serait l'analyse de votre BSOD: Le 0x9 paramètre = A fatal error occurred while preparing the hibernate file. Certaines versions de Samsung Magician peut gâcher les paramètres d'alimentation, Panneau de contrôle > Options d'alimentation > utiliser le plan de performance équilibré ou élevé. Comment faire pour désactiver et réactiver la mise en veille prolongée sur un ordinateur Windows: https://support.microsoft.com/fr-fr/kb/920730

Ne rien ^^

During troubleshooting (7-10 days), enable Defender and check that Windows firewall is active (and take extra care!). If no BSODs in that time, you can download a new Kaspersky and install it again - but do keep a watch on Kaspersky's forum for W10 issues during that time, if problems there increase, don't install it (yet), if problems decrease, it should be 'safe' to install the latest version.

Good work, the AV at fault scenario fits well with the earlier BSOD types. Enable Defender and check that Windows firewall is enabled. ^^ Google looks accurate Is there a Kaspersky tool/method to remove any leftover parts, to ensure they cannot interfere further? Watch Kaspersky over the next 7 - 10 days for an updated version, or you can test a fresh Kaspersky install after that period, if you remain free of further BSODs.

I had 5/9 days frozen - but with a clean install, 1607 should be good. 2016 Juillet = 1607, 2015 Novembre = 1511. USB d'installation est bonne:

I think the above version might be more stable, some bugs with multiple drive systems on version 1607. On W10 the full BSOD details are probably in the QR code on screen, or, as usual, in the Management Event Logs.

Hi, my French is very poor, https://translate.google.com/ might be useful. W10 is 1511 or 1607? The STOP 0x000000EF: CRITICAL_PROCESS_DIED BSODs do not usually leave dumps, usually they cannot, I think because that would require the dead critical process. Crashes during boot, like these are usually drivers/filters, often 3rd party 'utilities' that run close to the kernel, AV/3rd party defrag/motherboard/graphics utilities, etc. or incorrect/corrupt drivers 'updated' by Windows in the previous session (?chipset/graphics?). It could easily be malware, root/bootkit, etc. Hardware/memory is less likely but may be data corruption/page file corruption. "Memory management" often refers to a 3rd party driver loading in the wrong memory space, causing corruption of the memory data that should already reside there (exact BSOD details, 0x0000000 (0x0000000, 0x0000000, 0x0000000) can tell us if it was a failure to read, failure to write, etc. - can be useful). The clean install is a good suggestion, I would use a fresh download ISO, in case the original is 'bad'. Perhaps install offline, if you can, it could be an updated driver that causes the problem.