Bonjour à tous,
Alors voila j'ai voulu me monter une config HTPC Gamer, j'ai tout acheté et tout monté. Jusque là pas de problème, bien cher mais le résultat est sympa.
Et depuis l'installation de Windows 7 OEM des écrans bleus intempestifs. Ce qui est super stressant (2 à 4 reboots par jour)
J'ai installé Who Crashed afin d'avoir une idée des problèmes mais cela ne m'aide pas beaucoup. Je pensais à un problème de mémoire et à cette fin j'ai lancé le logiciel Windows de controle de la mémoire et il ne trouve rien.
Donc j'ai besoin de votre aide afin de m'aider à mieux comprendre le problème. Merci à tous pour votre contribution.
Voici les fichiers Dmp :
http://www.sendspace.com/file/nwodsv
http://www.sendspace.com/file/ltnsc0
http://www.sendspace.com/file/z2hbxe
http://www.sendspace.com/file/ly26ix
Voici ci dessous les infos de Who crashed :
On Thu 18/11/2010 21:50:37 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x2, 0x60894, 0x11FFFF, 0x1)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\111810-16832-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Thu 18/11/2010 21:42:15 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x42BE, 0x42CC0200857C)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\111810-16676-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Thu 18/11/2010 16:17:03 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002E7DCDC)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\111810-14539-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Thu 18/11/2010 16:15:20 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF680000278C0, 0xAE7000004FC71825, 0xFFFFF6FC500286B0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\111810-21715-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
Ecran bleu bien stressant - votre aide fortement appréciée
Re: Ecran bleu bien stressant - votre aide fortement appréciée
Bonjour,
Voici quelques indications extraites des fichiers dumps :
MEMORY_MANAGEMENT (1a)
PROCESS_NAME: dwm.exe
IMAGE_NAME: ntkrnlmp.exe
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists
PROCESS_NAME: svchost.exe
IMAGE_NAME: memory_corruption
MEMORY_MANAGEMENT (1a)
PROCESS_NAME: chrome.exe
IMAGE_NAME: ntkrnlmp.exe
IRQL_NOT_LESS_OR_EQUAL (a)
PROCESS_NAME: GUI.exe
IMAGE_NAME: symsnap.sys
Pour moi, c'est un problème matériel et fort probablement lié à la mémoire.
Si tu as overclocké, il faudrait revoir tes paramètres.
@+
Voici quelques indications extraites des fichiers dumps :
MEMORY_MANAGEMENT (1a)
PROCESS_NAME: dwm.exe
IMAGE_NAME: ntkrnlmp.exe
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists
PROCESS_NAME: svchost.exe
IMAGE_NAME: memory_corruption
MEMORY_MANAGEMENT (1a)
PROCESS_NAME: chrome.exe
IMAGE_NAME: ntkrnlmp.exe
IRQL_NOT_LESS_OR_EQUAL (a)
PROCESS_NAME: GUI.exe
IMAGE_NAME: symsnap.sys
Pour moi, c'est un problème matériel et fort probablement lié à la mémoire.
Si tu as overclocké, il faudrait revoir tes paramètres.
@+