BleuScreen erreur : IRQL_NOT_LESS_OR_EQUAL
Leamsi60
Messages postés
1
Date d'inscription
Statut
Membre
Dernière intervention
-
Malekal_morte- Messages postés 180304 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Malekal_morte- Messages postés 180304 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Bonsoir,
Le 30/11, je décide de faire quelques MaJ de mes drivers (carte graphique et processeur et windows), mais à un moment, j'ai eu la fameuse erreur cité dans le titre. Depuis, je peux retourner sur mon pc, mais l'erreur vient au bout de x temps et ainsi de suite. J'ai essayé de mettre mon pc à une date antérieur, mais il n'y a qu'une date et elle est après ces MaJ. J'ai absolument besoin du pc, je suis en étude d'informatique et il m'est essentiel.
Je crois pas que l'erreur vienne de ma CG, car ils me disent que la MaJ n'a pas été fait, j'ai vérifié si c'était mes composants, ils marchent niquel.. J'ai absolument besoin d'aide.. j'ai un projet à fini pour lundi :'(
LOG whocrashed :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 02/12/2017 21:31:15 your computer crashed
crash dump file: C:\Windows\Minidump\120217-60965-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0xA (0xFFFF80001B03D770, 0x2, 0x0, 0xFFFFF8000378483F)
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 Sat 02/12/2017 21:31:15 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFF80001B03D770, 0x2, 0x0, 0xFFFFF8000378483F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Thu 30/11/2017 14:09:44 your computer crashed
crash dump file: C:\Windows\Minidump\113017-53601-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x50 (0xFFFF80001B03AA9A, 0x0, 0xFFFFF800037E18FC, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Le 30/11, je décide de faire quelques MaJ de mes drivers (carte graphique et processeur et windows), mais à un moment, j'ai eu la fameuse erreur cité dans le titre. Depuis, je peux retourner sur mon pc, mais l'erreur vient au bout de x temps et ainsi de suite. J'ai essayé de mettre mon pc à une date antérieur, mais il n'y a qu'une date et elle est après ces MaJ. J'ai absolument besoin du pc, je suis en étude d'informatique et il m'est essentiel.
Je crois pas que l'erreur vienne de ma CG, car ils me disent que la MaJ n'a pas été fait, j'ai vérifié si c'était mes composants, ils marchent niquel.. J'ai absolument besoin d'aide.. j'ai un projet à fini pour lundi :'(
LOG whocrashed :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 02/12/2017 21:31:15 your computer crashed
crash dump file: C:\Windows\Minidump\120217-60965-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0xA (0xFFFF80001B03D770, 0x2, 0x0, 0xFFFFF8000378483F)
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 Sat 02/12/2017 21:31:15 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFF80001B03D770, 0x2, 0x0, 0xFFFFF8000378483F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Thu 30/11/2017 14:09:44 your computer crashed
crash dump file: C:\Windows\Minidump\113017-53601-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x50 (0xFFFF80001B03AA9A, 0x0, 0xFFFFF800037E18FC, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
A voir également:
- BleuScreen erreur : IRQL_NOT_LESS_OR_EQUAL
- Erreur 0x80070643 - Accueil - Windows
- Erreur 4201 france tv ✓ - Forum Réseaux sociaux
- J'aime par erreur facebook notification - Forum Facebook
- Code erreur f3500-31 ✓ - Forum Bbox Bouygues
- Iptv erreur de lecture - Forum TV & Vidéo
1 réponse
Salut,
Réinstalle proprement les pilotes de la carte graphique : https://www.malekal.com/ddu-reinstaller-proprement-pilotes-cartes-graphiques/
Réinstalle proprement les pilotes de la carte graphique : https://www.malekal.com/ddu-reinstaller-proprement-pilotes-cartes-graphiques/