Ecran bleu dumping memory physical

Le matériel conseillé, compatibilité, problèmes, périphériques.

Ecran bleu dumping memory physical

Messagepar Franck456 » Dim 3 Juil 2011 11:04

Bonjour ,

Voila depuis quelque mois j'ai cette écran bleu qui s'affiche a chaque fois que je joue a css ou autre.

( C'est pas le meme exactement )
Image


J'ai fait un scan avec who crashed voila ce qui me dit :

On Thu 30/06/2011 07:55:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063011-16224-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031C13E0, 0xFFFFF8800A79BF50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 which cannot be identified at this time.


On Thu 30/06/2011 07:55:27 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: 0x3B (0xC0000005, 0xFFFFF800031C13E0, 0xFFFFF8800A79BF50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 which cannot be identified at this time.


On Sat 25/06/2011 17:26:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062711-17784-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x523DCC)
Bugcheck code: 0xD1 (0x1, 0x2, 0x1, 0xFFFFF88005B30DCC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 260.63
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 260.63
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 260.63 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Sat 25/06/2011 08:09:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062511-15132-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x83CAE)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF88001884CAE, 0x2, 0xFFFFF80002FF9E00)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 24/06/2011 14:42:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062411-19827-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6461D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002ECB61D, 0xFFFFF880031859C8, 0xFFFFF88003185230)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 which cannot be identified at this time.


On Thu 23/06/2011 18:25:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062311-18813-01.dmp
This was probably caused by the following module: hal.dll (hal+0x471F)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 19/06/2011 15:06:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061911-17472-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x8415A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EEB15A, 0xFFFFF880033166F8, 0xFFFFF88003315F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 which cannot be identified at this time.


On Sun 19/06/2011 11:07:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061911-18891-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0xC0000221 (0xFFFFF8A0001500F0, 0x0, 0x0, 0x0)
Error: STATUS_IMAGE_CHECKSUM_MISMATCH
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 driver or a system DLL has been corrupted.
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. There is a possibility this problem was caused by a virus or other malware.
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 10/05/2011 15:08:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051311-17721-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x13532F)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600015532F, 0xFFFFF880081E9080, 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 which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

9 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 260.63 , NVIDIA Corporation)




Mais il y a pas tout les crash :S

J'ai le dernier driver pour la carte graphique

Voila merci d'avance
Franck456
 
Messages: 10
Inscription: Dim 3 Juil 2011 10:59

Re: Ecran bleu dumping memory physical

Messagepar Jango78 » Dim 3 Juil 2011 13:18

Bonjour,

Sans trop m'avancer il semblerait que la carte graphique Nvidia GeForce machinchose soit en cause.

D'après le log, version installée du pilote nvlddmkm.sys = 260.63 Bêta datant de 2010.

Il y a peut-être un binz avec l'installation récente [275.33 ?] par-dessus une version ancienne ayant laissé des résidus :hein:
Avatar de l’utilisateur
Jango78
 
Messages: 1748
Inscription: Dim 19 Avr 2009 13:02
Localisation: IDF

Re: Ecran bleu dumping memory physical

Messagepar Franck456 » Dim 3 Juil 2011 13:33

Il n'y a pas de version 275.33

Voila ma carte graphique http://www.gigabyte.fr/products/product ... 530#driver

( widows 7 64bit)
Franck456
 
Messages: 10
Inscription: Dim 3 Juil 2011 10:59

Re: Ecran bleu dumping memory physical

Messagepar Jango78 » Dim 3 Juil 2011 14:46

Re,

Il s'agit donc d'une GeForce GTX 460.

Effectivement la version 260.63 date bien de Septembre 2010, donc relativement obsolète, alors que les 275.33 certifiés WHQL de Nvidia ont été publiés le mois dernier avec son lot de correction de bugs...

http://www.nvidia.fr/object/win7-winvis ... er-fr.html
Avatar de l’utilisateur
Jango78
 
