Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sat 31/01/2015 22:13:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\020115-29859-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x9F (0x3, 0xFFFFE001015EF4D0, 0xFFFFD0013D8D3960, 0xFFFFE00109CB29A0) Error: DRIVER_POWER_STATE_FAILURE 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 driver is in an inconsistent or invalid power state. 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 Sat 31/01/2015 22:13:20 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: 0x9F (0x3, 0xFFFFE001015EF4D0, 0xFFFFD0013D8D3960, 0xFFFFE00109CB29A0) Error: DRIVER_POWER_STATE_FAILURE Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. 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 Fri 30/01/2015 21:55:28 GMT your computer crashed crash dump file: C:\Windows\Minidump\013115-17343-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x9F (0x3, 0xFFFFE0011D101470, 0xFFFFF800506EC960, 0xFFFFE00122778BD0) Error: DRIVER_POWER_STATE_FAILURE 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 driver is in an inconsistent or invalid power state. 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 26/01/2015 21:07:51 GMT your computer crashed crash dump file: C:\Windows\Minidump\012815-16796-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x9F (0x3, 0xFFFFE00040BDD060, 0xFFFFF80128AEC960, 0xFFFFE00046441910) Error: DRIVER_POWER_STATE_FAILURE 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 driver is in an inconsistent or invalid power state. 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 25/01/2015 20:39:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\012615-18531-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x9F (0x3, 0xFFFFE001EC3EF060, 0xFFFFF80079ACA960, 0xFFFFE001F54A5BD0) Error: DRIVER_POWER_STATE_FAILURE 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 driver is in an inconsistent or invalid power state. 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 Sat 24/01/2015 18:52:04 GMT your computer crashed crash dump file: C:\Windows\Minidump\012515-19593-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x9F (0x3, 0xFFFFE00026526060, 0xFFFFD0003CE5B960, 0xFFFFE0002D3720F0) Error: DRIVER_POWER_STATE_FAILURE 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 driver is in an inconsistent or invalid power state. 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 Fri 23/01/2015 17:34:02 GMT your computer crashed crash dump file: C:\Windows\Minidump\012315-17468-01.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0) Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. Google query: CUSTOM_ERROR On Thu 22/01/2015 21:17:31 GMT your computer crashed crash dump file: C:\Windows\Minidump\012315-17609-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x9F (0x3, 0xFFFFE00067FF3280, 0xFFFFD000B665B960, 0xFFFFE0006D496940) Error: DRIVER_POWER_STATE_FAILURE 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 driver is in an inconsistent or invalid power state. 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 22/01/2015 05:09:47 GMT your computer crashed crash dump file: C:\Windows\Minidump\012215-33187-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x9F (0x3, 0xFFFFE000C7BEF060, 0xFFFFD001FD05B960, 0xFFFFE000D5793BD0) Error: DRIVER_POWER_STATE_FAILURE 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 driver is in an inconsistent or invalid power state. 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 Tue 20/01/2015 22:00:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\012115-17750-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x9F (0x3, 0xFFFFE00032DE4060, 0xFFFFD0002065B960, 0xFFFFE00037FA4010) Error: DRIVER_POWER_STATE_FAILURE 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 driver is in an inconsistent or invalid power state. 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 16 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: iastora.sys (Intel 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. 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.