Forum-seven : Communauté francaise de Windows 7

Bonsoir,
J'imagine que vous devez en avoir marre de répondre à ce sujet mais là je n'y arrive plus...
Je n'y connais pas grand chose mais j'ai essayé de chercher un peu à gauche et à droite afin de chercher des solutions mais rien n'y fait : vérification des barrettes, réinstallation de W7, test sfc /scannow, Memtest86, ..... , whocrashed.
Je vous joint le rapport de l'analyse de whocrashed qui m'a trouvé une erreur mais que je ne sais pas interpréter :

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 20/10/2010 16:15:30 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80023CB8F0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\102010-13572-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.

Si qq'un peut m'apporter de l'aide.
Merci bcp.

Bonsoir,
Voici ce que nous dit http://www.docmemo.com/windows/erreursstop.php

Code 0x0000001A

Logiciel : Erreur STOP Windows
Intitulé : MEMORY_MANAGEMENT
Solution
Problème de gestion de mémoire ou problème matériel.
[1] Si vous venez d'installer un nouveau matériel, désinstallez-le.
[2] La mémoire vive est peut-être endommagée. Voyez si les barrettes sont bien clipsées sur la carte mère. Si c'est le cas, essayez de repérer une éventuelle barrette défectueuse. Retirez une barrette et redémarrez. Si l'erreur n'apparaît plus, remplacez la barrette extraite par une nouvelle.

Pas mieux.
@+

Merci pour ta réponse.
J'ai vérifié plusieurs fois les barrettes, je ne pense pas que cela viennent de celles-ci.
Si c'est un problème logiciel comment arriver à faire la part des choses et identifier quels fichiers, logiciels, drivers est fautif ?

Bonsoir,
Cela ne peut être qu'un logiciel ou périphérique installé au moment du premier crash.
@+

Bonsoir,
Hier soir j'ai réinstallé complètement mon PC matériel + logiciel (uniquement W7).
Jusqu'à présent j'ai essayé plusieurs configuration concernant mes barrettes de RAM, toutes les combinaisons barrettes - slots mais rien n'y fait, je n'arrive pas à déterminer d'où cela provient. J'ai lancé des analyses sur chaque barrettes, à chaque fois il ne trouve rien.
Depuis hier soir et ma réinstallation j'ai eu 2 blue screen dont voici les rapports, c'est vraiment frustrant de ne pas pouvoir se servir de son PC, please HELP ME !!!!
Merci

Nom du journal :System
Source : Microsoft-Windows-Kernel-Power
Date : 27/10/2010 20:18:16
ID de l’événement :41
Catégorie de la tâche :(63)
Niveau : Critique
Mots clés : (2)
Utilisateur : Système
Ordinateur : We-PC
Description :
Le système a redémarré sans s’arrêter correctement au préalable. Cette erreur peut survenir si le système ne répond plus, s’est bloqué ou n’est plus alimenté de façon inattendue.
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2010-10-27T18:18:16.460808700Z" />
<EventRecordID>547</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>We-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Nom du journal :System
Source : Microsoft-Windows-Kernel-Power
Date : 28/10/2010 18:45:09
ID de l’événement :41
Catégorie de la tâche :(63)
Niveau : Critique
Mots clés : (2)
Utilisateur : Système
Ordinateur : We-PC
Description :
Le système a redémarré sans s’arrêter correctement au préalable. Cette erreur peut survenir si le système ne répond plus, s’est bloqué ou n’est plus alimenté de façon inattendue.
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2010-10-28T16:45:09.396428000Z" />
<EventRecordID>1046</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>We-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">26</Data>
<Data Name="BugcheckParameter1">0x41790</Data>
<Data Name="BugcheckParameter2">0xfffffa80023fa240</Data>
<Data Name="BugcheckParameter3">0xffff</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Bonjour
Ton alimentation est-elle suffisante pour ta configuration ?
@+

