Liebe Leute,

ihr habt mir vor einigen Jahren bereits einmal mit einem Trojanerproblem geholfen, seitdem benutze ich Malwarebytes Antimalware in der Pro Version. Nun habe ich ein Problem mit dem Windows Standbymodus - bzw. gelegentlich (zuletzt häufigeren) Crashs sobald ich in den Standby gehen will. Erstmals ist das Problem vor 2-3 Wochen aufgetreten. Hardware habe ich keine verändert.

Board: Asus H97M-Plus mit Bios 2502
CPU: Inte i7-4790k
Ram: 4x Kingston KHX2400c11D3/4GX

Temparaturprobleme kann ich eigentlich ausschließen. Die CPU-Temparatur liegt aktuell bei 37° idle - Last nich über 60°. Hierführ habe ich vor einigen Monaten viel gemacht und in eine vernünftige Kühlung investiert, da ich zuvor bei Spielen gelegentlich Probleme hatte. Seitdem gibt es diesbezüglich keine Schwierigkeiten mehr. Voe allem spiele ich kaum noch und die Grafikkarte (GTX960) stellt zumeist nur den Desktop dar.

Bios habe ich vor ein paar Tagen aktualisiert in der Hoffnung das Problem zu lösen.
Heute habe ich Bitdefender deinstalliert, da ich dachte villeicht ist die Antivirensoftware schuld. Diese habe ich (glaube ich) kurz bevor das Problem zum ersten mal aufgetreten ist installiert.

In der Hoffnung selber einen Treiber zu identifizieren, der für das Problem verantwortlich ist, habe ich WhoCrashed ausgeführt.
Folgendes für mich nichtssagendes Resultat ist dabei rausgekommen (siehe unten)

Für eure Hilfe wäre ich dankbar.

Danke, Daniel

WhoCrashed Log:

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

computer name: ARBEITSZIMMER
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., H97M-PLUS
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17121374208 total
VM: 2147352576, free: 1888833536




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 02.08.2015 16:47:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080215-7222-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800C7A5700, 0xFFFFF80000B9A3D8, 0xFFFFFA8011985010)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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 Sun 02.08.2015 16:47:19 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: 0x9F (0x3, 0xFFFFFA800C7A5700, 0xFFFFF80000B9A3D8, 0xFFFFFA8011985010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Sun 02.08.2015 07:53:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080215-7534-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800C7CA4D0, 0xFFFFF800041F63D8, 0xFFFFFA80173AE510)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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 01.08.2015 19:01:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080115-7753-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800C7A9980, 0xFFFFF80000B9A3D8, 0xFFFFFA8015414CA0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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 27.07.2015 15:17:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072715-7347-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800C7AABB0, 0xFFFFF800041BF3D8, 0xFFFFFA8019264AA0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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 22.07.2015 17:50:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072215-7347-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800C7AABB0, 0xFFFFF80000B9A3D8, 0xFFFFFA8012E7C400)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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 22.07.2015 06:07:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072215-7706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800C7AA980, 0xFFFFF80000B9A3D8, 0xFFFFFA8013B77340)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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 Sun 19.07.2015 14:53:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071915-7129-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800C7A94D0, 0xFFFFF80000B9A3D8, 0xFFFFFA800CEE1450)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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 Sun 19.07.2015 08:57:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071915-7269-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800C7A6060, 0xFFFFF80000B9A3D8, 0xFFFFFA80100630F0)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state.
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
--------------------------------------------------------------------------------

9 crash dumps have 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 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.

Hi,

wenn du noch einen älteren Wiederherstellungspunkt haben solltest, würde ich den zurückspielen.....

Deine "Analysedaten" sagen leider nicht viel aus: Sobald der "Treiber" nämlich irgendwie "Kernel" heißt, handelt es sich um einen Absturz - mehr Aussagen lassen sich damit leider nicht treffen.

Was mir so spontan dazu einfällt, wäre:

1) Energiemanagement auf Standardwerte setzen

2) Auslagerungsdatei auf Standard setzen falls verändert

3) Sämtliche Tuningtools (wie TuneUp, GlaryUtilities etc.) zurücksetzen, deinstallieren und nie (!!) mehr verwenden

4) ACPI im Bios überprüfen bzw. auch im BIOS Default-Werte verwenden

Liebe Grüße, Alois

Post © Alois 2015 – Alle Rechte vorbehalten – kein Teil darf in irgendeiner Form ohne schriftliche Genehmigung des Autors kritisiert werden!

@Daniel Wien
Dir ist bei der Suche sicherlich diese Anleitung entgangen, wie man MiniDumps auswertet

Danke. Ich hab Windows neu installiert, jetzt läuft es wieder problemlos.

Brutal aber wirksam - danke für deine Rückmeldung!

Liebe Grüße, Alois