BSoD beim Start; w10pro64bit

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-7LTAL32
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: Akoya P5360 E MD8881/2478, MEDION, H110H4-EM
CPU: GenuineIntel Intel(R) Core(TM) i5-6402P CPU @ 2.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8507248640 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 25.10.2017 15:47:38 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-55453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960) 
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80373EF2588)
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. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

One crash dump has been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.