Forum Login
Blue screen et crash écran noir et redémarrage sur session
il y a 3 ans 10 mois - il y a 3 ans 10 mois #284589 par Sleaders
Bonjour je me présente Jordan j'ai 27 ans et je suis toujours nouveau dans le montage pc 
voilà j'ai monter moi même mon pc comme la plus part d'entre vous ! mais depuis le début j'ai des gros soucies de blue screen
entre :
IRL_NOT_LESS_OR_EQUAL
et tant d'autre ...
la plus part du temps mon pc affiche aussi un écran noir puis la session Windows redémarrage !
j'ai eu beaucoup de problème au début avec des .Dll manquant !
j'ai donc du tous les réinstallez !
j'ai :
tester les rams avec le vérificateur de ram windows tout es OK
tester avec le scannow /F tout es ok
mis mes pilotes a jours via le site du fabriquand ( BIOS , Processeur , carte graphique )
j'ai essayer de regarder via bluescreenview mais il ne m'affiche juste ntoskrnl.exe a toutes les lignes !
j'ai tenter de regarder les fichier .dump avec Windbg et la il maffiche : memory_corruption
je ne sait plus vraiment quoi faire a présent ... si tout va bien de partout ^^' , mon cablemanagement es très propre je l'ai encore vérifier ce matin .
quelqu'un aurait une petite idées ?
on ma conseiller de réinitialisé Windows mais je n'ai pas de lecteur CD et via windows lui même il m'affiche une erreur d'admin...
hâte de vous lire
voilà j'ai monter moi même mon pc comme la plus part d'entre vous ! mais depuis le début j'ai des gros soucies de blue screen
entre :
IRL_NOT_LESS_OR_EQUAL
et tant d'autre ...
la plus part du temps mon pc affiche aussi un écran noir puis la session Windows redémarrage !
j'ai eu beaucoup de problème au début avec des .Dll manquant !
j'ai donc du tous les réinstallez !
j'ai :
tester les rams avec le vérificateur de ram windows tout es OK
tester avec le scannow /F tout es ok
mis mes pilotes a jours via le site du fabriquand ( BIOS , Processeur , carte graphique )
j'ai essayer de regarder via bluescreenview mais il ne m'affiche juste ntoskrnl.exe a toutes les lignes !
j'ai tenter de regarder les fichier .dump avec Windbg et la il maffiche : memory_corruption
Attention : Spoiler !
je ne sait plus vraiment quoi faire a présent ... si tout va bien de partout ^^' , mon cablemanagement es très propre je l'ai encore vérifier ce matin .
quelqu'un aurait une petite idées ?
on ma conseiller de réinitialisé Windows mais je n'ai pas de lecteur CD et via windows lui même il m'affiche une erreur d'admin...
hâte de vous lire
Connexion ou Créer un compte pour participer à la conversation.
Merci d'avance, pour l'utilisation de ces liens, L'équipe Config-gamer.fr |
|
--Vous 
il y a 3 ans 10 mois #284642 par Sleaders
Réponse de Sleaders sur le sujet Blue screen et crash écran noir et redémarrage sur session
Re-bonjour et bonne année !
voila les résultats
Bluescreenview :
123120-7031-01.dmp 31/12/2020 19:03:25 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+3f5780 x64 ntoskrnl.exe+3f5780 C:\Windows\Minidump\123120-7031-01.dmp 12 15 19041 1 103 188
et voilà le resultats Whocrashed
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 31/12/2020 20:38:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123120-12203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139 (0x3, 0xFFFFA30DEED31680, 0xFFFFA30DEED315D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 31/12/2020 20:38:37 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+0x8299)
Bugcheck code: 0x139 (0x3, 0xFFFFA30DEED31680, 0xFFFFA30DEED315D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
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 31/12/2020 19:02:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123120-7031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
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 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 Thu 31/12/2020 09:43:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123120-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139 (0x3, 0xFFFFFC8AAAE6F7D0, 0xFFFFFC8AAAE6F728, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 30/12/2020 19:49:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123020-5265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8044A84A3A3)
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 Wed 30/12/2020 19:39:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123020-7015-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x2ec7)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8040CEFA320)
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.
The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\LiveKernelReports\PoW32kWatchdog-20201229-0141.dmp
Conclusion
7 crash dumps have been found and analyzed. Only 6 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
voila les résultats
Bluescreenview :
123120-7031-01.dmp 31/12/2020 19:03:25 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+3f5780 x64 ntoskrnl.exe+3f5780 C:\Windows\Minidump\123120-7031-01.dmp 12 15 19041 1 103 188
et voilà le resultats Whocrashed
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 31/12/2020 20:38:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123120-12203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139 (0x3, 0xFFFFA30DEED31680, 0xFFFFA30DEED315D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 31/12/2020 20:38:37 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+0x8299)
Bugcheck code: 0x139 (0x3, 0xFFFFA30DEED31680, 0xFFFFA30DEED315D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
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 31/12/2020 19:02:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123120-7031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
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 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 Thu 31/12/2020 09:43:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123120-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x139 (0x3, 0xFFFFFC8AAAE6F7D0, 0xFFFFFC8AAAE6F728, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 30/12/2020 19:49:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123020-5265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8044A84A3A3)
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 Wed 30/12/2020 19:39:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123020-7015-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x2ec7)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8040CEFA320)
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.
The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\LiveKernelReports\PoW32kWatchdog-20201229-0141.dmp
Conclusion
7 crash dumps have been found and analyzed. Only 6 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
Connexion ou Créer un compte pour participer à la conversation.