Um mich kurz zu fassen:
Ich habe in letzter Zeit schonmal häufiger Bluescreens mit meinem Laptop.
Allerdings noch nie während ich am zocken war. Habe mir nun WhoCrashed runtergeladen und nachgeschaut woran es denn liegen könnte, allerdings half mir das nicht wirklich weiter und ich wollte mich an Leute wenden die vielleicht mehr Ahnung davon haben.
Kurze Datenzusammenfassung vom Laptop:
i7 4700MQ
4GB HD 8970M
16GB DDR3 RAM
120GB SSD + 1TB HDD
Windows 8 64-Bit
Analysen:
On Thu 09.01.2014 00:43:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010914-5984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFF3E0, 0x2, 0x1, 0xFFFFF8024F530870)
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 Thu 09.01.2014 00:43: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 (0xFFFFFD7FFFFFF3E0, 0x2, 0x1, 0xFFFFF8024F530870)
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 Wed 08.01.2014 08:03:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010814-6234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800A4F31286, 0xFFFFD0003D985EA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 04.01.2014 19:00:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-6093-01.dmp
This was probably caused by the following module: ks.sys (ks+0x1E477)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80001B2E477, 0x0, 0x3C)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
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.
On Fri 03.01.2014 22:03:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-5734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7F (0x8, 0xFFFFD000207EC1B0, 0xFFFFD00025797000, 0xFFFFF8032FD4C5B4)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 03.01.2014 21:55:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-5781-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3222)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002F2B222, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\usbport.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: USB 1.1 & 2.0-Porttreiber
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.
Ich habe in letzter Zeit schonmal häufiger Bluescreens mit meinem Laptop.
Allerdings noch nie während ich am zocken war. Habe mir nun WhoCrashed runtergeladen und nachgeschaut woran es denn liegen könnte, allerdings half mir das nicht wirklich weiter und ich wollte mich an Leute wenden die vielleicht mehr Ahnung davon haben.
Kurze Datenzusammenfassung vom Laptop:
i7 4700MQ
4GB HD 8970M
16GB DDR3 RAM
120GB SSD + 1TB HDD
Windows 8 64-Bit
Analysen:
On Thu 09.01.2014 00:43:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010914-5984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xA (0xFFFFFD7FFFFFF3E0, 0x2, 0x1, 0xFFFFF8024F530870)
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 Thu 09.01.2014 00:43: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 (0xFFFFFD7FFFFFF3E0, 0x2, 0x1, 0xFFFFF8024F530870)
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 Wed 08.01.2014 08:03:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010814-6234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800A4F31286, 0xFFFFD0003D985EA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 04.01.2014 19:00:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-6093-01.dmp
This was probably caused by the following module: ks.sys (ks+0x1E477)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80001B2E477, 0x0, 0x3C)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
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.
On Fri 03.01.2014 22:03:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-5734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7F (0x8, 0xFFFFD000207EC1B0, 0xFFFFD00025797000, 0xFFFFF8032FD4C5B4)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 03.01.2014 21:55:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-5781-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3222)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002F2B222, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\usbport.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: USB 1.1 & 2.0-Porttreiber
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.
