Crash d'ordinateur

Fermé
Taboc Messages postés 1 Date d'inscription lundi 13 avril 2015 Statut Membre Dernière intervention 13 avril 2015 - Modifié par Taboc le 13/04/2015 à 14:51
LZB Messages postés 25 Date d'inscription lundi 10 octobre 2011 Statut Membre Dernière intervention 13 avril 2015 - 13 avril 2015 à 14:53
Bonjour,
Depuis 2 semaines, mon ordinateur crashe régulièrement. J'ai fait des analyses antivirus, cela ne change rien. Il se trouve que depuis que j'ai mis à jour windows 8.1 en septembre dernier, je n'ai pas fait de mises à jour. Du coup j'en ai beaucoup à faire, c'est peut-être lié... Mais dès que j'essaye de les faire mon ordinateur crashe. Plus généralement, dès que je fais quelque chose qui prend un peu de mémoire, ça plante : écran bleu de la mort, avec le smiley ":(", et des messages d'erreur variés... Ca va un peu mieux depuis que j'ai désactivé avast, mais mon ordinateur reste quasiment inutilisable...

Le gestionnaire de tâches montre que le disque tourne quasi constamment à 100%, même lorsqu'aucune application ne fonctionne...

J'ai fait une analyse avec whocrashed, pour que vous puisse savoir un peu plus précisément ce qu'il se passe... Voici ce qu'il dit :
(les crashs d'aujourd'hui ont eu lieu quand j'ai essayé de faire les mises à jour)

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

computer name: ALEXIS-PC
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: SATELLITE C855-226, TOSHIBA, Intel, PLCSF8
CPU: GenuineIntel Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4172513280 total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 13/04/2015 12:03:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041315-25859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000D43184C0, 0xFFFFC0014A00F586)
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 Mon 13/04/2015 12:03:36 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltGetRequestorProcess+0x4A8)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000D43184C0, 0xFFFFC0014A00F586)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 13/04/2015 10:53:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041315-35156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001D12DF4C0, 0xBBE1763000)
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 Mon 13/04/2015 08:54:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041315-23687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001FDBDD0F0, 0x744AA64C)
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 Mon 13/04/2015 07:42:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041315-78703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x7A (0x5, 0x0, 0x4000, 0xFFFFE000119E7670)
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 Sun 12/04/2015 18:01:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041215-29406-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Sun 12/04/2015 14:07:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041215-20062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x50 (0xFFFFF6801035B778, 0x0, 0xFFFFF800DB4E967D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 12/04/2015 14:00:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041215-22062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801727C4D61, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 12/04/2015 13:56:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041215-24484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00033507A40, 0x713A832)
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 Fri 10/04/2015 16:30:11 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041015-25484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x41287, 0x96B76FFFF, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

26 crash dumps have been found and analyzed. Only 10 are included in this report.
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.



Voilà, sauriez-vous ce qui arrive à mon pc et ce que je pourrais faire pour qu'il aille mieux ?
Merci !!

Taboc
A voir également:

1 réponse

LZB Messages postés 25 Date d'inscription lundi 10 octobre 2011 Statut Membre Dernière intervention 13 avril 2015 5
13 avril 2015 à 14:53
Bonjour,
apparemment tu n'es pas le premier à qui cela arrive. À en lire le rapport de crash c'est à cause de quelques Dump. J'ai fait une recherche ce serait la solution à ton problème : https://www.networkworld.com/article/2320271/how-to-solve-windows-system-crashes-in-minutes.html
En espérant t'avoir aidé.
LZB
0