Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD iaStoreA.sys and ntoskrnl.exe 0x0000001e

27 Feb 2013   #1
jtodd12

Windows 7 Home Premium 64bit
 
 
BSOD iaStoreA.sys and ntoskrnl.exe 0x0000001e

Hello all! I'm a newcomer here looking for some help. I just started receiving the BSOD this weekend on my desktop. It has been working flawlessly since last summer. I only made a couple of changes this weekend.

1. I installed 3dMark11
2. changed video cables and monitors to connect a laptop dock with dual monitors.

I have since:
uninstalled 3dMark,
reconnected the monitors,
uninstalled, installed and then upgraded the Intel Rapid Storage drivers/software,
uninstalled and reinstalled Paragon recovery(due to another error that I thought pointed to it),
done a system restore,
checked as many of the drivers to make sure they are as up to date as possible.

From reading other threads, I believe the following is what is needed to help. I appreciate any help that you can provide.

http://dl.dropbox.com/u/3699279/jtodd12.zip

http://dl.dropbox.com/u/3699279/022713-17565-01.dmp





My System SpecsSystem Spec
.
27 Feb 2013   #2
x BlueRobot

 

Code:
BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys

Probably caused by : iaStorA.sys ( iaStorA+64024 )
Code:
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Your Intel(R) C600 series chipset SATA AHCI Controller, seems to be causing some issues, have you tried using a a earlier version?

Code:
Driver	c:\windows\system32\drivers\iastora.sys (3.6.0.1086, 564.46 KB (578,008 bytes), 2/27/2013 10:51 AM)
Update System Specifications:
My System SpecsSystem Spec
27 Feb 2013   #3
jtodd12

Windows 7 Home Premium 64bit
 
 

Thank you for the reply.

I did have 3.5 installed this weekend when the system went to BSOD. I just installed the 3.2 version that came on the disc with the motherboard, just not sure that is the root cause, but it could be. I'll see if it happens again with 3.2 now.

Does the ntoskrnl.exe have a part in this possibly?
My System SpecsSystem Spec
.

27 Feb 2013   #4
x BlueRobot

 

ntoskrnl.exe is the Windows Kernel, and Windows system drivers and files are rarely the true cause for the BSOD. The BSOD may point to this file, since Windows managed to crash when this process was occurring, and not at the time when the problem may have happened.

You could think of it like this, the problematic driver is trying to to steal money from the bank; Windows the security for the bank is distracted by something, the problematic driver manages to steal the money (cause the issue), however, when Windows finally turns around they see the ntoskrnl.exe, who is then wrongly framed for the robbery.
My System SpecsSystem Spec
27 Feb 2013   #5
jtodd12

Windows 7 Home Premium 64bit
 
 

. Ok, thank you.

I am just surprised that Intel drivers would cause a problem with their chipset, over multiple versions. I'll see how it goes for awhile.
My System SpecsSystem Spec
27 Feb 2013   #6
x BlueRobot

 

I've seen quite a few BSODs be caused by that Intel driver, I believe some versions are more stable than others.
My System SpecsSystem Spec
27 Feb 2013   #7
jtodd12

Windows 7 Home Premium 64bit
 
 

It just happened again with the old Intel RSTe driver, version 3.2.

Here is the dump file.

http://dl.dropbox.com/u/3699279/022713-15927-01.dmp

I decided to run driver verifier because of this. This is the resulting dump file.

http://dl.dropbox.com/u/3699279/022713-15475-01.dmp

This seems to point to Paragon recovery, so I have removed that application and the drivers.
My System SpecsSystem Spec
28 Feb 2013   #8
x BlueRobot

 

Code:
BugCheck C4, {62, fffffa8010a76ee8, fffffa8010a76d20, 1}

*** WARNING: Unable to verify timestamp for uimx64.sys
*** ERROR: Module load completed but symbols could not be loaded for uimx64.sys
Probably caused by : uimx64.sys
Code:
7: kd> lmvm uimx64
start             end                 module name
fffff880`05b58000 fffff880`05b70000   uimx64   T (no symbols)           
    Loaded symbol image file: uimx64.sys
    Image path: \SystemRoot\system32\DRIVERS\uimx64.sys
    Image name: uimx64.sys
    Timestamp:        Thu Nov 22 12:07:52 2012 (50AE1598)
    CheckSum:         00025973
    ImageSize:        00018000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your correct, and it's more specifically the Paragon Image Mounter SCSI Port Driver (Driver Reference Table - uimx64.sys).

The other dump file pointed to the same bugcheck and driver as in the first post.
My System SpecsSystem Spec
28 Feb 2013   #9
jtodd12

Windows 7 Home Premium 64bit
 
 

Another one, this time different as well.

http://dl.dropbox.com/u/3699279/022813-14757-01.dmp
My System SpecsSystem Spec
28 Feb 2013   #10
x BlueRobot

 

Code:
BugCheck D1, {0, 2, 0, fffff880017510d2}

*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+63e80 )
Let's eliminate the possibility of the hard-drive causing any problems:

Run some hard-drive diagnostics and follow these steps:Find your hard-drive manufacturer and run their tests.

Additional Tests:Post a screenshot of Crystal Disk Info summary: Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.

Check for any file system errors and bad sectors using Option #2 of:Use this command with Disk Check:

Code:
chkdsk C: /f /r
My System SpecsSystem Spec
Reply

 BSOD iaStoreA.sys and ntoskrnl.exe 0x0000001e




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD ntoskrnl.exe+75b90 0x0000001e
Hello Forum, I am hoping that someone will be able to help me with BSOD relating to ntoskrnl.exe - I think I have looked up a similar thread and followed the advice but have not solved the problem. I have installed some maintenance software to try to clean up the computer cclean,...
BSOD Help and Support
BSOD Stop: 0x0000001E on ntoskrnl.exe
Working on a Friends Computer who have been getting this error message with every boot into the OS, (although it boots into the Desktop, Win 7 Home, then BSOD) Safe Mode works Fine, there seems to be no spyware/virus issues, and hardware checks outs System is a DELL Inspiron 620s ...
BSOD Help and Support
BSOD ntoskrnl.exe 0x0000001e
Hey, I need help with this, any help will help. Thanks,
BSOD Help and Support
BSOD, 0x0000001E, ntoskrnl.exe
Is Windows 7 . . . - x86 (32-bit) or x64 ? 64bit - the original installed OS on the system? Yes - an OEM or full retail version? OEM - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? 5 months - What is the age of OS...
BSOD Help and Support
ntoskrnl.exe 0x0000001E BSOD
Specs: - Windows 7 Home Premium x64 - Original and only OS ever on the system - Came pre-installed - The entire system is about 2 months old - The install is 2 months old. - No other security system besides Microsoft Security Essentials I'm getting a BSOD caused by the ntoskrnl.exe driver....
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 23:47.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App