iastor.sys BSOD, Stop 0x0000007E...

[supersport2002]

Hello All,

I am new to this forum so I hope I can explain everything well. I will not be able to attach the required dump files to this thread and I will explain below. Here is my problem:

I have a relatively new Toshiba Laptop u845w-s400 and about a week ago started getting the following BSOD:

Stop 0x0000007E (0xc0000005 0x8145B450 0x82DC8BB4 0x82DC8790)
iastor.sys 8145B450 base at 8142A000 date stamp 4e6fffb2

I tried updating the system BIOS and that did not help. I then updates the intel RAID drivers and that also did not help. I tried running tdsskiller.exe and other malware tools and they did not find anything nor did that help. I tried running chkdsk and that did not help. At that point I tried to use the Toshiba recovery tools with the boot disk that I got with the laptop. I could not get far enough to fix anything before getting the BSOD again. I tried that several times before trying to erase the hard disk from the recover tools. I will run all the way to the end and BSOD at 99% either with quick erase or full. I then downloaded the Win7 iso and created a Win7 boot DVD so I could do a clean install of windows since now I do not have a bootable computer after the failed hard drive erase. At first Win7 could not see my HDD's so I downloaded some drivers to reference during install. I can then see the drives, so I deleted then in the Win7 install process and then formatted them and created new, but when I go to perform the clean install I get the iastor.sys BSOD before I reach 1% on "expanding Windows files". I can't do anything without getting the BSOD and I cannot find anymore things to try on the net so I am at my wits end with this new laptop. :banghead:

Does anyone have any ideas???? I would hate to spend $$ to have it fixed when I recently just bought it... I would greatly appreciate any help. Thank you.....

 

[Northernsoul55]

Hi,

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (go to top of page)
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

If you are unable to successfully boot into Windows because of the BSOD error, Windows has an option to reload registry information from the last successful boot. To revert to the last successful boot:
1. Reboot the computer.
2. Near the end of the BIOS messages or graphic, but well before anything appears from Windows, press the F8 key. You may only have a few seconds to get the right spot to press F8 before it attempts to go into Windows. If the BIOS complains about a pressed key or asks you to go into BIOS setup, you've pressed F8 too soon (Don't go into BIOS setup).
3. When successful, you should see a black screen with white text "Windows Advanced Options". Use the up or down arrow keys to highlight Last Known Good Configuration and press Enter.

:ar: http://www.sevenforums.com/tutorials/666-advanced-boot-options.html

Or can you boot into safe-mode?

:ar: http://www.sevenforums.com/tutorials/69585-safe-mode.html

If you can do either of the above and gain access to your Windows:

1. Navigate to C:/windows/system32/drivers
2. Locate iastor.sys and rename to iastor.sys.old
3. Reboot into normal mode.
This will disable the driver and stop your BSOD.

Then please download and install the following stable driver:
File name:iata_enu.exe
Version: 11.2.0.1006

:ar: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=21730

Hope this helps, post back your feedback.
Cheers
Dave

 

[Kaktussoft]

Open device manager. Expand branch "IDE ATA/API controllers". Right click on the intel sata driver->upgrade driver. From computer. Pick from list. Put checkmark at "display compatible hardware" (or something alike)
Now click on "standard AHCI1.0 serial ATA controller", press next.

 

[supersport2002]

Thank you for your replies Northernsoul55 and Kaktussoft.

The problem with trying these two options is that I do not have a bootable HDD anymore since the erase hard disk did not get to finish through the toshiba recovery tools and I have tried to format in the Win7 install. I can now only boot from the Win7 bootable DVD or the recovery DVD's that I got with the computer. I would have thought that formatting from the Win7 clean install options would have cleaned out all old drivers and solve the problem, but it still persists. I have to install a driver from a USB drive when running the Win7 install for it to even recognize my drives.

Also, I forgot to mention that this computer has a small SSD, I do not know how this might affect anything.

Can I still try the above mentioned possible solutions without being able to boot to the HDD? If so how would I go about that?

Thank you for your help...I hope we can get this figured out.

 

[Northernsoul55]

Have you tried a Repair Install?

:ar: http://www.sevenforums.com/tutorials/3413-repair-install.html

