- #1
D
Duketom
Gast
Hallo!
Mein Windows 8 stürzt immer wieder ab
mit whocrashed habe ich es analysiert und folgende Fehlermeldung bekommen,: Klingt für mich nach einem Windowsproblem oder ? wie kann man dies beheben ?
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 22.05.2013 13:54:11 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF802C022606C)
Bugcheck code: 0xD1 (0xFFFFF802C022606C, 0x2, 0x8, 0xFFFFF802C022606C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 22.05.2013 04:24:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052213-17534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x905C0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800C38955C0, 0xFFFFF88002DC59D8, 0xFFFFF88002DC5210)
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 20.05.2013 16:10:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052013-17784-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6943)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800193F943, 0xFFFFF8801EC1AC50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 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 Mon 20.05.2013 15:41:26 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052013-18954-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF801DDC00A30, 0xFFFFF801DDC00988, 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 24.04.2013 16:25:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042413-19328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x50 (0xFFFFF8015BAB2067, 0x8, 0xFFFFF8015BAB2067, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.
Mein Windows 8 stürzt immer wieder ab
mit whocrashed habe ich es analysiert und folgende Fehlermeldung bekommen,: Klingt für mich nach einem Windowsproblem oder ? wie kann man dies beheben ?
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 22.05.2013 13:54:11 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF802C022606C)
Bugcheck code: 0xD1 (0xFFFFF802C022606C, 0x2, 0x8, 0xFFFFF802C022606C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 22.05.2013 04:24:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052213-17534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x905C0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800C38955C0, 0xFFFFF88002DC59D8, 0xFFFFF88002DC5210)
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 20.05.2013 16:10:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052013-17784-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x6943)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800193F943, 0xFFFFF8801EC1AC50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 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 Mon 20.05.2013 15:41:26 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052013-18954-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF801DDC00A30, 0xFFFFF801DDC00988, 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 24.04.2013 16:25:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042413-19328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x50 (0xFFFFF8015BAB2067, 0x8, 0xFFFFF8015BAB2067, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.
