FORUM D’ENTRAIDE INFORMATIQUE (FEI)Site d’assistance et de sécurité informatique

[humanraph]

Bonjour à tous, et merci à ceux qui consacreront un peu de leur temps à m'aider.


Mon problème est le suivant:

Depuis le 28/05/2013, j'ai de nombreux BSOD sur un PC qui marchait parfaitement auparavant.
Je n'ai malheureusement pas pu effectuer de récupération de système car celle-ci n'était pas configurée.

Je ne parviens vraiment pas à localiser la source de mes problèmes qui sont les suivants:

- plantages du PC intempestifs qui arrivent un peu n'importe quand mais particulièrement lorsque j'utilise beaucoup de ressources et lorsque j'installe un gros logiciel genre un jeu vidéo ou un CSM (joomla, microsoft webmatrix). En moyenne un à 2 plantages par jour.

- beaucoup de fonctions windows ne fonctionnent pas, n'arrivent pas à s'installer ou coupent régulièrement

- la réparation de windows  ne fonctionne pas. Je l'ai toutefois réinstallé 2 fois. J'ai eu à chaque fois l'impression qu'il était plus stable jusqu'à la remise en marche de mes disques durs de données et l'installation de logiciels qui à chaque fois ont provoqué de nouveaux BSOD.

Ma configuration

System Information
OS name:  Microsoft Windows 7 Édition Familiale Premium
OS version:  6.1.7601 Service Pack 1 7601
System name:  RAPH-PC
System manufacturer:  MSI
System model:  MS-7758
Processor:  GenuineIntel Intel64 Family 6 Model 58 Stepping 9 3.401  GHz
BIOS:  American Megatrends Inc., V2.10

Intel® Rapid Storage Technology enterprise Information
Kit installed:  12.8.0.1016
User interface version:  12.8.0.1016
Language:  English (United States)
Driver version:  12.8.0.1016
ISDI version:  12.8.0.1016

Storage System Information
Controller name:  Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller
Type:  SATA
Mode:  AHCI
Number of SATA ports:  5
Number of volumes:  0
Number of spares:  0
Number of available disks:  4
Rebuild on Hot Plug:  Disabled
Manufacturer:  32902
Model number:  7682
Product revision:  4
Direct attached disk:  S14CNEACB51946M
Direct attached disk:  Z3T7ZZB4
Direct attached disk:  WD-WCAUF2728668
Direct attached disk:  WD-WCAUF0482078

Disk on Controller 0, Port 0
Status:  Normal
Type:  SATA SSD
Location type:  Internal
Size:  112 GB
System disk:  Yes  
Disk data cache:  Enabled
Command queuing:  NCQ
SATA transfer rate: 6 Gb/s
Model:  Samsung SSD 840 Series                  
Serial number:  S14CNEACB51946M
SCSI device ID:  0
Firmware:  DXT08B0Q
Physical sector size:  512 Bytes
Logical sector size:  512 Bytes

Disk on Controller 0, Port 2
Status:  Normal
Type:  SATA disk
Location type:  Internal
Size:  466 GB
System disk:  No
Disk data cache:  Enabled
Command queuing:  NCQ
SATA transfer rate: 3 Gb/s
Model:  ST500DM002-1BD142                      
Serial number:  Z3T7ZZB4
SCSI device ID:  2
Firmware:  KC45    
Physical sector size:  4096 Bytes
Logical sector size:  512 Bytes

Disk on Controller 0, Port 3
Status:  Normal
Type:  SATA disk
Location type:  Internal
Size:  596 GB
System disk:  No
Disk data cache:  Enabled
Command queuing:  NCQ
SATA transfer rate: 3 Gb/s
Model:  WDC WD6400AACS-00G8B1                  
Serial number:  WD-WCAUF2728668
SCSI device ID:  3
Firmware:  05.04C05
Physical sector size:  512 Bytes
Logical sector size:  512 Bytes

Disk on Controller 0, Port 4
Status:  Normal
Type:  SATA disk
Location type:  Internal
Size:  596 GB
System disk:  No
Disk data cache:  Enabled
Command queuing:  NCQ
SATA transfer rate: 3 Gb/s
Model:  WDC WD6400AAVS-00G9B0                  
Serial number:  WD-WCAUF0482078
SCSI device ID:  4
Firmware:  05.04C05
Physical sector size:  512 Bytes
Logical sector size:  512 Bytes

