BSoD en boucle, redémarrage en boucle ...
Ministal
-
Ministal -
Ministal -
Bonjour,
Je viens vers vous car j'ai épuisé toutes le solutions.
Tout d'abord ma configuration : i7 4790, MSI GTX 970, MSI Z99 Gaming, Corsair G650m, SSD san disk, HDD WD, lecteur disque Asus et je crois que c'est tout ;)
Voici le bug, mon pc a eu des blues screen provenant de la RAM, donc je l'ai faite changé, puis rien pendant quelques temps, après j'ai eu des bluescreen pendant un an, parfois ça dure une semaine tout les soirs avec redémarrage en boucle puis d'un seul coup ça remarche, après ça recommence, parfois j'ai rien pendant un mois et des fois ça recommence, le bug provient lors d'une utilisation sur le web, ou sur des gros jeux, ou même parfois au démarrage.
Ce que j'ai fais : - changer la cm
-réinstallation système sur le ssd puis le Hdd en coupant l'un et l'autre à chaque fois.
-test avec une autre CG
-changement barrette de ra
-deconnection de tout les périphériques
-Test de maj de tout les drivers
-scan avec sys (négatif)
-changement du cable d'alim
-maj du bios
-Certainement pleins d'autres choses que j'ai oublié.
Je suis vraiment perdu pourtant je ne suis pas novice en la matière, j'ai passé mon ordi à un pro il pensait que ça venait de la cm mais ça a recommencé et je ne sais plus quoi en faire.
Voici les soucis des BSoD : -Systeme_service_exception
-IRQL_Not_less_or_Equal
-KMODE_Exception_not_handled
-Page_Fault_in_Nonpaged_area
Si quelqu'un connait ce genre d'erreur, l'a déjà rencontré je lui en serait reconnaissant.
Merci de votre aide.
Je viens vers vous car j'ai épuisé toutes le solutions.
Tout d'abord ma configuration : i7 4790, MSI GTX 970, MSI Z99 Gaming, Corsair G650m, SSD san disk, HDD WD, lecteur disque Asus et je crois que c'est tout ;)
Voici le bug, mon pc a eu des blues screen provenant de la RAM, donc je l'ai faite changé, puis rien pendant quelques temps, après j'ai eu des bluescreen pendant un an, parfois ça dure une semaine tout les soirs avec redémarrage en boucle puis d'un seul coup ça remarche, après ça recommence, parfois j'ai rien pendant un mois et des fois ça recommence, le bug provient lors d'une utilisation sur le web, ou sur des gros jeux, ou même parfois au démarrage.
Ce que j'ai fais : - changer la cm
-réinstallation système sur le ssd puis le Hdd en coupant l'un et l'autre à chaque fois.
-test avec une autre CG
-changement barrette de ra
-deconnection de tout les périphériques
-Test de maj de tout les drivers
-scan avec sys (négatif)
-changement du cable d'alim
-maj du bios
-Certainement pleins d'autres choses que j'ai oublié.
Je suis vraiment perdu pourtant je ne suis pas novice en la matière, j'ai passé mon ordi à un pro il pensait que ça venait de la cm mais ça a recommencé et je ne sais plus quoi en faire.
Voici les soucis des BSoD : -Systeme_service_exception
-IRQL_Not_less_or_Equal
-KMODE_Exception_not_handled
-Page_Fault_in_Nonpaged_area
Si quelqu'un connait ce genre d'erreur, l'a déjà rencontré je lui en serait reconnaissant.
Merci de votre aide.
A voir également:
- BSoD en boucle, redémarrage en boucle ...
- Forcer redemarrage windows - Guide
- Bsod - Guide
- Vlc lecture en boucle ✓ - Forum Lecteurs et supports vidéo
- Xiaomi s'éteint tout seul et se rallume en boucle - Forum Xiaomi
- Huawei s'allume et s'éteint en boucle - Forum Huawei
1 réponse
Je vous ajoute les rapports de WhoCrashed :
On Fri 17/02/2017 22:47:57 your computer crashed
crash dump file: C:\Windows\Minidump\021817-4265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x4E (0x2, 0x4524, 0x21EFFF, 0x1)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 17/02/2017 22:47:57 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x2, 0x4524, 0x21EFFF, 0x1)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 17/02/2017 22:08:24 your computer crashed
crash dump file: C:\Windows\Minidump\021717-4593-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Fri 17/02/2017 22:05:18 your computer crashed
crash dump file: C:\Windows\Minidump\021717-4312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x19 (0xE, 0xFFFF958F2B4951E0, 0x6A0068, 0x875F8EE683123D8C)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 17/02/2017 19:18:44 your computer crashed
crash dump file: C:\Windows\Minidump\021717-4421-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xD2005)
Bugcheck code: 0xD1 (0x1F53117F, 0xA, 0x1, 0xFFFFF804230D2005)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispiwu.inf_amd64_b67dc924fff8de6d\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 376.53
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 376.53
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 376.53 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 17/02/2017 22:47:57 your computer crashed
crash dump file: C:\Windows\Minidump\021817-4265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x4E (0x2, 0x4524, 0x21EFFF, 0x1)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 17/02/2017 22:47:57 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x2, 0x4524, 0x21EFFF, 0x1)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 17/02/2017 22:08:24 your computer crashed
crash dump file: C:\Windows\Minidump\021717-4593-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Fri 17/02/2017 22:05:18 your computer crashed
crash dump file: C:\Windows\Minidump\021717-4312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x19 (0xE, 0xFFFF958F2B4951E0, 0x6A0068, 0x875F8EE683123D8C)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 17/02/2017 19:18:44 your computer crashed
crash dump file: C:\Windows\Minidump\021717-4421-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xD2005)
Bugcheck code: 0xD1 (0x1F53117F, 0xA, 0x1, 0xFFFFF804230D2005)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispiwu.inf_amd64_b67dc924fff8de6d\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 376.53
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 376.53
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 376.53 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
