TeraByte Unlimited

I'll be brief. I had an issue arise today and want to know how to prevent it in the future, and to know it's origin. The problem is solved on my own, but don't want it again for risk of data corruption.

My system was working fine as it was - Win 7, 64 Bit, English, SP1 with IFW 2.94 and a modified Recovery Environment using IFW. In addition, my system uses Intel Rapid Start Technology - iastora.sys

System was fine, but then I installed the newest IFW release 2.95 - I installed over my existing installation and made no other changes. I rebooted! Then that is when my machine had the BSOD

It would blue screen with starting windows normally, safe mode, as well as trying repairing the computer option. System would hang forever when trying to use last known good configuration. It failed with BSOD with iastora.sys

I've always had problems with IFW and Intel RST being compatible and booting up not seeing the SATA drive being accelerated by Intel. However, my system was working, while accelerated, but destroyed after installing the new version.

I could find nothing to recover my system until I REMOVED the MSATA card from my machine - then on booting I got the Intel RST Control Panel (CTRL + I) and was able to remove the acceleration option, my system booted fine and I reset/re-enabled the acceleration.

Then I used IFW 2.95 and told it to again modify the boot recovery environment.

Then my system was fine.

Question then is, why did installing 2.95 over 2.94 destroy things to the point of all options BSOD?

I really hate the risks and complications of Intel RST technology, but it does work for speed purposes. I used to have to disable all acceleration even to chkdsk the root drive being accelerated, but now it's fine under UEFI at least.

So why did it happen in the first place and how to prevent it from happening again?

Suggestions?

Hello,

The program doesn't cause a BSOD or any issue with your IASTORA.SYS driver.
PHYLock gets added to upperfilters if it doesn't exist and phylock.sys is
installed to driver folder. If your AV program doesn't allow or deletes the
phylock.sys from your driver folder you'd get a BSOD 0x7B. Nothing with
existing drivers would be affected and boot last known good configuration
wouldn't help (unless phylock wasn't already in upperfilters, which would
only occur in a new install, not an update).

Also, as far as IFW seeing a drive, it's simply asking windows to open a drive. You can use "drive management" to see what drive number it would be.

Do you reboot daily or occasionally, have you run a memory test in a while, maybe your cache drive is starting to go?


"TraumaDoc" wrote in message news:[email protected]...

I'll be brief. I had an issue arise today and want to know how to prevent
it in the future, and to know it's origin. The problem is solved on my own,
but don't want it again for risk of data corruption.

My system was working fine as it was - Win 7, 64 Bit, English, SP1 with IFW
2.94 and a modified Recovery Environment using IFW. In addition, my system
uses Intel Rapid Start Technology - iastora.sys

System was fine, but then I installed the newest IFW release 2.95 - I
installed over my existing installation and made no other changes. I
rebooted! Then that is when my machine had the BSOD

It would blue screen with starting windows normally, safe mode, as well as
trying repairing the computer option. System would hang forever when trying
to use last known good configuration. It failed with BSOD with iastora.sys

I've always had problems with IFW and Intel RST being compatible and booting
up not seeing the SATA drive being accelerated by Intel. However, my
system was working, while accelerated, but destroyed after installing the
new version.

I could find nothing to recover my system until I REMOVED the MSATA card
from my machine - then on booting I got the Intel RST Control Panel (CTRL +
I) and was able to remove the acceleration option, my system booted fine and
I reset/re-enabled the acceleration.

Then I used IFW 2.95 and told it to again modify the boot recovery
environment.

Then my system was fine.

Question then is, why did installing 2.95 over 2.94 destroy things to the
point of all options BSOD?

I really hate the risks and complications of Intel RST technology, but it
does work for speed purposes. I used to have to disable all acceleration
even to chkdsk the root drive being accelerated, but now it's fine under
UEFI at least.

So why did it happen in the first place and how to prevent it from happening
again?

Suggestions?

