Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY

[Invité sdivine]

Bonjour, j'ai suivi le conseil que vous avez donner plus haut et jai fais lanalyse. ceci est le resultat . cela fait 2 fois que mon ordi plante et je veux savoir ce qui se passe et japprécirais énormément votre aide précieuse !!!

 

Merci

 

 

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

Home Edition Notice

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

 

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

 

Click here for more information on the professional edition.

Click here to buy the the professional edition of WhoCrashed.

 

 

 

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

System Information (local)

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

 

computer name: STÉPHANIE-PC

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

windows dir: C:\Windows

CPU: AuthenticAMD AMD Athlon II Dual-Core M320 AMD586, level: 16

2 logical processors, active mask: 3

RAM: 4293246976 total

VM: 2147352576, free: 1978277888

 

 

 

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

Crash Dump Analysis

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

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Thu 2/9/2012 11:29:47 PM GMT your computer crashed

crash dump file: C:\Windows\Minidump\020912-32495-01.dmp

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

Bugcheck code: 0xBE (0xFFFFF8A008594DE8, 0x800000009BB83121, 0xFFFFF88003124650, 0xB)

Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY

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

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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.

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 2/9/2012 11:29:47 PM GMT your computer crashed

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

This was probably caused by the following module: fltmgr.sys (fltmgr!FltGetStreamHandleContext+0x5FF)

Bugcheck code: 0xBE (0xFFFFF8A008594DE8, 0x800000009BB83121, 0xFFFFF88003124650, 0xB)

Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY

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 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.

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 1/28/2012 5:24:36 PM GMT your computer crashed

crash dump file: C:\Windows\Minidump\012812-35864-01.dmp

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

Bugcheck code: 0x109 (0xA3A039D89AD8E7C3, 0x0, 0x9F6266D3B9B65F81, 0x101)

Error: CRITICAL_STRUCTURE_CORRUPTION

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 kernel has detected critical kernel code or data corruption.

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.

 

 

 

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

Conclusion

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

 

3 crash dumps have been found and analyzed.

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é Notpa]

Bonjour Sdivine,

 

Plutôt que de rajouter un autre problème à un problème déjà existant et assez ancien, je te conseille de créer un nouveau sujet et de copier/coller ton résultat d'ici dans ton nouveau sujet. D'autant plus qu'il ne s'agit pas de mêmes raisons :

 

le sujet actuel concerne 0x1E Error: KMODE_EXCEPTION_NOT_HANDLED

et tu as 0xBE Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY

 

Merci de t'inscrire avant de créer ce nouveau sujet. C'est gratos et apporte plein d'avantages !

 

A bientôt sur l'autre sujet.

 

Notpa

[Dylav]

J'ai désimbriqué Sdivine, qui bénéficie désormais d'un sujet à part entière…

 

Le sujet d'origine était « Écran bleu sous Windows 7 et plantages aléatoires ».

 

 

[Invité Notpa]

Sdivine,

 

Plusieurs pistes à explorer :

 

- problème de mémoire : article Microsoft

- problème de driver : article PcGuide

- etc (surtout de problèmes de drivers vidéos)

 

La plupart des sites (merci Google !) indiquent un problème de driver inadapté ou corrompu.

 

On a donc besoin de savoir quels périphériques tu utilises (marque, type, modèle) :

- carte vidéo

- carte son

- carte réseau

 

et quelles sont les versions des drivers installés. Si tu ne sais pas, aide-toi de Everest Home Edition. Il t'apportera les réponses à mes questions.

 

A+

Notpa