Windows 7 Ultimate 64 Bit - Ständige Bluescreens

darkKO

PCGH-Community-Veteran(in)
Windows 7 Ultimate 64 Bit - Ständige Bluescreens

Hallo Freunde...

Ich bekomm in letzter Zeit ständige Bluescreens.

Unter folgenden Vorraussetzungen (meistens jedenfalls) tauchen die BS´s auf:

Beim herunterfahren (sehr häufig)
Beim beenden von Google Chrome (relativ häufig)
Beim beenden von Steam (eher selten)
Beim starten von Windows (eher selten)
manchmal einfach so im Idle (selten)

und das sind die Bluescreens:

IMG_20140323_062846.jpg IMG_20140402_020759.jpg IMG_20140507_161746.jpg IMG_20140920_125957.jpg

Beim Spielen oder im normalen Betrieb kommen eigentlich nie Bluescreens. Einzig bei CS:GO kam mal einer, aber das ist schon ne Weile her und ist daher wohl eher als sporadisch zu betrachten.

Der letzte Bluescreen (wdf01000.sys) kam übrigens erst vorhin beim hochfahren das erste Mal. Die anderen tauchen relativ häufig in wechselnder Reihenfolge auf.

Hier ein aktueller Screenshot der Hardware Info´s:

desktop.jpg
123.gif

Ich denke, auf dem Screen sind alle relevanten Infos vorhanden, falls nicht, einfach fragen.

Folgendes habe ich bereits gemacht:

Alle Treiber aktualisiert
RAM mit Memtest86 getestet. Keine Fehler
Wärmeleitpaste erneuert (Lüfter drehen auch alle)

---------------

So, irgendwer vielleicht ne Ahnung an was es liegen könnte? Beim Googeln kam meist irgendwas mit Speicherfehlern (RAM, Graka) raus, aber da Memtest keine Fehler angezeigt hat und ich problemlos stundenlang ohne Probleme zocken kann denke ich eigentlich nicht, dass es am RAM oder der Grafikkarte liegt, oder was meint ihr.

Ach ja, die Sysinfo in meiner Sig ist nicht mehr so ganz aktuell:

Folgende Änderungen hats mittlerweile gegeben

Grafikkarte: Gigabyte Radeon 7870 GHz OC, 2 GB
Soundkarte: Asus Xonar DX (PCIe)
Tastatur: A4Tech X7
Maus: Trust GXT33
CPU nicht mehr übertaktet (läuft jetzt im Standardtakt)
die Festplatten (siehe Screen oben)

//EDIT

Gerade das Programm "WhoCrashed" entdeckt...Das spuckt mir folgende Analysen der Minidumps aus (vielleicht kann ja jemand was damit anfangen):

Code:
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 14.09.2014 23:36:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091514-16504-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002B260D) 
Bugcheck code: 0x50 (0xFFFFF900C38FFCF0, 0x0, 0xFFFFF960002B260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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. 



On Tue 09.09.2014 18:50:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090914-10717-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600035260D) 
Bugcheck code: 0x50 (0xFFFFF900C3C0A150, 0x0, 0xFFFFF9600035260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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. 



On Mon 01.09.2014 14:07:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090114-16036-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600030260D) 
Bugcheck code: 0x50 (0xFFFFF900C29C5030, 0x0, 0xFFFFF9600030260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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. 



On Fri 29.08.2014 17:10:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082914-15771-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xC7DBB) 
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88012199DBB, 0xFFFFF88003EB3368, 0xFFFFF88003EB2BD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.). 
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Sun 24.08.2014 21:34:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082514-12012-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002D260D) 
Bugcheck code: 0x50 (0xFFFFF900C3583CF0, 0x0, 0xFFFFF960002D260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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. 



On Sun 24.08.2014 00:07:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082414-11980-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880) 
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80004AD3B2C)
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 Mon 18.08.2014 21:31:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081914-12573-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002B260D) 
Bugcheck code: 0x50 (0xFFFFF900C4A7DCF0, 0x0, 0xFFFFF960002B260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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. 



On Sun 17.08.2014 00:27:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081714-12012-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002A260D) 
Bugcheck code: 0x50 (0xFFFFF900C45DDCF0, 0x0, 0xFFFFF960002A260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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. 



On Thu 14.08.2014 21:30:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081514-16130-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600032260D) 
Bugcheck code: 0x50 (0xFFFFF900C44E6CF0, 0x0, 0xFFFFF9600032260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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. 



On Mon 11.08.2014 21:29:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081214-11528-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600029260D) 
Bugcheck code: 0x50 (0xFFFFF900C2855CF0, 0x0, 0xFFFFF9600029260D, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
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.

und:

Zwischenablage02.jpg

//Nochmal EDIT

Hab gerade noch das BIOS geupdatet (auf die aktuelle Version 17.20). Glaub zwar nicht, dass es was bringt, aber mal abwarten.
 
Zuletzt bearbeitet:
AW: Windows 7 Ultimate 64 Bit - Ständige Bluescreens

Hallo,

Hast du was übertaktet an deinem System?


Ich hatte vor kurzem mir auch völlig unerklärliche Bluescreens.
Nachdem ich die Übertaktung rausgenomm und Windows neu installiert habe wurde es nicht besser.
Hab den PC dann vom Strom genommen (NT entladen) und die Batterie onboard entfernt für ein paar Stunden. Nun gehts wieder. :)

MfG
 
AW: Windows 7 Ultimate 64 Bit - Ständige Bluescreens

Nein, alles Standardtakt. Hab früher mal übertaktet, aber das ist schon ne ganze Weile her.
 
AW: Windows 7 Ultimate 64 Bit - Ständige Bluescreens

Hm, okay. Sollte es wieder Bluescreens geben probier einfach mal das Selbe wie ich aus.
Einfach den PC komplett vom Strom nehmen (NT entladen, einfach nochmal den Powerbutton lieb drücken :ugly:), Batterie raus und ein paar Stunden (2-3) in ruhe lassen.
Schaden kann es ja nicht, bis auf dass du dann natürlich wieder das BIOS neu einstellen musst.

MfG
 
AW: Windows 7 Ultimate 64 Bit - Ständige Bluescreens

Hast du deine Bluescreens eigentlich schon mal gegoogelt ?

Hast du meinen Startpost eigentlich schon mal durchgelesen?

...So, irgendwer vielleicht ne Ahnung an was es liegen könnte? Beim Googeln kam meist irgendwas mit Speicherfehlern (RAM, Graka) raus, aber da Memtest keine Fehler angezeigt hat und ich problemlos stundenlang ohne Probleme zocken kann denke ich eigentlich nicht, dass es am RAM oder der Grafikkarte liegt, oder was meint ihr...
 
Zurück