Pc portable asus rog écran bleu avec smiley :(
Fermé
Maximilien070497
Messages postés
16
Date d'inscription
lundi 4 janvier 2016
Statut
Membre
Dernière intervention
3 avril 2016
-
3 avril 2016 à 18:32
Utilisateur anonyme - 4 avril 2016 à 13:47
Utilisateur anonyme - 4 avril 2016 à 13:47
A voir également:
- Pc portable asus rog écran bleu avec smiley :(
- Double ecran pc - Guide
- Écran noir pc portable - Guide
- Activer pave tactile pc portable asus - Guide
- Écran bleu - Guide
- Nettoyer pc portable - Guide
1 réponse
Utilisateur anonyme
3 avril 2016 à 18:38
3 avril 2016 à 18:38
Salut,
Je te propose d'installer WhoCrashed et de nous faire un copier coller de tout ce qu'il te sort, ça nous permettras de déterminer la cause du problème.
Bonne soirée
Skid
Je te propose d'installer WhoCrashed et de nous faire un copier coller de tout ce qu'il te sort, ça nous permettras de déterminer la cause du problème.
Bonne soirée
Skid
3 avril 2016 à 19:06
System Information (local)
--------------------------------------------------------------------------------
Computer name: PC-MAXIMILIEN
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: G771JM, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8467165184 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 27/03/2016 20:50:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032716-5890-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x6A5, 0x28A9C5AB550, 0xFFFFD000266A3000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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 27/03/2016 20:50:02 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: 0x12B (0xFFFFFFFFC00002C4, 0x6A5, 0x28A9C5AB550, 0xFFFFD000266A3000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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.
3 avril 2016 à 19:10
Essaye de passer un coup de memtest86+ et regarder si y a des erreur dans les adresses mémoires.
Si y en a, je te propose de faire marcher la garantie du pc si elle y est toujours, si ce n'est pas le cas, acheter de la nouvelle ram.
3 avril 2016 à 19:17
3 avril 2016 à 19:19
Si tu veut passer à 16, faut espérer que le pc a assez de ports et que la ram de base n'est pas soudée à la carte mère.
3 avril 2016 à 19:28
Je vien juste de telecharger memtest86+ pour windows 10 et je l'ouvre avec winrar mes je n'est que 2 fichiers et quand je fait clique droit "monter" sa m'en ouvre d'autre, problème?
Je ne voudrais pas t'ennuyer plus longtemps mes peux tu encore me donner un petit coup de main :)