Ecran bleu à répétition
Fermé
FoxLemon
Messages postés
4
Date d'inscription
jeudi 19 juin 2014
Statut
Membre
Dernière intervention
19 juin 2014
-
Modifié par FoxLemon le 19/06/2014 à 14:29
EGP-Swyx Messages postés 6654 Date d'inscription dimanche 18 mars 2012 Statut Contributeur Dernière intervention 7 janvier 2019 - 19 juin 2014 à 16:41
EGP-Swyx Messages postés 6654 Date d'inscription dimanche 18 mars 2012 Statut Contributeur Dernière intervention 7 janvier 2019 - 19 juin 2014 à 16:41
A voir également:
- Ecran bleu à répétition
- Ecran noir pc - Guide
- Retourner ecran windows - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Enregistrer son ecran - Guide
4 réponses
EGP-Swyx
Messages postés
6654
Date d'inscription
dimanche 18 mars 2012
Statut
Contributeur
Dernière intervention
7 janvier 2019
620
Modifié par EGP-Swyx le 19/06/2014 à 14:30
Modifié par EGP-Swyx le 19/06/2014 à 14:30
Bonjour,
Installe whocrashed,
poste nous le rapport complet avec la conclusion
Cordialement, Swyx
(technicien de montage/maintenance hardware informatique)
Installe whocrashed,
poste nous le rapport complet avec la conclusion
Cordialement, Swyx
(technicien de montage/maintenance hardware informatique)
FoxLemon
Messages postés
4
Date d'inscription
jeudi 19 juin 2014
Statut
Membre
Dernière intervention
19 juin 2014
19 juin 2014 à 14:44
19 juin 2014 à 14:44
Merci pour ta rapidité, voilà le rapport :
System Information (local)
--------------------------------------------------------------------------------
computer name: YGGDRASILL-VAIO
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: VPCEB3L1E, Sony Corporation, VAIO
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4141977600 total
VM: 2147352576, free: 1980977152
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 19/06/2014 12:06:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061914-26769-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000146483, 0xFFFFF88007C71070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Thu 19/06/2014 12:06:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x863)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000146483, 0xFFFFF88007C71070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Wed 18/06/2014 13:18:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061814-24663-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x6CF9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000746CF9, 0xFFFFF88007C12120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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 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 Wed 28/05/2014 16:37:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052814-30778-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600036260D)
Bugcheck code: 0x50 (0xFFFFF900C2E85CF0, 0x0, 0xFFFFF9600036260D, 0x0)
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 Mon 26/05/2014 18:26:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052614-24289-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000C6483, 0xFFFFF880087E2070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Fri 09/05/2014 21:50:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051014-88436-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600030260D)
Bugcheck code: 0x50 (0xFFFFF900C3CAECF0, 0x0, 0xFFFFF9600030260D, 0x0)
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 Wed 19/03/2014 22:00:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032014-33290-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600032260D)
Bugcheck code: 0x50 (0xFFFFF900C44CACF0, 0x0, 0xFFFFF9600032260D, 0x0)
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 25/02/2014 23:28:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022614-37565-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002F260D)
Bugcheck code: 0x50 (0xFFFFF900C22A8CF0, 0x0, 0xFFFFF960002F260D, 0x0)
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 11/02/2014 19:25:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021114-35115-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800038545FE, 0xFFFFF88008DC8010, 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 Fri 31/01/2014 16:48:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013114-74131-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800038945FE, 0xFFFFF88002B05CD0, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has 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:
athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)
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: YGGDRASILL-VAIO
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: VPCEB3L1E, Sony Corporation, VAIO
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4141977600 total
VM: 2147352576, free: 1980977152
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 19/06/2014 12:06:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061914-26769-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000146483, 0xFFFFF88007C71070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Thu 19/06/2014 12:06:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x863)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000146483, 0xFFFFF88007C71070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Wed 18/06/2014 13:18:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061814-24663-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x6CF9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000746CF9, 0xFFFFF88007C12120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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 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 Wed 28/05/2014 16:37:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052814-30778-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600036260D)
Bugcheck code: 0x50 (0xFFFFF900C2E85CF0, 0x0, 0xFFFFF9600036260D, 0x0)
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 Mon 26/05/2014 18:26:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052614-24289-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000C6483, 0xFFFFF880087E2070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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 Fri 09/05/2014 21:50:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051014-88436-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600030260D)
Bugcheck code: 0x50 (0xFFFFF900C3CAECF0, 0x0, 0xFFFFF9600030260D, 0x0)
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 Wed 19/03/2014 22:00:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032014-33290-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600032260D)
Bugcheck code: 0x50 (0xFFFFF900C44CACF0, 0x0, 0xFFFFF9600032260D, 0x0)
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 25/02/2014 23:28:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022614-37565-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002F260D)
Bugcheck code: 0x50 (0xFFFFF900C22A8CF0, 0x0, 0xFFFFF960002F260D, 0x0)
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 11/02/2014 19:25:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021114-35115-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800038545FE, 0xFFFFF88008DC8010, 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 Fri 31/01/2014 16:48:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013114-74131-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800038945FE, 0xFFFFF88002B05CD0, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has 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:
athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)
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.
EGP-Swyx
Messages postés
6654
Date d'inscription
dimanche 18 mars 2012
Statut
Contributeur
Dernière intervention
7 janvier 2019
620
19 juin 2014 à 14:47
19 juin 2014 à 14:47
Alors d'après le rapport c'est la carte réseau qui crash.
met à jour le pilote de la carte réseau LAN (pas wifi)
Tiens moi au courant =)
met à jour le pilote de la carte réseau LAN (pas wifi)
Tiens moi au courant =)
FoxLemon
Messages postés
4
Date d'inscription
jeudi 19 juin 2014
Statut
Membre
Dernière intervention
19 juin 2014
19 juin 2014 à 14:59
19 juin 2014 à 14:59
Ok, merci ! Si Drakker network adaptater est bien le nom de la carte réseau, alors je viens de la mettre à jour. Les autres éléments dans la section carte réseau (Atheros AR9285 Wireless Network Adapater notamment) étaient déjà à jour.
Whocrashed permet-il de vérifier que le problème est réglé ?
Whocrashed permet-il de vérifier que le problème est réglé ?
EGP-Swyx
Messages postés
6654
Date d'inscription
dimanche 18 mars 2012
Statut
Contributeur
Dernière intervention
7 janvier 2019
620
19 juin 2014 à 15:16
19 juin 2014 à 15:16
Non c'est la Atheros qui déconne.
Va sur le site du constructeur de ton pc ou bien de ta carte mère et télécharge le dernier pilote certifié
Va sur le site du constructeur de ton pc ou bien de ta carte mère et télécharge le dernier pilote certifié
FoxLemon
Messages postés
4
Date d'inscription
jeudi 19 juin 2014
Statut
Membre
Dernière intervention
19 juin 2014
19 juin 2014 à 16:22
19 juin 2014 à 16:22
Nouvel écran bleu suite à l'installation du pilote. Je suis allé ici --> https://drivers.informer.com/atheros-ar9285-wireless-network-adapter/
(donc il se peut que j'ai absolument pas pris le bon truc vu que je n'y connais absolument rien...)
La tête de l'écran bleu à légèrement changé: http://www.noelshack.com/2014-25-1403187601-dsc-0189-1.jpg
j'ai voulu le redémarrer suite à cela, mais je retombais systématiquement sur l'écran bleu, du coup je suis passé au mode sans échec sans prise en charge réseau et ai fait une restauration .-.
(donc il se peut que j'ai absolument pas pris le bon truc vu que je n'y connais absolument rien...)
La tête de l'écran bleu à légèrement changé: http://www.noelshack.com/2014-25-1403187601-dsc-0189-1.jpg
j'ai voulu le redémarrer suite à cela, mais je retombais systématiquement sur l'écran bleu, du coup je suis passé au mode sans échec sans prise en charge réseau et ai fait une restauration .-.
EGP-Swyx
Messages postés
6654
Date d'inscription
dimanche 18 mars 2012
Statut
Contributeur
Dernière intervention
7 janvier 2019
620
19 juin 2014 à 16:41
19 juin 2014 à 16:41
très bonne chose la restauration. t'as eu le bon réflexe. si tu ne sais pas quel driver prendre, vu que j'ai cru voir que c'était un pc portable : Site du constructeur -> Support et pilots. tu rentre la référence et go.