L'éternel écran bleu (celui-ci après un certain temps passé)
LaShab64
Messages postés
4
Statut
Membre
-
LaShab64 Messages postés 4 Statut Membre -
LaShab64 Messages postés 4 Statut Membre -
Bonjour à tous,
Je viens donc faire appel à vous pour un problème récurent depuis plus d'un an ou 2.
L'écran bleu universel de Windows apparaît donc sur mon PC, après un certain temps d'utilisation, de façon aléatoire que je sois sur un jeu ou sur Internet ou même avant de regarder l'ordinateur, pendant qu'il s'allumait. Je suis sur Vista, et je me souviens qu'il était apparu il y a longtemps puis avait disparu tout seul et est revenu depuis 2/3 mois 1 fois par semaine comme 2 fois en 2 jours ou 1 fois par mois.
Je voudrais savoir si quelqu'un pouvait essayer de me "guider" pour résoudre ce problème, les différents tutoriels étant souvent différents pour chaque problème et pas très précis, du moins ce que j'ai vu.
Merci d'avance.
Je viens donc faire appel à vous pour un problème récurent depuis plus d'un an ou 2.
L'écran bleu universel de Windows apparaît donc sur mon PC, après un certain temps d'utilisation, de façon aléatoire que je sois sur un jeu ou sur Internet ou même avant de regarder l'ordinateur, pendant qu'il s'allumait. Je suis sur Vista, et je me souviens qu'il était apparu il y a longtemps puis avait disparu tout seul et est revenu depuis 2/3 mois 1 fois par semaine comme 2 fois en 2 jours ou 1 fois par mois.
Je voudrais savoir si quelqu'un pouvait essayer de me "guider" pour résoudre ce problème, les différents tutoriels étant souvent différents pour chaque problème et pas très précis, du moins ce que j'ai vu.
Merci d'avance.
A voir également:
- L'éternel écran bleu (celui-ci après un certain temps passé)
- Supprimer rond bleu whatsapp - Guide
- Écran bleu - Guide
- Double ecran - Guide
- Trousseau mot de passe iphone - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
5 réponses
D'accord merci beaucoup, dès que je l'ai fait je poste le résultat.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 10/10/2012 17:45:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101012-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFC8189488, 0xFFFFFFFFC81894D8, 0xA0A0605)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.
On Wed 10/10/2012 17:45:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFC8189488, 0xFFFFFFFFC81894D8, 0xA0A0605)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe BAD_POOL_HEADER
On Mon 08/10/2012 17:30:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100812-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xEE7D7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8313E7D7, 0xFFFFFFFFA36F2844, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Mon 08/10/2012 17:27:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100812-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x230A1)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF830BC98C, 0xFFFFFFFF803F4C38, 0xFFFFFFFF803F4934)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a system thread 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.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Wed 03/10/2012 18:02:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100312-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x54B7)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFB36A9180, 0xFFFFFFFFB36A91F0, 0xA0E0607)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: aswmonflt.sys AVAST Software BAD_POOL_HEADER
On Tue 02/10/2012 17:15:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100212-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC05108E0, 0xFFFFFFFF863A7980, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Mon 01/10/2012 16:30:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100112-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC0474670, 0xFFFFFFFFAB3C3D78, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Sun 30/09/2012 11:20:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini093012-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1122F)
Bugcheck code: 0x44 (0xFFFFFFFF873687D8, 0xE7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 28/09/2012 19:16:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini092812-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3FF9)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFFFFF83022FF9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 19/08/2012 15:16:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081912-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x7C046)
Bugcheck code: 0x116 (0xFFFFFFFFB84B3510, 0xFFFFFFFF8FD50856, 0xFFFFFFFFC00000B5, 0xA)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 which cannot be identified at this time.
On Sat 04/08/2012 09:03:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080412-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x8C462)
Bugcheck code: 0x50 (0xFFFFFFFF8E7F2000, 0x1, 0xFFFFFFFF90294462, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 306.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 306.23
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 306.23 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. 4 third party drivers have 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 306.23 , NVIDIA Corporation)
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)
aswsp.sys (avast! self protection module, AVAST Software)
ntkrpamp.exe
J'espère que c'est bien ce que tu me demandais sinon je referais ^^'
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 10/10/2012 17:45:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101012-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFC8189488, 0xFFFFFFFFC81894D8, 0xA0A0605)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.
On Wed 10/10/2012 17:45:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFC8189488, 0xFFFFFFFFC81894D8, 0xA0A0605)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe BAD_POOL_HEADER
On Mon 08/10/2012 17:30:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100812-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xEE7D7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8313E7D7, 0xFFFFFFFFA36F2844, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Mon 08/10/2012 17:27:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100812-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x230A1)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF830BC98C, 0xFFFFFFFF803F4C38, 0xFFFFFFFF803F4934)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a system thread 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.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Wed 03/10/2012 18:02:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100312-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x54B7)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFB36A9180, 0xFFFFFFFFB36A91F0, 0xA0E0607)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: aswmonflt.sys AVAST Software BAD_POOL_HEADER
On Tue 02/10/2012 17:15:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100212-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC05108E0, 0xFFFFFFFF863A7980, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Mon 01/10/2012 16:30:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100112-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x1A (0x3451, 0xFFFFFFFFC0474670, 0xFFFFFFFFAB3C3D78, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.
On Sun 30/09/2012 11:20:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini093012-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1122F)
Bugcheck code: 0x44 (0xFFFFFFFF873687D8, 0xE7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 28/09/2012 19:16:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini092812-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3FF9)
Bugcheck code: 0xA (0x1, 0x2, 0x1, 0xFFFFFFFF83022FF9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 19/08/2012 15:16:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081912-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x7C046)
Bugcheck code: 0x116 (0xFFFFFFFFB84B3510, 0xFFFFFFFF8FD50856, 0xFFFFFFFFC00000B5, 0xA)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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 which cannot be identified at this time.
On Sat 04/08/2012 09:03:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini080412-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x8C462)
Bugcheck code: 0x50 (0xFFFFFFFF8E7F2000, 0x1, 0xFFFFFFFF90294462, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 306.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 306.23
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 306.23 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. 4 third party drivers have 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 306.23 , NVIDIA Corporation)
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)
aswsp.sys (avast! self protection module, AVAST Software)
ntkrpamp.exe
J'espère que c'est bien ce que tu me demandais sinon je referais ^^'
Salut !
1) Pour plus info sur le BSOD :
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
Cela pourrait t'aider...
remarque : BSOD veut dire Bleu Screen Of Death, ce petit malin qui affecte tous les systèmes Windows...
2) Telecharge WhoCrashed
Un petit programme qui va te creer un rapport sur le BSOD...
Ensuite tu postera ce rapport dans ta prochaine réponse. Ainsi, on pourra savoir quel est le fichier responsable...
A+
Alex
1) Pour plus info sur le BSOD :
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
Cela pourrait t'aider...
remarque : BSOD veut dire Bleu Screen Of Death, ce petit malin qui affecte tous les systèmes Windows...
2) Telecharge WhoCrashed
Un petit programme qui va te creer un rapport sur le BSOD...
Ensuite tu postera ce rapport dans ta prochaine réponse. Ainsi, on pourra savoir quel est le fichier responsable...
A+
Alex
Ah ça veut donc dire que c'est ce programme qui est responsable des crashs ? Les autres programmes sont régulièrement à jour, de suite quand une MAJ sort d'ailleurs surtout pour Avast et Nvidia.
Je précise que parfois l'ordinateur freeze (beaucoup plus souvent que le BSOD) et je ne peux plus rien faire sauf le redémarrer manuellement. Peut-être que ça a un rapport ? Si c'est bien ce processus qui a un problème, est-il "réparable", est-ce grave etc ?
Merci,
Je précise que parfois l'ordinateur freeze (beaucoup plus souvent que le BSOD) et je ne peux plus rien faire sauf le redémarrer manuellement. Peut-être que ça a un rapport ? Si c'est bien ce processus qui a un problème, est-il "réparable", est-ce grave etc ?
Merci,
Oui bien sur, les << Freeze >> sont signe d'un gros problème surtout qu'on ne peut pas comme tu l'a dit avoir d'autre solution que de l'éteindre a la manuelle. Oui c'est assez Grave. Mais ce n'est pas dramatique...
Ca vient surement de ta carte graphique vu qu'il y a ses Freeze.
Il semble que c'est la dernière version du pilote de la carte graphique ?
Si c'est le cas, il faudrait essayer avec une version antérieure ou alors le pilote de Windows.
Ca vient surement de ta carte graphique vu qu'il y a ses Freeze.
Il semble que c'est la dernière version du pilote de la carte graphique ?
Si c'est le cas, il faudrait essayer avec une version antérieure ou alors le pilote de Windows.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
J'avais mis à jour le pilote il y a un mois environ et c'est là que les problèmes avaient recommencé, et il y a eu une nouvelle MAJ il y a 3/4 jours je crois depuis plus rien alors je vais tenter de laisser comme ça pour l'instant je verrais si ça se reproduit avec cette version.
En tout cas merci beaucoup de ton aide, je reposterais si j'ai encore besoin :)
En tout cas merci beaucoup de ton aide, je reposterais si j'ai encore besoin :)
Je vais te traduire la conclusion de WhoCrashed :
11 crash dumps ont été trouvés et analysés. 4 pilotes tiers ont été identifiés pour être la cause de plantage du système sur votre ordinateur. Il est fortement recommandé que vous vérifiez les mises à jour de ces pilotes sur leurs sites Web d'entreprise. Cliquez sur les liens ci-dessous pour effectuer une recherche avec Google pour mises à jour de ces pilotes:
nvlddmkm.sys (NVIDIA sous Windows pilote en mode noyau, la version 306.23, NVIDIA Corporation)
aswmonflt.sys (avast! du système de fichiers pour Windows 2003/Vista MiniFilter, AVAST Software)
aswsp.sys (module avast! auto-protection, AVAST Software)
Ntkrpamp.exe
Traduction par Google
Cela veut dire que tu a un problème avec tes drivers ou pilotes.
Mais kezaco Nrkrspamp ?
Que fait ntkrpamp.exe sur mon ordinateur ?
ntkrpamp.exe est un process lié à Microsoft® Windows® Operating System de Microsoft Corporation. ntkrpamp.exe est un processus système nécessaire au fonctionnement approprié de votre système. Il ne doit pas être supprimé. Vérifiez maintenant pour identifier les processus inutilisés qui ralentissent votre ordinateur.
Source : www.processlibrary.com
Ca veut dire que le problème de Bsod est soit liée a tes drivers ou soit à ton systeme Windows.
Car Nrkrspamp est un processus essentiel au bon fonctionnement de Windows...