BlueScreenRésolu/Fermé

Question

Bonjour a tous :)

je me suis prit un petit bluescreen, si quelqu'un pourrais me dire comment évité a nouveau la situation ? 
j'ai malheureusement pas eue le temp de prendre en photos le fameux, mais une fois revenus sur windows une fenêtre d'erreur c'est affiché avec ceci écrit dessus:

Signature du problème :
  Nom d’événement de problème:	BlueScreen
  Version du système:	6.1.7601.2.1.0.256.48
  Identificateur de paramètres régionaux:	1036

Informations supplémentaires sur le problème :
  BCCode:	3b
  BCP1:	00000000C0000005
  BCP2:	FFFFF80002FAE6FB
  BCP3:	FFFFF8800CAE7A10
  BCP4:	0000000000000000
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	256_1

Fichiers aidant à décrire le problème :
  C:\Windows\Minidump\090416-15865-01.dmp
  C:\Users\blix\AppData\Local\Temp\WER-47361-0.sysdata.xml

quelqu'un pourrais m'aider a résoudre le problème? je suis sur windows 7 64bits
merci beaucoup d'avance. 

Configuration: Intel I7 4790K/ 16go de ram/ msi gtx960/ corsair HX850I/ enermax liqmax II 240

Utilisateur anonyme · Accepted Answer

Salut,

Après quelques minutes de lecture de tout le topic j'ai ptet quelques solutions :

- Essayer de faire des memtest86+ afin de voir si tu n'a pas un soucis de ram
- Check si tu n'a pas une corruption dans Windows via la commande sfc / scannow (sur une cmd en administrateur)
- Vérifier si tu n'a pas des dossier type WindowsBT ou WindowsWS (c'est des dossiers cachés) dans la racine de ton disque C:

J'attend ton retour ^^

-Skid

blix83 · Answer

j'ai un rapport de WhoCrashed si vous avez besoins?

System Information (local)
--------------------------------------------------------------------------------

Computer name: BLIX-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: MS-7917, MSI, Z97 GAMING 5 (MS-7917)
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17125117952 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 04/09/2016 00:44:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090416-15865-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FAE6FB, 0xFFFFF8800CAE7A10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.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 Sun 04/09/2016 00:44:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x9E68) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FAE6FB, 0xFFFFF8800CAE7A10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 02/09/2016 20:03:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090216-16754-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBAD09) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000BAD09, 0xFFFFF8800BF1E070, 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. 





--------------------------------------------------------------------------------
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 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.

Dacro · Answer

Bonjour blix83 as-tu essayé de faire un nettoyage de registre et autres avec ADW Cleaneur? À savoir que l'écran bleu où l'écran de la mort sert à mettre en sécurité un organe de l'ordinateur le problème peut aussi venir d'un driver.

blix83 · Answer

donc voila le dernier rapport de who crashed:

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: BLIX-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: MS-7917, MSI, Z97 GAMING 5 (MS-7917)
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17125117952 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 05/09/2016 19:07:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090516-12729-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800033CF281, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Mon 05/09/2016 19:07:39 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800033CF281, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 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 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.

blix83 · Answer

merci :)

BlueScreen

5 réponses

Discussions similaires

Newsletters