DerSchnetzler
Cadet 4th Year
- Registriert
- Okt. 2006
- Beiträge
- 82
Hallo zusammen,
ich hoffe ich bin hier im richtigen Unterforum gelandet. Ich habe folgendes Problem. Im September habe ich mir einen komplett neuen PC mit folgenden Komponenten zusammengestellt.
AMD Ryzen 7 3700X 3,6 GHz
Gigabyte X570 Aorus Elite, AMD X570-Mainboard
2 x G.Skill Aegis Series, DDR4-3200, CL16 - 32 GB Dual-Kit
2 x Gigabyte Aorus NVMe SSD, PCIe 4.0 M.2 Typ 2280
be quiet! Straight Power 11 Netzteil, 80 PLUS Gold, modular -
750 Watt
Western Digital Black, SATA 6G, 7200 U/min, 3,5 Zoll - 2 TB
InLine Schnittstellenkarte 2x USB 3.1 - Typ A + Typ C - inkl. LP
Alpenföhn Brocken ECO Advanced - 120mm
NVIDIA GEFORCE RTX 3080 FE (mit viel Glück aus dem offiziellen NVIDIA Store gekauft
)
Als Betriebssystem wird Windows 10 Education genutzt
Bei diesem System kommt es nun in unregelmäßigen Abständen zu Bluescreens und Abstürzen. Es lässt sich hier meines Erachtens nach
kein wirkliches Muster ermitteln. Das Problem ist sowohl nach/während des Systemstarts, auf dem Desktop als auch während des Spielens aufgetreten. Die Temperaturen der Komponenten sind laut Sensoren i.O., alle Treiber und Windows sind aktuell. Ich habe bereits den Burn-In Test sowie den Windows eigenene Speichertest durchlaufen lassen ohne dass hierbei Probleme registriert worden wären. Ich habe die Crashdumps mit WhoCrashed ausgelesen und unten angehangen. Ich hoffe jemand hat eine Idee, welche Komponente bzw. welcher Treiber (oder was auch immer) Ursache des Problems sein könnte. Vielen Dank euch allen schonmal.
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-V928BMA
Windows version: Windows 10, 10.0, version 2004, build: 19041
Windows dir: C:\Windows
Hardware: X570 AORUS ELITE, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor 8664, level: 23
16 logical processors, active mask: 65535
RAM: 68659867648 bytes (63,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 02.11.2020 14:43:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110220-8062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802730C9734,
0xFFFFBE046A124688, 0xFFFFBE046A123EC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Mon 02.11.2020 14:43:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x2A47)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF802730C9734, 0xFFFFBE046A124688,
0xFFFFBE046A123EC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a 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 Mon 26.10.2020 17:56:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102620-6328-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80646D3DECE)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80646D3DECE, 0xFFFF878E0E5D8180, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
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 file system driver. Since there is no other responsible
driver detected, this could be pointing to a malfunctioning drive or corrupted
disk. It's suggested that you run CHKDSK.
On Fri 23.10.2020 06:06:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102320-7546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1A (0x403, 0xFFFFBCBFFABF2488, 0x9600000FCAE54025, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error
occurred. The page table and PFNs are out of sync . This is probably a hardware
error, especially if parameters 3 & 4 differ by only a single bit.
This is likely to be caused by a hardware problem. This error suggests a case of
memory corruption because of a hardware problem. It is suggested you do a test on
your RAM modules (memory test) and make sure your system is not getting
overheated. 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.
12.11.2020:
Beschreibung
Aufgrund eines Hardwareproblems ist Windows nicht mehr voll funktionsfähig.
Problemsignatur
Problemereignisame: LiveKernelEvent
Code: 1a1
Parameter 1: ffffae888df9b040
Parameter 2: 0
Parameter 3: 0
Parameter 4: 0
Betriebssystemversion: 10_0_19042
Service Pack: 0_0
Produkt: 256_1
Betriebsystemversion: 10.0.19042.2.0.0.256.121
Gebietsschema-ID: 1031
ich hoffe ich bin hier im richtigen Unterforum gelandet. Ich habe folgendes Problem. Im September habe ich mir einen komplett neuen PC mit folgenden Komponenten zusammengestellt.
AMD Ryzen 7 3700X 3,6 GHz
Gigabyte X570 Aorus Elite, AMD X570-Mainboard
2 x G.Skill Aegis Series, DDR4-3200, CL16 - 32 GB Dual-Kit
2 x Gigabyte Aorus NVMe SSD, PCIe 4.0 M.2 Typ 2280
be quiet! Straight Power 11 Netzteil, 80 PLUS Gold, modular -
750 Watt
Western Digital Black, SATA 6G, 7200 U/min, 3,5 Zoll - 2 TB
InLine Schnittstellenkarte 2x USB 3.1 - Typ A + Typ C - inkl. LP
Alpenföhn Brocken ECO Advanced - 120mm
NVIDIA GEFORCE RTX 3080 FE (mit viel Glück aus dem offiziellen NVIDIA Store gekauft
)Als Betriebssystem wird Windows 10 Education genutzt
Bei diesem System kommt es nun in unregelmäßigen Abständen zu Bluescreens und Abstürzen. Es lässt sich hier meines Erachtens nach
kein wirkliches Muster ermitteln. Das Problem ist sowohl nach/während des Systemstarts, auf dem Desktop als auch während des Spielens aufgetreten. Die Temperaturen der Komponenten sind laut Sensoren i.O., alle Treiber und Windows sind aktuell. Ich habe bereits den Burn-In Test sowie den Windows eigenene Speichertest durchlaufen lassen ohne dass hierbei Probleme registriert worden wären. Ich habe die Crashdumps mit WhoCrashed ausgelesen und unten angehangen. Ich hoffe jemand hat eine Idee, welche Komponente bzw. welcher Treiber (oder was auch immer) Ursache des Problems sein könnte. Vielen Dank euch allen schonmal.
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-V928BMA
Windows version: Windows 10, 10.0, version 2004, build: 19041
Windows dir: C:\Windows
Hardware: X570 AORUS ELITE, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor 8664, level: 23
16 logical processors, active mask: 65535
RAM: 68659867648 bytes (63,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 02.11.2020 14:43:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110220-8062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802730C9734,
0xFFFFBE046A124688, 0xFFFFBE046A123EC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Mon 02.11.2020 14:43:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x2A47)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF802730C9734, 0xFFFFBE046A124688,
0xFFFFBE046A123EC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a 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 Mon 26.10.2020 17:56:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102620-6328-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80646D3DECE)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80646D3DECE, 0xFFFF878E0E5D8180, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
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 file system driver. Since there is no other responsible
driver detected, this could be pointing to a malfunctioning drive or corrupted
disk. It's suggested that you run CHKDSK.
On Fri 23.10.2020 06:06:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102320-7546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1A (0x403, 0xFFFFBCBFFABF2488, 0x9600000FCAE54025, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error
occurred. The page table and PFNs are out of sync . This is probably a hardware
error, especially if parameters 3 & 4 differ by only a single bit.
This is likely to be caused by a hardware problem. This error suggests a case of
memory corruption because of a hardware problem. It is suggested you do a test on
your RAM modules (memory test) and make sure your system is not getting
overheated. 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.
12.11.2020:
Beschreibung
Aufgrund eines Hardwareproblems ist Windows nicht mehr voll funktionsfähig.
Problemsignatur
Problemereignisame: LiveKernelEvent
Code: 1a1
Parameter 1: ffffae888df9b040
Parameter 2: 0
Parameter 3: 0
Parameter 4: 0
Betriebssystemversion: 10_0_19042
Service Pack: 0_0
Produkt: 256_1
Betriebsystemversion: 10.0.19042.2.0.0.256.121
Gebietsschema-ID: 1031
