[:.Tker.:]
Legacy Member
Goedendag,
Ik heb een nieuwe 3dkaart en ram kitje in mijn pc gestoken.
Met driver cleaner heb ik ook al de drivers van mijn vorige 3d kaart verwijdert. Daarna heb ik de nieuwste drivers afgehaald voor de nieuwe 3d kaart.
Nu al zo een 5 keer een bluescreen gehad bij het opstarten , tijdens en afsluiten van een spel (BF3, Haunted hells reach, Killingfloor, enz...)
als iemand me hiermee kan helpen.
Dank bij voorbaat.
huidige specs:
-MS Windows 7 Ultimate 64-bit SP1
-AMD Athlon II X4 645 Quad Core 3.1 GHz
-8,00 GB RAM
-MSI 880GM-E41
-MSI AMD Radeon HD 6870
-500GB HDD
-500 watt voeding
Crashlogjes:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 27/11/2011 21:10:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112711-19952-01.dmp
uptime: 12:15:15
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008666990, 0xFFFFFA80086669D0, 0x404000B)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 which cannot be identified at this time.
On Sun 27/11/2011 21:10:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 12:15:15
This was probably caused by the following module: ntfs.sys (Ntfs+0x2D53)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008666990, 0xFFFFFA80086669D0, 0x404000B)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates that a pool header is corrupt.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 24/11/2011 18:32:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112411-14211-01.dmp
uptime: 03:45:12
This was probably caused by the following module: atikmdag.sys (atikmdag+0x3A5C23)
Bugcheck code: 0xD1 (0x9C, 0x2, 0x1, 0xFFFFF88004A0BE7D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies 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, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 19/11/2011 15:49:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111911-16707-01.dmp
uptime: 05:40:27
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x18 (0xFFFFFA8006A32570, 0xFFFFFA80084C3A20, 0x1, 0xFFFFFA80084C39FF)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
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 which cannot be identified at this time.
On Fri 11/11/2011 18:09:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111111-18688-01.dmp
uptime: 06:51:52
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA800A600000, 0x2, 0x0, 0xFFFFF80003078E30)
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 which cannot be identified at this time.
Ik heb een nieuwe 3dkaart en ram kitje in mijn pc gestoken.
Met driver cleaner heb ik ook al de drivers van mijn vorige 3d kaart verwijdert. Daarna heb ik de nieuwste drivers afgehaald voor de nieuwe 3d kaart.
Nu al zo een 5 keer een bluescreen gehad bij het opstarten , tijdens en afsluiten van een spel (BF3, Haunted hells reach, Killingfloor, enz...)
als iemand me hiermee kan helpen.
Dank bij voorbaat.
huidige specs:
-MS Windows 7 Ultimate 64-bit SP1
-AMD Athlon II X4 645 Quad Core 3.1 GHz
-8,00 GB RAM
-MSI 880GM-E41
-MSI AMD Radeon HD 6870
-500GB HDD
-500 watt voeding
Crashlogjes:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 27/11/2011 21:10:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112711-19952-01.dmp
uptime: 12:15:15
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008666990, 0xFFFFFA80086669D0, 0x404000B)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 which cannot be identified at this time.
On Sun 27/11/2011 21:10:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 12:15:15
This was probably caused by the following module: ntfs.sys (Ntfs+0x2D53)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008666990, 0xFFFFFA80086669D0, 0x404000B)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates that a pool header is corrupt.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 24/11/2011 18:32:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112411-14211-01.dmp
uptime: 03:45:12
This was probably caused by the following module: atikmdag.sys (atikmdag+0x3A5C23)
Bugcheck code: 0xD1 (0x9C, 0x2, 0x1, 0xFFFFF88004A0BE7D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies 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, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 19/11/2011 15:49:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111911-16707-01.dmp
uptime: 05:40:27
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x18 (0xFFFFFA8006A32570, 0xFFFFFA80084C3A20, 0x1, 0xFFFFFA80084C39FF)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
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 which cannot be identified at this time.
On Fri 11/11/2011 18:09:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111111-18688-01.dmp
uptime: 06:51:52
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA800A600000, 0x2, 0x0, 0xFFFFF80003078E30)
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 which cannot be identified at this time.