Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD iastora.sys Win 7

  • Please log in to reply
1 reply to this topic

#1 Airbus480


  • Members
  • 1 posts

Posted 20 March 2016 - 04:57 AM

· OS - Windows 8.1, 8, 7, Vista ? Windows 7 Professional
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system?
Windows 7 Professional
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Purchased because custom built PC
· Age of system (hardware) almost a year old, built last MAY 2015
· Age of OS installation - have you re-installed the OS? almost a year old, No not reinstalled the OS

· CPU - i7-5820K
· Video Card MSI GTX 980 4G GAMING
· MotherBoard - ASROCK X99 WS
· Power Supply - AEROCOOL STRIKE 
· System Manufacturer
· Exact model number (if laptop, check label on bottom)

· Laptop or Desktop?

Whocrashed said "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 driver - x64, Intel Corporation)."

First time had a BSOD that involves iastora.sys I have to note that the Task Manager "Up Time" before the BSOD happened is more than 5 days but less than 6 but was able to reach 14 days without BSOD back then...

Attached Files

Edited by Airbus480, 20 March 2016 - 05:12 AM.

BC AdBot (Login to Remove)


#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,091 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:13 AM

Posted 20 March 2016 - 06:20 PM

Unfortunately it appears that the system has pirated software.
Please get a legitimate copy installed and we'll be glad to help.

Here's suggestions on how to ensure that your version is legitimate:  http://windows.microsoft.com/en-us/windows/genuine

Please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

As a courtesy, I will offer an analysis of your issues using the reports you provided.
I will not answer any questions about the analysis until the system is made legitimate.
If you do make it legitimate, please submit a new set of reports for us to check.

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

C: drive only has about 7% free space; D: drive only has about 8% free space; and the J: drive is so full that I can't tell the exact % (approx 0.02%).  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty)

This device has problems in Device Manager:


Sentinel64    ROOT\LEGACY_SENTINEL64\0000    This device is not present, is not working properly, or does not have all its drivers installed.

This likely belongs to the Sentinel system driver by SafeNet.

Please uninstall the program.

If, after uninstalling, the device remains in Device Manager, please right click on it and select "Uninstall"

Then reboot to see if the device remains gone.


Please uninstall XFastLAN and XFastUSB - as they are known to cause BSOD's on some Windows systems


Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).


Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html

NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.

MSI Afterburner and Riva Tuner (along with EVGA Precision) is known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.

Please uninstall the Western Digital software.  The wdcsam64.sys driver dates from 2008 and is known to cause BSOD's in some Windows systems.


As the lone memory dump blames the Intel RST driver, please update your Intel RST to the latest, W7 compatible version.


Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

VSTwindrvr6.sys     Fri Jul  4 03:28:01 2008 (486DD101)
Jungo WinDriver Device Driver Download - http://www.jungo.com/st/contact-form/?product=WinDriver[br]Support - http://www.jungo.com/st/support/windriver/
pwdrvio.sys         Mon Jun 15 21:43:45 2009 (4A36F8D1)
MiniTool Partition Wizard http://www.partitionwizard.com/free-partition-manager.html
AsrAppCharger.sys   Tue May 10 04:28:46 2011 (4DC8F73E)
ASRock App Charger Likely BSOD cause - haven't seen recently (15Jan2013) http://www.asrock.com/feature/appcharger/index.asp


The following is for informational purposes only.
**************************Sun Mar 20 05:37:01.512 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\032016-15771-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: 7601.19160.amd64fre.win7sp1_gdr.160211-0600
System Uptime: 9 days 18:59:22.503
*** 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+8ff04 )
BugCheck D1, {10, 2, 1, fffff88001292f04}
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001292f04, address which referenced memory
FAILURE_BUCKET_ID:  X64_0xD1_iaStorA+8ff04
CPUID:        "Intel® Core™ i7-5820K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3299
  BIOS Version                  P2.10
  BIOS Release Date             01/07/2016
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             X99 WS

