[Enfermedehors]

Le BSOD proviendrait d'un est provoquée par un conflit entre la mémoire paginée (la mémoire virtuelle) et des données (data) demandées par le noyau (Kernel).
Les causes souvent évoquées :
Disque dur défectueux : on a vérifié et tu as fait un chkdsk.
Fichiers corrompus dans la partition système : tu n'as pas pu faire le sfc et le dism.
Un virus : El Magnifico a tout vérifié
Un conflit avec un logiciel ou un pilote. Est-ce que tu as installé un programme peu de temps avant l'apparition des BSOD ?
Dans un des deux rapports de crash, avgsnx.sys est en cause, l'installation d'AVG est récente ?

Comme tu ne peux pas faire de sfc et que les commandes DISM plantent, il faudrait faire une réinstallation sans perte de logiciels et données.
Tout est expliqué ici : https://www.malekal.com/reparer-windows ... e-donnees/

[aristotelous]

Encore un, tout frais

System Information (local)
--------------------------------------------------------------------------------

Computer name: SALON
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: Aspire E5-471, Acer, EA40_HB
CPU: GenuineIntel Intel(R) Core(TM) i3-4030U CPU @ 1.90GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4218793984 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Thu 26/04/2018 19:34:36 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042618-25359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1552A0)
Bugcheck code: 0x7A (0xFFFFF6E00042E378, 0xFFFFFFFFC00000C0, 0x5853A880, 0xFFFFC00085C6F248)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 26/04/2018 19:34:36 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlImageNtHeaderEx+0x2B72)
Bugcheck code: 0x7A (0xFFFFF6E00042E378, 0xFFFFFFFFC00000C0, 0x5853A880, 0xFFFFC00085C6F248)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 25/04/2018 14:19:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042518-18578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1552A0)
Bugcheck code: 0x7A (0xFFFFF6E0002265E0, 0xFFFFFFFFC00000C0, 0x149F13880, 0xFFFFC00044CBC000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[aristotelous]

Oups, je n'avais pas vu ton message.
Le checkdisk, je ne l'ai pas fait en ligne de commande hein? Juste l'outil de vérification du HDD?

J'ai en effet installé une nouvelle imprimante juste avant que les plantages ne commencent. AVG est installé depuis longtemps mais me casse les pieds à vouloir installer des trucs en plus.

J'essaie ce que tu me proposes.

[Enfermedehors]

Dans celui-là non plus, aucun pilote n'a pu être identifié.
Les BSOD arrivent quand tu fais quelque chose de particulier ?

J'ai en effet installé une nouvelle imprimante juste avant que les plantages ne commencent

Si ce n'est pas trop fastidieux, désinstalle-la, le temps de voir si les BSOD reviennent.

J'ai oublié de te poser une question !
Tu n'as pas fait la migration vers Windows 10 volontairement, ou parce que tu n'as pas pu, que la mise à niveau a échoué ?

[aristotelous]

Je n'ai pas réussi à identifier une action en particulier qui provoquerait le BSOD.
Je ne vois plus l'imprimante dans les périphériques ni dans les programmes mais je ne me souviens pas de l'avoir désinstallée. As tu une astuce pour vérifier?
Et je n'ai pas migré vers windows 10

[Enfermedehors]

Dans tes logs, je vois un programme Canon dans C:\Program Files (x86)\, mais pas de processus actif ni de service ou de tâches planifiée, donc elle ne peut pas âtre en cause.

[aristotelous]

Merci, au moins, cette hypothèse est éliminée!
J'ai récupéré la clé de windows, je tenterai la réparation demain, bonne soirée et encore merci du temps que tu prends pour m'aider!

[Enfermedehors]

Si Windows 8 était préinstallé, tu ne devrais pas avoir besoin de la clé.
Bonne soirée.

[aristotelous]

Bonjour,
j'ai bien réinstallé windows 8, j'espère que ça va aller mieux!

[aristotelous]

Eh bien un nouveau crash... au secours

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sat 28/04/2018 12:42:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042818-18781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x7A (0xFFFFF6E000361E18, 0xFFFFFFFFC000000E, 0x222B6880, 0xFFFFC0006C3C3B10)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 28/04/2018 12:42:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: avgsnx.sys (avgSnx+0x2CE34)
Bugcheck code: 0x7A (0xFFFFF6E000361E18, 0xFFFFFFFFC000000E, 0x222B6880, 0xFFFFC0006C3C3B10)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\avgsnx.sys
product: AVG Internet Security System
company: AVG Technologies CZ, s.r.o.
description: AVG Virtualization Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgsnx.sys (AVG Virtualization Driver, AVG Technologies CZ, s.r.o.).
Google query: avgsnx.sys AVG Technologies CZ, s.r.o. KERNEL_DATA_INPAGE_ERROR





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

avgsnx.sys (AVG Virtualization Driver, AVG Technologies CZ, s.r.o.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.