NOTHING else changed in my system. It is a laptop. It had been booted for 2 days probably and I installed NO program in the last week. I simply did the IFW update and rebooted and had this problem. There were no preceeding problems and nothing after. What exactly could make Normal Windows/Safe Mode (all)/Last KNown Good Gonfig/Safe Mode all to BSOD simply by doing ths update. That is why it makes no sense, because the only change at all was doing ths update. So, something caused this failure.

In the past - prior to 2.94 my system would NOT see drives linked to acceleration and the msata during boot - not even during safe/recovery environment/etc. If I wanted to do checkdisk on C drive - the acclerated drive, i had to disable acceleartion entirely. Even IFW would not see those partitions on an accelerated drive. NOW IT is fne for some spontaneous reason

Some drive caused an issue, it is only common sense, since the problem did not exist prior to the update - I rebooted once that same day 8 hours beforehand due to shutting down while i left home. Came back and no problems until updating IFW and boom, BSOD. I have had no other problems, memory, system, logs, nothing.

Something clearly caused it - related to the modified recovery envirnment or something, so I'm not sure how there can be a suggestion nothing. It is only common sense - the problem came immediatley upon this new update ... a driver or some sort, RD, etc.

Anyway, thanks. I have no prolbem no and solved it on my own, but want to be sure it doesnt cause more issues. Lsat nght I notitced that there WERE NTFS issues also - some corruption that reqquired chkdsk and it fiixed it.... so the bsod crash did do something.

I'm sure it's all related to the Intel RST, I hate it, but use it for the speed deal.

When using Intel Rapid Storage Technology with IFW it is important to
use 'Acceleration mode - Enhanced' rather than 'Acceleration mode -
Maximized'.

'Enhanced' will write data to the disk immediately, while 'Maximized'
buffers the writes to the SSD first (sometimes over reboots). Taking a
backup with any of the imaging products when RST is in 'Maximized'
mode can result in corrupt images.

I have RST set to 'Enhanced' and have had no problems with restored
images.

I don't know if this is related to your problem, but it is something
to watch out for.


On Sat, 18 Apr 2015 18:31:36 PDT, TraumaDoc wrote:

>NOTHING else changed in my system. It is a laptop. It had been booted for 2 days probably and I installed NO program in the last week. I simply did the IFW update and rebooted and had this problem. There were no preceeding problems and nothing after. What exactly could make Normal Windows/Safe Mode (all)/Last KNown Good Gonfig/Safe Mode all to BSOD simply by doing ths update. That is why it makes no sense, because the only change at all was doing ths update. So, something caused this failure.
>
>In the past - prior to 2.94 my system would NOT see drives linked to acceleration and the msata during boot - not even during safe/recovery environment/etc. If I wanted to do checkdisk on C drive - the acclerated drive, i had to disable acceleartion entirely. Even IFW would not see those partitions on an accelerated drive. NOW IT is fne for some spontaneous reason
>
>Some drive caused an issue, it is only common sense, since the problem did not exist prior to the update - I rebooted once that same day 8 hours beforehand due to shutting down while i left home. Came back and no problems until updating IFW and boom, BSOD. I have had no other problems, memory, system, logs, nothing.
>
>Something clearly caused it - related to the modified recovery envirnment or something, so I'm not sure how there can be a suggestion nothing. It is only common sense - the problem came immediatley upon this new update ... a driver or some sort, RD, etc.
>
>Anyway, thanks. I have no prolbem no and solved it on my own, but want to be sure it doesnt cause more issues. Lsat nght I notitced that there WERE NTFS issues also - some corruption that reqquired chkdsk and it fiixed it.... so the bsod crash did do something.
>
>I'm sure it's all related to the Intel RST, I hate it, but use it for the speed deal.
>

And upgrade wouldn't have changed anything that could cause a bsod.
Spontaneous things tend to be hardware and just show up, everything fine one
minute, few hours later things giving trouble, then go away, come back,
etc.. I'd suggest first checking RAM with memtest86+ overnight since that
can affect a lot of things - at least that way you know the problem won't
grow...

"TraumaDoc" wrote in message news:[email protected]...

