Ich suche dringend nach jemandem der mir sagen kann was das für ein treiber ist der für die Bluescreens sorgt.
Folgend die Inhalte der dmp Dateien.
System Information (local)
Computer name:
KARLARIA
Windows version: Windows Server 2016 , 10.0, build: 17763
Windows
dir: C:\Windows
Hardware: MS-7817, MSI, B85M-E45 (MS-7817)
CPU:
GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Intel586, level: 6
4
logical processors, active mask: 15
RAM: 17043132416 bytes
(15,9GB)
Crash Dump Analysis
Crash dumps
are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 24.01.2019 16:50:39 your computer
crashed or a problem was reported
crash dump file:
C:\Windows\Minidump\012419-6593-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x1B3440)
Bugcheck code: 0xA
(0xFFFFE8060FE93CB0, 0x2, 0x0, 0xFFFFF806117BF37B)
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 is a
software bug.
This bug check belongs to the crash dump test that you have
performed with WhoCrashed or other software. It means that a crash dump file was
properly written out.
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 24.01.2019 16:50:39 your computer crashed or a problem was
reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably
caused by the following module: win32kfull.sys
(win32kfull!NtUserWin32kSysCallFilterStub+0x5E8)
Bugcheck code: 0xA
(0xFFFFE8060FE93CB0, 0x2, 0x0, 0xFFFFF806117BF37B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path:
C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop
Win32k Kernel Driver
Bug check description: This indicates that Microsoft
Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or
above. This is a software bug.
This bug check belongs to the crash dump test
that you have performed with WhoCrashed or other software. It means that a crash
dump file was properly written out.
The crash took place in a 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
Thu 24.01.2019 16:19:10 your computer crashed or a problem was
reported
crash dump file: C:\Windows\Minidump\012419-6703-01.dmp
This
was probably caused by the following module:
hidparse.sys (0xFFFFF802185924E8)
Bugcheck code:
0xD1 (0x21, 0x2, 0x0, 0xFFFFF802185924E8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path:
C:\Windows\system32\drivers\hidparse.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Parsing
Library
Bug check description: This indicates that a kernel-mode driver
attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with
WhoCrashed or other software. It means that a crash dump file was properly
written out.
The crash took place in a 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
Thu 24.01.2019 14:12:13 your computer crashed or a problem was
reported
crash dump file: C:\Windows\Minidump\012419-7625-01.dmp
This
was probably caused by the following module:
ntoskrnl.exe (nt+0x1B3440)
Bugcheck code: 0x3B
(0xC000001D, 0xFFFFF8051E9A279B, 0xFFFF8504FBCF3930, 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.