ATAPI device on Controller 0, Port 1
Location type:  Internal
SATA transfer rate: 1.5 Gb/s
Model:  HL-DT-ST DVDRAM GH24NS95                
Serial number:  KD3CB594440
Firmware:  RN00  

Quelques infos complémentaires qui ont peut-être un lien avec mes problèmes:


- J'ai installé mon OS sur un disque dur SSD, et je possède 3 autres disques durs SATA de données.
- Lorsque je tente des vérifications des erreurs sur mes disques durs (clic droit sur le poste de travail / outils / vérification des disques), celles-ci prennent énormément de temps (plus de 10 heures). Cela ne me semble pas normal.
- Sur certains sites Internet, mon navigateur chrome plante souvent, alors que ce n'est pas le cas si je surfe sur un autre de mes PCs.
- Dans le passé, un de mes disques SATA, qui contenait mon OS a complètement planté. J'ai dû le formater à partir d'un autre disque et récupérer mes données grâce au logiciel ZAR (Zero Assumption Recovery) qui a créé des milliers de fichiers dans lesquels j'allais à la pêche pour parfois retrouver des fichiers intacts et souvent des fichiers illisibles.

MERCI POUR VOTRE AIDE!

Human Raph

[Invité]

Bonjour,

Pour connaitre la source et la cause de tes BSOD, il faut un utilitaire comme WhoCrashed 4.02 ou BlueScreenView

Après une analyse et un rapport, il faudra le poster.

[humanraph]

Merci Le grimpeur.