NOTHING else changed in my system. It is a laptop. It had been booted for
2 days probably and I installed NO program in the last week. I simply did
the IFW update and rebooted and had this problem. There were no preceeding
problems and nothing after. What exactly could make Normal Windows/Safe
Mode (all)/Last KNown Good Gonfig/Safe Mode all to BSOD simply by doing ths
update. That is why it makes no sense, because the only change at all was
doing ths update. So, something caused this failure.

In the past - prior to 2.94 my system would NOT see drives linked to
acceleration and the msata during boot - not even during safe/recovery
environment/etc. If I wanted to do checkdisk on C drive - the acclerated
drive, i had to disable acceleartion entirely. Even IFW would not see those
partitions on an accelerated drive. NOW IT is fne for some spontaneous
reason

Some drive caused an issue, it is only common sense, since the problem did
not exist prior to the update - I rebooted once that same day 8 hours
beforehand due to shutting down while i left home. Came back and no
problems until updating IFW and boom, BSOD. I have had no other problems,
memory, system, logs, nothing.

Something clearly caused it - related to the modified recovery envirnment or
something, so I'm not sure how there can be a suggestion nothing. It is
only common sense - the problem came immediatley upon this new update ... a
driver or some sort, RD, etc.

Anyway, thanks. I have no prolbem no and solved it on my own, but want to
be sure it doesnt cause more issues. Lsat nght I notitced that there WERE
NTFS issues also - some corruption that reqquired chkdsk and it fiixed
it.... so the bsod crash did do something.

I'm sure it's all related to the Intel RST, I hate it, but use it for the
speed deal.

within windows itself it shouldn't matter since it's asking windows to read
the drive and the low level driver takes care of providing the data. volume
level caching would be different unless using VSS since that is volume
level. Offline would matter IF it didn't flush the cache on a reboot (which
would be a bad design - even if caching writes, a clean reboot should flush
to disk).

"Tom Cole" wrote in message news:[email protected]...

When using Intel Rapid Storage Technology with IFW it is important to
use 'Acceleration mode - Enhanced' rather than 'Acceleration mode -
Maximized'.

'Enhanced' will write data to the disk immediately, while 'Maximized'
buffers the writes to the SSD first (sometimes over reboots). Taking a
backup with any of the imaging products when RST is in 'Maximized'
mode can result in corrupt images.

I have RST set to 'Enhanced' and have had no problems with restored
images.

I don't know if this is related to your problem, but it is something
to watch out for.


On Sat, 18 Apr 2015 18:31:36 PDT, TraumaDoc wrote:

>NOTHING else changed in my system. It is a laptop. It had been booted for
>2 days probably and I installed NO program in the last week. I simply did
>the IFW update and rebooted and had this problem. There were no preceeding
>problems and nothing after. What exactly could make Normal Windows/Safe
>Mode (all)/Last KNown Good Gonfig/Safe Mode all to BSOD simply by doing ths
>update. That is why it makes no sense, because the only change at all was
>doing ths update. So, something caused this failure.
>
>In the past - prior to 2.94 my system would NOT see drives linked to
>acceleration and the msata during boot - not even during safe/recovery
>environment/etc. If I wanted to do checkdisk on C drive - the acclerated
>drive, i had to disable acceleartion entirely. Even IFW would not see
>those partitions on an accelerated drive. NOW IT is fne for some
>spontaneous reason
>
>Some drive caused an issue, it is only common sense, since the problem did
>not exist prior to the update - I rebooted once that same day 8 hours
>beforehand due to shutting down while i left home. Came back and no
>problems until updating IFW and boom, BSOD. I have had no other problems,
>memory, system, logs, nothing.
>
>Something clearly caused it - related to the modified recovery envirnment
>or something, so I'm not sure how there can be a suggestion nothing. It is
>only common sense - the problem came immediatley upon this new update ... a
>driver or some sort, RD, etc.
>
>Anyway, thanks. I have no prolbem no and solved it on my own, but want to
>be sure it doesnt cause more issues. Lsat nght I notitced that there WERE
>NTFS issues also - some corruption that reqquired chkdsk and it fiixed
>it.... so the bsod crash did do something.
>
>I'm sure it's all related to the Intel RST, I hate it, but use it for the
>speed deal.
>