Bluescreen à répétition(Résolu)

[Marvindu13]

Bonjour, ça fait 2 semaine que mon nouvelle ordinateur a des bluescreen a repetition.

mon ordi:

- Processeur AMD Phenom II X4 955 Black Edition

-Mémoire DDR3 4 Go

-Disque dur 1 To Sata II

-Carte mère MSI GF615M-P33

-Carte graphique Sapphire Radeon HD 6870,

-Windows 7

Je ne suis pas tres doué en informatique , je suis allez sur des dizaines et des dizaines de forum mais je ne trouve pas la solution donc je vous fait un rapport de whocrashed j'espére que ça peut vous aider a trouver mon probleme.merci d'avance

 

System Information (local)

--------------------------------------------------------------------------------

 

computer name: RIMCO-PC

windows version: Windows 7 Service Pack 1, 6.1, build: 7601

windows dir: C:\Windows

CPU: AuthenticAMD AMD Phenom II X4 955 Processor AMD586, level: 16

4 logical processors, active mask: 15

RAM: 3220430848 total

VM: 2147352576, free: 1992110080

 

 

 

--------------------------------------------------------------------------------

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Sun 04/09/2011 16:42:47 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)

Bugcheck code: 0x1A (0x5003, 0xFFFFFFFF8BE00000, 0x334D, 0x334009A)

Error: MEMORY_MANAGEMENT

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.

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: ntkrpamp.exe .

Google query: ntkrpamp.exe MEMORY_MANAGEMENT

 

 

 

 

On Sun 04/09/2011 00:23:54 GMT your computer crashed

crash dump file: C:\Windows\Minidump\090411-13962-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0xCF494)

Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)

Error: UNEXPECTED_KERNEL_MODE_TRAP

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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

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 Sat 03/09/2011 18:17:18 GMT your computer crashed

crash dump file: C:\Windows\Minidump\090311-15740-01.dmp

This was probably caused by the following module: volsnap.sys (volsnap+0x11753)

Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFFFFF877AA753)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\volsnap.sys

product: Système d’exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote de cliché instantané du volume

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.

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 Sat 03/09/2011 14:34:49 GMT your computer crashed

crash dump file: C:\Windows\Minidump\090311-15054-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0x7D5E1)

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF97C9D5E1, 0xFFFFFFFF959C2BC8, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

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 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 02/09/2011 01:47:32 GMT your computer crashed

crash dump file: C:\Windows\Minidump\090211-15475-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)

Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFA2086A7C, 0xFFFFFFFFA2086660, 0xFFFFFFFF8B2D14BD)

Error: NTFS_FILE_SYSTEM

file path: C:\Windows\system32\drivers\ntfs.sys

product: Système d’exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote du système de fichiers NT

Bug check description: This indicates a problem occurred in the NTFS file system.

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 02/09/2011 01:41:47 GMT your computer crashed

crash dump file: C:\Windows\Minidump\090211-15444-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEEB4)

Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x3DC, 0x3E00B8)

Error: MEMORY_MANAGEMENT

file path: C:\Windows\system32\ntkrnlpa.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 Mon 29/08/2011 01:27:39 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082911-13806-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x32492B)

Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85E9A8FC, 0x0, 0x0)

Error: WHEA_UNCORRECTABLE_ERROR

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Mon 29/08/2011 00:40:23 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082911-14726-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEEB4)

Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x3977, 0x3979EEE)

Error: MEMORY_MANAGEMENT

file path: C:\Windows\system32\ntkrnlpa.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 Sun 28/08/2011 15:18:42 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082811-17565-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x120C6B)

Bugcheck code: 0x19 (0x20, 0xFFFFFFFF87FA3674, 0xFFFFFFFF87FA3694, 0x8040000)

Error: BAD_POOL_HEADER

file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.

 

 

On Sun 28/08/2011 00:35:18 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082811-13603-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3DB)

Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)

Error: MEMORY_MANAGEMENT

file path: C:\Windows\system32\ntkrnlpa.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 Fri 26/08/2011 21:50:48 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082611-16926-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0xA40DE)

Bugcheck code: 0x50 (0xFFFFFFFFFBE8F9A9, 0x1, 0xFFFFFFFF977B40DE, 0x2)

Error: PAGE_FAULT_IN_NONPAGED_AREA

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 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 which cannot be identified at this time.

 

 

On Fri 26/08/2011 21:01:28 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082611-16520-01.dmp

This was probably caused by the following module: hal.sys (hal+0x3829)

Bugcheck code: 0xBE (0xFFFFFFFF92971441, 0xFFFFFFFFB9058121, 0xFFFFFFFF8D0E86F0, 0xA)

Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY

Bug check description: This is issued if a driver attempts to write to a read-only memory segment.

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: hal.sys .

Google query: hal.sys ATTEMPTED_WRITE_TO_READONLY_MEMORY

 

 

 

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

12 crash dumps have been found and analyzed. 2 third party drivers have 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:

 

hal.sys

 

ntkrpamp.exe

 

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

 

 

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.

 

 

<config>Windows 7 / Safari 535.1</config>

Modifié le 15 septembre 2011 par Marvindu13

[Tonton]

Bonjour Marvindu13 et bienvenue sur Zébulon !

 

• On va tester la RAM avec Memtest86+.
  
• Lien & tuto :
  
• Pour que le test soit valable :
  - à effectuer à partir d'un CD bootable ou d'une clé bootable (et non à partir du système lui-même)
  - durée du test : env. 12 heures
  
• En cas d’apparition d’erreurs avant ces 12 heures, le test peut bien évidemment être arrêté

@+,

Tonton

[Marvindu13]

Ok je te remercie je vais faire ça je te tien au nouvelle

[Tonton]

OK, ça marche comme ça.

[thorgal]

Bonjour vous deux et bienvenue au petit nouveau sur le forum,

 

Je tiens à préciser que le test se fait pour chaque barrette indépendament. C'est à dire qu'il ne faut en laisser qu'une dans un port à chaque essai de Memtest. Comme cela, tu sauras quelle ram est défectueuse et les erreurs ne seront pas cachées par l'exploitation des autres barrettes pendant le test.

 

C'est relativement long comme test mais ça rend pas mal de service au final !

 

Bon courage...

[Marvindu13]

Je te remercie thorgal heuresement que je ne les pas encore fait! je vous donnerais les new du test mercredi ou jeudi.( je n'est pas de cd vierge) et les boutique sont fermée aujourdui).

[thorgal]

Pas de problème ! Fais ça bien comme il faut surtout. Déjà que c'est long, ce serait bête de mal le faire !!

 

Bon courage...

[Tonton]

Bonjour thorgal et Marvindu13,

 

Je tiens à préciser que le test se fait pour chaque barrette indépendament.

C'est précisé dans l'un des tutos dont le lien est fourni, mais c'est un point important, ce qui justifie pleinement cette remarque !

 

@ Marvindu13 : à ta dispo pour la suite dès que tu seras en possession des (précieuses) informations.

 

Bonne soirée,

Tonton

[thorgal]

Salut Tonton57,

 

Oui, tu fais le test et tu tiens au courant, si le problème persiste, je suis certain que l'ami Tonton saura trouver une autre idée à vérifier pour retrouver un fonctionnement normal.

[Marvindu13]

Salut j'ai enfin fait le test est il n'y a aucun probleme au niveau des RAM.