Windows 10: BSOD after upgrading to W10 [UNEXPECTED_STORE_EXCEPTION]

Upgraded to W10 from W7 1-2 weeks ago and have been getting BSOD on a daily basis (1 a day).

There is no pattern, the only thing i can think of is that it happens when having several programs running, causing heavy RAM usage (only have 4 GB of RAM). When using Windows 7 i never had any BSOD issues.

What happens is that everything freezes, then it crashes after 5-10 seconds showing BSOD with UNEXPECTED STORE EXCEPTION as error message.


Would appreciate some help!



Edit: After the crash Windows restarts and goes into BIOS mode where i cant see my Boot Disk (the list is empty), so I have to manually shut the computer off by holding in the power button. When starting it again it boots up properly. It's a laptop btw.

:)

 

BSoD after upgrade UNEXPECTED_STORE_EXCEPTION

We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
If you have any questions about the procedure please ask

 

BSoD after upgrade UNEXPECTED_STORE_EXCEPTION

I can't even boot my laptop and I have tried to boot in safe mode. I keep getting the "NTFS_file_system"error and on my last boot it changed to "FAT_file_system" error. Is there anything I can do to boot my system?

 

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

There doesn't seem to be any log or something present in the files.
Please run following tests, based on the bugcheck and your description.





Diagnostics Test

HDD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

• Short Drive Self Test
• Short generic
• Long generic

If the short generic fails, no need for the long generic.


Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk
Disk Check - Windows 7 Help Forums



Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

I ran the first 2 Seatools tests on my external HDD with no issues, currently running the Long Generic.

Ran chkdsk on my SSD too and no issues found.

Resultrs from HDTune, found some errors in Error Scan, could not complete benchmarking. Got an error message after a few seconds upon starting the test.

Attachment 67773Attachment 67774Attachment 67775

 

Unexpected_store_exception sounds to me like a problem with the hard drive even though there is no dump for analysis, it is an assumption which I can't 100% verify, but the error HDTune found could confirm it.

 

Ok thank you, updated my previous post with screen shots of the SSD.

 

Please do 2 things
1. Backup your data a.s.a.p.
2. Run in an admin command prompt (search command promt > right click > run as administrator) the command
Code: chkdsk C: /f /r[/quote] If you already ran this command, please do it again.
Chkdsk marks the bad sectors and moves the data to another sector, but this is a temporary solution because bad sectors relates to a hard drive that soon will fail completely and become unbootable. You'll need to replace it in time before it fails completely.

 

If you already ran this command, please do it again.
Chkdsk marks the bad sectors and moves the data to another sector, but this is a temporary solution because bad sectors relates to a hard drive that soon will fail completely and become unbootable. You'll need to replace it in time before it fails completely.[/quote] Ok thanks, I have done that for now, will check back if BSOD still occur/mark as solved if they dont. (unless there's something else I should do now)

 

Just keep me posted *Smile

 

So I just got the same kind of BSOD, ran the HDTune Error Scan again with the same result:


Attachment 68161

 

Chkdsk only lets the system know what sectors are bad but does nothing else.
Damaged sectors aren't repairable, this is the reason why I recommended to backup your data.
A hard drive can hold only an x amount of data that says what sectors are damaged, but the data it can hold might not be a lot what may mean that your system doesn't know about the other bad sectors what may cause problems when these bad sectors are being used.
You'll need to replace the hard drive.

 

Damn ok, so you're 100% certain this is what's causing the BSOD's?

 

It is a cause, I've not often seen a single cause.

 

Your eventlog is filled with "The device, \Device\Ide\iaStor0, did not respond within the timeout period." and usually this message is being posted due to hardware problems with either the controller or, more likely, a device that is attached to the controller in question.

And iaStor is the driver for Intel Rapid Storage Technology.

I would recommend that you try to update it so if it would solve any of your issues, this is a driver update utility from intel:
Intel Driver Update Utility

Cheers, Boris *Smile