Also please look at the following thread:

:ar: http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html

cheers

Dave

 

[supersport2002]

Have you tried a Repair Install?

:ar: http://www.sevenforums.com/tutorials/3413-repair-install.html

Wouldn't I need to be able to boot into Windows to be able to do a repair install?

Also please look at the following thread:

:ar: http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html

I will give this a try tomorrow after work and post back here with the results. Thank you again for the help. I also read somewhere that when the OEM install of Win7 it might have put some of the OS on the SSD which is why it wont let me do the clean install and why I am still getting the BSOD and some say to take it out physically and then do the clean install on the main HDD then reinstalling the SSD (or possibly leaving it out). Does this make any sense to you? Would it be worth trying if the above does not work? Food for thought...

 

[supersport2002]

Also please look at the following thread:

:ar: http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html

cheers

Dave

Update: I tried running the Windows Defender Offline tool by creating a bootable DVD but it does not run since it cannot find a Windows system disk to check...

I will try some of the other tools tomorrow, but I think I will run into the same problem since right now there is not really a windows system disk that anything can check.

I am still stumped why the clean install will not work even though the computer is looking at a clean iastor.sys file that I have to point the installer to when trying to run the install dvd....:sarc: because the installer does not even see a hard drive when looking for the install space...

I will try more tomorrow....

 

[Northernsoul55]

From what your saying, it seems you do not have Windows installed or its damaged and
If the installer cant see your HDD when installing says its either Formatted incorrectly or worse damaged.

Is the HDD be recognized in the BIOS?

Try to follow this guide for SSD and see if after that you are allowed to install?

:ar: http://www.sevenforums.com/tutorials/91339-ssd-hdd-optimize-windows-reinstallation.html

Cheers

Dave

 

[nsteblay]

I have exactly the same laptop with exactly the same problem.

Things I've tried ...

* Ensure latest Windows Update
* Update the Intel Iastor.sys driver with the latest from Intel
* Systems restore to a very early point in time

If I run SF_Diagnostics and then analyze the dump file using DaRT7 I see that the Iastor.sys driver is what is in memory and active at the time of the crash.

I am not sure what that driver is being used for on this system. This driver is typically used for RAID based systems. It does look like the Samsung supports two hard drives so maybe RAID is supported. It could also be related to the SSD that is incorporated. I don't know.

I may try reinstalling the O/S if I can't get resolution soon.

Nick

 

[Kaktussoft]

I have exactly the same laptop with exactly the same problem.

Things I've tried ...

* Ensure latest Windows Update
* Update the Intel Iastor.sys driver with the latest from Intel
* Systems restore to a very early point in time

If I run SF_Diagnostics and then analyze the dump file using DaRT7 I see that the Iastor.sys driver is what is in memory and active at the time of the crash.

I am not sure what that driver is being used for on this system. This driver is typically used for RAID based systems. It does look like the Samsung supports two hard drives so maybe RAID is supported. It could also be related to the SSD that is incorporated. I don't know.

I may try reinstalling the O/S if I can't get resolution soon.

Nick

Do this #3

 

[Arc]

I have exactly the same laptop with exactly the same problem.

Things I've tried ...

* Ensure latest Windows Update
* Update the Intel Iastor.sys driver with the latest from Intel
* Systems restore to a very early point in time

If I run SF_Diagnostics and then analyze the dump file using DaRT7 I see that the Iastor.sys driver is what is in memory and active at the time of the crash.

I am not sure what that driver is being used for on this system. This driver is typically used for RAID based systems. It does look like the Samsung supports two hard drives so maybe RAID is supported. It could also be related to the SSD that is incorporated. I don't know.

I may try reinstalling the O/S if I can't get resolution soon.

Nick

Do this #3

He needs to be able to boot into windows to open the device manager, I think? Here as he says ....

Wouldn't I need to be able to boot into Windows to be able to do a repair install?

@ supersport2002, try to boot into System Recovery Options . Try Safe Mode with Command Prompt. In the command prompt .... enter the command ....

start msconfig

It will open the system configuration window, with the "general" tab selected.

