Problème pc écran bleu

Locky44 Messages postés 2 Statut Membre -  
Locky44 Messages postés 2 Statut Membre -
Bonjour,

J'ai depuis un petit moment mon PC qui plante avec l'apparition de l'écran bleu. J'ai effectué plusieurs recherches puis une analyse avec Whocrashed mais la je commence à être largué.

Si quelqu'un pouvait m'éclairer sur ce que signifie le rapport ci-dessous et m'aider à résoudre mon problème j'en serais ravis :).

Par avance merci.


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

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M4A79XTD EVO
CPU: AuthenticAMD AMD Phenom(tm) II X2 555 Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4294103040 total

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 02/03/2015 18:16:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030215-27284-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xBE (0xFFFFF88001BC8700, 0x8000000124B00121, 0xFFFFF880057E7290, 0xA)
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 that cannot be identified at this time.



On Mon 02/03/2015 18:16:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2899)
Bugcheck code: 0xBE (0xFFFFF88001BC8700, 0x8000000124B00121, 0xFFFFF880057E7290, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
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 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 that cannot be identified at this time.



On Mon 23/02/2015 22:41:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022315-21699-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0xA (0xFFFFF880049B9B80, 0x2, 0x0, 0xFFFFF80002E66006)
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 that cannot be identified at this time.



On Tue 20/01/2015 17:26:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012015-28828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF80002E9921F)
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 that cannot be identified at this time.



On Tue 13/01/2015 18:50:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011315-29187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFCC00000001C, 0x0, 0xFFFFF80002EC1E9A, 0x7)
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.
A voir également:

2 réponses

Gourlae Messages postés 162 Statut Membre 17
 
Salut!
Visiblement c'est un problème de driver. As-tu mis ceux de ta carte graphique à jour, ou changé d'antivirus(ou encore mis à jour d'autres trucs récemment)?
C'est peut-être aussi (beaucoup moins sûr) un problème de disque dur.
Si c'est le cas, fais windows +R ->tapes CMD et ensuite chkdsk /f /r C:
Ça peut être aussi (peu sûr encore) la ram: tu peux la tester grâce à memtest86+ en bootant ce soft sur une clé usb. Tu ne pourras ne tester qu'une barrette par une. Il y a aussi le le diagnostic de mémoire windows sur windows 7 et 8 (je sais pas sinon)
J'espère t'avoir aidé!
0
Locky44 Messages postés 2 Statut Membre
 
J'ai fait des mises à jour de mes drivers après que l'écran bleu ai commencé à apparaître pensant que ça pouvait être ça.
Sinon je ne vois pas de mise à jour qui pourrait être la cause c'est arrivé comme ça sans raison apparente.
Mais je vais regarder tous ça plus testé la ram comme tu me propose.
Merci je repasserais dire ce qu'il en ai ;)
0