ASUS N56VZ S4023V

[snakepit]

bonjour,
j'ai un petit soucis avec mon ASUS N56VZ S4023V, en fait quand je travaille et que j'ouvre plusieurs application, ou meme seulement lecture de musique plus internet, il plante, il s'arrete un ecran bleu s'affiche quelques seconde puis redemarre, j'ai pensé que ça pourrait etre ma barette memoire qui serait morte, mais je ne suis pas sur, comment savoir et que dois je faire? si c'est la barette memoire, que dois je acheter car il y a tellement de modele que je suis un peu paumé, et combien je peut mettre au maximum en Go?
si c'est pas ça, de quoi ça pourrait venir?
j'ai aussi fire fox qui deconne pas mal et ne peut pas restaurer mes onglets, bref mon PC n'est plus tres fiable!!!

merci pour tous vos conseils

[EinsteinZero]

Bonsoir
un écran bleu ça peu avoir plein de cause....
pourrais tu faire un rapport avec whocrashed (log sans installation) il suffit de lancer le logiciel et de faire un copier coller de son rapport

[EinsteinZero]

merci pour tes conseils, alors voilà, j'ai eu ça:
attention, c'est tres long.

Code: Tout sélectionner

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 24/03/2014 20:44:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032414-31995-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80020D9360, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 24/03/2014 20:44:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x23D6E)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80020D9360, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 Mon 24/03/2014 19:45:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032414-24211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80020D9300, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 23/03/2014 08:23:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032314-38984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80020D9300, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 22/03/2014 21:09:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032214-28454-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80020D9360, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 22/02/2014 19:50:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-20826-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF6FC8076DEB0, 0x0, 0x0, 0xFFFFF800036C5B2B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 08/02/2014 11:56:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020814-25318-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80020D9300, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 30/01/2014 17:18:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-28875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80020D9360, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 16/01/2014 18:38:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011614-30732-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF880014C3900)
Bugcheck code: 0x50 (0xFFFFF8A0E07477A8, 0x1, 0xFFFFF880014C3900, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that invalid system memory has been referenced.
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 Thu 02/01/2014 20:54:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010214-21559-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA809D3CC348, 0x0, 0xFFFFF800039BECDC, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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
--------------------------------------------------------------------------------

19 crash dumps have been found and analyzed. Only 10 are included in this report. 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.

[EinsteinZero]

Bonsoir
je me suis permis de mettre ton rapport entre balises [code] afin d'en raccourcir la longueur sur la page

sinon, pour le reste, ça ressemble énormément à un souci sur une barrette de Ram....

il faudrait, si tu as plusieurs barrette en enlever une pour voir si ça stabilise la bête et, ensuite changer de barrette pour en tester une autre pour voir si c'est alors stable...

si une barrette reste instable....tu as de très fortes chance d'avoir trouver la cause du souci

si tu n'as qu'une seule barrette sur la machine...2 options

1> tu achètes ou tu te fais prêter une nouvelle barrette de Ram pour voir si ça règle le soucis

2> tu utilise un CD memtest pour tester le composant suspect


Remarque technique très importante de la modération
ceci dit, merci de retirer le lien facebook de ta signature car depuis des soucis de "CopyRight" sur le site d'un forumeur ce genre de lien n'est plus toléré, à défaut on risque de devenir désagréable

Pour l'instant je me suis contenté de masquer ta signature......

[snakepit]

ok, merci pour tout, alors la signature est modifiée, desolé je n'etais pas au courant....

juste une chose pour la memoire, je n'ai qu'une barette donc je dois en acheter une, mais je ne sais pas quoi choisir, il y a tellement de modele que j'ai peur de ne pas prendre le bon, saurais tu me conseiller?

merci beaucoup

[EinsteinZero]

Rapidement (je parts au boulot)
il suffit normalement d'ouvrir le compartiment mémoire pour relever les caractéristiques sur la barrette

[Pac428]

Salut

Sinon, utilise PC-Wizard pour récupérer l'info :

Download : http://www.cpuid.com/downloads/pc-wizar ... -setup.exe

C'est là dans les fenêtres :



++ Snakepit

[snakepit]

merci pour PC wizard,
j'ai trouvé ça:
mais pour moi c'est un peu du chinois!!

est ce que je peux trouver ça sur net on net? j'habite Stockholm, il me faut un site qui envoie a l'etranger!!

Informations générales :
ChannelA-DIMM0 (BANK 0 ) :
ChannelB-DIMM0 (BANK 2 ) :


Informations SPD EEPROM (C
Fabricant : Hyundai Electro
Part Number : HMT351S6CFR8C
Numéro de série : BA9E440D1
Type : DDR3-SDRAM PC3-12800
Format : SO-DIMM (67,6 x 15
Taille : 4096 Mo (2 ranks,
Module Buffered : Non

Module Registered : Non

Module SLi Ready (EPP) : No
Module XMP : Non

Largeur : 64bits

Correction d'erreur (ECC) :
Voltage : 1.50v

Prefetch Buffer : 8bits

Fabrication : semaine 15 de
Sonde Thermique : Non

Dissipateur Thermique : Non
Fréquences supportées : 381
CAS Latency (tCL) : 5 clock
RAS to CAS (tRCD) : 5 clock
RAS Precharge (tRP) : 5 clo
Cycle Time (tRAS) : 14 cloc
Min TRC : 19 clocks @ 381 M


Informations Contrôleur Mémoire :

Contrôleur mémoire : System Memory

Location : Carte mère

Correction d'erreur : Non

Nombre de connecteurs : 4

Taille maximum des modul... 32768 Mo

[snakepit]

autre chose, combien je peux mettre de RAM maxi sur cet ordi? et combien de barrette?
merci encore a vous

[snakepit]

est ce que ce model fonctionnerai par exemple?
qu'est ce que c'est le : SO-DIMM DDR3?

http://www.materiel.net/barrette-memoir ... 97677.html

[Pac428]

Salut Snakepit.

combien je peux mettre de RAM maxi sur cet ordi? et combien de barrette?

Réponse PCW :

Nombre de connecteurs : 4
Taille maximum des modul... 32768 Mo

quatre barrettes de huit Go de DDR3 PC 12800 format So-Dimm.

Mais : deux ports du contrôleur ne sont pas utilisés par Asus, ce qui redescend à deux fois 8 Go.

http://www.ldlc.com/fiche/PB00130018.html

So-Dimm, ce sont les barrettes pour portable.

La barrette de ton lien est dans les clous, mais c'est du 8 Go alors que tu as du 4 Go.

Donc juste pour remplacer, je mettrais plutôt celle-là :

http://www.materiel.net/barrette-memoir ... 93318.html

Qui doit ressembler de plus près à ta barrette actuelle:

Hyundai/Hynix HMT351S6CFR8C Numéro de série : BA9E440D1 et qui doit ressembler à ça :

http://www.amazon.com/PC3-12800-1600MHz ... B00A8J2OUM

Si tu veux par contre monter ton portable au max de 16Go, je mettrais celle-là en deux exemplaires:

http://www.materiel.net/barrette-memoir ... 93785.html

++

[snakepit]

ok, ta derniere proposition me parait la meilleure, je vais faire ça et comme ça si un jour je veux en mettre une deuxieme pour avoir 16Go ce sera peut etre encore mieux!!! mais je crois qu'actuellement mon portable a 6 Go donc si je remplace par 8 c'est dejà du bonus!!!
merci encore et j'espere qu'apres ça je n'aurai plus de probleme!!!
dois je reformater si j'ai encore une instabilité?

encore un grand merci a tous

[EinsteinZero]

Bonjour
s'il y a instabilité, on ne formate qu'après avoir essayé tout le reste car un pb matériel n'est jamais réglé par un formatage

là je pense que tu as 98% de chance qu'une nouvelle barrette de ram règle le souci...évidement reste 2% de pas de bol

j'y crois pas beaucoup