Mon ordi me fait ecran bleu apres 2 min
lemafieu973
Messages postés
11
Statut
Membre
-
qwerty- Messages postés 17655 Date d'inscription Statut Contributeur Dernière intervention -
qwerty- Messages postés 17655 Date d'inscription Statut Contributeur Dernière intervention -
Bonjour, depuis quelque temps j'allume mon ordi et 2min apres ecran bleu et redémarrage
J'ai une photo regardez
https://i21.servimg.com/u/f21/11/91/75/38/p1000910.jpg
J'ai une photo regardez
https://i21.servimg.com/u/f21/11/91/75/38/p1000910.jpg
A voir également:
- Mon ordi me fait ecran bleu apres 2 min
- Supprimer rond bleu whatsapp - Guide
- Ordi qui rame - Guide
- Ecran bleu ordi - Guide
- Double ecran - Guide
- Supercopier 2 - Télécharger - Gestion de fichiers
16 réponses
salut,
downloade "whocrahed"
https://download.cnet.com/WhoCrashed/3000-2094_4-75205821.html
et poste le rapport qu'il va te donner stp
downloade "whocrahed"
https://download.cnet.com/WhoCrashed/3000-2094_4-75205821.html
et poste le rapport qu'il va te donner stp
c'est un programme qui va me donner la cause des plantages dans un rapport (il va chercher cela dans le "dump" du crash, qui se créé lors de l"ecran bleu...)
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
si oui, en haut a gauche il y a un bouton vert "analyze"
tu cliques dessus.
ensuite tu descend simplement plus bas dans la fenêtre jusqu'a trouver "system information(local)"
et a partir de ça tu copie / colle tout le contenu jusqu'en bas ici même
tu cliques dessus.
ensuite tu descend simplement plus bas dans la fenêtre jusqu'a trouver "system information(local)"
et a partir de ça tu copie / colle tout le contenu jusqu'en bas ici même
computer name: ANGEFAMILY
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5300 @ 2.60GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294103040 total
VM: 2147352576, free: 1942941696
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5300 @ 2.60GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294103040 total
VM: 2147352576, free: 1942941696
System Information (local)
--------------------------------------------------------------------------------
computer name: ANGEFAMILY
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5300 @ 2.60GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294103040 total
VM: 2147352576, free: 1942941696
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 27/12/2011 17:57:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122711-23571-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAE01F)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880014AF01F, 0x0, 0x118)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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 Tue 27/12/2011 17:57:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAE01F)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880014AF01F, 0x0, 0x118)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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 Mon 26/12/2011 20:55:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122611-22776-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF880084E8E15, 0x1, 0xFFFFF80003C96E78, 0x0)
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 which cannot be identified at this time.
On Mon 26/12/2011 17:04:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122611-23571-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF3000ECDE6D0, 0x0, 0xFFFFF88001203C55, 0x7)
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 which cannot be identified at this time.
On Sun 25/12/2011 18:46:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122511-27253-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80003CA3AE8)
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 which cannot be identified at this time.
On Tue 20/12/2011 18:26:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122011-23259-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80003CB29D6, 0xFFFFF8800386E100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 13/12/2011 09:37:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121311-22495-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF10013B174C1, 0x1, 0xFFFFF80003CBDB55, 0x7)
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 which cannot be identified at this time.
On Mon 05/12/2011 16:33:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120511-23337-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA800C1BE8A0, 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 which cannot be identified at this time.
On Mon 05/12/2011 16:28:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120511-21699-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1F3F1E)
Bugcheck code: 0xD1 (0x48CE000, 0xE, 0x8, 0x48CE000)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 258.96
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 258.96
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 258.96 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 28/10/2011 18:57:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-22105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F4DA)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003CE4B60, 0xFFFFF80000BA2740)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 27/03/2011 16:21:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032711-21762-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x24EC)
Bugcheck code: 0x50 (0xFFFFF880CB079065, 0x1, 0xFFFFF8800787FE4D, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: aswmonflt.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA
On Sat 26/03/2011 17:55:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032611-20841-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF800038E1610)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 04/02/2011 20:22:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020411-30700-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF0800EBA9070, 0x1, 0xFFFFF88001253F75, 0x7)
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 which cannot be identified at this time.
On Sat 29/01/2011 23:01:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013011-20763-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70710)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Wed 19/01/2011 21:17:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011911-27378-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC5 (0x75B5018, 0x2, 0x1, 0xFFFFF800039AE90D)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
37 crash dumps have been found and analyzed. Only 15 are included in this report. 3 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:
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 258.96 , NVIDIA Corporation)
unknown_module_00000000'00000002.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.
--------------------------------------------------------------------------------
computer name: ANGEFAMILY
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5300 @ 2.60GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294103040 total
VM: 2147352576, free: 1942941696
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 27/12/2011 17:57:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122711-23571-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAE01F)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880014AF01F, 0x0, 0x118)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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 Tue 27/12/2011 17:57:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAE01F)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880014AF01F, 0x0, 0x118)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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 Mon 26/12/2011 20:55:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122611-22776-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF880084E8E15, 0x1, 0xFFFFF80003C96E78, 0x0)
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 which cannot be identified at this time.
On Mon 26/12/2011 17:04:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122611-23571-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF3000ECDE6D0, 0x0, 0xFFFFF88001203C55, 0x7)
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 which cannot be identified at this time.
On Sun 25/12/2011 18:46:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122511-27253-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80003CA3AE8)
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 which cannot be identified at this time.
On Tue 20/12/2011 18:26:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122011-23259-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80003CB29D6, 0xFFFFF8800386E100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 13/12/2011 09:37:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121311-22495-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF10013B174C1, 0x1, 0xFFFFF80003CBDB55, 0x7)
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 which cannot be identified at this time.
On Mon 05/12/2011 16:33:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120511-23337-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA800C1BE8A0, 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 which cannot be identified at this time.
On Mon 05/12/2011 16:28:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120511-21699-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1F3F1E)
Bugcheck code: 0xD1 (0x48CE000, 0xE, 0x8, 0x48CE000)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 258.96
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 258.96
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 258.96 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 28/10/2011 18:57:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-22105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F4DA)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8003CE4B60, 0xFFFFF80000BA2740)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 27/03/2011 16:21:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032711-21762-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x24EC)
Bugcheck code: 0x50 (0xFFFFF880CB079065, 0x1, 0xFFFFF8800787FE4D, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: aswmonflt.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA
On Sat 26/03/2011 17:55:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032611-20841-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF800038E1610)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 04/02/2011 20:22:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020411-30700-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF0800EBA9070, 0x1, 0xFFFFF88001253F75, 0x7)
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 which cannot be identified at this time.
On Sat 29/01/2011 23:01:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013011-20763-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70710)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Wed 19/01/2011 21:17:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011911-27378-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC5 (0x75B5018, 0x2, 0x1, 0xFFFFF800039AE90D)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
37 crash dumps have been found and analyzed. Only 15 are included in this report. 3 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:
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 258.96 , NVIDIA Corporation)
unknown_module_00000000'00000002.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.
bon alors d'apres ce rapport, je vois que tu plantes assez souvent,
apparement, AVAST a un conflit , as tu un autre antivirus qu'avast ?
si non, alors je commencerais par désinstaller avast, et voir si ça plante encore.
Si ça plante plus c'était lui.
Le rapport pointe aussi un problème avec le driver de ta carte graphique,
downloade les derniers drivers nvidia, désinstalle l'ancien et installes le nouveau que tu as downloadé.
ensuite je conseille un nettoyage de la base de registre avec Ccleaner ...
toujours efficace.
https://www.commentcamarche.net/telecharger/utilitaires/5647-ccleaner/
apparement, AVAST a un conflit , as tu un autre antivirus qu'avast ?
si non, alors je commencerais par désinstaller avast, et voir si ça plante encore.
Si ça plante plus c'était lui.
Le rapport pointe aussi un problème avec le driver de ta carte graphique,
downloade les derniers drivers nvidia, désinstalle l'ancien et installes le nouveau que tu as downloadé.
ensuite je conseille un nettoyage de la base de registre avec Ccleaner ...
toujours efficace.
https://www.commentcamarche.net/telecharger/utilitaires/5647-ccleaner/
