--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: PATRICK-PC
windows version: Windows 10 , 10.0, build: 10240
windows dir: C:\WINDOWS
Hardware: Precision M4600, Dell Inc., 03HYJK
CPU: GenuineIntel Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17134792704 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 07/08/2015 11:39:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080715-21265-01.dmp
This was probably caused by the following module: ks.sys (ks+0x4387D)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF8002B4CB705)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
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 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 Fri 07/08/2015 11:39:49 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!NtDeviceIoControlFile+0xA)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF8002B4CB705)
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.
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: ntdll.sys .
Google query: ntdll.sys IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. A third party driver has 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:
ntdll.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.
[RESOLU] IRQL_NOT_LESS_OR_EQUAL avec Windows 10
-
Auteur du sujetFlyman30
- Habitué
- Messages : 464
- Enregistré le : il y a 15 ans
- Localisation : Lozère
[RESOLU] IRQL_NOT_LESS_OR_EQUAL avec Windows 10
Voilà ce que me dise les fichiers dump, que faire ?
-
- Nouveau
- Messages : 86
- Enregistré le : il y a 15 ans
Bonjour,
Sans prétendre détenir la solution universelle, j'ai eu ce même message en début d'installation de Windows 10. Et la mémoire vive équipant mon ordinateur était en cause.
Suppression des deux dernières barrettes ajoutées (qui tournaient bien sous Windows 7, et le problème de plantage systématique a été éliminé......
A tester... 8)
Sans prétendre détenir la solution universelle, j'ai eu ce même message en début d'installation de Windows 10. Et la mémoire vive équipant mon ordinateur était en cause.
Suppression des deux dernières barrettes ajoutées (qui tournaient bien sous Windows 7, et le problème de plantage systématique a été éliminé......
A tester... 8)
-
Auteur du sujetFlyman30
- Habitué
- Messages : 464
- Enregistré le : il y a 15 ans
- Localisation : Lozère
Je n'ai pas de plantage systématique, j'ai du réinstaller des drivers DELL et fait un sfc /scannow qui m'a réparé des fichiers, et pour le moment tout baigne enfin je crois
-
- Modérateur
- Messages : 2902
- Enregistré le : il y a 12 ans
Mon avis que tu devrais vérifier ton dur et ta ram, tous ces fichiers ks.sys et ntdll.sys sont des fichiers systèmes
-
Auteur du sujetFlyman30
- Habitué
- Messages : 464
- Enregistré le : il y a 15 ans
- Localisation : Lozère
Stiouf il s'agit d'un problème de Driver d'après les conclusion du Dump, problème que je pense avoir règlé
Qui est en ligne
Utilisateurs parcourant ce forum : Aucun utilisateur enregistré et 0 invité