3rd Party Drivers:
The following is for information purposes only.
**************************Sun Mar 20 05:37:01.512 2016 (UTC - 4:00)**************************
wdcsam64.sys        Wed Apr 16 04:39:08 2008 (4805BB2C)
VSTwindrvr6.sys     Fri Jul  4 03:28:01 2008 (486DD101)
pwdrvio.sys         Mon Jun 15 21:43:45 2009 (4A36F8D1)
intelppm.sys        Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsrAppCharger.sys   Tue May 10 04:28:46 2011 (4DC8F73E)
speedfan.sys        Sat Dec 29 15:59:35 2012 (50DF59B7)
AsrDrv101.sys       Tue Jan 15 01:25:51 2013 (50F4F66F)
AsrRamDisk.sys      Thu May  9 04:50:45 2013 (518B6365)
cfosspeed6.sys      Wed May 29 12:47:24 2013 (51A6311C)
avkmgr.sys          Mon Sep 16 07:14:23 2013 (5236E80F)
iusb3hub.sys        Thu Feb 20 07:13:04 2014 (5305F150)
iusb3xhc.sys        Thu Feb 20 07:13:07 2014 (5305F153)
iusb3hcs.sys        Thu Feb 20 07:14:51 2014 (5305F1BB)
nipbcfk.sys         Fri Feb 28 15:26:53 2014 (5310F10D)
RTKVHD64.sys        Tue Mar 11 08:56:41 2014 (531F0809)
e1d62x64.sys        Fri Mar 14 14:22:47 2014 (532348F7)
iaStorA.sys         Fri May  2 19:06:56 2014 (53642510)
iaStorF.sys         Fri May  2 19:07:00 2014 (53642514)
iocbios2.sys        Wed Jun 18 02:48:56 2014 (53A13658)
niorbk.dll          Wed Jul 30 20:10:50 2014 (53D9898A)
nidimk.dll          Thu Sep 18 22:42:12 2014 (541B9804)
nidimkl.sys         Thu Sep 18 22:42:13 2014 (541B9805)
TeeDriverx64.sys    Tue Sep 23 16:01:14 2014 (5421D18A)
cpuz138_x64.sys     Thu Oct 23 11:03:05 2014 (544918A9)
nimdbgk.dll         Thu Feb  5 13:51:32 2015 (54D3BBB4)
nimdbgkl.sys        Thu Feb  5 13:51:36 2015 (54D3BBB8)
nimxdfk.dll         Thu Feb  5 14:35:02 2015 (54D3C5E6)
nimxdfkl.sys        Thu Feb  5 14:35:12 2015 (54D3C5F0)
SCDEmu.SYS          Fri Feb 27 22:20:51 2015 (54F13413)
idmwfp.sys          Fri Apr 17 12:06:19 2015 (55312F7B)
RTCore64.sys        Fri Apr 24 03:01:47 2015 (5539EA5B)
nipalk.sys          Wed May 20 19:41:24 2015 (555D1BA4)
rzudd.sys           Thu May 21 00:40:22 2015 (555D61B6)
nipxirmk.dll        Tue May 26 19:52:32 2015 (55650740)
nipxirmkl.sys       Tue May 26 19:52:34 2015 (55650742)
e1r62x64.sys        Fri Jun  5 03:33:17 2015 (557150BD)
nipcibrd.sys        Thu Jun 11 23:59:08 2015 (557A590C)
nipxibrc.sys        Fri Jun 12 02:12:27 2015 (557A784B)
NiViPciK.sys        Fri Jun 12 13:28:49 2015 (557B16D1)
NiViPciKl.sys       Fri Jun 12 13:28:55 2015 (557B16D7)
NiViPxiK.sys        Fri Jun 12 13:29:56 2015 (557B1714)
NiViPxiKl.sys       Fri Jun 12 13:29:59 2015 (557B1717)
mbam.sys            Tue Aug 11 13:35:19 2015 (55CA3257)
nvhda64v.sys        Mon Sep 21 05:44:17 2015 (55FFD171)
MpFilter.sys        Fri Oct 30 02:29:35 2015 (56330E4F)
nvvad64v.sys        Thu Dec 17 07:47:18 2015 (5672AED6)
NvStreamKms.sys     Tue Dec 22 15:54:00 2015 (5679B868)
nvlddmkm.sys        Mon Jan 11 02:01:35 2016 (5693534F)
avgntflt.sys        Wed Jan 13 09:21:51 2016 (56965D7F)
avnetflt.sys        Fri Jan 15 12:38:05 2016 (56992E7D)
avipbb.sys          Thu Jan 21 04:44:22 2016 (56A0A876)


nipcibrd.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.


Edited by usasma, 20 March 2016 - 06:31 PM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users