Messages: 1748
Inscription: Dim 19 Avr 2009 13:02
Localisation: IDF

Re: Ecran bleu dumping memory physical

Messagepar Franck456 » Dim 3 Juil 2011 19:26

Re,

J'ai s'en faire expres installer le driver pour vista que suis je *** .
Bon après multiple redémarrage ( au début il se démarrais comme vista )
Maintenant jai le démarrage de widows7 ...
mais il met un écran bleu que jai pas le temp de voir .
Je voudrais savoir ou est le truc "redémarrage si erreur" dans le bios pour que je vous fasse parvenir l'écran bleu
Défois il freez en étant dans le BIOS :evil:

Merci d'avance
Franck456
 
Messages: 10
Inscription: Dim 3 Juil 2011 10:59

Re: Ecran bleu dumping memory physical

Messagepar Jango78 » Dim 3 Juil 2011 21:17

Franck456 a écrit:Je voudrais savoir ou est le truc "redémarrage si erreur" dans le bios pour que je vous fasse parvenir l'écran bleu

Probablement dans le menu Boot du BIOS, avec une option du style Wait for F1 if Error qui doit être Enabled.

Tout dépend de la version du BIOS et son fabricant [AMI, Phoenix, etc...].
Avatar de l’utilisateur
Jango78
 
Messages: 1748
Inscription: Dim 19 Avr 2009 13:02
Localisation: IDF

Re: Ecran bleu dumping memory physical

Messagepar Franck456 » Lun 4 Juil 2011 10:49

Re,

Voila l'écran bleu

Image
Franck456
 
Messages: 10
Inscription: Dim 3 Juil 2011 10:59

Re: Ecran bleu dumping memory physical

Messagepar Jango78 » Lun 4 Juil 2011 11:36

Bonjour,

Je peux juste indiquer la signification du code et son interprétation rapide.

Erreur STOP 0x24 = NTFS_FILE_SYSTEM
A la base c'est un problème matériel... pouvant concerner par ex. un disque dur [échec d'accès à la partition système, problème de pilotes, structure de partition corrompue, système de fichiers corrompu], ou éventuellement une barrette mémoire devenue défectueuse.

Le driver Ntfs.sys est parfois en cause pour ce qui concerne le système.

Peut-être d'autres avis... :?:
Avatar de l’utilisateur
Jango78
 
Messages: 1748
Inscription: Dim 19 Avr 2009 13:02
Localisation: IDF

Re: Ecran bleu dumping memory physical

Messagepar Franck456 » Lun 4 Juil 2011 11:43

Oui comme jai dit dans un poste précédant jai installé le driver de ma carte graphique mais pour vista alor que j'ai widows 7 :(
Franck456
 
Messages: 10
Inscription: Dim 3 Juil 2011 10:59

Re: Ecran bleu dumping memory physical

Messagepar Jango78 » Lun 4 Juil 2011 12:17

Mais certains pilotes Vista fonctionnent parfaitement sur Seven.

Je crois qu'il est quasi impossible d'avoir la certitude absolue et garantir à 100% que le problème vient des pilotes de la carte graphique.

Normalement Windows Update est capable de détecter la carte via une recherche des mises à jour et proposer un téléchargement si ladite carte, ou son circuit graphique, est référencée dans sa base de données avec des pilotes compatibles plus ou moins récents.

L'hypothèse basée sur des pilotes inadéquats de la carte graphique impliquerait donc leur désinstallation par tout moyen, puis l'installation de pilotes compatibles.

Et si ce n'est pas la carte graphique, un autre composant matériel ou logiciel est forcément impliqué... :hein:
Avatar de l’utilisateur
Jango78
 
Messages: 1748
Inscription: Dim 19 Avr 2009 13:02
Localisation: IDF

Suivante

Retourner vers Matériels

Qui est en ligne

Utilisateurs parcourant ce forum: Aucun utilisateur enregistré et 1 invité

Livre photo