Multiple BSOD Everyday - Unexpected Store Exception, Critical Process Died, etc.

I've been experiencing multiple crashes on my laptop every day for about a month now. This has happened to me before but before I just had to do a system restore but I saved my files. Now, it will crash try to go into recovery mode but it fails and says I need a recovery CD or USB. I then have to restart my computer until I hopefully see the loading dots. I tried to scan the C: driver but it says it is NTFS. I've also gotten Unmountable Boot Volume, DPC Watchdog Violation, and Critical Service Failed crashes.
 

Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffc00da4efa9a0, fffff8009fe579f0, ffffc00da4f8bc60}

Implicit thread is now ffffc00d`9f18b040
*** WARNING: Unable to verify timestamp for IntcDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for IntcDAud.sys
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys

Followup:     MachineOwner
Hi,
of the three dump files sent, the first is corrupt and unreadable, the second is above and the third is a Bugcheck EF Critical process died.

The reason I posted up the second dump is because it includes a driver which gives us somewhere to start at least. Plus it backs up your mentioning of drive issues as the probable cause relates to the Intel Storage driver.

iaStorA.sys Mon Nov 19 20:09:40 2012: Intel RST (Rapid Storage Technology) driver. You can find a 2015 version of this driver on your support page linked below.

Laptops need to use drivers supplied by the manufacturer and your support page can be found here:
Support for Inspiron 3521 | Drivers & downloads | Dell UK

I would also update what you can especially chipset drivers.

Please post any new dump files.
 
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffc00da4efa9a0, fffff8009fe579f0, ffffc00da4f8bc60}

Implicit thread is now ffffc00d`9f18b040
*** WARNING: Unable to verify timestamp for IntcDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for IntcDAud.sys
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys

Followup:     MachineOwner
Hi,
of the three dump files sent, the first is corrupt and unreadable, the second is above and the third is a Bugcheck EF Critical process died.

The reason I posted up the second dump is because it includes a driver which gives us somewhere to start at least. Plus it backs up your mentioning of drive issues as the probable cause relates to the Intel Storage driver.

iaStorA.sys Mon Nov 19 20:09:40 2012: Intel RST (Rapid Storage Technology) driver. You can find a 2015 version of this driver on your support page linked below.

Laptops need to use drivers supplied by the manufacturer and your support page can be found here:
Support for Inspiron 3521 | Drivers & downloads | Dell UK

I would also update what you can especially chipset drivers.

Please post any new dump files.
Okay so I updated my BIOS and the Intel RST. I will update when there are any new dump files.
Thanks for the drivers page by the way. I couldn't find it when I looked.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Much thanks for the update, I hope all goes well but if not please post again.
 
Okay so, I'm back. My computer crashed a couple times earlier it didn't go to the failed recovery page but the first crash said no boot device found until I restarted it. Then, it crashed again after I logged on.
 

Attachments

I ran just the Chkdsk and then the Chkdsk /scan but the chkdsk said there was a problem and the scan said there were no problems so I'm confused.
Here's the Chdsk:
 

Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
I'm just about to nip off to an appointment but will be back in a couple of hours. I'll definitely post back shortly.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hmm.. it might simply mean the data on the drive is corrupt.

Would you mind running a chkdsk again but this time use the chkdsk /r command as this will both look for and try to repair broken sectors.
 
Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 4/12/2018 7:56:06 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
1026816 file records processed.
File verification completed.
13774 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
12516 reparse records processed.
1156788 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
12516 reparse records processed.

Stage 3: Examining security descriptors ...
Cleaning up 194 unused index entries from index $SII of file 0x9.
Cleaning up 194 unused index entries from index $SDH of file 0x9.
Cleaning up 194 unused security descriptors.
Security descriptor verification completed.
64987 data files processed.
CHKDSK is verifying Usn Journal...
38352360 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
1026800 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
13997152 free clusters processed.
Free space verification is complete.
Adding 2 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

473774237 KB total disk space.
416239568 KB in 621124 files.
395256 KB in 64988 indexes.
12 KB in bad sectors.
1150801 KB in use by the system.
65536 KB occupied by the log file.
55988600 KB available on disk.

4096 bytes in each allocation unit.
118443559 total allocation units on disk.
13997150 allocation units available on disk.

Internal Info:
00 ab 0f 00 18 77 0a 00 fc 9c 13 00 00 00 00 00 .....w..........
48 2f 00 00 9c 01 00 00 00 00 00 00 00 00 00 00 H/..............

Windows has finished checking your disk.
Please wait while your computer restarts.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Much thanks.

It looks like the scan did find and repair certain errors:

Adding 2 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

No further action is required.

Please post if the chkdsk scan has helped regarding the crashes.
 
It crashed again :( This time I got Process1 Initialization Failed which is new. Then, when it restarted I got a lot of Checking Media Failed messages and I then it said No Boot Device Found and then I restarted it again.
 

Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EF, {ffffad0ff39a2580, 0, 0, 0}

Probably caused by : memory_corruption

Followup:     memory_corruption
Hi,
the very last dump file sent was unreadable and this in itself can sometimes mean issues with the HDD.

I looked over your dxdiag and noticed your current free space:
hdd.JPG


Ideally one needs around 25% of the drive left free so windows can work properly. Please remove unwanted or no longer used applications as well as backing up what data you can to clear up some space.

Check the S.M.A.R.T. data (Self-Monitoring, Analysis, and Reporting Technology) for your drive by running this command in an admin command prompt. Type:

wmic diskdrive get status

Press enter and status, if the drive is fine, should show as OK.

We can check this further by using an application called 'Speedfan'. It's basic function is to allow you to control system fans but it also has an extremely handy feature.
Speedfan

Speedfan has a tab dedicated to SMART data and you can also get a basic online report. I used my aging SSD as an example here:

sf.jpg sf2.jpg If you can post up something similar it may help to see if your HDD is the actual culprit.

Oh and please try and create some free space. The more the better.. :) You may have found that your machine is a little sluggish? Freeing up the space will definitely help in this regard.
 
Last edited:

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hmm.. those results don't look too good.

See if moving stuff over helps but if not you might be want to think about upgrading your drive as it's looking a tad suspect.
 
Top