Ecran bleu
Fermé
Barlatshi
Messages postés
53
Date d'inscription
jeudi 17 mai 2012
Statut
Membre
Dernière intervention
27 octobre 2015
-
12 avril 2014 à 13:39
Barlatshi Messages postés 53 Date d'inscription jeudi 17 mai 2012 Statut Membre Dernière intervention 27 octobre 2015 - 12 avril 2014 à 14:47
Barlatshi Messages postés 53 Date d'inscription jeudi 17 mai 2012 Statut Membre Dernière intervention 27 octobre 2015 - 12 avril 2014 à 14:47
A voir également:
- Ecran bleu
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran samsung - Guide
- Ecran noir pc - Guide
- Capture d'écran whatsapp - Guide
3 réponses
lilidurhone
Messages postés
43343
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juillet 2024
3 807
12 avril 2014 à 13:40
12 avril 2014 à 13:40
Hello
Utilise Whocrashed
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
Utilise Whocrashed
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
Barlatshi
Messages postés
53
Date d'inscription
jeudi 17 mai 2012
Statut
Membre
Dernière intervention
27 octobre 2015
5
12 avril 2014 à 14:33
12 avril 2014 à 14:33
ok merci je regarde !
Barlatshi
Messages postés
53
Date d'inscription
jeudi 17 mai 2012
Statut
Membre
Dernière intervention
27 octobre 2015
5
12 avril 2014 à 14:47
12 avril 2014 à 14:47
Voila le rapport de Whocrashed. Le soucie c'est que ça le fait sur des fichier différent à chaque fois :-(
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: ASUS-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: N73SV, ASUSTeK Computer Inc.
CPU: GenuineIntel Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4201349120 total
VM: 2147352576, free: 1960009728
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 12/04/2014 10:19:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041214-14227-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9E6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600029C9E6, 0xFFFFF8800BC35100, 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 Sat 12/04/2014 10:19:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9E6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600029C9E6, 0xFFFFF8800BC35100, 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 Tue 08/04/2014 11:09:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-16348-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x6CF9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000616CF9, 0xFFFFF88008C100D0, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: ASUS-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: N73SV, ASUSTeK Computer Inc.
CPU: GenuineIntel Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4201349120 total
VM: 2147352576, free: 1960009728
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 12/04/2014 10:19:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041214-14227-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9E6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600029C9E6, 0xFFFFF8800BC35100, 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 Sat 12/04/2014 10:19:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9E6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600029C9E6, 0xFFFFF8800BC35100, 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 Tue 08/04/2014 11:09:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-16348-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x6CF9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000616CF9, 0xFFFFF88008C100D0, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