Bonsoir,
Je reviens vers vous car je n'ai toujours pas résolu mes problèmes de blue-screen et cela devient plus que gênant.
Ceux-ci ne se manifestent qu'à l'allumage du PC, m'obligeant à éteindre celui-ci et à le rallumer dans la foulée, à la suite de cette manip aucun problème, les blue-screens ne sont pas intempestifs, uniquement à l'allumage.
Ci-joint le CR de bluescreenview de ce jour, je ne suis pas expert mais je crois comprendre que le problème vient du driver kernel (en même temps je ne fais que lire, je ne sais pas ce que c'est ...
Mes drivers sont tous à jour, que faut-il faire ?
Help me !
==================================================
Dump File : 062811-18080-01.dmp
Crash Time : 28/06/2011 18:13:08
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`023ef770
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7fd00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\062811-18080-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274 536
==================================================

Bonsoir,
j'ai exactement le même problème: mon PC plante un démarrage sur deux.
J'allume le PC puis celui-ci plante et reboot. Viens l'écran qui demande si l'on veut démarrer en safe mode ou normal, je choisis normal et tout marche bien (pendant plusieurs heures). Puis j'éteins le PC normalement. Puis au prochain allumage il plante quasiment au démarrage etc...
J'ai le même message d'erreur
Caused By Address : ntoskrnl.exe+7fd00 avec Event ID 41

Pour info j'utilise Windows 7 professionnel 64bit avec 8Gb de RAM (RAM qui passe 2 passes de Memest86)
Je pensais que cela venait de la carte graphique ou de son driver mais comment expliquer que un démarrage sur deux tout fonctionne parfaitement et sur plusieurs heures ???
Mon alimentation est forcément suffisante (Seasonic X760 pour config I5 2500K + Corsair H60 + Asus P8H67-i deluxe + Gskill 8Gb + MSI lightning HD6970 et WIndows 7 64 bit installé sur SSD M4 64GB)

Pour info ce problème persiste même après une clean installation de Windows 7. Mes drivers aussi sont à jour (seule exception: le driver AHCI du SSD M4 qui est celui de microsoft car le driver Intel RST a des problèmes avec le M4 )

Je pense avoir remarqué qu'à chaque boot qui va planter, la luminosité à l'air moins élevé que lorsque le PC reboot et fonctionne.

Je serai aussi très intéressé par une proposition de solution.

Merci d'avance.

Content de voir que je ne suis pas le seul avec ce problème, par contre pas beaucoup de solution en perspective ...
J'en ai vraiment marre de tout ça, je ne sais pas quoi faire, j'ai essayé le formatage, tous mes drivers sont également à jour, mes RAM sont ok .... que faire.
Ci-joint le dernier rapport de whocrash si quelqu'un avec des propositions passe dans le coin qu'il n'hésite surtout pas ...

System Information (local)
--------------------------------------------------------------------------------

computer name: WE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6433464320 total
VM: 2147352576, free: 1989750784



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 24/07/2011 17:32:12 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, 0xFFFFF960001A68B4, 0xFFFFF8800C579E00, 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 Sun 24/07/2011 17:30:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072411-14430-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031A85AD, 0xFFFFF8800BFC0720, 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 21/07/2011 10:46:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-18532-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80023FBEF0, 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 which cannot be identified at this time.


On Thu 21/07/2011 10:45:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-14336-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000316055E, 0xFFFFF8800C346720, 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 21/07/2011 10:43:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-14398-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF6FC54018ED8, 0x0, 0xFFFFF80002E98288, 0x2)
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 which cannot be identified at this time.


On Thu 21/07/2011 10:41:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-14476-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA88078B7F18, 0x2, 0x0, 0xFFFFF80002F08A24)
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 which cannot be identified at this time.


On Thu 21/07/2011 10:40:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-14398-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x5002, 0xFFFFF70001080000, 0x11FD, 0x811FEFFFFFFFE)
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 which cannot be identified at this time.


On Thu 21/07/2011 10:38:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-15116-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80023EF470, 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 which cannot be identified at this time.


On Thu 21/07/2011 10:36:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-14976-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF6FC54026610, 0x0, 0xFFFFF80002EE6288, 0x2)
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 which cannot be identified at this time.


On Thu 21/07/2011 10:35:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-15178-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000300DA9B, 0xFFFFF8800CA8CF60, 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 21/07/2011 10:33:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-14508-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF9063FBEDE70, 0x1, 0xFFFFF80002ECC924, 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 which cannot be identified at this time.


On Thu 21/07/2011 10:31:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-15147-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000316B55E, 0xFFFFF8800C4C2720, 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 21/07/2011 10:30:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-14554-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80023D8640, 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 which cannot be identified at this time.


On Thu 21/07/2011 10:28:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-15210-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000317C77C, 0xFFFFF8800CE41030, 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 Wed 20/07/2011 16:05:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072011-16926-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x1A (0x5002, 0xFFFFF781C0000000, 0x95CD, 0x895CEFFFFFFFE)
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 which cannot be identified at this time.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\071811-17862-01.dmp

salut les fou ds ecran bleu...
fait ds test avec 1 seul barette memoire et undeclocker vos ram cad a ds frequence plus basse que celle prevus par vos ram
et tiendez moi au jus....
installer sa " http://www.hwinfo.com/download32.html " et verffier vos timing memoire ...
++