| Radelklaus | 06.06.2016 12:05 |
Moin moin Sandra,
jap, hatte ich auch so gedacht :) meinte, ob ich noch ergänzend etwas tun kann.
Bin mir nicht sicher, ob alle Updates installiert wurden. Was ich mitbekommen habe, die Installation von .NET Framework (KB3136000) wurde beendet. Hierzu befanden sich auch noch Installationsdateien im Root-Verzeichnis.
Während der 24h abgesicherter Modus ist kein BlueScreen aufgetreten. Jetzt habe ich wieder "normal" gebootet, weil ich im abgesicherten Modus keine VMware starten kann.
Hast du noch ne Idee? Am kommenden WE könnte ich den Laptop länger im abgesicherten Modus laufen lassen.
Danke und Grüße
Klaus
Schau mal Sandra,
habe hier das Ergebnis von WhoCrashed eingestellt: Code:
System Information (local)
--------------------------------------------------------------------------------
computer name: AA_PROG01
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Precision 7710, Dell Inc., 072J5K
CPU: GenuineIntel Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 34231144448 total
VM: 2147352576, free: 1898946560
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 04.06.2016 09:26:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060416-7846-01.dmp
This was probably caused by the following module: stdcfltn.sys (stdcfltn+0x1D18)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8027A5A500, 0xFFFFFA8027A5A5C0, 0xC0C0022)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\stdcfltn.sys
product: Disk Class Filter Driver for Accelerometer
company: ST Microelectronics
description: Disk Class Filter Driver for Accelerometer
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.
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: stdcfltn.sys (Disk Class Filter Driver for Accelerometer, ST Microelectronics).
Google query: ST Microelectronics BAD_POOL_HEADER
On Fri 03.06.2016 09:27:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060316-8658-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80299E0580, 0xFFFFFA80299E0640, 0xC0C0001)
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 Thu 02.06.2016 09:33:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060216-7519-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x19 (0x20, 0xFFFFFA802F9076C0, 0xFFFFFA802F907780, 0xC0C0003)
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 01.06.2016 11:41:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060116-12214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8029760400, 0xFFFFFA80297604C0, 0xC0C0001)
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 Tue 31.05.2016 11:21:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053116-7722-01.dmp
This was probably caused by the following module: stdcfltn.sys (stdcfltn+0x1D18)
Bugcheck code: 0x19 (0x20, 0xFFFFFA802B6F0B80, 0xFFFFFA802B6F0C40, 0xC0C0002)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\stdcfltn.sys
product: Disk Class Filter Driver for Accelerometer
company: ST Microelectronics
description: Disk Class Filter Driver for Accelerometer
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.
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: stdcfltn.sys (Disk Class Filter Driver for Accelerometer, ST Microelectronics).
Google query: ST Microelectronics BAD_POOL_HEADER
On Mon 30.05.2016 10:02:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053016-12807-01.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0xC948C)
Bugcheck code: 0xD1 (0xFFFFF8800BC25000, 0x2, 0x1, 0xFFFFF8800114648C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastora.sys
product: Intel(R) Rapid Storage Technology driver
company: Intel Corporation
description: Intel(R) Rapid Storage Technology driver - x64
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: iastora.sys (Intel(R) Rapid Storage Technology driver - x64, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 30.05.2016 10:02:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0xC948C)
Bugcheck code: 0xD1 (0xFFFFF8800BC25000, 0x2, 0x1, 0xFFFFF8800114648C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastora.sys
product: Intel(R) Rapid Storage Technology driver
company: Intel Corporation
description: Intel(R) Rapid Storage Technology driver - x64
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: iastora.sys (Intel(R) Rapid Storage Technology driver - x64, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 27.05.2016 09:31:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052716-134660-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70380)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8024F7F080, 0xFFFFFA8024F7F140, 0xC0C0008)
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 Sun 22.05.2016 09:36:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052216-8377-01.dmp
This was probably caused by the following module: stdcfltn.sys (stdcfltn+0x1D18)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80254C71C0, 0xFFFFFA80254C7280, 0xC0C0018)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\stdcfltn.sys
product: Disk Class Filter Driver for Accelerometer
company: ST Microelectronics
description: Disk Class Filter Driver for Accelerometer
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.
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: stdcfltn.sys (Disk Class Filter Driver for Accelerometer, ST Microelectronics).
Google query: ST Microelectronics BAD_POOL_HEADER
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
9 crash dumps have been found and analyzed. 2 third party drivers have 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:
stdcfltn.sys (Disk Class Filter Driver for Accelerometer, ST Microelectronics)
iastora.sys (Intel(R) Rapid Storage Technology driver - x64, Intel Corporation)
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.
Hilft dir das weiter?
LG Klaus |
