Aller au contenu

Folax

Membres
  • Compteur de contenus

    5
  • Inscription

  • Dernière visite

Visiteurs récents du profil

198 visualisations du profil

Folax's Achievements

Junior Member

Junior Member (3/12)

0

Réputation sur la communauté

  1. Folax

    [BSOD] nvlddmkm.sys

    Coucou pusteInik, C'est étrange car la barrette c'est écrit : 3000Mhz dessus.. C'est une Ballistix.. Ma carte graphique c'est une Inno3D GeForce GTX 1650 Ma RAM qui fonctionne est celle-ci : Corsair Vengeance LPX 8Go Merci !
  2. Folax

    [BSOD] nvlddmkm.sys

    Toutes les mises à jour Windows ont été faites, oui. Là j'ai remis mon ancienne barrette de RAM, et à priori, plus de crash, mais c'est problématique.. Car ma barrette de 16Go fait planté le PC et les jeux.. Et le pilote je l'installe directement sur le site NVIDIA
  3. Folax

    [BSOD] nvlddmkm.sys

    Re, Après avoir réalisé une mise à jour complète de Windows + Réinstallation complète de mes drivers NVIDIA à l'aide de DDU. Mon jeu se ferme tout seul sans message de crash, dans mon WhoCrashed le fameux "nvlddmkm.sys" fait toujours apparition. Je ne sais plus réellement quoi faire..
  4. Folax

    [BSOD] nvlddmkm.sys

    Merci de la réponse ma barrette c'est celle-ci : 16 Go de mémoire totale de type DDR4 à 1.5 GHz (1.5x1 GHz) Timings mémoire: 16.0 clocks-18 clocks-18 clocks-38 clocks-1 TT Barrette Crucial Technology de 16 Go --- J'utilise déjà DriversCloud pour mes mises à jours de drivers, ma carte graphique c'est une Inno3D GeForce GTX 1650 et elle a été mise à jour hier également. Et où est-ce que je peut réaliser la mise à jour du système ? Merci !
  5. Folax

    [BSOD] nvlddmkm.sys

    Bonjour, bonsoir ! J'aurai potentiellement besoin d'aide concernant un problème que j'ai sur mon PC depuis aujourd'hui, j'ai acquis une nouvelle barrette de ram donc en single channel. Depuis l'installation de celle-ci, mes jeux crash et je me suis pris deux BSOD avec le motif tout en bas "éléments ayant échoué : nvlddmkm.sys" J'ai réalisé un WhoCrashed, mais je ne m'y connais pas du tout en lecture de crash-report malheureusement donc si quelqu'un peut m'aider ça serait grave gentil. --- Computer name: DESKTOP-0R8039M Windows version: Windows 10, 10.0, version 1909, build: 18363 Windows dir: C:\WINDOWS Hardware: ASUSTeK COMPUTER INC., PRIME B450-PLUS CPU: AuthenticAMD AMD Ryzen 5 2400G with Radeon Vega Graphics 8664, level: 23 8 logical processors, active mask: 255 RAM: 17102471168 bytes (15,9GB) Crash Dump Analysis Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps. Crash dump directories: C:\WINDOWS C:\WINDOWS\Minidump On Tue 23/03/2021 02:25:00 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032321-14500-01.dmp This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8017D3CA980) Bugcheck code: 0xD1 (0x20, 0xC, 0x0, 0xFFFFF8017D3CA980) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_69d6cb4608dadaa3\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 461.92 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 461.92 Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 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 461.92 , NVIDIA Corporation). Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL On Mon 22/03/2021 23:05:50 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\032221-14312-01.dmp This was probably caused by the following module: win32kfull.sys (0xFFFFAB9CE1A63F7D) Bugcheck code: 0x50 (0xFFFFABBF8EBEB787, 0x0, 0xFFFFAB9CE1A63F7D, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\WINDOWS\system32\win32kfull.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Full/Desktop Win32k Kernel 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. The crash took place in a 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. 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 461.92 , NVIDIA Corporation) 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. --- Merci beaucoup et bonne journée/soirée ! Folax.
×
×
  • Créer...