Photoshop edit BSOD IAsTORa.SYS

Hello,
I a have been having app crash issues with Adobe LR6 for the last week or so. Today, while in Photoshop CS6, editing an image , I received a BSOD; iaStorA.sys..... Any help is appreciated!

Hi Russ,

I don't see any crash dumps in the folder you attached. Is anything in C:\Windows\Minidump, or does C:\Windows\MEMORY.DMP exist?

If iaStorA.sys is indeed the problem, I see you are running version 14.5.0.1081 of the Intel Rapid Store driver (iaStorA.sys). The latest upstream release from Intel is 15.5.0.1051 and the last release Dell approved is 12.6.0.1033. I would suggest installing either of those versions.

Intel's latest release

Last release approved by Dell

Thanks "Spectrum" for the reply. Before I attempt updates from either IBM or Dell please review the attached dump file (hope it works this time);

Thanks,
Wayne

Wayne,

The dump file appears to be corrupted, but that would be in line with a problem occurring in the storage subsystem, and iastorA.sys is the intel RAID driver. I would strongly suggest updating your Rapid Store driver, and if problems continue, running HDTune to check your hard drive's health.

Code:

*** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.

Memory Manager detected corruption of a pagefile page while performing an in-page operation.The data read from storage does not match the original data written.  This indicates the data was corrupted by the storage stack, or device hardware.

Looking at the event logs there is more evidence of a problem in your storage subsystem.

Namely, there are 55 occurrences of the driver having to reset the raid controller. Resets generally occur when the driver encounters an error and attempts to recover from it.

Code:

Log Name: System  Source: iaStorA 

Event ID: 129  

Task: N/A  

Level: Warning  

Opcode: N/A  

Keyword: Classic  

User: N/A  

User Name: N/A  

Computer: XPS8700  

Description: Reset to device, \Device\RaidPort0, was issued.

BSOD Minidump - Configure to Create in Windows 10 How to configure Windows 10 to configure Dump Files to be written in the event of a Blue Screen of Death (BSOD).

Bad block found via windows event log too:

Code:

2017-05-22T18 18:11.709  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-05-23T18 18:06.178  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-05-24T18 18:13.097  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-05-26T15 34:44.939  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-05-29T18 18:19.609  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-05-31T18 18:29.406  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-06-01T18 18:05.668  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-06-03T18 18:05.289  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-06-04T18 18:42.338  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-06-05T18 18:23.128  Error: The device, \Device\Harddisk1\DR1, has a bad block.  
2017-06-06T18 18:22.662  Error: The device, \Device\Harddisk1\DR1, has a bad block.

After u installed another controller driver u should check your disks:

Diagnostic Test

 HDD TEST

Run HDTune to check health and scan for errors.

   Note

It may take some time, but look for signs of any errors or failure.

You can also run a disk check using chkdsk. Refer to the tutorial for details of how to do this.

Spectrum & BSODHunter,

Many thanks for your assistance! So far I have changed the system dump collection from automatic to kernel. I ran the dump file collector again and the size of the file changed slightly but not sure there is any new relevant information. See file attached. I also updated the Intel Rapid Store Driver as requested to ver 15.5.0.1051. I will run HD Tune next...........

Wayne

Code:

0x0000001A:    MEMORY_MANAGEMENT (8.06.2017 03:38:10) [Windows 10] 
 
CAUSED BY:     memory_corruption    
 
PROCESS:       MemCompression 
 
Usual causes:  Device driver, memory, kernel

I say disk or RAM memory. First step should be checking the disk. Second would be checking the RAM with memtest

Wayne,

To be clear, since updating the Rapid Store driver, have you encountered anymore BSODs? I'd echo BSODHunter's advice, run HDTune anyways to rule out a failing disk.

OK, I scanned the disc (C:) and it did find issues and did a repair and a restart. I re-ran the check disc and no errors were found. Should I still check the RAM with memtest?