Ecran bleu intempestif...
damiengevrais2001
Messages postés
207
Statut
Membre
-
damiengevrais2001 Messages postés 207 Statut Membre -
damiengevrais2001 Messages postés 207 Statut Membre -
Bonjour à tous,
Voila depuis quelques temps j'ai un blue screen intempestif qui apparait plusieurs fois par jour au bout d'environ 5 minutes apres avoir démarré mon ordinateur. J'ai utilisé le logiciel "Anticrash", il n'a rien trouvé. J'ai utilisé le logiciel BluescreenView, j'ai tous les messages d'erreurs qui sont affichés.
Je suis désespéré, j'ai besoin d'aide .
Merci d'avance.
Cordialement
PS : Voici ma config
Windows 7x64 édition familliale premium SP1
Processeur 2.10 G, RAM 4G
Voila depuis quelques temps j'ai un blue screen intempestif qui apparait plusieurs fois par jour au bout d'environ 5 minutes apres avoir démarré mon ordinateur. J'ai utilisé le logiciel "Anticrash", il n'a rien trouvé. J'ai utilisé le logiciel BluescreenView, j'ai tous les messages d'erreurs qui sont affichés.
Je suis désespéré, j'ai besoin d'aide .
Merci d'avance.
Cordialement
PS : Voici ma config
Windows 7x64 édition familliale premium SP1
Processeur 2.10 G, RAM 4G
A voir également:
- Ecran bleu intempestif...
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Ecran bleu windows 10 - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
9 réponses
Hello,
Installe WhoCrashed
Clic sur analyse et copie colle ici le rapport, on va voir ce qu'on peut faire.
Cordialement
Installe WhoCrashed
Clic sur analyse et copie colle ici le rapport, on va voir ce qu'on peut faire.
Cordialement
Voici le rapport et merci de bien vouloir essayer de m'aider
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 21/01/2014 20:42:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012214-23852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
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 that cannot be identified at this time.
On Tue 21/01/2014 20:42:12 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/01/2014 20:29:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-19749-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80002AF194A, 0x0, 0x58000000000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/01/2014 20:25:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-22542-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0xA, 0x1, 0xFFFFF80002A6CF03)
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 21/01/2014 20:20:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-20170-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80002AA02F5, 0x2, 0xFFFFFA8003D5AA00)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/01/2014 19:47:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-24039-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x44 (0xFFFFFA80040EB4D0, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/01/2014 13:37:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-26332-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF96000171EC7)
Bugcheck code: 0x50 (0xFFFFFFFFC033F31E, 0x1, 0xFFFFF96000171EC7, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 21/01/2014 13:16:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-29234-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880093A1AB8, 0xFFFFF880093A1310, 0xFFFFF8800142701D)
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 that cannot be identified at this time.
On Tue 21/01/2014 10:00:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-42479-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DE6AA7, 0xFFFFF88009C10060, 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 that cannot be identified at this time.
On Tue 21/01/2014 09:50:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-37752-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF80002AB22A0)
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 that cannot be identified at this time.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 21/01/2014 20:42:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012214-23852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
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 that cannot be identified at this time.
On Tue 21/01/2014 20:42:12 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/01/2014 20:29:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-19749-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80002AF194A, 0x0, 0x58000000000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/01/2014 20:25:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-22542-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0xA, 0x1, 0xFFFFF80002A6CF03)
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 21/01/2014 20:20:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-20170-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80002AA02F5, 0x2, 0xFFFFFA8003D5AA00)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/01/2014 19:47:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-24039-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x44 (0xFFFFFA80040EB4D0, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 21/01/2014 13:37:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-26332-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF96000171EC7)
Bugcheck code: 0x50 (0xFFFFFFFFC033F31E, 0x1, 0xFFFFF96000171EC7, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 21/01/2014 13:16:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-29234-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880093A1AB8, 0xFFFFF880093A1310, 0xFFFFF8800142701D)
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 that cannot be identified at this time.
On Tue 21/01/2014 10:00:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-42479-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DE6AA7, 0xFFFFF88009C10060, 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 that cannot be identified at this time.
On Tue 21/01/2014 09:50:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-37752-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF80002AB22A0)
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 that cannot be identified at this time.
Tu as l'air d'avoir de graves problèmes de drivers, sont-ils à jour ? Tu en as installé un récemment avant que ça commence à crasher ?
justement il me semble que tout est à jour, car quand je vais dans le gestionnaire de périphérique, j'ai fait un par un pour mettre à jour, et ils était tous à jour.
Mais si j'utilise par exemple un logiciel pour trouver les mise à jour de drivers, il m'en trouve plusieurs.
Je ne comprend pas trop
Mais si j'utilise par exemple un logiciel pour trouver les mise à jour de drivers, il m'en trouve plusieurs.
Je ne comprend pas trop
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Quel est le nom de ce logiciel ? Il y a certains de ces soft qui te téléchargent de mauvais drivers, ou venant de mauvais sites, et ça te créer ce genre d'érreures.
Si tu as du temps, les meilleurs drivers se trouvent sur les site constructeur.
Si tu n'en a pas, vas sur https://www.touslesdrivers.com/?v_page=29
Installe le plugin, fais la détection, puis télécharge et installe les drivers.
Si tu as du temps, les meilleurs drivers se trouvent sur les site constructeur.
Si tu n'en a pas, vas sur https://www.touslesdrivers.com/?v_page=29
Installe le plugin, fais la détection, puis télécharge et installe les drivers.
Bien vu EGP-Swyx
Tu le trouveras ici :
https://www.commentcamarche.net/telecharger/utilitaires/14733-memtest86/
Tu as ici la fiche pour les tutos :
https://www.commentcamarche.net/informatique/composants/1437-tester-la-memoire-vive-ram-d-un-ordinateur-avec-memtest86/#tester-depuis-une-cle-usb
Tu le trouveras ici :
https://www.commentcamarche.net/telecharger/utilitaires/14733-memtest86/
Tu as ici la fiche pour les tutos :
https://www.commentcamarche.net/informatique/composants/1437-tester-la-memoire-vive-ram-d-un-ordinateur-avec-memtest86/#tester-depuis-une-cle-usb
oui. sinon en mode super basique. tu télécharges UNETBOOTIN et dans l'onglet "distribution" il doit y avoir "ultimate boot CD" . Unetbootin télécharge, installe et rend bootable la clef. bien utile ce soft.
@thrallcss : Merci pour le coup de chapeau =). mais il est aussi probable qu'un pilote soit à l'origine du souci. alors à tester en 2e option
@thrallcss : Merci pour le coup de chapeau =). mais il est aussi probable qu'un pilote soit à l'origine du souci. alors à tester en 2e option
Merci à vous,
Je vais essayer tout ca en début d'après midi et je vous donne mes resultat.
En ce qui concerne les MAJ des pilotes sur le site de Toshiba, les dernières mise a jour date de 2010 maximum... Pas très au point
A tout à l'heure.
Cordialement
PS : en mode sans echec aucun écran bleu depuis 1 jour
Je vais essayer tout ca en début d'après midi et je vous donne mes resultat.
En ce qui concerne les MAJ des pilotes sur le site de Toshiba, les dernières mise a jour date de 2010 maximum... Pas très au point
A tout à l'heure.
Cordialement
PS : en mode sans echec aucun écran bleu depuis 1 jour
Voila je viens de faire le test avec testmem86. 0 erreurs trouvés. Donc les barrettes fonctionne bien? Pour la recherche de pilotes, j'ai utilisé PC Health Advisor.
