Ecran bleu au démarrage de Windows 7 Fermé

Question

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	dcmdpst.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
tkrnlpa.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
tkrnlpa.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 !



Configuration: Windows 7 / Firefox 15.0.1

Pokemoon · Accepted Answer

Le problème c'est que je n'est pas de point de restauration... J'en avait déjà fait pourtant ... :/

Gi_Joe · Answer

Demarre en mode sans echec et fait une réstauration systeme a la derniere date ou ton pc fonctionner correctement

Gi_Joe · Answer

Meme pas a il y a un mois ?
Entre une date et lance, tu vera bien

Pokemoon · Answer

Je suis en mode sans échec actuellement, mais chuis un peux perdu dans le panneau de config

Gi_Joe · Answer

Vas dans le menu démarrer, fonction recherche tu tape : restauration du systeme

tu le lance , et tu selectionne une date.

Sa devrait le faire ;)

Pokemoon · Answer

Non aucun point trouver :(

Gi_Joe · Answer

Trés bien, vitesse supérieure.

Supprime Avast antivirus, et redemarre en mode normal

Pokemoon · Answer

Ok je le fais de suite ;)

Pokemoon · Answer

Toujours pareil....

Pokemoon · Answer

J'ai fais une nouvelle 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: 1987231744



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 15/09/2012 23:10:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-26473-01.dmp
This was probably caused by the following module: tdcmdpst.sys (tdcmdpst+0x973) 
Bugcheck code: 0xC9 (0x23E, 0xFFFFFFFF8FA272E2, 0xFFFFFFFF828E8EB8, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION 
file path: C:\Windows\system32\drivers	dcmdpst.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 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	dcmdpst.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
tkrnlpa.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
tkrnlpa.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
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 . 
Google query: aswsnx.sys 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
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 . 
Google query: aswsnx.sys 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
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 . 
Google query: aswsnx.sys CRITICAL_OBJECT_TERMINATION





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 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: 

tdcmdpst.sys (Toshiba ODD Writing Driver For x86., TOSHIBA Corporation.)

aswsnx.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.

Gi_Joe · Answer

Lance windows Update et regarde si tu as des mises a jours a faire

Pokemoon · Answer

Wndows update se lance pas Oo

Pokemoon · Answer

J'ai pas de service pack installer sinon

Gi_Joe · Answer

Essaye Menu démarrer / Ordinateur clique droit propriété / gestionnaire des périphériques.

Dis moi si tu as un point dexclamation jaune ?

Pokemoon · Answer

Non

Gi_Joe · Answer

Essai de taper tdcmdpst.sys dans la recherche, si tu trouve un resultat, supprime le fichier.
Et fait de même avec
aswsnx.sys

Gi_Joe · Answer

Juste au cas ou, coupe le PC , retire la batterie, appuis 30 secondes sur le bouton dallumage et laisse le debbrancher tout la nuit ^^

Pokemoon · Answer

Ca fait quoi ? lol

Pokemoon · Answer

Ps : Bonne nuit

Pokemoon · Answer

Toujours un écran bleu ....

Pokemoon · Answer

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 ><

Pokemoon · Answer

J'ai pas vraiment compris ^^'

Pokemoon · Answer

Je tente d'installer les derniers drivers de mon pc (carte mère et autres)
Et aussi le SP1 pour Windows 7.

Gi_Joe · Answer

Si t'y arrive je pense que ton probleme sera résolu

Pokemoon · Answer

Une erreur s'est produite en installant SP1, y'avait marquer qu'il manquer un fichier mais je sais plus lequel

Pokemoon · Answer

Up !

Cléclé · Answer

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

Pokemoon · Answer

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

Pokemoon · Answer

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

Pokemoon · Answer

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.

Pokemoon · Answer

Mais ca fonctionne toujours en mode sans échec

salima · Answer

bonsoir 

http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/

Pokemoon · Answer

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 ?

Ch93 · Answer

Quand tu redémarres en appuyant F8 essaie de choisir "Dernière bonne configuration connue..." plutôt que le mode sans échec.

Ch93 · Answer

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 !

Pokemoon · Answer

Salut, j'ai remarquer que y'a un point d'exclamation jaune sur lecteur de CD/DVDROM

Pokemoon · Answer

Petite question : par moment le pc fait des genre de "bip" mais je sais pas d'ou il viennent ... :/

Ch93 · Answer

Si ton PC émet des bips c'est qu'il y a un soucis au niveau matériel probablement...

Pokemoon · Answer

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

Pokemoon · Answer

Up !!

Pokemoon · Answer

Voila ce que j'obtiens comme écran bleu :





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: ntkrnlpa.exe

CRITICAL_OBJECT_TERMINATION

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: 0x000000f4 (0x00000003, 0x9c1a3560, 0x9c1a36cc, 0x83031200)

*** ntkrnlpa.exe - Address 0x82ee4e64 base at 0x82e08000 DateStamp 0x4f5585

Pokemoon · Answer

AH oui et depuis que le pc fait écran bleu l'option "Protection du système" à disparu 



http://static.commentcamarche.net/www.commentcamarche.net/faq/images/0-91Yn0wx7-restor-s-.png



(Moi il n'y a que 4 onglets au lieu de 5 comme sur l'image)

Pokemoon · Answer

Sinon j'ai une autre question :

Pourquoi je n'ai pas accès a la protection du système et a Windows Update ?

Sachant que le pc ne trouve aucuns points de restauration alors que j'en avait fait plusiuers et que "NORMALEMENT" le dernier point est indestructible pour des raisons de sécurité ????

Pokemoon · Answer

Merci a tous pour votre aide ....

Mais je trouve bizzare c'est que quand je laisse le pc démmarer tout seul, il se "bloque" sur les 4 fenêtres de couleurs (le logo windows) et je suis obligé de l'éteindre en appuyant UNE fois sur le bouton d'alimentation. Et quand je lance la dernière bonne configuration connue (via F8 au démarrage) la il me fait un écran bleu. J'ai essayé la réparation automatique mais le pc ne trouve aucun problème...

Sachant qu'en mode sans echec je n'est pas accès a l'option "Protection du système" et donc pas accès a mes points de restaurations ...

Pokemoon · Answer

L'indice de performance est de 3,9 et il doit être actualisé, or, il est grisé et je ne peux pas cliquer dessus ...

Pokemoon · Answer

Je pense l'emmener chez un spécialiste ... 

Je suis assez soulager car j'ai lus sur ce site que si l'ordinateur fait des "bips" c'est presque sûr que ce sois un problème matériel, or le mien (pour je ne sais quelle raison) ne fait plus de bips ^^

Pokemoon · Answer

Bon et bien cet ordinateur est trèèèèèès bizarre :/ 

Ca fait 3 jours qu'il démarre correctement alors que j'ai rien fais dessus ^^'
Je note cependant que tout mes fichiers sont toujours la mais que je n'ai plus aucunes mise a jours d'installer (j'en avait fais avant le bug) et aussi que le pc est devenu très lent ...

Bune · Answer

Jai exactement le meme probleme ! Comment tu fais pour aller sur le bureau en mode sans echec ? Moi sa lance direct startup repair je ne peu pas aller sur le bureau :( peut tu me dire comment aller sur le bureau stp ?

Bune · Answer

Les Toshiba font des "BIPS" Car ils n'ont presque plus de batterie ou parcequ'il ne charge pas correctement.

Ecran bleu au démarrage de Windows 7

49 réponses

Discussions similaires