Ecran bleu au démarrage de Windows 7
Pokemoon
Messages postés
64
Date d'inscription
Statut
Membre
Dernière intervention
-
Bune -
Bune -
Bonjour, ça fait 2 jours que mon pc (un Toshiba portable) m'affiche un écran bleu juste après le chargement du logo Windows puis redémarre..
Mais je peux tout de même accéder a mon bureau grâce au mode sans échec.
J'ai fais une analyse avec le logiciel "WhoCrashed", je vous donne l'analyse :
System Information (local)
--------------------------------------------------------------------------------
computer name: BROTHERS-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3219578880 total
VM: 2147352576, free: 1988894720
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 15/09/2012 21:14:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-26676-01.dmp
This was probably caused by the following module: tdcmdpst.sys (tdcmdpst+0x973)
Bugcheck code: 0xC9 (0x23E, 0xFFFFFFFF900092E2, 0xFFFFFFFFA0F68EB8, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\tdcmdpst.sys
company: TOSHIBA Corporation.
description: Toshiba ODD Writing Driver For x86.
Bug check description: This is the bug check code for all Driver Verifier
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: tdcmdpst.sys (Toshiba ODD Writing Driver For x86., TOSHIBA Corporation.).
Google query: tdcmdpst.sys TOSHIBA Corporation. DRIVER_VERIFIER_IOMANAGER_VIOLATION
On Sat 15/09/2012 20:54:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-18969-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE64)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF870D5920, 0xFFFFFFFF870D5A8C, 0xFFFFFFFF8307B200)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 15/09/2012 11:49:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-17284-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE64)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF89602A50, 0xFFFFFFFF89602BBC, 0xFFFFFFFF8307D200)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 15/09/2012 11:43:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-17752-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x17789)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF896AE030, 0xFFFFFFFF896AE19C, 0xFFFFFFFF83067200)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software CRITICAL_OBJECT_TERMINATION
On Sat 15/09/2012 11:28:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-18798-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x17789)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF89662600, 0xFFFFFFFF8966276C, 0xFFFFFFFF83036200)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software CRITICAL_OBJECT_TERMINATION
On Sat 15/09/2012 07:55:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-25256-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x17789)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8A27CD40, 0xFFFFFFFF8A27CEAC, 0xFFFFFFFF83061200)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software CRITICAL_OBJECT_TERMINATION
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. 2 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:
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
tdcmdpst.sys (Toshiba ODD Writing Driver For x86., TOSHIBA Corporation.)
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.
Pouvez vous m'aider a corriger ce problème d'écran bleu ? Merci d'avance !
Mais je peux tout de même accéder a mon bureau grâce au mode sans échec.
J'ai fais une analyse avec le logiciel "WhoCrashed", je vous donne l'analyse :
System Information (local)
--------------------------------------------------------------------------------
computer name: BROTHERS-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3219578880 total
VM: 2147352576, free: 1988894720
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 15/09/2012 21:14:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-26676-01.dmp
This was probably caused by the following module: tdcmdpst.sys (tdcmdpst+0x973)
Bugcheck code: 0xC9 (0x23E, 0xFFFFFFFF900092E2, 0xFFFFFFFFA0F68EB8, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\tdcmdpst.sys
company: TOSHIBA Corporation.
description: Toshiba ODD Writing Driver For x86.
Bug check description: This is the bug check code for all Driver Verifier
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: tdcmdpst.sys (Toshiba ODD Writing Driver For x86., TOSHIBA Corporation.).
Google query: tdcmdpst.sys TOSHIBA Corporation. DRIVER_VERIFIER_IOMANAGER_VIOLATION
On Sat 15/09/2012 20:54:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-18969-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE64)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF870D5920, 0xFFFFFFFF870D5A8C, 0xFFFFFFFF8307B200)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 15/09/2012 11:49:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-17284-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE64)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF89602A50, 0xFFFFFFFF89602BBC, 0xFFFFFFFF8307D200)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 15/09/2012 11:43:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-17752-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x17789)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF896AE030, 0xFFFFFFFF896AE19C, 0xFFFFFFFF83067200)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software CRITICAL_OBJECT_TERMINATION
On Sat 15/09/2012 11:28:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-18798-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x17789)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF89662600, 0xFFFFFFFF8966276C, 0xFFFFFFFF83036200)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software CRITICAL_OBJECT_TERMINATION
On Sat 15/09/2012 07:55:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-25256-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x17789)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8A27CD40, 0xFFFFFFFF8A27CEAC, 0xFFFFFFFF83061200)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software CRITICAL_OBJECT_TERMINATION
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. 2 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:
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
tdcmdpst.sys (Toshiba ODD Writing Driver For x86., TOSHIBA Corporation.)
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.
Pouvez vous m'aider a corriger ce problème d'écran bleu ? Merci d'avance !
A voir également:
- Ecran bleu au démarrage de Windows 7
- Supprimer rond bleu whatsapp - Guide
- Photofiltre 7 - Télécharger - Retouche d'image
- Ordinateur lent au démarrage - Guide
- Clé windows 7 - Guide
- Reinitialiser pc au demarrage - Guide
49 réponses
Quand je clic sur Windows update ca ne fait rien... Je peux même pas vérifier si j'ai des mises a jours a faire ><
Je tente d'installer les derniers drivers de mon pc (carte mère et autres)
Et aussi le SP1 pour Windows 7.
Et aussi le SP1 pour Windows 7.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Une erreur s'est produite en installant SP1, y'avait marquer qu'il manquer un fichier mais je sais plus lequel
Salut
Désactive tout les programmes au démarrage avec Ccleaner et fait un scan complais avec Malwarebit, fait bien les mises a jours de définition avant de lancé le scan.
Puis test
Désactive tout les programmes au démarrage avec Ccleaner et fait un scan complais avec Malwarebit, fait bien les mises a jours de définition avant de lancé le scan.
Puis test
Voila ce qu'il y a marquer sur l'écran bleu : (Réaliser avec le logiciel BlueScreenView)
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: dtsoftbus01.sys
DRIVER_VERIFIER_IOMANAGER_VIOLATION
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x000000c9 (0x0000023e, 0x857a22e2, 0xa725eeb8, 0x00000000)
*** dtsoftbus01.sys - Address 0x857a22e2 base at 0x857a1000 DateStamp 0x4f103595
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
The problem seems to be caused by the following file: dtsoftbus01.sys
DRIVER_VERIFIER_IOMANAGER_VIOLATION
If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Technical Information:
*** STOP: 0x000000c9 (0x0000023e, 0x857a22e2, 0xa725eeb8, 0x00000000)
*** dtsoftbus01.sys - Address 0x857a22e2 base at 0x857a1000 DateStamp 0x4f103595
D'après "BlueScreenView" voici la liste des fichiers qui ont provoquer mon écran bleu lors de mon DERNIER essaie :
cdrom.sys
dtsoftbus01.sys (ce fichier vient du logiciel Daemon Tools, toujours d'après BlueScreenView)
ntoskrnl.exe
PxHelp20.sys
tdcmdpst.sys
Wdf01000.sys
cdrom.sys
dtsoftbus01.sys (ce fichier vient du logiciel Daemon Tools, toujours d'après BlueScreenView)
ntoskrnl.exe
PxHelp20.sys
tdcmdpst.sys
Wdf01000.sys
Bon, j'ai bidouiller pas mal de choses et maintenant quand je lance l'ordi normalement il se bloque au chargement de windows (sur le logo) puis pour l'éteindre je dois appuyer UNE seule fois sur le bouton power ... bizarre..
Si j'essaye de démarrer avec la dernière bonne configuration connue ca me met un écran bleu.
Si j'essaye de démarrer avec la dernière bonne configuration connue ca me met un écran bleu.
bonsoir
http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
Je viens de remarquer que dans les "Propriétés système" l'onglet "Protection du système" à disparu... Peut être à cause du mode sans échec ?
Quand tu redémarres en appuyant F8 essaie de choisir "Dernière bonne configuration connue..." plutôt que le mode sans échec.
C'est bien W7 ?
Ouvre l'invite de commande en mode administrateur, puis tape CHKDSK /F
Réponds O pour Oui et redémarre ton PC sans rien toucher ou appuyer et laisse faire !
Ouvre l'invite de commande en mode administrateur, puis tape CHKDSK /F
Réponds O pour Oui et redémarre ton PC sans rien toucher ou appuyer et laisse faire !
J'ai aussi un autre problème : je ne peux absolument pas accéder a Windows Update, quand je clique dessus ya un chargement mais rien ne se passe