Ecran bleu au démarrage de Windows 7
Fermé
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
-
16 sept. 2012 à 00:51
Bune - 22 sept. 2013 à 12:57
Bune - 22 sept. 2013 à 12:57
A voir également:
- Ecran bleu au démarrage de Windows 7
- Pc lent au démarrage - Guide
- Reinitialiser pc au demarrage - Guide
- Programme au démarrage windows 10 - Guide
- Problème de demarrage windows 10 - Guide
- Double ecran - Guide
49 réponses
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 00:57
16 sept. 2012 à 00:57
Le problème c'est que je n'est pas de point de restauration... J'en avait déjà fait pourtant ... :/
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 00:57
16 sept. 2012 à 00:57
Meme pas a il y a un mois ?
Entre une date et lance, tu vera bien
Entre une date et lance, tu vera bien
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 00:59
16 sept. 2012 à 00:59
Je suis en mode sans échec actuellement, mais chuis un peux perdu dans le panneau de config
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 01:02
16 sept. 2012 à 01:02
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 ;)
tu le lance , et tu selectionne une date.
Sa devrait le faire ;)
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 01:15
16 sept. 2012 à 01:15
Lance windows Update et regarde si tu as des mises a jours a faire
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 00:54
16 sept. 2012 à 00:54
Demarre en mode sans echec et fait une réstauration systeme a la derniere date ou ton pc fonctionner correctement
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:04
16 sept. 2012 à 01:04
Non aucun point trouver :(
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 01:06
16 sept. 2012 à 01:06
Trés bien, vitesse supérieure.
Supprime Avast antivirus, et redemarre en mode normal
Supprime Avast antivirus, et redemarre en mode normal
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:08
16 sept. 2012 à 01:08
Ok je le fais de suite ;)
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:13
16 sept. 2012 à 01:13
Toujours pareil....
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:13
16 sept. 2012 à 01:13
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\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 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
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.
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\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 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
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.
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:17
16 sept. 2012 à 01:17
Wndows update se lance pas Oo
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:18
16 sept. 2012 à 01:18
J'ai pas de service pack installer sinon
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 01:21
16 sept. 2012 à 01:21
Essaye Menu démarrer / Ordinateur clique droit propriété / gestionnaire des périphériques.
Dis moi si tu as un point dexclamation jaune ?
Dis moi si tu as un point dexclamation jaune ?
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:23
16 sept. 2012 à 01:23
Non
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 01:25
16 sept. 2012 à 01:25
Essai de taper tdcmdpst.sys dans la recherche, si tu trouve un resultat, supprime le fichier.
Et fait de même avec
aswsnx.sys
Et fait de même avec
aswsnx.sys
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 01:25
16 sept. 2012 à 01:25
puis redemarre
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:27
16 sept. 2012 à 01:27
Trouver aucun fichier ><
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 01:29
16 sept. 2012 à 01:29
sa me stresse, je vais me coucher ^^ a demain, et bon courage
Gi_Joe
Messages postés
127
Date d'inscription
samedi 15 septembre 2012
Statut
Membre
Dernière intervention
25 septembre 2012
215
16 sept. 2012 à 01:30
16 sept. 2012 à 01:30
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
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:32
16 sept. 2012 à 01:32
Ca fait quoi ? lol
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:32
16 sept. 2012 à 01:32
Ps : Bonne nuit
Edawards
Messages postés
17125
Date d'inscription
dimanche 25 juillet 2010
Statut
Membre
Dernière intervention
21 juillet 2020
1 935
16 sept. 2012 à 01:53
16 sept. 2012 à 01:53
Bonsoir,
Vous avez branché ou installé un programme avant que cela se produise?
Vous avez branché ou installé un programme avant que cela se produise?
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 01:59
16 sept. 2012 à 01:59
oui
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 02:00
16 sept. 2012 à 02:00
c'était "Hidemyip"
(pour masquer son ip)
(pour masquer son ip)
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 02:01
16 sept. 2012 à 02:01
Edawards
Messages postés
17125
Date d'inscription
dimanche 25 juillet 2010
Statut
Membre
Dernière intervention
21 juillet 2020
1 935
16 sept. 2012 à 02:02
16 sept. 2012 à 02:02
On peut savoir lequel ou quoi comme programme?
Pokemoon
Messages postés
64
Date d'inscription
dimanche 16 septembre 2012
Statut
Membre
Dernière intervention
22 octobre 2012
3
16 sept. 2012 à 06:46
16 sept. 2012 à 06:46
Toujours un écran bleu ....
Edawards
Messages postés
17125
Date d'inscription
dimanche 25 juillet 2010
Statut
Membre
Dernière intervention
21 juillet 2020
1 935
16 sept. 2012 à 07:59
16 sept. 2012 à 07:59