Dear Community,
I hope you guys can help me out with my problem.
I am new on this board, so "HELLO" to everybody.
Yesterday, I got 2 BSOD, followed by a reboot.
I followed the instructions showing in the next link:
http://www.eightforums.com/bsod-crashes-debugging/12109-bsod-different-types.html
...and I did, what was described here:
Verifying Drivers: Enable or disable the Driver verifier in Windows 8
After e restart, it did not show anything to me.
Then, I tried the program: "BurnIn", kept it running for a while but no luck.
Finally, I tried "WhoCrashed", and this is, where I need your help.
My knowledge is not good enough to analyse it.
Welcome to WhoCrashed (HOME EDITION) v 4.02
System Information (local)
computer name: LUR
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 34299125760 total
VM: 2147352576, free: 1920741376
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 28.07.2013 18:40:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-14390-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF88001D35478)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001D35478)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port 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.
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 28.07.2013 18:40:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0x69AD9)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001D35478)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastora.sys
product: Intel Rapid Storage Technology Enterprise driver
company: Intel Corporation
description: Intel Rapid Storage Technology Enterprise 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 Rapid Storage Technology Enterprise driver - x64, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 28.07.2013 14:14:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-14156-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF88001D7E478)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001D7E478)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port 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.
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.
Conclusion
3 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:
iastora.sys (Intel Rapid Storage Technology Enterprise 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 actually 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.
Thank You everybody!!!
Cheers,
Sven
I hope you guys can help me out with my problem.
I am new on this board, so "HELLO" to everybody.
Yesterday, I got 2 BSOD, followed by a reboot.
I followed the instructions showing in the next link:
http://www.eightforums.com/bsod-crashes-debugging/12109-bsod-different-types.html
...and I did, what was described here:
Verifying Drivers: Enable or disable the Driver verifier in Windows 8
After e restart, it did not show anything to me.
Then, I tried the program: "BurnIn", kept it running for a while but no luck.
Finally, I tried "WhoCrashed", and this is, where I need your help.
My knowledge is not good enough to analyse it.
computer name: LUR
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 34299125760 total
VM: 2147352576, free: 1920741376
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 28.07.2013 18:40:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-14390-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF88001D35478)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001D35478)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port 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.
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 28.07.2013 18:40:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0x69AD9)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001D35478)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iastora.sys
product: Intel Rapid Storage Technology Enterprise driver
company: Intel Corporation
description: Intel Rapid Storage Technology Enterprise 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 Rapid Storage Technology Enterprise driver - x64, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 28.07.2013 14:14:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-14156-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF88001D7E478)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001D7E478)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port 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.
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.
3 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:
iastora.sys (Intel Rapid Storage Technology Enterprise 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 actually 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.
Thank You everybody!!!
Cheers,
Sven
Last edited:
My Computer
System One
-
- OS
- Windows 8 Pro
- Computer type
- PC/Desktop
- Motherboard
- Rampage IV Formula
- Memory
- 2x 16GB Corsair Vengeance Dual-Kit DDR3
- Graphics Card(s)
- ASUS GeForce GTX 780, 3GB
- Browser
- Firefox 22.0