Blue Screen de la mort - intermittent...
beton04f
Messages postés
47
Statut
Membre
-
beton04f Messages postés 47 Statut Membre -
beton04f Messages postés 47 Statut Membre -
Bonjour à tous,
Je suis sur Windows 7 Pro 64bit.
Je subit, depuis 2 mois environ, des blues screens de la mort de manière intermittente, les derniers en date :
25/09/2011 04:15:10 GMT
24/09/2011 20:50:35 GMT
15/09/2011 22:23:36 GMT
03/09/2011 11:05:19 GMT
03/09/2011 10:43:02 GMT
03/09/2011 09:31:20 GMT
02/09/2011 21:39:23 GMT
29/08/2011 15:43:31 GMT
17/08/2011 12:17:29 GMT
16/08/2011 14:51:31 GMT
27/07/2011 18:51:12 GMT
10/07/2011 11:32:54 GMT
Donc c'est très aléatoire, et j'avoue ne pas savoir quoi faire...
Si vous avez une idée de où chercher, je suis preneur !
Bon dimanche à tous !
Je suis sur Windows 7 Pro 64bit.
Je subit, depuis 2 mois environ, des blues screens de la mort de manière intermittente, les derniers en date :
25/09/2011 04:15:10 GMT
24/09/2011 20:50:35 GMT
15/09/2011 22:23:36 GMT
03/09/2011 11:05:19 GMT
03/09/2011 10:43:02 GMT
03/09/2011 09:31:20 GMT
02/09/2011 21:39:23 GMT
29/08/2011 15:43:31 GMT
17/08/2011 12:17:29 GMT
16/08/2011 14:51:31 GMT
27/07/2011 18:51:12 GMT
10/07/2011 11:32:54 GMT
Donc c'est très aléatoire, et j'avoue ne pas savoir quoi faire...
Si vous avez une idée de où chercher, je suis preneur !
Bon dimanche à tous !
A voir également:
- Blue Screen de la mort - intermittent...
- Blue screen - Guide
- Screen whatsapp - Accueil - Messagerie instantanée
- Blue griffon - Télécharger - HTML
- Apowersoft screen recorder - Télécharger - Capture d'écran
- Double screen pc - Guide
13 réponses
tu as accès au bureau malgré ces blue screen?
installe Whocrashed exécute le et poste le rapport.
on devrait pouvoir t'aider un peu mieux après ça.
installe Whocrashed exécute le et poste le rapport.
on devrait pouvoir t'aider un peu mieux après ça.
Bonjour,
je ne suis pas experte en ordi mais j'ai un peu d'expérience.
Les écrans bleus sont liés a pas mal de problème du style carte mère en souffrance, ventilos trop poussièreux ou un petit virus qui s'intalle.
alors un petit nettoyage, et un scan anti virus ca peut aider..
Pour ma part le dernier en date c'était du à trop de poussière dans l'ordi.
ensuite il y a d'autre causes plus poussés mais là cela dépasse mes compétences !!
En espérant avoir pu t'aider
je ne suis pas experte en ordi mais j'ai un peu d'expérience.
Les écrans bleus sont liés a pas mal de problème du style carte mère en souffrance, ventilos trop poussièreux ou un petit virus qui s'intalle.
alors un petit nettoyage, et un scan anti virus ca peut aider..
Pour ma part le dernier en date c'était du à trop de poussière dans l'ordi.
ensuite il y a d'autre causes plus poussés mais là cela dépasse mes compétences !!
En espérant avoir pu t'aider
@piloutie :
Effectivement, le Blue Screen peut être provoqué par un problème matériel dû à un manque d'entretien (surchauffe). Ce n'est pas, à priori, mon cas. La machine est récente et propre.
Elle semble exempte de virus. Je fais un scan chaque nuit.
Merci.
@Eclipse :
Après le BlueScreen, la machine redémarre ou je la redémarre de force.
Elle plante ensuite à nouveau, au choix :) : 1h, 1 jour ou 1 semaine après, c'est très variable.
Je colle, à la fin du message le rapport WhoCrashed.
Merci beaucoup pour ton aide, j'avoue ne pas savoir quoi faire (à part taper !, mais ça solutionne rarement les problèmes informatiques).
Bonne journée.
---------------
System Information (local)
--------------------------------------------------------------------------------
computer name: REMI-ASUS
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8580521984 total
VM: 2147352576, free: 1945378816
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 25/09/2011 04:15:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092511-12714-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88005EA3B28, 0xFFFFF88005EA3380, 0xFFFFF88001319185)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 24/09/2011 20:50:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-14227-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFE900C064CAC8, 0x0, 0xFFFFF96000144BD4, 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 Thu 15/09/2011 22:23:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091611-14539-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D79910, 0xFFFF, 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 which cannot be identified at this time.
On Sat 03/09/2011 11:05:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-11278-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF68000086E00, 0x0, 0x0, 0xFFFFF80002E7C27B)
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 Sat 03/09/2011 10:43:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-12370-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D795E0, 0xFFFF, 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 which cannot be identified at this time.
On Sat 03/09/2011 09:31:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-13135-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D795E0, 0xFFFF, 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 which cannot be identified at this time.
On Fri 02/09/2011 21:39:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090211-14289-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF68000073F00, 0x0, 0x0, 0xFFFFF80002E7E27B)
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 Mon 29/08/2011 15:43:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082911-14820-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFEA8008C1BDCB, 0x1, 0xFFFFF80002EDAF93, 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 Wed 17/08/2011 12:17:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081711-14570-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF708401CBB98, 0x1, 0xFFFFF80002F08924, 0x5)
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 Tue 16/08/2011 14:51:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081611-20358-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D795E0, 0xFFFF, 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 which cannot be identified at this time.
On Wed 27/07/2011 18:51:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072711-16770-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFFAE001252C3B, 0x0, 0xFFFFF80002EB6675, 0x5)
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 10/07/2011 11:32:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071011-16848-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D79610, 0xFFFF, 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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed.
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.
Effectivement, le Blue Screen peut être provoqué par un problème matériel dû à un manque d'entretien (surchauffe). Ce n'est pas, à priori, mon cas. La machine est récente et propre.
Elle semble exempte de virus. Je fais un scan chaque nuit.
Merci.
@Eclipse :
Après le BlueScreen, la machine redémarre ou je la redémarre de force.
Elle plante ensuite à nouveau, au choix :) : 1h, 1 jour ou 1 semaine après, c'est très variable.
Je colle, à la fin du message le rapport WhoCrashed.
Merci beaucoup pour ton aide, j'avoue ne pas savoir quoi faire (à part taper !, mais ça solutionne rarement les problèmes informatiques).
Bonne journée.
---------------
System Information (local)
--------------------------------------------------------------------------------
computer name: REMI-ASUS
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8580521984 total
VM: 2147352576, free: 1945378816
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 25/09/2011 04:15:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092511-12714-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88005EA3B28, 0xFFFFF88005EA3380, 0xFFFFF88001319185)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 24/09/2011 20:50:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-14227-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFE900C064CAC8, 0x0, 0xFFFFF96000144BD4, 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 Thu 15/09/2011 22:23:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091611-14539-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D79910, 0xFFFF, 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 which cannot be identified at this time.
On Sat 03/09/2011 11:05:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-11278-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF68000086E00, 0x0, 0x0, 0xFFFFF80002E7C27B)
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 Sat 03/09/2011 10:43:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-12370-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D795E0, 0xFFFF, 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 which cannot be identified at this time.
On Sat 03/09/2011 09:31:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090311-13135-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D795E0, 0xFFFF, 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 which cannot be identified at this time.
On Fri 02/09/2011 21:39:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090211-14289-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFF68000073F00, 0x0, 0x0, 0xFFFFF80002E7E27B)
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 Mon 29/08/2011 15:43:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082911-14820-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFEA8008C1BDCB, 0x1, 0xFFFFF80002EDAF93, 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 Wed 17/08/2011 12:17:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081711-14570-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF708401CBB98, 0x1, 0xFFFFF80002F08924, 0x5)
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 Tue 16/08/2011 14:51:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081611-20358-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D795E0, 0xFFFF, 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 which cannot be identified at this time.
On Wed 27/07/2011 18:51:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072711-16770-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFFAE001252C3B, 0x0, 0xFFFFF80002EB6675, 0x5)
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 10/07/2011 11:32:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071011-16848-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003D79610, 0xFFFF, 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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed.
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.
1) Mets a jour tes drivers dans un premier temps.
2) Quel est ton antivirus? et essaie un scan en ligne.
3) ensuite il est possible que ça soit une infection par un vers. probleme connu sous xp. ( oui tu es sous w7 je sais ) mais ça reste une piste.
je te propose de lire ces 2 post, qui traitent d'un probleme très proche.
en espérant que ça règle ton probleme.
https://forums.commentcamarche.net/forum/affich-1436446-c-windows-system32-ntoskrnl-exe-help
https://www.clubic.com/forum/t/ntoskrnl-exe-manquant/334594
2) Quel est ton antivirus? et essaie un scan en ligne.
3) ensuite il est possible que ça soit une infection par un vers. probleme connu sous xp. ( oui tu es sous w7 je sais ) mais ça reste une piste.
je te propose de lire ces 2 post, qui traitent d'un probleme très proche.
en espérant que ça règle ton probleme.
https://forums.commentcamarche.net/forum/affich-1436446-c-windows-system32-ntoskrnl-exe-help
https://www.clubic.com/forum/t/ntoskrnl-exe-manquant/334594
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
1) J'ai mis à jour les drivers la semaine dernière (CarteGraphique, Ecrans, Son, carte mère...) avec les dernières versions disponibles.
2) Avira Antivir - Je viens de faire un scan en ligne avec HouseCall de TrendMicro qui ne détecte rien de spécial
3)
Les 2 posts traitent du fichier défectueux ntoskrnl.exe. Ce n'est pas mon cas, le fichier est bon (même s'il est à l'origine de certains blue screens). Le plantage n'intervient que de temps en temps, après le redémarrage, tout fonctionne.
Merci pour ton aide.
2) Avira Antivir - Je viens de faire un scan en ligne avec HouseCall de TrendMicro qui ne détecte rien de spécial
3)
Les 2 posts traitent du fichier défectueux ntoskrnl.exe. Ce n'est pas mon cas, le fichier est bon (même s'il est à l'origine de certains blue screens). Le plantage n'intervient que de temps en temps, après le redémarrage, tout fonctionne.
Merci pour ton aide.
le fichier "ntoskrnl.exe " est a l'origine de quasi tout tes blue screen
connus pour être un vers sous xp dans certain cas.
après je te recommande plutot d'essayer un scan en ligne via Bit Defender
sinon essayes ces antispyware Ad Aware et Malwarebytes
connus pour être un vers sous xp dans certain cas.
après je te recommande plutot d'essayer un scan en ligne via Bit Defender
sinon essayes ces antispyware Ad Aware et Malwarebytes
Je fais une analyse avec les 3 outils que tu m'indiques, je te dirai le résultat.
Tu me conseilles donc, par sécurité, de supprimer et remplacer ntoskrnl.exe par une version reprise du CD d'installation afin d'être certain de ne pas avoir une verson infectée ?
Tu me conseilles donc, par sécurité, de supprimer et remplacer ntoskrnl.exe par une version reprise du CD d'installation afin d'être certain de ne pas avoir une verson infectée ?
Salut à tous,
Un nouveau blue-screen aujourd'hui !
Si quelqu'un peu m'aiguiller... !!
Je vais le jeter :)
Un nouveau blue-screen aujourd'hui !
Si quelqu'un peu m'aiguiller... !!
Je vais le jeter :)
essayes cette procédure:
https://support.microsoft.com/fr-fr/help/927392/use-bootrec-exe-in-the-windows-re-to-troubleshoot-startup-issues
ou celle ci
https://www.thesiteoueb.net/faq-astuces/fiche-pratique-709-comment-reparer-le-demarrage-de-windows-7.html
( c'est les même au choix)
https://support.microsoft.com/fr-fr/help/927392/use-bootrec-exe-in-the-windows-re-to-troubleshoot-startup-issues
ou celle ci
https://www.thesiteoueb.net/faq-astuces/fiche-pratique-709-comment-reparer-le-demarrage-de-windows-7.html
( c'est les même au choix)
J'ai envoyé un coup de memtest.exe qui m'a signaler des erreurs sur 2 barrettes mémoires installées juste avant le début des problèmes.
Je viens de les changer.
Espérant que ça résolve le chimilblique
Je viens de les changer.
Espérant que ça résolve le chimilblique
