BSOD ntoskrnl.exe (nt+0x7F1C0)

[ajv1988]

Hi,

I built my first computer in early May and every couple days I get the BSOD. Yesterday it happened when I woke the computer up from sleep mode and opened the start menu. I clicked on control panel and BSOD! Based on the crash dump analysis below from 'WhoCrashed' I tried to update the Intel(R) Rapid Storage Technology Driver from the ASUS website but every time I do I get an error that says 'Installation Failed' or something along those lines.

I've done a mem86 test on my RAM and that checked out. I also did a full test on my HDD and that checked out too.
Here are my system specs:

-ASUS P8Z68-V PRO/GEN3 motherboard BIOS Version 3101
-Intel i7-2700k CPU
-GeForce GTX 550Ti Graphics Card
-Corsair Vengeance 4GB RAM
-Western Caviar 2TB HDD


Below is the Crash Dump Analysis from 'WhoCrashed'. Any help on this would be greatly appreciated!

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 6/10/2012 5:39:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060912-24226-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41284, 0x1E5F001, 0xD27, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 6/10/2012 5:39:50 AM 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: 0x1A (0x41284, 0x1E5F001, 0xD27, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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 Sat 6/9/2012 1:23:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060812-33711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF800034BEF39)
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.


On Fri 6/8/2012 2:57:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-34647-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800180FF90, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Mon 6/4/2012 12:04:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060312-32541-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800180FF90, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Sat 6/2/2012 2:41:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060112-39936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8A08AA38860, 0x0, 0xFFFFF800035B2DD3, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.


On Sat 5/26/2012 2:38:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052512-30622-01.dmp
This was probably caused by the following module: iastor.sys (iaStor+0x2BC73)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800AC7DC73, 0xFFFFF88003370458, 0xFFFFF8800336FCB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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: iastor.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Google query: iastor.sys Intel Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Fri 5/25/2012 3:18:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052512-28516-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20251)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800471A251, 0xFFFFF88008AA9AA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


On Fri 5/25/2012 3:15:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052512-26925-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF900D079F51E, 0x0, 0xFFFFF800034ABD82, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.


On Sat 5/19/2012 1:08:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051812-50747-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x411, 0xFFFFF68000019B80, 0x880000000E259886, 0xFFFFF68004019B81)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

10 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:

iastor.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 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.

 

[writhziden]

We need the full crash reports to give a detailed analysis. Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the full reports.

 

[ajv1988]

Okay here are the full crash reports

 

[James7679]

Hello ajv1988.

First, if you are overclocking, please stop for testing purposes.

Your .dmps indicate a possible memory failure.
1. Please download and install CPUz and upload the screen tabs.
2. Also, please follow this tutorial.
3. I also see that you have both AVG and Norton installed. For testing purposes, please uninstall both and install MSE(Miscrosoft Security Essentials). After testing is done you can either stick with MSE, which is recommended, or pick ONE of your current AV programs.
4. Also, please download and install Malwarebytes FREE(don't start trial) and run a full scan on all User accounts.

Please do the above, one at a time, and note the results and post back.

Thanks

 

[ajv1988]

1. I've attached the screen tabs from CPUz in a Word Document
2. I performed a memory86 test. I've performed this test in the past on my one 4 GB stick of RAM without error, however when I tried today I didn't even get 1 second in before I had errors. Luckily I have another 4 GB stick of RAM and performed the the memory86 test on that and it completed without errors after 7 passes.
3. I had uninstalled AVG previously so it looks like some things might have been left over even after I uninstalled it. I did a search on my computer and deleted anything that had AVG in it. I also uninstalled Norton and then installed MSE. I did a quick scan with MSE and everything checked out there.
4. I downloaded Malwarebytes and did a full system scan. It found multiple threats which I removed.

I found it strange that my RAM had passed the memory86 test previously but not when I ran the test today. Here's to hoping this fixes the problem. Thanks for the help

 

[James7679]

Memtest can miss errors. We see instances, more and more, where this happens. Good you caught it.

Let us know how things progress.

 

[writhziden]

In regards to memory passing sometimes but not others, here is some good further reading: Finicky RAM