hallo ich habe seit mehreren wochen das problem das mein pc nicht mehr richtig funktioniert.
zuerst war es nur bei videos und im chrome.
diablo 3 läuft stundenlang ohne probleme.
das system wurde vor ca 2 wochen neu aufgespielt und alle aktuellen treiber installiert.
neuerdings schreibt er keine minidumb dateien mehr.
wir wollen morgen ein neues netzteil einbauen
ich bedanke mich schonmal im voraus
ich habe who crashed installiert und hier das ergebnis :
On Mon 02.09.2013 19:04:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88001A4449C)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001A4449C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 01.09.2013 11:44:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\minidump 2.9.2013\090113-13899-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C4449C)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001C4449C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-Treiber
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 01.09.2013 11:44:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090113-13899-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C4449C)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001C4449C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-Treiber
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 Thu 29.08.2013 20:38:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082913-13447-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-Treiber
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 Thu 29.08.2013 20:38:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082913-13447-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-Treiber
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 Thu 29.08.2013 13:41:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082913-13930-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-Treiber
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 Thu 29.08.2013 13:41:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082913-13930-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-Treiber
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 Wed 28.08.2013 11:50:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13400-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-Treiber
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 Wed 28.08.2013 11:50:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082813-13400-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-Treiber
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 Wed 28.08.2013 11:10:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13743-02.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF8800461BA03)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x 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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 28.08.2013 11:10:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082813-13743-02.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF8800461BA03)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x 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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 28.08.2013 02:11:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13993-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x19 (0x22, 0xFFFFFA8000000000, 0x0, 0x0)
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 that cannot be identified at this time.
On Wed 28.08.2013 02:11:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082813-13993-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x19 (0x22, 0xFFFFFA8000000000, 0x0, 0x0)
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 that cannot be identified at this time.
On Wed 28.08.2013 02:05:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-12994-01.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF88003EAFA03)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x 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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 28.08.2013 02:05:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082813-12994-01.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF88003EAFA03)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x 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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL