Ram - bluescreen

whocrashed
^^

J'avais déjà essayé un logiciel du genre sans résultat, je vais réessayer ne sait-on jamais.

Hier j'avais un processus windows qui me bouffait 1 200K à 2 000K, je l'ai supprimé, ça a diminué ma quantité de RAM utilisé mais 5go étaient encore utilisés.

Je suis sur windows 7.

J'essayerai de mettre une photo du bluescreen ici.

On Tue 26/04/2016 23:33:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042716-31044-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA8017019B70, 0x2, 0x0, 0xFFFFF80002D3FF9F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 26/04/2016 23:33:10 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA8017019B70, 0x2, 0x0, 0xFFFFF80002D3FF9F)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 26/04/2016 19:02:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042616-15584-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA801F055CA0, 0x2, 0x0, 0xFFFFF80002D46F9F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 26/04/2016 18:39:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042616-14118-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA801BFC6980, 0x2, 0x0, 0xFFFFF80002D8BF9F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 26/04/2016 18:08:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042616-22807-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA801C03B700, 0x2, 0x0, 0xFFFFF80002C7B618)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.


Conclusion


5 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.

Encore ce soir j'ai ( pour moi ) une consommation excessive de ma RAM 4,5go alors que j'ai deux pages internet plus deux logiciels.

Je ne peux pas ajouter de screen donc je ne peux pas montrer mes processus ...

d'apres la page bleu,
c'est un soucis de ram excessive du as un soucis de drivers...

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.


après faut toujours interpréter avec des pincette car une autre panne peut en causé la conséquence... mais deja apparemment c'est plus logiciel que materiel.

as tu installé des drivers récemment, sont ils a jours?