Nvlddmkm.sys avec GTX780M
Fermé
SnakeFyE
Messages postés
2
Date d'inscription
mardi 19 novembre 2013
Statut
Membre
Dernière intervention
21 novembre 2013
-
19 nov. 2013 à 18:42
SnakeFyE Messages postés 2 Date d'inscription mardi 19 novembre 2013 Statut Membre Dernière intervention 21 novembre 2013 - 21 nov. 2013 à 01:04
SnakeFyE Messages postés 2 Date d'inscription mardi 19 novembre 2013 Statut Membre Dernière intervention 21 novembre 2013 - 21 nov. 2013 à 01:04
A voir également:
- Nvlddmkm.sys avec GTX780M
- Nvlddmkm.sys ✓ - Forum Matériel & Système
- &Quot;Erreur NVLDDMKM.sys sur Windows 10, MSI GE60 2PL" - Forum Carte graphique
- DRIVER_IRQL_NOT_LESS_OR_EQUAL nvlddmkm.sys - Windows 11
- Nvlddmkm.sys sur une carte graphique de Nvidia sous Windows 10 ✓ - Forum Carte graphique
- Plantage de "nvlddmkm.sys" (écran qui s'éteint et se rallume) - Forum Windows 10
1 réponse
SnakeFyE
Messages postés
2
Date d'inscription
mardi 19 novembre 2013
Statut
Membre
Dernière intervention
21 novembre 2013
21 nov. 2013 à 01:04
21 nov. 2013 à 01:04
Rebonjour, après installation du logiciel WhoCrashed j'ai ce résultat
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 20/11/2013 22:50:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-25359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8019DD60BF4, 0xF, 0xFFFFE00004FF7C20)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 that cannot be identified at this time.
On Wed 20/11/2013 22:50:58 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: pxgx112.sys (PXGX112+0x1321)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8019DD60BF4, 0xF, 0xFFFFE00004FF7C20)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\pxgx112.sys
product: Hid gaming driver
company:
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.
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: pxgx112.sys ( ).
Google query: KMODE_EXCEPTION_NOT_HANDLED
On Tue 19/11/2013 17:24:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-34812-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x56FBA)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8039B8DCBF4, 0xFFFFF80002056FBA, 0xFFFFE000049D9000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 331.82
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 331.82
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED
On Mon 18/11/2013 16:07:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111813-20062-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x1FA60)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8018F368BF4, 0xF, 0xFFFFE00004CFFA10)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote XHCI USB
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 that cannot be identified at this time.
On Sat 16/11/2013 01:06:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111613-29109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF802D16F2004, 0x0, 0x9)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 that cannot be identified at this time.
On Thu 14/11/2013 16:23:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111413-32109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8015016C004, 0x0, 0x9)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 that cannot be identified at this time.
ca a vraiment l'air d'être un problème d'installation de windows, ou de différents drivers je ne sais pas, mais pas spécialement l'air d'être lié au hardware.
quelqu'un pourrait m'aider s'il vous plait :)
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 20/11/2013 22:50:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-25359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8019DD60BF4, 0xF, 0xFFFFE00004FF7C20)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 that cannot be identified at this time.
On Wed 20/11/2013 22:50:58 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: pxgx112.sys (PXGX112+0x1321)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8019DD60BF4, 0xF, 0xFFFFE00004FF7C20)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\pxgx112.sys
product: Hid gaming driver
company:
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.
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: pxgx112.sys ( ).
Google query: KMODE_EXCEPTION_NOT_HANDLED
On Tue 19/11/2013 17:24:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-34812-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x56FBA)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8039B8DCBF4, 0xFFFFF80002056FBA, 0xFFFFE000049D9000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 331.82
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 331.82
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED
On Mon 18/11/2013 16:07:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111813-20062-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x1FA60)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8018F368BF4, 0xF, 0xFFFFE00004CFFA10)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote XHCI USB
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 that cannot be identified at this time.
On Sat 16/11/2013 01:06:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111613-29109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF802D16F2004, 0x0, 0x9)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 that cannot be identified at this time.
On Thu 14/11/2013 16:23:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111413-32109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF8015016C004, 0x0, 0x9)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 that cannot be identified at this time.
ca a vraiment l'air d'être un problème d'installation de windows, ou de différents drivers je ne sais pas, mais pas spécialement l'air d'être lié au hardware.
quelqu'un pourrait m'aider s'il vous plait :)