Bonsoir,
Je suis désespéré. Mon ordinateur m'affiche un écran totalement bleu quand je suis sur Minecraft. J'ai déjà posté des messages sur d'autres forums mais sans résultat.
Voici mon message habituel sur les forums :
"Bonsoir,
J'ai un petit souci avec mon ordinateur portable : dès que je lance une application, au bout de quelques minutes mon ordinateur m'affiche un écran (totalement) bleu. Je précise ''totalement'' parce que certains écrans bleus affichent des textes de codes. Est-ce que quelqu'un aurait une solution à me proposer ??
PS : Je suis un peu nul en informatique donc expliquez en détail, merci. "
[resolu] écran bleu
-
nardino
- Modérateurs
- Messages : 11993
- Enregistré le : 05 févr. 2007, 17:38
- Localisation : Reims
- Contact :
Re: écran bleu
Bonjour,
Télécharge WhoCrashed Home Edition 3.01 de Resplendence
Tu l'installes et tu le lances par Analyze.
Tu postes un copier-coller de ce qui apparait .
Quel sont le type et la marque de ta carte vidéo ?
@+
Télécharge WhoCrashed Home Edition 3.01 de Resplendence Tu l'installes et tu le lances par Analyze.
Tu postes un copier-coller de ce qui apparait .Quel sont le type et la marque de ta carte vidéo ?
@+
Clic sur l'image pour ouvrir le site.
Re: écran bleu
Voici le copier-coller :
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-FAMILLE
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) Duo CPU T2350 @ 1.86GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2011697152 total
VM: 2147352576, free: 1998876672
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 5/03/2011 20:19:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030511-02.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2E931)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 5/03/2011 20:19:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2E931)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 5/03/2011 14:31:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030511-01.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x3A2FA)
Bugcheck code: 0x50 (0xFFFFFFFFD5973FBE, 0x1, 0xFFFFFFFF880188B1, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
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.
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: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. PAGE_FAULT_IN_NONPAGED_AREA
On Fri 4/03/2011 21:51:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030411-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA886E)
Bugcheck code: 0x50 (0xFFFFFFFFC8CE1CCB, 0x0, 0xFFFFFFFF8EAE053F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 which cannot be identified at this time.
On Thu 24/02/2011 8:04:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini022411-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x1D72B)
Bugcheck code: 0xA (0x0, 0x1B, 0x0, 0xFFFFFFFF822BB5D5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. IRQL_NOT_LESS_OR_EQUAL
On Wed 23/02/2011 22:19:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini022311-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4AFE7)
Bugcheck code: 0x1 (0xFFFFFFFF9737249A, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 23/02/2011 21:18:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini022311-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6D3B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF97356D3B, 0xFFFFFFFF9CE25B78, 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 Sat 19/02/2011 21:38:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini021911-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x3453F)
Bugcheck code: 0x50 (0xFFFFFFFFC9ADAC9B, 0x0, 0xFFFFFFFF8E8E253F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 11/02/2011 22:39:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini021211-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6A8A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF968E6A8A, 0xFFFFFFFFA6E0DC90, 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 Thu 10/02/2011 22:30:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini021011-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x1D72B)
Bugcheck code: 0xA (0x12, 0x1B, 0x0, 0xFFFFFFFF822E45D5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. IRQL_NOT_LESS_OR_EQUAL
On Wed 9/02/2011 22:43:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020911-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x9A2B2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF9BD3FC78, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Mon 7/02/2011 22:51:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020811-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x16F62)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8F0C1F62, 0xFFFFFFFF9AE85CA8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Mon 7/02/2011 19:19:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020711-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x25EC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8E2B25EC, 0xFFFFFFFFA83E4B58, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 4/02/2011 20:23:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020411-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2A3DA)
Bugcheck code: 0xBE (0xFFFFFFFF952FE520, 0x683B3121, 0xFFFFFFFFB58F5B68, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 8/01/2011 21:49:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011011-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2265D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x308E5551, 0xFFFFFFFF9C0FB928, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
31 crash dumps have been found and analyzed. Only 15 are included in this report. 6 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
mfehidk.sys (McAfee Link Driver, McAfee, Inc.)
stkcmini.sys (Syntek USB 2.0 Video Mini Driver, Syntek)
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.
Le type et la marque de ma carte vidéo est : ATI RADEON XPRESS 1100
Je précise que mon ordinateur est un ordinateur portable. Il parait que c'est important de la préciser
System Information (local)
--------------------------------------------------------------------------------
computer name: PC-DE-FAMILLE
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) Duo CPU T2350 @ 1.86GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2011697152 total
VM: 2147352576, free: 1998876672
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 5/03/2011 20:19:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030511-02.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2E931)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 5/03/2011 20:19:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2E931)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 5/03/2011 14:31:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030511-01.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x3A2FA)
Bugcheck code: 0x50 (0xFFFFFFFFD5973FBE, 0x1, 0xFFFFFFFF880188B1, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
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.
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: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. PAGE_FAULT_IN_NONPAGED_AREA
On Fri 4/03/2011 21:51:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini030411-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA886E)
Bugcheck code: 0x50 (0xFFFFFFFFC8CE1CCB, 0x0, 0xFFFFFFFF8EAE053F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 which cannot be identified at this time.
On Thu 24/02/2011 8:04:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini022411-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x1D72B)
Bugcheck code: 0xA (0x0, 0x1B, 0x0, 0xFFFFFFFF822BB5D5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. IRQL_NOT_LESS_OR_EQUAL
On Wed 23/02/2011 22:19:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini022311-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4AFE7)
Bugcheck code: 0x1 (0xFFFFFFFF9737249A, 0x0, 0xFFFF, 0x0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 23/02/2011 21:18:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini022311-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6D3B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF97356D3B, 0xFFFFFFFF9CE25B78, 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 Sat 19/02/2011 21:38:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini021911-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x3453F)
Bugcheck code: 0x50 (0xFFFFFFFFC9ADAC9B, 0x0, 0xFFFFFFFF8E8E253F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 11/02/2011 22:39:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini021211-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6A8A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF968E6A8A, 0xFFFFFFFFA6E0DC90, 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 Thu 10/02/2011 22:30:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini021011-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x1D72B)
Bugcheck code: 0xA (0x12, 0x1B, 0x0, 0xFFFFFFFF822E45D5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. IRQL_NOT_LESS_OR_EQUAL
On Wed 9/02/2011 22:43:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020911-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x9A2B2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF9BD3FC78, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Mon 7/02/2011 22:51:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020811-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x16F62)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8F0C1F62, 0xFFFFFFFF9AE85CA8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Mon 7/02/2011 19:19:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020711-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x25EC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8E2B25EC, 0xFFFFFFFFA83E4B58, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 4/02/2011 20:23:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini020411-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2A3DA)
Bugcheck code: 0xBE (0xFFFFFFFF952FE520, 0x683B3121, 0xFFFFFFFFB58F5B68, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 8/01/2011 21:49:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011011-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2265D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x308E5551, 0xFFFFFFFF9C0FB928, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
31 crash dumps have been found and analyzed. Only 15 are included in this report. 6 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
mfehidk.sys (McAfee Link Driver, McAfee, Inc.)
stkcmini.sys (Syntek USB 2.0 Video Mini Driver, Syntek)
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.
Le type et la marque de ma carte vidéo est : ATI RADEON XPRESS 1100
Je précise que mon ordinateur est un ordinateur portable. Il parait que c'est important de la préciser
-
nardino
- Modérateurs
- Messages : 11993
- Enregistré le : 05 févr. 2007, 17:38
- Localisation : Reims
- Contact :
Re: écran bleu
Bonjour
La première démarche consistera à mettre à jour les pilotes graphiques.
Pour cela tu peux te rendre sur ce site
http://www.touslesdrivers.com/index.php?v_page=29
Tu installe l'activeX avec Internet Explorer ou maconfig.com avec Firefox ou autre navigateur.
N'installe pas les pilotes bêta, choisis les WHQL (certifié Microsoft)
@+
La première démarche consistera à mettre à jour les pilotes graphiques.
Pour cela tu peux te rendre sur ce site
http://www.touslesdrivers.com/index.php?v_page=29
Tu installe l'activeX avec Internet Explorer ou maconfig.com avec Firefox ou autre navigateur.
N'installe pas les pilotes bêta, choisis les WHQL (certifié Microsoft)
@+
Clic sur l'image pour ouvrir le site.
Re: écran bleu
Oui, mais je ne comprends pas très bien ce que je dois faire. Il y a plusieurs mises à jour (Atheros Communications L2 Fast Ethernet , ATI Technologies Inc SB600 Non-Raid-5 SATA , Realtek Semiconductor Corp. Mass Storage Device (USB Mass Storage Device)). J'ai lu qu'il fallait peut-être désinstaller l'ancien pilote, etc
Je précise, je ne suis pas spécialement fort en informatique .. Peux tu m'aider ? (tu en fais déjà beaucoup
)
Je précise, je ne suis pas spécialement fort en informatique .. Peux tu m'aider ? (tu en fais déjà beaucoup
)-
nardino
- Modérateurs
- Messages : 11993
- Enregistré le : 05 févr. 2007, 17:38
- Localisation : Reims
- Contact :
Re: écran bleu
Bonsoir
Peux-tu me préciser ton système d'exploitation (32 ou 64 bits) ainsi que les références de ta carte graphique.
@+
Peux-tu me préciser ton système d'exploitation (32 ou 64 bits) ainsi que les références de ta carte graphique.
@+
Clic sur l'image pour ouvrir le site.
Re: écran bleu
Bonsoir,
système d'exploitation : 32 bits
Carte vidéo ATI RADEON XPRESS 1100 (128 Mo)
Moniteur Moniteur Plug-and-Play générique
système d'exploitation : 32 bits
Carte vidéo ATI RADEON XPRESS 1100 (128 Mo)
Moniteur Moniteur Plug-and-Play générique
-
nardino
- Modérateurs
- Messages : 11993
- Enregistré le : 05 févr. 2007, 17:38
- Localisation : Reims
- Contact :
Re: écran bleu
Bonsoir
Voici le pilote pour ta carte graphique intégrée.
http://support.amd.com/us/gpudownload/w ... ng=English
Tu le télécharges et tu l'installes, après avoir désinstallé celui qui est en place.
@+
Voici le pilote pour ta carte graphique intégrée.
http://support.amd.com/us/gpudownload/w ... ng=English
Tu le télécharges et tu l'installes, après avoir désinstallé celui qui est en place.
@+
Clic sur l'image pour ouvrir le site.
Re: écran bleu
Ok, donc je résume. Je télécharge ce pilote ; je désinstalle celui de mon ordinateur ; j'installe le pilote téléchargé ; je redémarre mon ordinateur. C'est bien ça ??
NB : Je ne sais pas si tu as fait attention que mon ordinateur était un ordi portable. J'ai lu sur d'autres sites que les pilotes étaient différents (pc fixe et portable).
Aussi, il n'y a aucun risque de désinstaller la carte graphique ??
NB : Je ne sais pas si tu as fait attention que mon ordinateur était un ordi portable. J'ai lu sur d'autres sites que les pilotes étaient différents (pc fixe et portable).
Aussi, il n'y a aucun risque de désinstaller la carte graphique ??
-
nardino
- Modérateurs
- Messages : 11993
- Enregistré le : 05 févr. 2007, 17:38
- Localisation : Reims
- Contact :
Re: écran bleu
Bonsoir,
"Je télécharge ce pilote ; je désinstalle celui de mon ordinateur ; je redémarre mon ordinateur; j'installe le pilote téléchargé ."
Avec Windows 7 pas de problème . En fait dans ton cas il s'agit d'un chipset graphique intégré à la carte-mère.
Je suis allé le chercher chez AMD.
@+
"Je télécharge ce pilote ; je désinstalle celui de mon ordinateur ; je redémarre mon ordinateur; j'installe le pilote téléchargé ."
Avec Windows 7 pas de problème . En fait dans ton cas il s'agit d'un chipset graphique intégré à la carte-mère.
Je suis allé le chercher chez AMD.
@+
Clic sur l'image pour ouvrir le site.
Re: écran bleu
Bonjour,
Je n'ai pas Windows 7
Est-ce un souci ? Je sais que quasiment tout le monde est avec ça 
Je n'ai pas Windows 7
Est-ce un souci ? Je sais que quasiment tout le monde est avec ça -
nardino
- Modérateurs
- Messages : 11993
- Enregistré le : 05 févr. 2007, 17:38
- Localisation : Reims
- Contact :
Re: écran bleu
Bonjour
Avec Vista non plus pas de problème.
@+
Avec Vista non plus pas de problème.
@+
Clic sur l'image pour ouvrir le site.
Re: écran bleu
Bonjour,
J'ai désinstallé l'ancienne carte graphique pour mettre la nouvelle. Mais Il y a un petit souci car Minecraft m'indique ceci :
Bad video card drivers!
-----------------------
Minecraft was unable to start because it failed to find an accelerated OpenGL mode.
This can usually be fixed by updating the video card drivers.
--- BEGIN ERROR REPORT 7fe0271 --------
Generated 7/03/11 13:22
Minecraft: Minecraft Beta 1.3_01
OS: Windows Vista (x86) version 6.0
Java: 1.6.0_24, Sun Microsystems Inc.
VM: Java HotSpot(TM) Client VM (mixed mode), Sun Microsystems Inc.
LWJGL: 2.4.2
[failed to get system properties (java.lang.NullPointerException)]
org.lwjgl.LWJGLException: Pixel format not accelerated
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:185)
at org.lwjgl.opengl.Display.createWindow(Display.java:311)
at org.lwjgl.opengl.Display.create(Display.java:856)
at org.lwjgl.opengl.Display.create(Display.java:784)
at org.lwjgl.opengl.Display.create(Display.java:765)
at net.minecraft.client.Minecraft.a(SourceFile:260)
at net.minecraft.client.Minecraft.run(SourceFile:632)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT ea399cec ----------
Et lorsque je regarde une vidéo, l'ordinateur m'indique ceci : Le pilote d'affichage R300 ne répondait plus et a été récupéré correctement (ça crée des coupures ..)
EDIT : J'ai réussi à régler le problème. Merci de ton aide
J'ai désinstallé l'ancienne carte graphique pour mettre la nouvelle. Mais Il y a un petit souci car Minecraft m'indique ceci :
Bad video card drivers!
-----------------------
Minecraft was unable to start because it failed to find an accelerated OpenGL mode.
This can usually be fixed by updating the video card drivers.
--- BEGIN ERROR REPORT 7fe0271 --------
Generated 7/03/11 13:22
Minecraft: Minecraft Beta 1.3_01
OS: Windows Vista (x86) version 6.0
Java: 1.6.0_24, Sun Microsystems Inc.
VM: Java HotSpot(TM) Client VM (mixed mode), Sun Microsystems Inc.
LWJGL: 2.4.2
[failed to get system properties (java.lang.NullPointerException)]
org.lwjgl.LWJGLException: Pixel format not accelerated
at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method)
at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52)
at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:185)
at org.lwjgl.opengl.Display.createWindow(Display.java:311)
at org.lwjgl.opengl.Display.create(Display.java:856)
at org.lwjgl.opengl.Display.create(Display.java:784)
at org.lwjgl.opengl.Display.create(Display.java:765)
at net.minecraft.client.Minecraft.a(SourceFile:260)
at net.minecraft.client.Minecraft.run(SourceFile:632)
at java.lang.Thread.run(Unknown Source)
--- END ERROR REPORT ea399cec ----------
Et lorsque je regarde une vidéo, l'ordinateur m'indique ceci : Le pilote d'affichage R300 ne répondait plus et a été récupéré correctement (ça crée des coupures ..)
EDIT : J'ai réussi à régler le problème. Merci de ton aide
-
nardino
- Modérateurs
- Messages : 11993
- Enregistré le : 05 févr. 2007, 17:38
- Localisation : Reims
- Contact :
Re: écran bleu
Bonjour
Cela serait sympa de dire comment tu as résolu ton problème
@+
Cela serait sympa de dire comment tu as résolu ton problème
@+
Clic sur l'image pour ouvrir le site.
Re: écran bleu
Bonjour,
j'ai redémarré une nouvelle fois mon ordinateur. A ce moment là, une fenêtre s'est ouverte pour me proposer d'installer les drivers adéquats
J'ai du redémarrer une fois encore l'ordinateur ... depuis, je n'ai plus aucun problème (ne parlons pas trop vite 
).
Merci beaucoup de ton aide. Bonne journée,
j'ai redémarré une nouvelle fois mon ordinateur. A ce moment là, une fenêtre s'est ouverte pour me proposer d'installer les drivers adéquats
J'ai du redémarrer une fois encore l'ordinateur ... depuis, je n'ai plus aucun problème (ne parlons pas trop vite ). Merci beaucoup de ton aide. Bonne journée,