Guten Abend
Habe seit längerem Probleme mit meinem Rechner und habe mich jetzt mal dazu durchgerungen in ein forum zu posten

Es treten gefühlt zufällig freezes und bluescreens auf, nach mehrmaligen neu starten läuft er aber auch irgendwann stabil...

Prozessor AMD Phenom II X4 965
Grafikkarte geforce gtx 460 1gb
Dazu 12 GB RAM
und weiterhin eine ssd auf der windows 7 (64 bit) läuft sowie eine normale hdd mit einem terrabyte

Probleme gab es auch mit den grafikkarten treibern,welche sich aber nach einem update aufgelöst haben

Auslese von whocrash

Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASRock, 870 Extreme3
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 12884103168 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 22.11.2015 15:20:53 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: 0xC4 (0x91, 0x2, 0xFFFFFA800B66C060, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. 
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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 16.11.2015 17:32:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111615-10842-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0x1A (0x5001, 0xFFFFF70001080000, 0x114D, 0x114EFFFFFFFC)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
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 20.10.2015 08:18:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102015-9968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74890) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 19.10.2015 13:54:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-10124-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0x1A (0x41287, 0x80, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
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 14.10.2015 21:37:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101415-11372-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030E8EC0, 0x1, 0x6ED)
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 05.10.2015 16:04:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100515-10389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7E089) 
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800030CEB73)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Fri 25.09.2015 11:51:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092515-10888-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0xA (0xFFFFF88003000381, 0xD, 0x0, 0xFFFFF80003091B1C)
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 Sun 06.09.2015 17:07:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090615-10639-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800030D7750)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 Intel CPU generated a trap and the kernel failed to catch this trap.
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 05.09.2015 14:47:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090515-10155-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0xA (0x20, 0xD, 0x0, 0xFFFFF80003152082)
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 Thu 03.09.2015 21:48:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090315-10077-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) 
Bugcheck code: 0x40000082 (0xFFFFFFFFFFFFFBA8, 0x0, 0xFFFFF800030F3FCC, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 





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

21 crash dumps have been found and analyzed. Only 10 are included in this report. 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: 

amdsata.sys (AHCI 1.2 Device Driver, Advanced Micro Devices)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.
         

Danke für diese ausführliche Beschreibung

Arbeitsspeicherüberprüfung mit Memtest86+
Lade dir dazu folgendes Tool herunter:
Memtest86+ - Advanced Memory Diagnostic Tool

Ein dazugehöriges Tutorial:
[HowTo] Wie testet man den RAM mit Memtest86+?

Sobald rote Zeilen auf dem Schirm erscheinen, ist mindestens ein Riegel von deinem Arbeitsspeicher physikalisch beschädigt und er muss getauscht werden.

Zitat von burningice

Danke für diese ausführliche Beschreibung

Arbeitsspeicherüberprüfung mit Memtest86+
Lade dir dazu folgendes Tool herunter:
Memtest86+ - Advanced Memory Diagnostic Tool

Ein dazugehöriges Tutorial:
[HowTo] Wie testet man den RAM mit Memtest86+?

Sobald rote Zeilen auf dem Schirm erscheinen, ist mindestens ein Riegel von deinem Arbeitsspeicher physikalisch beschädigt und er muss getauscht werden.

Danke
Je mehr Informationen desto einfacher kann einem geholfen werden,ich finde das selbstvertändlich
Und auch danke für deine Antwort, ich melde mich wieder
Zunächst aber noch einen schönen Abend

Der Arbeitsspeicher scheint in Ordnung zu sein

Na dann.

Als nächstes benötige ich deine Dumpdateien. Dazu lade bitte folgende Dateien auf eine Dropbox oder dergleichen hoch und teile sie hier:

C:\Windows\memory.dmp
C:\Windows\Minidump\ (der komplette Ordner)

Insbesondere das vollständige memory.dmp ist beachtlich groß. Wenn es dir unmöglich ist, diese Datei hochzuladen, tun es notfalls auch nur die Minidump Dateien.

Zitat von burningice

Na dann.

Als nächstes benötige ich deine Dumpdateien. Dazu lade bitte folgende Dateien auf eine Dropbox oder dergleichen hoch und teile sie hier:

C:\Windows\memory.dmp
C:\Windows\Minidump\ (der komplette Ordner)

Insbesondere das vollständige memory.dmp ist beachtlich groß. Wenn es dir unmöglich ist, diese Datei hochzuladen, tun es notfalls auch nur die Minidump Dateien.

Wiedermals Danke für deine zeitige Antwort
Ich lade die Dateien momentan hoch
Nebenbei gefragt ist es theoretisch möglich dass diese Fehler und Freezes durch ein virtuelles laufwerk entstehen können?
Wie ich darauf komme ist dass ich,aufgrund von memorytest86 das virtuelle laufwerk ausschalten musste weil es sonst nicht möglich war die cd zu booten..
seit dem hatte ich bis jetzt keinen freeze mehr aber mal schauen...
Entchuldige bitte meine etwas übermudete klein und großschreibung sowie die grammatikfehler
MFG knechti

https://drive.google.com/file/d/0B-AsliHLwZHFNkN2ODZfQXBOcFU/view?usp=sharing

Ich hoffe das hat funktioniert

Wie haben sich die Probleme entwickelt?

Ansonsten mal bitte deinen Chipsatztreiber und Grafikkartentreiber komplett neuinstallieren.

Zitat von burningice

Wie haben sich die Probleme entwickelt?

Ansonsten mal bitte deinen Chipsatztreiber und Grafikkartentreiber komplett neuinstallieren.

Bis jetzt läuft er stabil

Mhh aber wo bekomme ich denn Chipsatztreiber?