wildsau666
Cadet 3rd Year
- Registriert
- Okt. 2006
- Beiträge
- 50
Hallo,
habe ein MSI 6QE mit Windows 10 und wenn ich das Notebook zuklappe habe ich beim Neustart immer wieder diese Fehlermeldung.
Kann mir jemand sagen, was ich mit dieser Information nun weiter anstelle?
habe ein MSI 6QE mit Windows 10 und wenn ich das Notebook zuklappe habe ich beim Neustart immer wieder diese Fehlermeldung.
System Information (local)
Computer name: XXXXXXX-NB
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: GT72S 6QE, Micro-Star International Co., Ltd., MS-1782
CPU: GenuineIntel Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 42900758528 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 07.09.2016 22:44:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090816-5921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8026FED2C9F)
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 Wed 07.09.2016 22:44:33 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 (0x8, 0x2, 0x0, 0xFFFFF8026FED2C9F)
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.
Kann mir jemand sagen, was ich mit dieser Information nun weiter anstelle?