Bug ordinateur portable :(

Fermé
fab727 Messages postés 7 Date d'inscription samedi 4 janvier 2014 Statut Membre Dernière intervention 19 janvier 2014 - 4 janv. 2014 à 11:04
fab727 Messages postés 7 Date d'inscription samedi 4 janvier 2014 Statut Membre Dernière intervention 19 janvier 2014 - 19 janv. 2014 à 08:51
Bonjours et bonne année a tous!
Voilà,j'ai un ordi portable samsung rv511,avec windows7.Par moment il se déconnecte d'internet,fait un arret sur image,ou écran bleu avec le message" A problem has been detected......."Je ne suis pas un grand spécialiste,mais pour le moment j'ai effectué une restauration complète via"samsung recovery solution"qui c'est bien déroulé mais sans succès.Et j'ai regardé dans gestionnaires de periphériques,rien ne semble d'anormal.
Merci à tous ceux qui pourront m'aider :)

9 réponses

salut sa peut être un problème de drivers.

Tu pourrais télécharger whocrashed et voir le diagnostique.

https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/

(¯'·.¸¸.·'¯'·.¸¸.-> <-.¸¸.·'¯'·.¸¸.·'¯)
0
fab727 Messages postés 7 Date d'inscription samedi 4 janvier 2014 Statut Membre Dernière intervention 19 janvier 2014
5 janv. 2014 à 09:40
merci pour ton aide,qui me permet d'avancer,problème non résolu pour le moment.
0
Utilisateur anonyme
5 janv. 2014 à 10:47
tu pourrais nous montrer ton rapport stp ?
0
fab727 Messages postés 7 Date d'inscription samedi 4 janvier 2014 Statut Membre Dernière intervention 19 janvier 2014
5 janv. 2014 à 17:20
Voila le rapport.
maintenant il semble que j'ai des problemes de mise à jour update.
Je n'ais plus internet explorer et n'arrive pas a le réinstaller.
Si quelqu'un à des suugestions!


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 04/01/2014 22:18:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeSynchronizeExecution+0x3A2B)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8800528B2C2, 0xFFFFF880035BCC58, 0xFFFFF880035BC4B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 04/01/2014 19:55:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-24804-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88005B8DB0E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF880054CA2C2, 0xFFFFF880035B5C58, 0xFFFFF880035B54B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Sat 04/01/2014 13:29:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-104536-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006A1C8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 03/01/2014 16:30:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-27315-01.dmp
This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x1D2C2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88005A722C2, 0xFFFFF880035CACA8, 0xFFFFF880035CA510)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\bcmwl664.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Fri 03/01/2014 16:11:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-25740-01.dmp
This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x1D2C2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88005CC72C2, 0xFFFFF88003248CA8, 0xFFFFF88003248510)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\bcmwl664.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Fri 03/01/2014 08:19:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-25537-01.dmp
This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x1D2C2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880090C32C2, 0xFFFFF880033B5CA8, 0xFFFFF880033B5510)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\bcmwl664.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Thu 02/01/2014 20:33:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010214-23836-01.dmp
This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x1D2C2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88005A8B2C2, 0xFFFFF880035A7CA8, 0xFFFFF880035A7510)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\bcmwl664.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Thu 02/01/2014 18:00:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010214-47096-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88005C6EB8C)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF880050682C2, 0xFFFFF880035BCCA8, 0xFFFFF880035BC510)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Thu 02/01/2014 11:04:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010214-35131-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006D97038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 02/01/2014 08:32:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010214-37221-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006D18038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

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

bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom 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.
0
Utilisateur anonyme
5 janv. 2014 à 17:27
salut apparemment il serait conseillé de mettre le driver bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation) à jour.

0

Vous n’avez pas trouvé la réponse que vous recherchez ?

Posez votre question
fab727 Messages postés 7 Date d'inscription samedi 4 janvier 2014 Statut Membre Dernière intervention 19 janvier 2014
5 janv. 2014 à 17:30
oui je l'est fait sa.comment savoir si sa a bien fonctionné?
0
Utilisateur anonyme
5 janv. 2014 à 17:38
pour voir tu fais devmgmt.msc dans la fenêtre exécuter (touche windows +r) et tu accède au gestionnaire de périphérique
0
Utilisateur anonyme
5 janv. 2014 à 17:33
salut essaye un autre navigateur pour voir, style chromium qui est la version open source de chrome et qui est génial ou firefox qui est excellent aussi.
0
fab727 Messages postés 7 Date d'inscription samedi 4 janvier 2014 Statut Membre Dernière intervention 19 janvier 2014
5 janv. 2014 à 18:55
finalement je viens de mettre google chrome comme navigateur,et il s'est installé correctement(dommage explorer me plaisait bien)
J'ai été dans gestionnaire et périphérique et là rien ne semble d'anormal.
0
fab727 Messages postés 7 Date d'inscription samedi 4 janvier 2014 Statut Membre Dernière intervention 19 janvier 2014
16 janv. 2014 à 10:21
Bonjour à tous.Je remonte le sujet pour dire que mon problème persiste toujours.
Déconnection internet,suivi quelques fois de l'écran bleu(pas à chaques fois).J'ai tous recommencé une deuxième fois.Quand j'installe le pilote broadcom il semble s'installer correctement,et quand je rallume l'ordi,samsung me mets un message du genre qu'un pilote n'est pas à jours.je clic sur mettre à jours,mais j'ai l'impression que c'est une ancienne version de broadom qui se mets sur l'ordi(dsl je ne sais pas si c'est les thermes exact,je ne suis pas un grand spécialiste)
Pour le reste l'ordi fonctionne parfaitement.Et quelques fois il ne va pas se déconnecter pendant plusieurs heures.Et quand il est parti à buger,à peine connceter il se redéconnecte quelques minutes plus tard.Et le lendemain sa fonctionne.A rien n'y comprendre :(
0
fab727 Messages postés 7 Date d'inscription samedi 4 janvier 2014 Statut Membre Dernière intervention 19 janvier 2014
19 janv. 2014 à 08:51
personne ne peut m'aider?
0