Hallo Community
Ich habe seit Tagen ein Problem... ständige Bluescreens...
Ich als Otto Normal Verbraucher habe leider keine Ahnung was diese bedeuten.
Hier die Crash Reports. vielleicht kann jemand von Euch ja damit was anfangen und mir somit helfen.
Vielen Dank schon einmal im Voraus.
System Information (local)
Crashdump Analyse:
Ich habe seit Tagen ein Problem... ständige Bluescreens...
Ich als Otto Normal Verbraucher habe leider keine Ahnung was diese bedeuten.
Hier die Crash Reports. vielleicht kann jemand von Euch ja damit was anfangen und mir somit helfen.
Vielen Dank schon einmal im Voraus.
System Information (local)
Computer name: MEDIACENTER-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P5N-D
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8588414976 bytes total
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P5N-D
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8588414976 bytes total
Crashdump Analyse:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 20.10.2015 13:13:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102015-29640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA7FFFFFD010, 0x2, 0x1, 0xFFFFF80002A4E841)
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 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 Tue 20.10.2015 13:13:17 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: 0xA (0xFFFFFA7FFFFFD010, 0x2, 0x1, 0xFFFFF80002A4E841)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 20.10.2015 13:09:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102015-30576-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFCE0, 0x2, 0x1, 0xFFFFF80002A99841)
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 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 Tue 20.10.2015 12:21:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102015-23556-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0x34A9, 0x2, 0x1, 0xFFFFF80002AD3A10)
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 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 19.10.2015 22:43:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102015-29421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFD0, 0x2, 0x1, 0xFFFFF80002AA82AC)
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 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 19.10.2015 19:51:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-26020-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A8160F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 19.10.2015 18:55:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-21793-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002ADB60F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Crash dumps are enabled on your computer.
On Tue 20.10.2015 13:13:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102015-29640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA7FFFFFD010, 0x2, 0x1, 0xFFFFF80002A4E841)
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 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 Tue 20.10.2015 13:13:17 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: 0xA (0xFFFFFA7FFFFFD010, 0x2, 0x1, 0xFFFFF80002A4E841)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 20.10.2015 13:09:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102015-30576-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFCE0, 0x2, 0x1, 0xFFFFF80002A99841)
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 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 Tue 20.10.2015 12:21:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102015-23556-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0x34A9, 0x2, 0x1, 0xFFFFF80002AD3A10)
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 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 19.10.2015 22:43:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102015-29421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFD0, 0x2, 0x1, 0xFFFFF80002AA82AC)
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 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 19.10.2015 19:51:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-26020-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A8160F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 19.10.2015 18:55:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-21793-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002ADB60F, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Zuletzt bearbeitet von einem Moderator:
