Pb : Plantage "écran bleu" au démarrage Fermé

Question

Bonjour, 

J'ai un problème de plantage récurrent sur un Asus N56VM que j'ai depuis seulement un mois. Il tourne sous windows 7 (x64), avec processeur Intel Core i5-3210M, RAM 4Go, cartes graphiques Intel HD Graphics 4000 et NVIDIA GeForce GT630M.


Il a planté une première fois alors que j'écoutais de la musique. J'ai eu droit à un écran bleu   et désormais dès que je redémarre, il plante juste après être le démarrage de windows, quand le bureau apparaît, toujours avec l'écran bleu, et le même message d'erreur. Malgré cela, je peux toujours démarrer en mode sans échec. J'ai donc fait tourner WhoCrashed et voici le rapport :

System Information (local)
--------------------------------------------------------------------------------

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4175282176 total
VM: 2147352576, free: 1970470912



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 17/10/2012 01:21:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101712-29047-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0x50 (0xFFFFFA0303D220E0, 0x1, 0xFFFFF800035E273C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 which cannot be identified at this time. 


On Wed 17/10/2012 01:21:48 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: 0x50 (0xFFFFFA0303D220E0, 0x1, 0xFFFFF800035E273C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 which cannot be identified at this time. 


On Wed 17/10/2012 00:39:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101712-29905-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0xC2 (0x99, 0xFFFFF8A004CC2000, 0x0, 0x0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 which cannot be identified at this time. 


On Wed 17/10/2012 00:16:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101712-40513-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0x50 (0xFFFFF8080FD74828, 0x1, 0xFFFFF800029C4617, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 which cannot be identified at this time. 


On Tue 16/10/2012 23:38:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101712-28220-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) 
Bugcheck code: 0x50 (0xFFFFFADE06C1F898, 0x0, 0xFFFFF880014E2AAB, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 which cannot be identified at this time. 


On Tue 16/10/2012 23:26:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101712-31278-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0x50 (0xFFFFFAEC03D24038, 0x0, 0xFFFFF800028BE328, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 which cannot be identified at this time. 



J'ai également testé la mémoire avec MemTest86+ et il a trouvé approximativement 25000 erreurs sur 8 tests.


N'ayant aucune connaissance en informatique, j'aimerais comprendre de quel problème il s'agit. Si c'est un problème de drivers, ou au niveau de windows 7, je peux en réinstaller ou reformater mon pc. Dans le cas ou ce serait un problème de hardware il faudrait que je renvoie l'ordi donc je voudrais être sur que c'est nécessaire avant de le faire.

Merci d'avance pour vos réponses


Configuration: Windows 7 / Chrome 22.0.1229.94

tribun · Answer

Bonjour 

Vois ceci en rapport avec Minidump.
 

https://forum.zebulon.fr/topic/55305-comment-reparer-lerreur-minidump

Mais si tu as testé ta Ram, une des deux barrettes peut être défectueuse.
Tester manuellement les deux barrettes retire en une et essaie ton pc au démarrage.
puis avec la seconde seulement.

B. Gvl · Answer

merci beaucoup pour le conseil,

Je pense aussi que c'est plutôt une panne matérielle.

Cependant s'il est nécessaire d'ouvrir le pc, il vaut mieux que je le renvoie au constructeur vu qu'il est encore sous garantie, sinon je risque de me voir reprocher le fait d'avoir voulu le tester moi même.

Je vais tout de même tenter une restauration du système auparavant. Si le problème persiste, j'aurais au moins la certitude que ce n'est pas au niveau du software.

tribun · Answer

Oui ! mieux vaut faire jouer la garantie surtout pour les portables, car ce n'est pas toujours évident d'ouvrir un portable ! et il ne sont pas universels.
@+