Frequent BSODs, UNEXPECTED_STORE_EXCEPTION

fuz111 said:

Philc43, I read through the link you gave me and I checked my BSOD file capture settings, it was set to small memory dump, I changed it to active memory dump, is that what you recommend?

Small memory dump is correct - because otherwise the memory.dmp file will be overwritten everytime you get a bluescreen, this is not the case with the mini-dumps.

Thanks zBook, it will probably take me a few days to go through each of those programs, Ill respond back when ive tried them.

Philc43, so then my settings were correct from the beginning? I wonder why no BSOD files were captured then?

Here are the results:
Seatools, already tried
HDDScan, no SMART, could perform surface test
DiskCheckUp, no SMART
GSmartControl, no SMART
Windows Drive Fitness Test, didnt recognize drive
HUTIL, could not run
Western Digital Data Life guard, could not perform SMART
Bart's Stuff Test, not sure how to use this application
Fujitsu wouldnt let me select my drive to perform any test
HDTune, already tried
EASIS drive check, couldnt perform SMART
Macroit, could perform tests for bad sectors, doesnt specifically mention SMART
Disk Scanner, could perform test for bad sectors, doesnt specifically mention SMART

By the way I got a BSOD yesterday (for the first time since I started this thread), same message (unexpected_store_exception), it happened when my battery was very low.

Thanks
Fuz

Please upload a new set of logs, as we need to see the crash dumps.

If there are no ".dmp" files in the .zip, please check if any files are in C:\Windows\Minidump\ and if C:\Windows\memory.dmp exists.

Here it is.

C:\Windows\Minidump\ - directory doesnt exist

C:\Windows\memory.dmp - went there, it launched visual studio then gave me a dialogue saying "debugging older format crash dumps is not supported"


thanks
fuz

See post #2 steps 11 -13.
Please post the whocrashed results into the thread.

After whocrashed created the dump it should have created new files.

Open file explorer > this PC > local C: drive > right upper corner search > enter these and post images of the results:

%SystemRoot%\MEMORY.DMP
C:\Windows\MEMORY.DMP
%SystemRoot%\Minidump

I just downloaded whocrashed. Here is the one result from I clicked analyze.


Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 4/24/2017 8:06:04 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0xC525B)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\iastora.sys
product: Intel(R) Rapid Storage Technology driver
company: Intel Corporation
description: Intel(R) Rapid Storage Technology driver - x64
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastora.sys (Intel(R) Rapid Storage Technology driver - x64, Intel Corporation).
Google query: Intel Corporation DPC_WATCHDOG_VIOLATION



I havent done the crash dump test yet.

Im attaching the images of the search results of those directories.

So are we officially giving up on the SMART test?

Thanks
Fuz

On the Dell website there are diagnostics.
See if they have an option to test the drive.
If possible also see if you can get confirmation from either or both Dell and / or Samsung regarding the RAID controller blocking SMART tests. If they have a report or link that would be useful. And if the problem is the controller can it be modified in any way just to perform a SMART test?
Some laptops have quick release for the drives. If you do then the drive could be checked if attached to another computer with a hard drive enclosure. That's the only other method that comes to mind. We do have the drive benchmarks from Atto.

Please open system control panel > advanced system settings > startup and recovery settings > post an image into the thread.

When available please post the results of the new Whocrashed test dump.

Download and install: voidtools

Everything or everything search works and an index.
All files on the internal or external drive will be indexed.
Everything can start on boot or can start when you need it.
As you type in a character it will display instantaneously the search results.
The more characters you enter the narrower the search results.

Please perform the search again using everything and see if there are more results.