E5570 Freezing - Errors 129 iaStorA + 508 ESENT

Question

I have some problems with my Latitude E5570, bought just under a year ago.
It was originally suffering from blue screens and also frequent lockups where the computer would freeze and become unresponsive for 30 seconds or so, often two or three times in a row.
First of all Dell support replaced the motherboard and RAM. The problems continued and Dell referred me to Microsoft suggesting it was a Windows problem. They suggested a repair of windows in place. The problems continued and they then suggested a clean install and still the freezes continued (but not so much the blue screens)

So generally the freezes happen with some combination of the following two errors:

Event 129 iaStorA (Reset to device \Device\RaidPort0 was issue)

Event 508 ESENT (svchost (4224,T,0) SRUJet: A request to write to the file "C:\Windows\system32\SRU\SRUDB.dat" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (28 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.)

From reading around I tried a few things.
Neither sfc /scannow nor chkdsk /r revealed any errors
One suggestion I saw was under power options setting PCI Express > Link State Power Management Settings changed to "off", the problem still occurred after changing this

If anyone has any ideas that would be great, could it be a hard drive issue (I have a 256gb SSD)

Thanks!

DELL-Jesse L · Answer

JamesOnline,

Run the diagnostics on the hardware to see if any errors are reported. To run the diags on the E5570 follow the information below.

Launching ePSA

During the boot process, ePSA is accessed from a cold boot by pressing the power button on and repeatedly pressing until the BIOS Boot Menu appears on the screen. Use the Up and Down Arrow keys to select Diagnostics on the menu, and then press .

Testing Devices using ePSA

ePSA begins by checking an area in the system memory to ensure it is safe, and then loads itself into the verified memory area. Then, ePSA automatically begins high-level algorithms on all system memory to ensure integrity.

The ePSA starts running the quick test on all the detected devices without waiting for user input.
To select a specific device to test, users can tap the Esc key and click on the right-arrow on the bottom right of the screen.

NOTE:
The Touchpad/Mouse will be non-functional when the test is in progress. This is as per design.

JamesOnline · Answer

Thanks for the reply Jesse, I ran that test and then the extended test when it prompted me. Both came back with no errors, I think the number was 77247, I wasn't sure how to access the logs from windows otherwise I would post them if that's useful?

JamesOnline · Answer

Reading around online it seems that people talking about frezzes in conjunction with error 129 are often talking about modifying AHCI settings / drivers to fix this issue, but no one clear solution and I'm unsure how to proceed exactly in my specific case. I'm slightly reluctant to start messing about with settings that I don't really understand. For example here are a couple of links

https://www.dell.com/community/Laptops-General/Event-ID-129-iaStorA-Reset-to-device-Device-RaidPort0-quot-could/td-p/5087956

http://www.nxhut.com/2015/01/storahci-id-129-reset-to-device.html

Is this the sort of thing you would expect Dell support to be able to help troubleshoot usually? (I'm still in warranty)

larryhayden · Answer

I have been having a similar issue with a pair of refurbished Dell Latitude E7450's with SSDs. The system periodically freezes up with a "Raid IaStor Error 129". Of course it is a single disk system, no RAID is required, which makes the error even particularly frustrating.

There seems to be quite a few folks with this issue, some on literally dozens of laptops, and a lot of complicated "fixes" which generally did not work. Ultimately I found a simple fix, which worked.

Some people had tried simply switching the SATA BIOS config from RAID to AHCI, but upon reboot Windows would not see the drive and failed to boot. Scary thinking that the data may have been lost. Windows had the RAID drivers and not the AHCI drivers active.

The fix that ultimately worked was so simple.

While still using the bothersome RAID driver, set windows to reboot in Windows Safe Minimal mode. Doing this forces Windows to rediscover the available devices using a minimal driver set. During the safe reboot, reconfigure the BIOS from RAID to AHCI and complete the boot. In this case, since the BIOS has been reset it will discover the disk and load the Windows AHCI drivers. Upon subsequent reboots the AHCI driver is used, the RAID driver is not even loaded, and the error goes away.

I found this answer, with the full instructions for using bcdedit to manage the safe boot, here:

https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-ide-to-ahci

Summarizing...

Click the Start Button and type cmd
Right-click the result and select Run as administrator
Type this command and press ENTER: bcdedit /set {current} safeboot minimal (ALT: bcdedit /set safeboot minimal)
Restart the computer and enter BIOS Setup
Change the SATA Operation mode to AHCI from either IDE or RAID
Save changes and exit Setup and Windows will automatically boot to Safe Mode.
Right-click the Windows Start Menu once more. Choose Command Prompt (Admin).
Type this command and press ENTER: bcdedit /deletevalue {current} safeboot (ALT: bcdedit /deletevalue safeboot)
Reboot once more and Windows will automatically start with AHCI drivers enabled.

ysmzf8a1ed · Answer

This is a late reply, but I would like to express my gratitude. This answer saved my Vosto7390/Win10 from  freezing often. Still a great answer in 2024/10. Now no stress at all!! Thank you!

Latitude

E5570 Freezing - Errors 129 iaStorA + 508 ESENT

Launching ePSA

Testing Devices using ePSA

Was this post helpful?

Register Now! for Secure Secrets with Kubernetes & DevSecOps - and grab a lab!