Zur Erklärung:
Der ruht vermutlich von dem Problem auf der Festplatte her:
ZitatAlles anzeigen
On Wed 28.08.2013 02:11:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13993-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x19 (0x22, 0xFFFFFA8000000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Der hier ist merkwürdig:
ZitatAlles anzeigen
On Mon 02.09.2013 19:04:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88001A4449C)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001A4449C)
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
Die anderen deuten auf ein Problem des LAN Treibers hin. System neu aufsetzen wegen des Software Festplattenfehlers, den Windows da angezeigt hat. Sind noch Treiberdateien oder Sachen in der Registry defekt, stürzt die Kiste wieder ab.