Aller au contenu
Site Communauté

tintin5356

Membres
  • Nbre de contenus

    41
  • Inscription

  • Dernière visite

Configuration PC

  • Système d'exploitation
    Windows 10

Succès de tintin5356

Matelot breveté

Matelot breveté (2/24)

  • Premier message
  • Collaborateur Rare
  • Une semaine déjà
  • 30 jours déjà
  • Audacieux

Badges récents

0

Réputation dans la communauté

  1. OKay, je vais en trouver et ensuite faire l'installation windows, drivers pour que j'ai mes ports USB utilisables. Merci bonne soirée, je vous redirais si BSOD sous W7.
  2. Mon clavier et ma souris sont en filaire (usb)
  3. J'ai lancé l'installation Windows 7 mais des la première fenêtre (choix des langues/) j'ai plus de souris ni clavier. En regardant Windows 7 ne prend pas en charge les ports USB 3.0. j'ai donc essayé de mettre la clé bootable derrière et juste le clavier devant mais rien y fait. Avez vous un conseil ?
  4. Pour windows 7, je vais prendre cette version: Je vais utiliser Ventoy, mais est-ce nécessaire d'utiliser WBU?
  5. Okay très bien merci. Car en écoutant le vendeur (matériel.net) il faudrait envoyer la CM et CPU pour test et diag mais ils prennent un billet pour ca...
  6. Très bien. J'allais vous demander cette option. Je vous tiens au courant. D'après vous, est-ce que cela pourrait être un problème matériel (CM, CPU) ou bien c'est sur que c'est un problème de soft?
  7. Ok merci. Sinon avez-vous une idée pour les BSOD malgré les mises à jour de la CM, CG?
  8. Ca a replanté 2 fois.... On Tue 26/01/2021 16:19:05 your computer crashed or a problem was reported crash dump file: C:\Windows\minidump\012621-6890-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220) Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFF8052EFC8576) 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 is a software bug. 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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 26/01/2021 16:19:05 your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8209) Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFF8052EFC8576) 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 is a software bug. 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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 26/01/2021 09:52:21 your computer crashed or a problem was reported crash dump file: C:\Windows\minidump\012621-6843-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220) Bugcheck code: 0xA (0xFFFFD0890371592C, 0xFF, 0x8A, 0xFFFFF807619EE243) 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 is a software bug. 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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  9. C'est peut être une question bête, mais comment voir si tous ls drivers sont bien installés?
  10. J'ai mis à jour ma CG avec un pilote antérieur. POur la CM, J'ai tout réinstallé pour être sur. Pr contre pour VGA drivers, j'obtiens ca à chaque fois: Est-ce normal? A voir si cela suffit. Pour le driver AMD CPU pouvez vous me transmettre le lien du forum pour avoir les informations sur une éventuelle résolution?? De plus serait-ce une solution de faire la manip de l'un des membres (je n'ai pas trouvé les paramètres dans le bios)? "Bonsoir, désolé pour mon absence, Depuis que j'ai désactivé "Core Performance Boost" et "AMD Cool&Quiet function", le pc a l'air beaucoup plus stable, je n'ai pas eu de nouveau BSOD. Voici quand même deux images de ryzen master, la première correspond au démarrage du pc, la seconde une vingtaine de minutes plus tard, j'ai aussi remarqué qu'on peux sélectionner un mode "auto OC" :"
  11. Oui en effet je n'ai pas de CG intégrée mais alors comment résoudre ce pb? Et oui j'ai une nvdia, GTX 1650 (pilotes à jour). POurquoi y a t il un pb de CG?
  12. En cherchant la résolution du problème, j'ai vu que vous étiez sur un sujet qui pourrait s'en approcher.
  13. Suite à vos instructions, j'ai tout réinstallé et bim un BSOD. Je vois que c 'est à cause d'un driver. Je n vois pas comment le mettre à jour. On Mon 25/01/2021 18:00:56 your computer crashed or a problem was reported crash dump file: C:\Windows\minidump\012521-8031-01.dmp This was probably caused by the following module: amdppm.sys (amdppm+0x206c) Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80134173358) Error: DPC_WATCHDOG_VIOLATION file path: C:\Windows\system32\drivers\amdppm.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Processor Device Driver Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Mon 25/01/2021 18:00:56 your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x79b9b) Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80134173358) Error: DPC_WATCHDOG_VIOLATION file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3621da861144492b\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 461.09 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 461.09 Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). 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.09 , NVIDIA Corporation). Google query: nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION On Mon 25/01/2021 18:29:42 your computer crashed or a problem was reported crash dump file: C:\Windows\minidump\012521-7546-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80012E67D9F) 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 is a software bug. 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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 25/01/2021 18:29:42 your computer crashed or a problem was reported crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8209) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80012E67D9F) 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 is a software bug. 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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  14. okay , je préfère m'assurer de bien faire. JE vous tiens au courant.
  15. OK donc j'installe Windows sans internet, ensuite j'execute WBU préalablement mis sur une clé usb, et ensuite installation des drivers. C'est bien ca?
×
×
  • Créer...