probleme menu windows

[seb5754]

salut j'ai un soucis avec le menu windows qui se trouve en bas a gauche , il ne fonctionne plus
si quelqu’un peut m'aider

[EinsteinZero]

bonsoir
on pourrait connaitre la version du windows qui pose problème ?
si c'est sous win 10 une méthode est expliquée >>ici<<

[seb5754]

Salut depuis quelque temps j'ai un soucis j'ai de temps en temps les messages suivants
unexpected store exception

critical process died

jai windows 10
si quelquun peut maider

[Pac428]

Bonjour Seb

J'ai regroupé tes deux sujets en supposant que c'est la même machine ^^.

Ça aurait été mieux de répondre à Einstein plutôt que de créer un nouveau sujet.

Merci d'avoir précisé que tu as Windows 10, mais ils arrivent quand tes messages ?

Tu pourrais essayer http://www.resplendence.com/downloads >>> WhoCrashed

et nous poster le rapport, ça aiderait sûrement.

++

[seb5754]

salut j'ai un ecran bleu qui m'ecris critical process died (carte mere , disque dur ....)
de quoi ceux la peut il venir ?
mercid'avance

[seb5754]

Code: Tout sélectionner

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-6LPMFOF
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., A55BM-E
CPU: AuthenticAMD AMD A6-6400K APU with Radeon(tm) HD Graphics AMD586, level: 21
2 logical processors, active mask: 3
RAM: 3430330368 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 20/06/2016 21:17:23 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE001C8876840)
Bugcheck code: 0xEF (0xFFFFE001C8876840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error.
Google query: CRITICAL_PROCESS_DIED



On Sat 18/06/2016 13:52:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061816-16734-01.dmp
This was probably caused by the following module: storport.sys (storport!RaidInitializeReportLunsSrb+0x0)
Bugcheck code: 0x154 (0xFFFFE001DB9D2000, 0xFFFFD000230623D0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
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
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed.
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.

[seb5754]

Code: Tout sélectionner

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-6LPMFOF
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., A55BM-E
CPU: AuthenticAMD AMD A6-6400K APU with Radeon(tm) HD Graphics AMD586, level: 21
2 logical processors, active mask: 3
RAM: 3430330368 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 20/06/2016 21:17:23 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE001C8876840)
Bugcheck code: 0xEF (0xFFFFE001C8876840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error.
Google query: CRITICAL_PROCESS_DIED



On Sat 18/06/2016 13:52:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061816-16734-01.dmp
This was probably caused by the following module: storport.sys (storport!RaidInitializeReportLunsSrb+0x0)
Bugcheck code: 0x154 (0xFFFFE001DB9D2000, 0xFFFFD000230623D0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
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
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed.
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.

[routman54]

Bonjour ,
Tu n'étais pas obligé de créer un deuxième sujet , ça n'ira pas plus vite pour autant .
Tu as deux rapports qui montre des causes différentes , bien souvent quand on trouve ce cas il s'agit d'un problème de rams , alors si tu en as deux ôtes en une pendant une journée , puis le lendemain même chose avec l'autre si tu as un crash lors de cette manipulation tu sauras laquelle changer .
Si tu n'as qu'une barrette essaies de t'en faire prêtre une , je vois que tu n'as que 4 Go de ram .
Bonne continuation .

[diogene]

Bonjour,

Je fusionne les deux sujets.
Bonne continuation.

[seb5754]

j'ai 2 barettes de 4 go
ok je vais essayer j'en avais deja enlever une

[seb5754]

defois j'ai aussi l'impression que le disque dur s'arrete et redemarre

[Pac428]

Salut

Teste ton disque dur alors.

https://osdn.jp/projects/crystaldiskinf ... _5-en.exe/

On va bien voir s'il est correct ou pas.

++ Seb

édit : tu peux aussi tester la mémoire : http://windows.microsoft.com/fr-fr/wind ... r-computer

Bon travail

[seb5754]

Code: Tout sélectionner

----------------------------------------------------------------------------
CrystalDiskInfo 6.7.5 (C) 2008-2016 hiyohiyo
                                Crystal Dew World : http://crystalmark.info/
----------------------------------------------------------------------------

    OS : Windows 10 Professional [10.0 Build 10586] (x64)
  Date : 2016/06/21 11:19:59

-- Controller Map ----------------------------------------------------------
 + Contrôleur AHCI SATA standard [ATA]
   - ST1000DM003-1SB10C
 - Contrôleur des espaces de stockage Microsoft [SCSI]

-- Disk List ---------------------------------------------------------------
 (1) ST1000DM003-1SB10C : 1000,2 GB [0/0/0, pd1] - st

----------------------------------------------------------------------------
 (1) ST1000DM003-1SB10C
----------------------------------------------------------------------------
           Model : ST1000DM003-1SB10C
        Firmware : CC41
   Serial Number : W9A01T7F
       Disk Size : 1000,2 GB (8,4/137,4/1000,2/1000,2)
     Buffer Size : Inconnu
     Queue Depth : 32
    # of Sectors : 1953525168
   Rotation Rate : 7200 RPM
       Interface : Serial ATA
   Major Version : ACS-3
   Minor Version : ACS-3 Revision 3b
   Transfer Mode : SATA/300 | SATA/600
  Power On Hours : 4154 heures
  Power On Count : 2035 x
     Temperature : 31 C (87 F)
   Health Status : Correct
        Features : S.M.A.R.T., APM, 48bit LBA, NCQ
       APM Level : C0C0h [ON]
       AAM Level : ----

[seb5754]

d'apres le test windows les memooires n'ont aucun soucis

[seb5754]

Code: Tout sélectionner

Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., A55BM-E
CPU: AuthenticAMD AMD A6-6400K APU with Radeon(tm) HD Graphics AMD586, level: 21
2 logical processors, active mask: 3
RAM: 7725297664 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 21/06/2016 10:04:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE0012AFA8840)
Bugcheck code: 0xEF (0xFFFFE0012AFA8840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error.
Google query: CRITICAL_PROCESS_DIED



On Mon 20/06/2016 22:20:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062116-14171-01.dmp
This was probably caused by the following module: ahcache.sys (ahcache!RtlStringCchPrintfA+0x79)
Bugcheck code: 0x7A (0xFFFFC000F84B4DE8, 0xFFFFFFFFC000000E, 0x55821860, 0xFFFFF800209A1300)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ahcache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Application Compatibility Cache
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 18/06/2016 13:52:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061816-16734-01.dmp
This was probably caused by the following module: storport.sys (storport!RaidInitializeReportLunsSrb+0x0)
Bugcheck code: 0x154 (0xFFFFE001DB9D2000, 0xFFFFD000230623D0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
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.
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.