[IMG][IMG]G:\_REFERENZMATERIAL\IT EDV\Bluescreen[/IMG][/IMG]Hallo,

seit etwa zwei Wochen stürzt mein PC beim oder kurz nach dem rauffahren oder bei der Rückkehr aus dem Standby-Modus hin- und wieder ab. Konkret circa bei jedem dritten Mal. Anbei hierzu die Screenshots.

Ich habe den Verdacht, dass dies damit zu tun hat, dass ich einmal bei eingeschaltetem PC den Monitor mit einem anderen PC kurzfristig verbunden habe, um diesen zu testen und anschliessend den Monitor wieder an meinem PC angeschlossen habe. Es könnte sein, dass dabei irgendwo am Mainboard oder auf der Grafikkarte ein Kurzschluss zustande gekommen ist.

Hier das Log von Bluescreenview:

==================================================
Dump File         : 091216-5132-01.dmp
Crash Time        : 12.09.2016 07:58:42
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`021af58f
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000001
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23455 (win7sp1_ldr.160516-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\091216-5132-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 311.272
Dump File Time    : 12.09.2016 07:59:39
==================================================

==================================================
Dump File         : 090616-5007-01.dmp
Crash Time        : 06.09.2016 09:15:40
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : ffffffff`fffbca24
Parameter 2       : 00000000`00000001
Parameter 3       : fffff800`02d71267
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23455 (win7sp1_ldr.160516-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\090616-5007-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275.632
Dump File Time    : 06.09.2016 09:16:53
==================================================

==================================================
Dump File         : 090516-5506-01.dmp
Crash Time        : 05.09.2016 14:28:18
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff800`02af85c7
Parameter 3       : fffff880`09380ec0
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23455 (win7sp1_ldr.160516-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\090516-5506-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275.744
Dump File Time    : 05.09.2016 14:29:25
==================================================

==================================================
Dump File         : 090516-9438-01.dmp
Crash Time        : 05.09.2016 09:26:44
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : ffffce7f`df8122f4
Parameter 2       : 00000000`00000001
Parameter 3       : fffff880`012a58e3
Parameter 4       : 00000000`00000007
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23455 (win7sp1_ldr.160516-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\090516-9438-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 268.800
Dump File Time    : 05.09.2016 09:37:10
==================================================
         

Einmal habe ich zudem die folgende Problemmeldung hierzu gespeichert. Weiß jemand einen guten Rat?

Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: a
BCP1: 000000010000009F
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002A718D3
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\090116-5070-01.dmp
C:\Users\Jan\AppData\Local\Temp\WER-18033-0.sysdata.xml

Lesen Sie unsere Datenschutzbestimmungen online:
hxxp://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen S

Lade Dir das Programm von Filepony und poste das Ergebnis.

hier das Ergebnis:

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

computer name: JAN-DELL
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Dell DXP061 , Dell Inc. , Dell Inc. , 0WG855
CPU: GenuineIntel Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 4225679360 total
VM: 2147352576, free: 1926791168




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 12.09.2016 05:58:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091216-5132-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800021AF58F, 0x0, 0x1)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Mon 12.09.2016 05:58:42 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800021AF58F, 0x0, 0x1)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 06.09.2016 07:15:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090616-5007-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0x50 (0xFFFFFFFFFFFBCA24, 0x1, 0xFFFFF80002D71267, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Mon 05.09.2016 12:28:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090516-5506-01.dmp
This was probably caused by the following module: hiber_iastor.sys (Unloaded_hiber_iaStor+0xFEEC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002AF85C7, 0xFFFFF88009380EC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hiber_iastor.sys . 
Google query: hiber_iastor.sys SYSTEM_SERVICE_EXCEPTION



On Mon 05.09.2016 07:26:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090516-9438-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF880012A58E3) 
Bugcheck code: 0x50 (0xFFFFCE7FDF8122F4, 0x1, 0xFFFFF880012A58E3, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates that invalid system memory has been referenced.
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. 




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

5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 

hiber_iastor.sys 

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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 actually 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.
         

Naja, in den Schlussfolgerungen kannst Du nachlesen, wo der Fehler liegt und was Du machen kannst. Folge erst mal den Anweisungen. Dann kannst Du die Minidumps erst mal löschen. Wenn wieder BSODs auftreten, kannst Du das Programm ja nochmal laufen lassen und das Ergebnis posten.

GL