BSOD qui m'enquiquine.
Résolu
TeePee2
Messages postés
4
Date d'inscription
Statut
Membre
Dernière intervention
-
TeePee2 Messages postés 4 Date d'inscription Statut Membre Dernière intervention -
TeePee2 Messages postés 4 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
Avant de poser ma question sur ce forum, j'ai beaucoup hésité car j'ai préféré cherché la solution par moi même afin de "faire mes devoirs", mais je n'y arrive pas.
J'ai un BSOD assez souvent, surtout lorsque je joue à un jeu en plein écran, lors d'un retour au bureau, ou même parfois quand je navigue sur internet.
Du coup j'en ai un peu ma claque et je me demandais si quelqu'un pouvait m'aider.
J'ai une carte graphique ATI radeon HD 5770 1Go, 16Go de Ram, je tourne sur Win7 Pro 64bits et j'ai un AMD Phenom II X4 965 3.40Ghz
Pour mettre toutes les chances de mon côté voici une photo de mon cher BSOD :
et une copie de ce cher mini dump :
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800'0365f000 PsLoadedModuleList = 0xfffff800'0389be70
Debug session time: Thu Sep 11 17:12:57.876 2014 (UTC - 4:00)
System Uptime: 0 days 4:36:35.562
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000232941, Address of the instruction which caused the bugcheck
Arg3: fffff880056d1150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
win32k!MulAssociateSharedSurface+11
fffff960'00232941 488b4118 mov rax,qword ptr [rcx+18h]
CONTEXT: fffff880056d1150 -- (.cxr 0xfffff880056d1150)
rax=fffff900c01b4c70 rbx=fffff900c0aac4d0 rcx=0000000000000000
rdx=0000000080000840 rsi=fffff900c0aac9a8 rdi=fffff900c0aac568
rip=fffff96000232941 rsp=fffff880056d1b20 rbp=0000000030121207
r8=0000000030121207 r9=8000000000000001 r10=0000000000000000
r11=fffff880056d1b48 r12=fffff900c010a010 r13=0000000080000840
r14=0000000003cb2b60 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!MulAssociateSharedSurface+0x11:
fffff960'00232941 488b4118 mov rax,qword ptr [rcx+18h] ds:002b:00000000'00000018=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff960001dd365 to fffff96000232941
STACK_TEXT:
fffff880'056d1b20 fffff960'001dd365 : 00000000'00000000 00000000'30121207 00000000'0293f7c0 fffff8a0'01f5b000 : win32k!MulAssociateSharedSurface+0x11
fffff880'056d1b50 fffff960'00200749 : 00000000'00000001 fffff880'056d1ca0 00000000'0293f7c0 00000000'00008385 : win32k!GreSetRedirectionSurfaceSignaling+0x125
fffff880'056d1ba0 fffff800'036cdad3 : fffffa80'0fecab60 00000000'00000000 00000000'00000020 00000000'00000000 : win32k!NtGdiHLSurfSetInformation+0x209
fffff880'056d1c20 000007fe'fd8b4efa : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000'0293f6f8 00000000'00000000 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : 0x7fe'fd8b4efa
FOLLOWUP_IP:
win32k!MulAssociateSharedSurface+11
fffff960'00232941 488b4118 mov rax,qword ptr [rcx+18h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!MulAssociateSharedSurface+11
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5130212e
STACK_COMMAND: .cxr 0xfffff880056d1150 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!MulAssociateSharedSurface+11
BUCKET_ID: X64_0x3B_win32k!MulAssociateSharedSurface+11
Followup: MachineOwner
---------
Merci encore,
si quelqu'un peut m'aider ce serait vraiment cool.
Avant de poser ma question sur ce forum, j'ai beaucoup hésité car j'ai préféré cherché la solution par moi même afin de "faire mes devoirs", mais je n'y arrive pas.
J'ai un BSOD assez souvent, surtout lorsque je joue à un jeu en plein écran, lors d'un retour au bureau, ou même parfois quand je navigue sur internet.
Du coup j'en ai un peu ma claque et je me demandais si quelqu'un pouvait m'aider.
J'ai une carte graphique ATI radeon HD 5770 1Go, 16Go de Ram, je tourne sur Win7 Pro 64bits et j'ai un AMD Phenom II X4 965 3.40Ghz
Pour mettre toutes les chances de mon côté voici une photo de mon cher BSOD :
et une copie de ce cher mini dump :
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800'0365f000 PsLoadedModuleList = 0xfffff800'0389be70
Debug session time: Thu Sep 11 17:12:57.876 2014 (UTC - 4:00)
System Uptime: 0 days 4:36:35.562
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000232941, Address of the instruction which caused the bugcheck
Arg3: fffff880056d1150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
win32k!MulAssociateSharedSurface+11
fffff960'00232941 488b4118 mov rax,qword ptr [rcx+18h]
CONTEXT: fffff880056d1150 -- (.cxr 0xfffff880056d1150)
rax=fffff900c01b4c70 rbx=fffff900c0aac4d0 rcx=0000000000000000
rdx=0000000080000840 rsi=fffff900c0aac9a8 rdi=fffff900c0aac568
rip=fffff96000232941 rsp=fffff880056d1b20 rbp=0000000030121207
r8=0000000030121207 r9=8000000000000001 r10=0000000000000000
r11=fffff880056d1b48 r12=fffff900c010a010 r13=0000000080000840
r14=0000000003cb2b60 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!MulAssociateSharedSurface+0x11:
fffff960'00232941 488b4118 mov rax,qword ptr [rcx+18h] ds:002b:00000000'00000018=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff960001dd365 to fffff96000232941
STACK_TEXT:
fffff880'056d1b20 fffff960'001dd365 : 00000000'00000000 00000000'30121207 00000000'0293f7c0 fffff8a0'01f5b000 : win32k!MulAssociateSharedSurface+0x11
fffff880'056d1b50 fffff960'00200749 : 00000000'00000001 fffff880'056d1ca0 00000000'0293f7c0 00000000'00008385 : win32k!GreSetRedirectionSurfaceSignaling+0x125
fffff880'056d1ba0 fffff800'036cdad3 : fffffa80'0fecab60 00000000'00000000 00000000'00000020 00000000'00000000 : win32k!NtGdiHLSurfSetInformation+0x209
fffff880'056d1c20 000007fe'fd8b4efa : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000'0293f6f8 00000000'00000000 : 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : 0x7fe'fd8b4efa
FOLLOWUP_IP:
win32k!MulAssociateSharedSurface+11
fffff960'00232941 488b4118 mov rax,qword ptr [rcx+18h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!MulAssociateSharedSurface+11
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5130212e
STACK_COMMAND: .cxr 0xfffff880056d1150 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!MulAssociateSharedSurface+11
BUCKET_ID: X64_0x3B_win32k!MulAssociateSharedSurface+11
Followup: MachineOwner
---------
Merci encore,
si quelqu'un peut m'aider ce serait vraiment cool.
A voir également:
- BSOD qui m'enquiquine.
- Bsod - Guide
- Kb5063060 bsod - Guide
- Bsod irql_not_less_or_equal ntoskrnl exe ✓ - Forum Windows 8 / 8.1
- Memory management bsod - Forum Windows 10
- Problème BSOD !!! - Forum Matériel & Système
3 réponses
bjr
le souci ,ont ne voit pas la numéros sur ton ,bleu screen
pour vraiment savoir si ça vient d un pilote ou matérielle
teste avec ça
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
autrement tu peut lire tout ça aussi
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/#logiciels-d-aide-au-diagnostic
le souci ,ont ne voit pas la numéros sur ton ,bleu screen
pour vraiment savoir si ça vient d un pilote ou matérielle
teste avec ça
https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/
autrement tu peut lire tout ça aussi
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/#logiciels-d-aide-au-diagnostic
SLt,
ça ne viendrait pas d'un thème qui bug?
Tu as essayé de désactiver les thèmes? Et Aéro pour voir?
ça ne viendrait pas d'un thème qui bug?
Tu as essayé de désactiver les thèmes? Et Aéro pour voir?
Ah super, merci de l'info, du coup j'ai installé who crashed et voila ce qu'il me dis :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 15/09/2014 23:56:10 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x7FEE9066F1A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000302945, 0xFFFFF880074E7150, 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.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_SERVICE_EXCEPTION
On Thu 11/09/2014 21:12:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091114-20763-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x232941)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000232941, 0xFFFFF880056D1150, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Tue 21/01/2014 09:30:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-19827-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600035260D)
Bugcheck code: 0x50 (0xFFFFF900C06A0310, 0x0, 0xFFFFF9600035260D, 0x0)
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 that cannot be identified at this time.
Tout en bas dans la conclusion il me conseille de regarder les mises a jour du driver
atikmpag.sys Advanced Micro Devices, Inc. AMD driver
du coup cela à t'il à voir avec ma carte graphique ATI Radeon?
Merci d'avance
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 15/09/2014 23:56:10 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x7FEE9066F1A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000302945, 0xFFFFF880074E7150, 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.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_SERVICE_EXCEPTION
On Thu 11/09/2014 21:12:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091114-20763-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x232941)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000232941, 0xFFFFF880056D1150, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Tue 21/01/2014 09:30:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-19827-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600035260D)
Bugcheck code: 0x50 (0xFFFFF900C06A0310, 0x0, 0xFFFFF9600035260D, 0x0)
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 that cannot be identified at this time.
Tout en bas dans la conclusion il me conseille de regarder les mises a jour du driver
atikmpag.sys Advanced Micro Devices, Inc. AMD driver
du coup cela à t'il à voir avec ma carte graphique ATI Radeon?
Merci d'avance