• Click the "startup" tab. Click "Disable all" > Apply > OK.
• Click on "services" tab. Check the "Hide all Microsoft Services"; Click "Disable all" > Apply > OK

Then try to boot again normally. Is it failing still?

If so, boot to System Recovery Options once again. Try Enable Boot Logging. It will create a file named ntbtlog.txt. Collect it and upload it. If you cannot do it within windows, Boot with a live Linux disc (I prefer Puppy Linux for those) and collect it in a USB stick, use the usb stick in another computer and upload it. It is necessary.

 

[supersport2002]

Update:

I tried alot of the options that were listed in the last few posts with no success. Every time I would try anything that would try and access the small SSD I would get the iastor.sys BSOD again, very frustrating by the way! From my research on this particular laptop the SSD is very small and not accessible through the OS because it is only used by the OS for certain things to help boot speed and similar tasks.

Since boot speed is not an issue on a non-working computer I decided to try something else. I took the laptop apart and physically removed the small SSD from the computer so when I tried booting it again I would be solely using the the larger main HDD. I put the computer back together and when I booted up it recognized that I had taken out the SSD and it made me convert the sole HDD to a non-RAID drive in the BIOS. I then proceeded to boot to my Win7 clean install DVD. It finally recognized my HDD without the need of an outside driver install via USB, I then deleted the existing partitions created a new partition and then formatted it with the Win7 install. was actually able to go through and do a fresh and clean install of Win7 with any problems. The only thing that I have to do now is go and download all of the hardware drivers that Win7 did not have from the Toshiba website and update them. I am working on that later today, but that should not be a problem. I will see after I get that done if I am going to bother putting the small SSD drive back in or not?? Not sure if I want to deal with that again or not. I will update again as soon as I get everything finished. Thank you everyone for all of the help.

 

[supersport2002]

He needs to be able to boot into windows to open the device manager, I think? Here as he says ....

Wouldn't I need to be able to boot into Windows to be able to do a repair install?

@ supersport2002, try to boot into System Recovery Options . Try Safe Mode with Command Prompt. In the command prompt .... enter the command ....

start msconfig

It will open the system configuration window, with the "general" tab selected.

• Click the "startup" tab. Click "Disable all" > Apply > OK.
• Click on "services" tab. Check the "Hide all Microsoft Services"; Click "Disable all" > Apply > OK

Then try to boot again normally. Is it failing still?

If so, boot to System Recovery Options once again. Try Enable Boot Logging. It will create a file named ntbtlog.txt. Collect it and upload it. If you cannot do it within windows, Boot with a live Linux disc (I prefer Puppy Linux for those) and collect it in a USB stick, use the usb stick in another computer and upload it. It is necessary.

The problem was that I had tried to delete the hard drive a few times from the Toshiba recovery tools and received the iastor.sys BSOD before it finished and there was no longer an OS on the computer for me to boot into.

 

[Arc]

Good to read your report. Clean reinstall is always a good idea, and it will release the RAID setup, too; which might not be a must for you.

For the best, either you dont install Intel Rapid Storage at all, or release this version only.

 

[nsteblay]

Thanks for your help. I think I found the problem I was having. Within the Device Manager / Storage Controllers I noticed another device other than the Intel Controller. I had installed the SlySoft Virtual Clonedrive for mounting ISO files. Apparently this driver was interacting with the IaStor.sys driver in a way that was causing the BSOD. Haven't had any issues since removing.

I have exactly the same laptop with exactly the same problem.

Things I've tried ...

* Ensure latest Windows Update
* Update the Intel Iastor.sys driver with the latest from Intel
* Systems restore to a very early point in time

If I run SF_Diagnostics and then analyze the dump file using DaRT7 I see that the Iastor.sys driver is what is in memory and active at the time of the crash.

I am not sure what that driver is being used for on this system. This driver is typically used for RAID based systems. It does look like the Samsung supports two hard drives so maybe RAID is supported. It could also be related to the SSD that is incorporated. I don't know.

I may try reinstalling the O/S if I can't get resolution soon.

Nick

Do this #3

 

[Northernsoul55]

Glad it is sorted for you nsteblay.

Also glad your issue is resolved too Supersport2002.

Post back any feedback

cheers

Dave