Hallo, ich habe heute mal Unterstützung nötig.
Mein PC startete heute mit mehreren Versuchen und Diagnosen, etc.
Derzeit läuft er wieder.
Bislang habe ich mich nur belesen und Who Crashed zur Hilfe genommen um hier euch nachfolgendes posten zu können.
Eventuell hängt mein Problem mit meinem gestrigen USB Anschluss von meinem Galaxy Tab A zusammen, da Treiber runtergeladen wurden.
Das Gerät ist nur gestern angeschlossen gewesen. Heute ist es nicht wie mein Handy unter Geräte zu finden.
Daher weiß ich gerade selber nicht weiter.
Ich bin nicht so die Fachfrau.
Ich bitte um Anweisung und werde mich schon jetzt bedanken. Dank folgt.
Alraune
Computer name: BERNIS-PC
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: ASUSTeK Computer INC., M2N-X
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 4294299648 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Mein PC startete heute mit mehreren Versuchen und Diagnosen, etc.
Derzeit läuft er wieder.
Bislang habe ich mich nur belesen und Who Crashed zur Hilfe genommen um hier euch nachfolgendes posten zu können.
Eventuell hängt mein Problem mit meinem gestrigen USB Anschluss von meinem Galaxy Tab A zusammen, da Treiber runtergeladen wurden.
Das Gerät ist nur gestern angeschlossen gewesen. Heute ist es nicht wie mein Handy unter Geräte zu finden.
Daher weiß ich gerade selber nicht weiter.
Ich bin nicht so die Fachfrau.
Ich bitte um Anweisung und werde mich schon jetzt bedanken. Dank folgt.
Alraune
Computer name: BERNIS-PC
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: ASUSTeK Computer INC., M2N-X
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 4294299648 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 08.09.2016 06:41:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-22281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0D0)
Bugcheck code: 0xF7 (0xF0C01B3DBA93, 0xF0C01B3DBA93, 0xFFFF0F3FE4C2456C, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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 08.09.2016 06:41:13 GMT 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: 0xF7 (0xF0C01B3DBA93, 0xF0C01B3DBA93, 0xFFFF0F3FE4C2456C, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 08.09.2016 06:41:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-22187-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 Thu 08.09.2016 06:37:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-28828-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 Thu 08.09.2016 06:32:57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-21718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0D0)
Bugcheck code: 0x139 (0x2, 0xFFFFF803B80876B0, 0xFFFFF803B8087608, 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 08.09.2016 06:30:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-23687-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 Thu 08.09.2016 05:49:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-22609-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3620F)
Bugcheck code: 0x124 (0x0, 0xFFFFAD0362631038, 0xB6000000, 0x181)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
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 Thu 08.09.2016 05:47:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-24906-01.dmp
This was probably caused by the following module: hal.dll (hal+0x1ABE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802CCA22ABE, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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.
Crash dumps are enabled on your computer.
On Thu 08.09.2016 06:41:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-22281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0D0)
Bugcheck code: 0xF7 (0xF0C01B3DBA93, 0xF0C01B3DBA93, 0xFFFF0F3FE4C2456C, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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 08.09.2016 06:41:13 GMT 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: 0xF7 (0xF0C01B3DBA93, 0xF0C01B3DBA93, 0xFFFF0F3FE4C2456C, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 08.09.2016 06:41:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-22187-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 Thu 08.09.2016 06:37:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-28828-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 Thu 08.09.2016 06:32:57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-21718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0D0)
Bugcheck code: 0x139 (0x2, 0xFFFFF803B80876B0, 0xFFFFF803B8087608, 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 08.09.2016 06:30:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-23687-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 Thu 08.09.2016 05:49:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-22609-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3620F)
Bugcheck code: 0x124 (0x0, 0xFFFFAD0362631038, 0xB6000000, 0x181)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
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 Thu 08.09.2016 05:47:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090816-24906-01.dmp
This was probably caused by the following module: hal.dll (hal+0x1ABE)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802CCA22ABE, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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.
Zuletzt bearbeitet von einem Moderator:
