BSOD On Startup error 0x0000001a

**axe0** · 01 Oct 2015

Please first do the following

Open an admin command prompt
Copy/paste "sfc/scannow" (without quotes) and press enter
When it finished reboot your system
Open again an admin command prompt
Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

LarryB · 01 Oct 2015

is it ok to do this in safe mode or would you prefer normal?

**axe0** · 01 Oct 2015

It doesn't really matter how you do it, via rescue media in command prompt, safe mode, normal boot or clean boot.
SFC does the same.

LarryB · 01 Oct 2015

no errors after two runs and a restart in between. cbs log file uploaded to opening post

Cheers

LarryB · 01 Oct 2015

running verifier on non MS drivers for now (Intel, Atheros-Wifi)

**axe0** · 01 Oct 2015

Keep us posted :)

LarryB · 01 Oct 2015

Hey Axe0

After running verifier against all non MS drivers, and after many black screens and no BSOD´s, I can finally trigger a BSOD against the iastor.sys driver. According to the system information this driver is associated with the Intel AHCI Controller.

I have enesure all Intel drivers are up to date including chipset, and also under IDE Controllers the Standard AHCI 1.0 Serial ATA Controller is up to date also, but according to the driver details it is not associated with iastor.sys

I can see multiple blogs on BSOD and iastor.sys and I am reviewing them. In the meantime I have copied up the latest log collector containin the latest dump file if you can take a look

For what it is worth the controller is set to AHCI in the BIOS and not IDE

Cheers!

**axe0** · 01 Oct 2015

Either I am looking at the wrong files, but I have downloaded every zip file you provided (cbs.log file is not needed as you say the problems are solved), or you might have cleaned your pc from dumps files accidentally?

In your most recent uploaded zip file, I see only dumps from 5 to 9 months old.

LarryB · 01 Oct 2015

just checked the zip file and not all of the files are there. Dump file is definitely in c:\windows\minidumps

Let me run the logger again. I´ll check the content of the zip file before uploading

LarryB · 01 Oct 2015

There´s something wrong with the log collector. I´ll download it again shortly. The odd thing is that all the files are generated and placed in temp folder SFDebugFiles. That folder is then zipped but it only takes the dump files.

Anyway I managed to copy and zip the SFDebugFolder and that is what I will attach in the next few minutes. It contains the latest dump at 20.10