ezra-croug
Nouveau membre
Bonjour à tous
alors voilà j'ai acheter ma tour il y'a moins de deux mois et au début tout était parfais, au début seulement, car une semaine ou deux plus tard mon problème actuelle apparut, des crash et encore des crash, pour un oui ou pour un non, plus sa va pire ses. Voici ma configue.
Cg-rtx2060
Pross-i5
Hdd-2tb
j'ai tenté plusieurs choses mais sans résultats concluant...
J'ai tout réinitialiser, mais rien, j'ai fait des verification des mes disques, j'ai mit à jours tout mes pilotes...
mais toujours rien mon pc plante encore et encore, j'ai installer who crashed peut-être que cela pourrais vous aider, voicie se qu'il nous raconte!..
System Information (local)
Computer name: DESKTOP-G8796SD
Windows version: Windows 10 , 10.0, version 1809, build: 17763
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., PRIME Z390-A
CPU: GenuineIntel Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz Intel8664, level: 6
6 logical processors, active mask: 63
RAM: 17090039808 bytes (15,9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
C:\
D:\
On Thu 18/07/2019 20:45:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071819-8890-01.dmp
This was probably caused by the following module:
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803589C3F73, 0xFFFFF28DCFC275E8, 0xFFFFF28DCFC26E30)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
description: NT Kernel & System
Bug check description: This indicates that a system thread 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 Thu 18/07/2019 20:45:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module:
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF803589C3F73, 0xFFFFF28DCFC275E8, 0xFFFFF28DCFC26E30)
Error:
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 18/07/2019 00:37:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071719-8625-01.dmp
This was probably caused by the following module:
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8034C628323, 0xFFFFFD8B6BA377A8, 0xFFFFFD8B6BA36FF0)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
description: NT Kernel & System
Bug check description: This indicates that a system thread 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\071719-8640-01.dmp
Conclusion
4 crash dumps have been found and analyzed. Only 3 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.
--------------------
Enfain bref voilà j'espère siencerement pouvoir trouver de l'aide car je suis carrément dégouter de devoir utiliser mon pc portable et regarder ma tour tristement .. merci d'avance, bonne journée/soirée
alors voilà j'ai acheter ma tour il y'a moins de deux mois et au début tout était parfais, au début seulement, car une semaine ou deux plus tard mon problème actuelle apparut, des crash et encore des crash, pour un oui ou pour un non, plus sa va pire ses. Voici ma configue.
Cg-rtx2060
Pross-i5
Hdd-2tb
j'ai tenté plusieurs choses mais sans résultats concluant...
J'ai tout réinitialiser, mais rien, j'ai fait des verification des mes disques, j'ai mit à jours tout mes pilotes...
mais toujours rien mon pc plante encore et encore, j'ai installer who crashed peut-être que cela pourrais vous aider, voicie se qu'il nous raconte!..
System Information (local)
Computer name: DESKTOP-G8796SD
Windows version: Windows 10 , 10.0, version 1809, build: 17763
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., PRIME Z390-A
CPU: GenuineIntel Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz Intel8664, level: 6
6 logical processors, active mask: 63
RAM: 17090039808 bytes (15,9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
C:\
D:\
On Thu 18/07/2019 20:45:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071819-8890-01.dmp
This was probably caused by the following module:
Vous devez être connecté pour voir les liens.
(nt+0x71FF73) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803589C3F73, 0xFFFFF28DCFC275E8, 0xFFFFF28DCFC26E30)
Error:
Vous devez être connecté pour voir les liens.
file path: C:\Windows\system32\ntoskrnl.exe
product:
Vous devez être connecté pour voir les liens.
company:
Vous devez être connecté pour voir les liens.
description: NT Kernel & System
Bug check description: This indicates that a system thread 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 Thu 18/07/2019 20:45:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module:
Vous devez être connecté pour voir les liens.
(nt!memset+0x4F21) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF803589C3F73, 0xFFFFF28DCFC275E8, 0xFFFFF28DCFC26E30)
Error:
Vous devez être connecté pour voir les liens.
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 18/07/2019 00:37:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071719-8625-01.dmp
This was probably caused by the following module:
Vous devez être connecté pour voir les liens.
(nt+0x576323) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8034C628323, 0xFFFFFD8B6BA377A8, 0xFFFFFD8B6BA36FF0)
Error:
Vous devez être connecté pour voir les liens.
file path: C:\Windows\system32\ntoskrnl.exe
product:
Vous devez être connecté pour voir les liens.
company:
Vous devez être connecté pour voir les liens.
description: NT Kernel & System
Bug check description: This indicates that a system thread 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\071719-8640-01.dmp
Conclusion
4 crash dumps have been found and analyzed. Only 3 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.
--------------------
Enfain bref voilà j'espère siencerement pouvoir trouver de l'aide car je suis carrément dégouter de devoir utiliser mon pc portable et regarder ma tour tristement .. merci d'avance, bonne journée/soirée