CONNEXION
  • RetourJeux
    • Sorties
    • Hit Parade
    • Les + populaires
    • Les + attendus
    • Soluces
    • Tous les Jeux
    • Gaming
  • RetourActu Gaming
    • News
    • Astuces
    • Tests
    • Previews
    • Toute l'actu gaming
  • RetourBons plans
    • Bons plans
    • Bons plans Smartphone
    • Bons plans Hardware
    • Bons plans Image et Son
    • Bons plans Amazon
    • Bons plans Cdiscount
    • Bons plans Decathlon
    • Bons plans Fnac
    • Tous les Bons plans
  • RetourJVTech
    • Actus High-Tech
    • Intelligence Artificielle
    • Smartphones
    • Mobilité urbaine
    • Hardware
    • Image et son
    • Tutoriels
    • Tests produits High-Tech
    • Guides d'achat High-Tech
    • JVTech
  • RetourCulture
    • Actus Culture
    • Culture
  • RetourVidéos
    • A la une
    • Gaming Live
    • Vidéos Tests
    • Vidéos Previews
    • Gameplay
    • Trailers
    • Chroniques
    • Replay Web TV
    • Toutes les vidéos
  • RetourForums
    • Hardware PC
    • PS5
    • Switch 2
    • Xbox Series
    • Switch
    • Pokemon pocket
    • FC 25 Ultimate Team
    • League of Legends
    • Tous les Forums
  • PC
  • PS5
  • Xbox Series
  • Switch 2
  • PS4
  • One
  • Switch
  • iOS
  • Android
  • MMO
  • RPG
  • FPS
En ce moment Genshin Impact Valhalla Breath of the wild Animal Crossing GTA 5 Red dead 2
Liste des sujets

Plusieur BSOTD

Suiky
Suiky
Niveau 8
15 avril 2015 à 03:47:44

salut, j'aimerais finir de jouer a gta v donc voici mes blue screen

avant je tien a présicer que mon directx et mes pilote sont a jours

voici ma config
q9550
750 ti
ram 6 gb
alim 465 watt de marque noname qui a 9ans
2 dd de 1 to chaque

On Wed 2015-04-15 01:41:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041415-18985-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74E90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 2015-04-15 01:41:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xCF70E)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
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 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED

On Wed 2015-04-15 01:29:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041415-25911-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xA242)
Bugcheck code: 0xD1 (0x2F1, 0x2, 0x1, 0xFFFFF8800720A242)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 2015-04-14 00:29:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041315-29562-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x56C8)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8800728D6C8, 0xFFFFF8800B083D80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION

On Sun 2015-04-12 22:31:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041215-18985-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x9EC2)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8800105EEC2, 0xFFFFF8800D4B2940, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.

je tien a dire que ma ram est ok 9mem test passer :)

maldoror56
maldoror56
Niveau 6
15 avril 2015 à 11:39:16

ton processeur me parrait un peu juste et ton alim qui a 9ans et noname, c'est pas top, apres je ne sais pas si c'est vraiment ca.
en regle general, evite tout ce qui est "noname" j'ai une alim de presque le meme age, mais c'est une corsair de 520W, ca fonctionne encore, mais meme la ca commence a etre un peu juste pour des compo recents.

il faut savoir que les alim noname montrent la puissance max dispo, alors que avec une marque plus serieuse, c'est la puissance que tu es sur d'avoir

Suiky
Suiky
Niveau 8
15 avril 2015 à 12:12:30

je suis mieux de changer d'alim? yop c ce que je croyait

Suiky
Suiky
Niveau 8
15 avril 2015 à 12:12:58

mais pourtant les bsotd dis que c pas un probmlème materiel

maldoror56
maldoror56
Niveau 6
15 avril 2015 à 14:53:27

en general les BSoD sont dus a des causes materiel, qui fait bugger le logiciel par exemple (a confirmer), mais en general, lorsque l'on commence a avoir des BSoD, il est temps de faire des sauvegardes car c'est tres mauvais signe

Suiky
Suiky
Niveau 8
15 avril 2015 à 23:32:43

penser vous que Lalim peut etre la cause .... voila un new bsotd

On Wed 2015-04-15 21:27:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041515-15958-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0xD1 (0xFFFFF880121DF1F3, 0x2, 0x8, 0xFFFFF880121DF1F3)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.

donc This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

maldoror56
maldoror56
Niveau 6
15 avril 2015 à 23:53:05

le pc raconte que ce n'a pas l'air materiel comme probleme et que ca se passe dans le noyau windows, tente une restoration du systeme a date anterieure (quand ca marchait) ou repare le systeme, sinon, reinstallation complete de l'OS.
et si ca merde encore apres la reinstallation du systeme, alors il y a un probleme materiel qui reste a identifier

Suiky
Suiky
Niveau 8
16 avril 2015 à 00:06:15

je vais réinstaller mon os chuit en *******

Suiky
Suiky
Niveau 8
16 avril 2015 à 00:26:06

merde microsoft a blocker le download des os

Suiky
Suiky
Niveau 8
16 avril 2015 à 12:45:19

pas regler :( j'ai restaurer le window mais celuici est rester)

On Thu 2015-04-16 10:34:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041615-27315-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x6EC4)
Bugcheck code: 0xD1 (0x1, 0x2, 0x1, 0xFFFFF88005334EC4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.

Suiky
Suiky
Niveau 8
17 avril 2015 à 00:48:07

voila encore un autre... chuis at6nné serieux j,ai complettment restauré mon window et ça continu :(

On Thu 2015-04-16 22:38:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x57BC)
Bugcheck code: 0xD1 (0xFFFFFA805D808AD0, 0x5, 0x0, 0xFFFFF880048457BC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

Sous forums
  • Aide à l'achat Mac
  • Macintosh
  • Création de Jeux
  • Programmation
  • Création de sites web
  • Linux
  • Internet
  • Steam Deck
  • Hardware
La vidéo du moment