Erreur écran bleu Windows Vista
ach35
Messages postés
8
Statut
Membre
-
maxou2600 Messages postés 1062 Statut Membre -
maxou2600 Messages postés 1062 Statut Membre -
Bonjour,
Depuis quelques jours j'ai un plantage au niveau de Windows Vista. A n'importe quel moment mon ordinateur affiche un écran bleu et se redémarre.
J'ai fouillé un peu partout sur internet, j'ai trouvé différentes solutions que je n'arrive pas à appliquer, sauf en ce qui concerne l'option de redémarrage automatique de l'ordinateur.
Le message qui s'affiche au niveau de l'écran bleu est le suivant :
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Stop 0x00000D1
0x8F2036F2
dxgkrnl.sys
Adress 8F2036F2 base at 8F200000
Date stamp 4893b1df
Auriez-vous une solution à mon problème ?
Merci d'avance pour vos réponses.
Depuis quelques jours j'ai un plantage au niveau de Windows Vista. A n'importe quel moment mon ordinateur affiche un écran bleu et se redémarre.
J'ai fouillé un peu partout sur internet, j'ai trouvé différentes solutions que je n'arrive pas à appliquer, sauf en ce qui concerne l'option de redémarrage automatique de l'ordinateur.
Le message qui s'affiche au niveau de l'écran bleu est le suivant :
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Stop 0x00000D1
0x8F2036F2
dxgkrnl.sys
Adress 8F2036F2 base at 8F200000
Date stamp 4893b1df
Auriez-vous une solution à mon problème ?
Merci d'avance pour vos réponses.
A voir également:
- Erreur écran bleu Windows Vista
- Supprimer rond bleu whatsapp - Guide
- Ecran bleu windows 10 - Guide
- Dupliquer ecran windows - Guide
- Retourner ecran windows - Guide
- Windows vista - Télécharger - Divers Utilitaires
6 réponses
Bonjour, Le message qui s'affiche au niveau de l'écran bleu est le suivant :
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Stop 0x00000D1
0x8F2036F2
dxgkrnl.sys
Adress 8F2036F2 base at 8F200000
Date stamp 4893b1df
le probleme doit venir d'un driver mal installé
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Stop 0x00000D1
0x8F2036F2
dxgkrnl.sys
Adress 8F2036F2 base at 8F200000
Date stamp 4893b1df
le probleme doit venir d'un driver mal installé
le probleme vient d'un pilote de carte graphique mal installé
https://www.luanagames.com/index.fr.html
https://www.luanagames.com/index.fr.html
Je n'en doute pas, mais ça fait 3 jours que je cherche sur internet comment pouvoir résoudre ce problème et je n'y arrive malheureusement pas. C'est pour ça que je poste sur le forum.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
L'analyse donne ça :
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 13/06/2011 14:29:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061311-03.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x36F2)
Bugcheck code: 0xD1 (0x4, 0x2, 0x1, 0xFFFFFFFF8F2036F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 Mon 13/06/2011 14:29:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x36F2)
Bugcheck code: 0xD1 (0x4, 0x2, 0x1, 0xFFFFFFFF8F2036F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 Mon 13/06/2011 13:47:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061311-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ACC4)
Bugcheck code: 0xD1 (0x16, 0x5, 0x0, 0x16)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 13/06/2011 12:53:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061311-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xECCDC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF8797ED26, 0xFFFFFFFF82922C64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 12/06/2011 14:00:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061211-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD2CB7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF828947BB, 0xFFFFFFFF9D0E1C50, 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 10/06/2011 21:31:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ACC4)
Bugcheck code: 0xD1 (0x0, 0x1B, 0x0, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 10/06/2011 20:07:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD38BA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF828E84A6, 0xFFFFFFFFA6EB3714, 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 10/06/2011 19:18:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A316)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFF812C8718, 0xFFFFFFFF812C8414, 0xFFFFFFFF828A4FCA)
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.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 13/06/2011 14:29:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061311-03.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x36F2)
Bugcheck code: 0xD1 (0x4, 0x2, 0x1, 0xFFFFFFFF8F2036F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 Mon 13/06/2011 14:29:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x36F2)
Bugcheck code: 0xD1 (0x4, 0x2, 0x1, 0xFFFFFFFF8F2036F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 Mon 13/06/2011 13:47:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061311-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ACC4)
Bugcheck code: 0xD1 (0x16, 0x5, 0x0, 0x16)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 13/06/2011 12:53:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061311-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xECCDC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF8797ED26, 0xFFFFFFFF82922C64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 12/06/2011 14:00:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061211-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD2CB7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF828947BB, 0xFFFFFFFF9D0E1C50, 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 10/06/2011 21:31:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5ACC4)
Bugcheck code: 0xD1 (0x0, 0x1B, 0x0, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 10/06/2011 20:07:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD38BA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF828E84A6, 0xFFFFFFFFA6EB3714, 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 10/06/2011 19:18:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061011-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A316)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFF812C8718, 0xFFFFFFFF812C8414, 0xFFFFFFFF828A4FCA)
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.
