[SOLVED] Unexpected_Store_Exception 0x00000154

P

peanuts-fire

Active member
Joined
Apr 17, 2022
Posts
29
  • This BSOD occurred randomly.
  • Computer created by my father.
  • Desktop
  • Windows 10 Pro
  • x64
  • full retail version
  • I don't know how many years I've been using it.
  • Probably about 4 years
  • Have you re-installed the OS?　No
  • i7 4770K
  • I do not know the brand of RAM.
  • GTX 1050Ti
  • ASUS Z87A
  • driver verifier disabled
  • What security software are you using? Windows Defender
  • Are you using proxy, vpn, ipfilters or similar software? Yes I use OpenVPN
  • Are you using Disk Image tools? Yes SoftPerfect RAMDISK
  • Are you currently under/overclocking? Are there overclocking software installed on your system? NO
memtest is pass 4 error 0
SysnativeFileCollectionApp is not finished yet
 
Last edited by a moderator:
Hi organic-rutabaga,

Could you run the Sysnative tool and attach the zip file it generates, it will give more insight into your problem.
 
Please reboot your computer and try it again.

Could you also share the situation when you have this crash?
 
I rebooted the system, but it will not proceed from Waiting for SystemInfo.
I was watching TV on my PC when I BSOD'd.
 
It is a bit worrisome that systeminfo does not work after a reboot, together with the 0x154 it may indicate drive problems.

I'd like you to do the following to provide more insight.
1. Provide all dump files in C:\Windows\Minidump
2. Run this command in a command prompt or powershell prompt (if you use powershell, replace %USERPROFILE% with the path to your username directory, e.g. C:\users\axe0), it'll create an eventlog.txt file on your desktop. Please attach this file to your post as well. Note that it might take some time for this command to finish.
Code: 
wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"
 
Yes, that's okay.

I'm surprised to see that the encoding in the eventlog is weird, but that may just be another sign of a hardware problem, particularly seeing a few events like the following.
Code: 
   2022-04-26T22:00:10.1810000Z        I/O on 31Q0A00GF5CG has failed.
   2022-04-26T22:00:11.7310000Z        I/O on 31Q0A00GF5CG has failed.
   2022-04-26T22:00:13.2160000Z        I/O on 31Q0A00GF5CG has failed.
   2022-04-26T22:00:14.5130000Z        I/O on 31Q0A00GF5CG has failed.
I don't know what this 31Q0A00GF5CFG device is though.

The dumps themselves are quite typical, a I/O error occurred while reading data into memory because a non-existent device was specified. Typically that's due to drive or RAM problems so let's start there.

I suggest running a hard drive diagnostics test.
Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test
 
31Q0A00GF5CG seems to be the serial number of my Toshiba HDD.
I will change the SATA cable. crystaldiskinfo says it's good
 
Yes, Speccy also did not indicate problems so that's not surprising.

Both read the SMART, the software for monitoring the health of a drive, but that's not the complete picture and the SMART readings are not always accurate.
 
Could you please attach it in your next post? Have you had any other issues since changing the SATA cable?
 
Okay, that's good news, we'll give it a few more days and then mark this thread as solved if the system doesn't crash again.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top