Voici le rapport de whocrashed:

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

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




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 11/08/2013 16:25:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-13977-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680003671E8, 0x5CD000013AD3B025, 0xFFFFFA800C0F10F0)
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 11/08/2013 15:27:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-15366-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x99, 0x18104C, 0x0, 0x1626CC)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 11/08/2013 01:02:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-17690-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF880010F53D1)
Bugcheck code: 0x50 (0xFFFFFA80B86831B0, 0x1, 0xFFFFF880010F53D1, 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 Sun 11/08/2013 01:02:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltFindExtraCreateParameter+0x311)
Bugcheck code: 0x50 (0xFFFFFA80B86831B0, 0x1, 0xFFFFF880010F53D1, 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 Wed 07/08/2013 13:32:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-11512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80039CE5E0, 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 Wed 07/08/2013 03:35:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-14305-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80039CE610, 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 Wed 07/08/2013 01:36:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-14570-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x196C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FF0796C, 0xFFFFF88005EC9A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.



On Mon 05/08/2013 16:42:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-17316-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80039CE5E0, 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 05/08/2013 16:35:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-15444-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800783D028, 0xFE200000, 0x4110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 Sun 04/08/2013 16:53:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080413-17846-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFF8A0603FC010, 0x0, 0xFFFFF80002E059BC, 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
--------------------------------------------------------------------------------

10 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.

[Invité]

Re,

As-tu un pc fixe

Est-ce-que tes pilotes sont tous à jour

Je vois un souci avec DirectX Graphiques MMS ainsi que les mémoires.

As-tu testé avec une barrette en moins puis l'autre et en changeant les emplacements

[humanraph]

Re,

As-tu un pc fixe OUI

Est-ce-que tes pilotes sont tous à jour OUI, j'ai fait une mise à jour grâce à l'outil présent sur ce site... mais je note encore plus de crashs depuis (au moins 5 aujourd'hui contre 1-2 d'habitude je vais essayer de reposter un rapport

Je vois un souci avec DirectX Graphiques MMS ainsi que les mémoires. oui...

As-tu testé avec une barrette en moins puis l'autre et en changeant les emplacements non

[humanraph]

Nouveau rapport (2 crashs en plus)...

Merci de votre aide

On Sun 11/08/2013 17:37:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-13384-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x21, 0xFFFFF8A00442C000, 0x17C0, 0x5F0017C0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 11/08/2013 17:29:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-13400-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80039CE610, 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 11/08/2013 16:25:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-13977-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680003671E8, 0x5CD000013AD3B025, 0xFFFFFA800C0F10F0)
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 11/08/2013 15:27:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-15366-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x99, 0x18104C, 0x0, 0x1626CC)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 11/08/2013 01:02:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-17690-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF880010F53D1)
Bugcheck code: 0x50 (0xFFFFFA80B86831B0, 0x1, 0xFFFFF880010F53D1, 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 Sun 11/08/2013 01:02:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltFindExtraCreateParameter+0x311)
Bugcheck code: 0x50 (0xFFFFFA80B86831B0, 0x1, 0xFFFFF880010F53D1, 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 Wed 07/08/2013 13:32:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-11512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80039CE5E0, 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 Wed 07/08/2013 03:35:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-14305-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80039CE610, 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 Wed 07/08/2013 01:36:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-14570-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x196C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FF0796C, 0xFFFFF88005EC9A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.



On Mon 05/08/2013 16:42:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-17316-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80039CE5E0, 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 05/08/2013 16:35:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-15444-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800783D028, 0xFE200000, 0x4110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 Sun 04/08/2013 16:53:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080413-17846-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFF8A0603FC010, 0x0, 0xFFFFF80002E059BC, 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
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

[Invité]

Re,

Test avec une seule barrette puis l'autre en redémarrant à chaque fois et en faisant ce que tu as l'habitude de faire pour voir si tu as un BSOD à chaque fois.

Tu as quoi comme carte graphique

[humanraph]

OK grimpeur je vais faire ça.
Ma carte graphique: Intel(R) HD Graphics (2112 Mo) (from Everest)

J'ai l'impression que c'est bizarre mais je n'ai que cette information dans mon gestionnaire de périphérique et à partir d'everest. Pas de nom plus précis...

[humanraph]

2 infos:
Ma carte graphique est intégrée à la carte mère (mainboard) qui est une MSI Z77A-G41
AU vu des nombreux BSOD, j'ai désactivé le redémarrage automatique de windows, mais pour faire le test des barrettes de RAM, dois-je le réactiver grimpeur?

[Invité]

Oui, laisse le redémarrage désactivé, et test avec une seule barrette (en enlevant l'alimentation du pc avant et en déchargeant celui-ci en appuyant sur le bouton power pendant trente secondes.

[humanraph]

Je vais faire ça, merci beaucoup.

Je pourrai voir les BSOD quand meme? ou une notification grâce aux dumps c'est ça?

[Invité]

Normalement la page doit ce figer avec le bsod pour pouvoir noter celui-ci.

[humanraph]

En effet! J'ai retiré la 1ère barrette.
Quelques heures sans écran bleu, et puis au bout d'un moment j'ai eu ce fameux écran (erreur de memory management).
J'ai donc maintenant remplacé cette barrette par ma 2ème barrette de RAM, dans un slot différent, et j'attends de voir...

Une chose surprenante, une fois que j'ai remplacé la barrette (en coupant l'alimentation comme tu m'as dit), le PC a fait une vérification de deux de mes disques (SATA) qui n'ont pas d'OS sans trouver d'erreurs il me semble.

[humanraph]

Bon, 24 heures sur la 2ème barrette et le PC me semble hyper stable.
J'ai pu installer un gros logiciel qui n'avait jamais voulu s'installer auparavant. Je suis hyper confiant.

Des conseils?

Merci,

HumanRaph

[Invité]

As-tu inversé les barrettes

Si problème avec les deux barrettes, la dernière rajoutée devra être changée .

Pour être sûr tu peux les tester avec memtest86.

[humanraph]

Cher grimpeur,
Je n'ai pas inversé les barrettes. Par contre depuis cette manip', je n'ai pas eu un seul écran bleu, tous mes programmes marchent, même ceux qui ne marchaient pas avant.
Je pense pouvoir considérer que mon problème est réglé et je t'envoie mille mercis.
Big free hug à toi:)

[2011N2]

Bonsoir,

Super, tant mieux pour toi.

Je passe ce sujet en résolu et je le verrouille. Tu peux mettre en valeur les messages ayant permis la résolution de ton problème comme ceci : http://www.forum-entraide-informatique. ... onse-utile

Bonne soirée et à bientôt,

Gabriel.