Hallo Leute,
ich brauche dringend eure Hilfe! Ich habe am vergangenen Samstag zwei neue RAM-Module in meinen PC eingebaut, um von 8GB auf 16GB aufzustocken. Es handelt sich um folgende Module:
Crucial Ballistix Sport DIMM Kit 8GB, DDR3-1600, CL9-9-9-24 (BLS2CP4G3D1609DS1S00/BLS2C4G3D169DS3CEU) Preisvergleich | Geizhals Deutschland
Diese sind definitiv kompatibel mit meinem bisherigen Arbeitsspeicher und mit meinem Mainboard...ich habe zwar leider nicht so viel Ahnung, aber das habe ich natürlich vorher überprüft! Mein Rechner läuft mit Windows 8 und auch im System wird der Arbeitsspeicher erkannt, also es werden 16GB angezeigt.
Hier mein mainboard und schon vorhandener RAM:
49363 - Gigabyte H87-HD3 Intel H87 So.1150 Dual Channel DDR3 ATX
8GB G.Skill RipjawsX DDR3-1600 DIMM CL9 Dual Kit - Hardware,
Nun zu meinem Problem: Der Rechner läuft eigentlich einwandfrei, ich kann ganz normal surfen, schreiben, programmieren...alles kein Problem! Nur, wenn ich spiele stürzt der PC gelegentlich ab (Bluescreen > Neustart). Dieses Problem tritt teilweise mehrmals relativ kurz hintereinander auf, teilweise auch gar nicht, oder in größeren Abständen. Auf den Bluescreens selbst kann man nichts lesen! Der Bildschirm ist einfach nur blau und es sind ein paar verzerrte weiße/graue Streifen zu sehen. Ich habe natürlich schonmal ein bisschen gegoogled, aber leider ohne Erfolg. Ich habe schon den Windows-internen Memory-Check laufen lassen und der hat ergeben, dass der Arbeitsspeicher keine Mängel aufweist.
Zudem habe ich mir das Programm "WhoCrashed" geladen, um die dumpfiles zu lesen. Hier das Ergebnis:
computer name: XXXXX
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: H87-HD3, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17052983296 total
VM: 2147352576, free: 1923174400
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 06.05.2014 18:05:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050614-5843-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF8017EA5A440)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800120267E, 0xFFFFF8801ABF6D60, 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.
Google query: SYSTEM_SERVICE_EXCEPTION
On Tue 06.05.2014 18:05:46 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8017EA5A440)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800120267E, 0xFFFFF8801ABF6D60, 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.
Google query: SYSTEM_SERVICE_EXCEPTION
On Tue 06.05.2014 10:15:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050614-6750-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88003991A52)
Bugcheck code: 0xD1 (0xFFFFFA8412BCC558, 0x2, 0x0, 0xFFFFF88003991A52)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 05.05.2014 09:28:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-7562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xC5 (0xFFFFF6FB40000000, 0x2, 0x0, 0xFFFFF800A768486C)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Sun 04.05.2014 23:49:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-7843-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF96000063267)
Bugcheck code: 0x50 (0xFFFFF901123CC630, 0x0, 0xFFFFF96000063267, 0x2)
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 04.05.2014 23:11:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-7859-01.dmp
This was probably caused by the following module: atikmdag.sys (0xFFFFF88004B8FFA0)
Bugcheck code: 0xD1 (0x144, 0xB, 0x0, 0xFFFFF88004B8FFA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 04.05.2014 23:09:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-6640-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800360C9F2)
Bugcheck code: 0xD1 (0xFFFFCE809D987398, 0x2, 0x0, 0xFFFFF8800360C9F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 04.05.2014 22:35:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-17515-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF801A80D7440)
Bugcheck code: 0xC2 (0x11, 0xFFFFFA800F4C0D00, 0xA080001, 0x2A65B8DB9BDC6974)
Error: BAD_POOL_CALLER
Bug check description: This indicates that the current thread is making a bad pool request.
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.
Google query: BAD_POOL_CALLER
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
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.
Wie ich lesen konnte, scheint es ja kein Hardware-Problem, sondern ein Software-/Treiber-Problem zu sein. Also habe ich versucht mit dem Stichwort "atikmdag.sys" ein entsprechendes Treiberupdate zu finden, allerdings ohne Erfolg!
Ich hoffe ihr könnt mir helfen!! Falls ihr zusätzliche Infos benötigt, dann gebt mir einfach Bescheid! Danke!!
Beste Grüße
maschmi
ich brauche dringend eure Hilfe! Ich habe am vergangenen Samstag zwei neue RAM-Module in meinen PC eingebaut, um von 8GB auf 16GB aufzustocken. Es handelt sich um folgende Module:
Crucial Ballistix Sport DIMM Kit 8GB, DDR3-1600, CL9-9-9-24 (BLS2CP4G3D1609DS1S00/BLS2C4G3D169DS3CEU) Preisvergleich | Geizhals Deutschland
Diese sind definitiv kompatibel mit meinem bisherigen Arbeitsspeicher und mit meinem Mainboard...ich habe zwar leider nicht so viel Ahnung, aber das habe ich natürlich vorher überprüft! Mein Rechner läuft mit Windows 8 und auch im System wird der Arbeitsspeicher erkannt, also es werden 16GB angezeigt.
Hier mein mainboard und schon vorhandener RAM:
49363 - Gigabyte H87-HD3 Intel H87 So.1150 Dual Channel DDR3 ATX
8GB G.Skill RipjawsX DDR3-1600 DIMM CL9 Dual Kit - Hardware,
Nun zu meinem Problem: Der Rechner läuft eigentlich einwandfrei, ich kann ganz normal surfen, schreiben, programmieren...alles kein Problem! Nur, wenn ich spiele stürzt der PC gelegentlich ab (Bluescreen > Neustart). Dieses Problem tritt teilweise mehrmals relativ kurz hintereinander auf, teilweise auch gar nicht, oder in größeren Abständen. Auf den Bluescreens selbst kann man nichts lesen! Der Bildschirm ist einfach nur blau und es sind ein paar verzerrte weiße/graue Streifen zu sehen. Ich habe natürlich schonmal ein bisschen gegoogled, aber leider ohne Erfolg. Ich habe schon den Windows-internen Memory-Check laufen lassen und der hat ergeben, dass der Arbeitsspeicher keine Mängel aufweist.
Zudem habe ich mir das Programm "WhoCrashed" geladen, um die dumpfiles zu lesen. Hier das Ergebnis:
computer name: XXXXX
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: H87-HD3, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17052983296 total
VM: 2147352576, free: 1923174400
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 06.05.2014 18:05:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050614-5843-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF8017EA5A440)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800120267E, 0xFFFFF8801ABF6D60, 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.
Google query: SYSTEM_SERVICE_EXCEPTION
On Tue 06.05.2014 18:05:46 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8017EA5A440)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800120267E, 0xFFFFF8801ABF6D60, 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.
Google query: SYSTEM_SERVICE_EXCEPTION
On Tue 06.05.2014 10:15:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050614-6750-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88003991A52)
Bugcheck code: 0xD1 (0xFFFFFA8412BCC558, 0x2, 0x0, 0xFFFFF88003991A52)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 05.05.2014 09:28:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-7562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xC5 (0xFFFFF6FB40000000, 0x2, 0x0, 0xFFFFF800A768486C)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Sun 04.05.2014 23:49:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-7843-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF96000063267)
Bugcheck code: 0x50 (0xFFFFF901123CC630, 0x0, 0xFFFFF96000063267, 0x2)
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 04.05.2014 23:11:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-7859-01.dmp
This was probably caused by the following module: atikmdag.sys (0xFFFFF88004B8FFA0)
Bugcheck code: 0xD1 (0x144, 0xB, 0x0, 0xFFFFF88004B8FFA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 04.05.2014 23:09:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-6640-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800360C9F2)
Bugcheck code: 0xD1 (0xFFFFCE809D987398, 0x2, 0x0, 0xFFFFF8800360C9F2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 04.05.2014 22:35:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050514-17515-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF801A80D7440)
Bugcheck code: 0xC2 (0x11, 0xFFFFFA800F4C0D00, 0xA080001, 0x2A65B8DB9BDC6974)
Error: BAD_POOL_CALLER
Bug check description: This indicates that the current thread is making a bad pool request.
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.
Google query: BAD_POOL_CALLER
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
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.
Wie ich lesen konnte, scheint es ja kein Hardware-Problem, sondern ein Software-/Treiber-Problem zu sein. Also habe ich versucht mit dem Stichwort "atikmdag.sys" ein entsprechendes Treiberupdate zu finden, allerdings ohne Erfolg!
Ich hoffe ihr könnt mir helfen!! Falls ihr zusätzliche Infos benötigt, dann gebt mir einfach Bescheid! Danke!!
Beste Grüße
maschmi
