Unexpected store exception

Page 1 of 3 123 LastLast

  1. Posts : 121
    Windows 10
       #1

    Unexpected store exception


    Attachment 255941

    I got the unexpected store exception. Few notes:
    Uploaded zip file as described.
    Crystaldiskinfo reports c5 current pending sector count: 1 for drive E (not my main drive).
    For my main drive, the health is good.

    Lately I updated to Windows 10 1909 (not sure if related). Windows update shows everything is up to date.
    After restart, I ran chkdsk for drive E and it is still running (eta: 3.5hours from now)
    Please advice.
    Thanks

    EDIT, chkdsk result:
    The type of the file system is NTFS.
    Volume label is Backup.

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

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

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    1472 data files processed.
    CHKDSK is verifying Usn Journal...
    10348648 USN bytes processed.
    Usn Journal verification completed.

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

    Stage 5: Looking for bad, free clusters ...
    52221374 free clusters processed.
    Free space verification is complete.
    Adding 1 bad clusters to the Bad Clusters File.

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

    488383487 KB total disk space.
    278962204 KB in 9418 files.
    6016 KB in 1473 indexes.
    4 KB in bad sectors.
    529771 KB in use by the system.
    4096 KB occupied by the log file.
    208885492 KB available on disk.

    4096 bytes in each allocation unit.
    122095871 total allocation units on disk.
    52221373 allocation units available on disk.
    Last edited by amos; 20 Nov 2019 at 01:34.
      My Computer


  2. Posts : 121
    Windows 10
    Thread Starter
       #2

    It just happened again, please help!
      My Computer


  3. Posts : 1,538
    Windows 8.1 Enterprise x64
       #3

    The crash dump you sent, however, indicates problems with the disk (wiring?):
    Code:
    ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
    IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
    Check wires from disk, test disk with SeaTools (SeaTools for DOS - Hard Drive Diagnostic)
      My Computer


  4. Posts : 121
    Windows 10
    Thread Starter
       #4

    "A device which does not exist was specified." -> Can I Know if the problem is drive E or C?

    Check wires from disk -> you mean the physical wires? E is USB, maybe something with that?

    It took 2 days for the problem to happen again, so if I will check now with your tool, it might say everything is OK, no?

    Also, I don't have a cd, is there another way or tool to run such/similar tool without the need of a cd?

    Thanks
      My Computer


  5. Posts : 41,547
    windows 10 professional version 1607 build 14393.969 64 bit
       #5

    Code:
    Adding 1 bad clusters to the Bad Clusters File.
    
    Windows has made corrections to the file system.

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) bcdedit /enum {badmemory}

    10) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    11) Make sure that there is no over clocking while troubleshooting.

    12) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free
    Backup and Restore with Macrium Reflect

    13) Save the backup image to another disk drive or the cloud

    14) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan


    15) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    16) Run HD Sentinel: (free or trial edition)
    Hard Disk Sentinel - HDD health and temperature monitoring
    Hard Disk Sentinel - HDD health and temperature monitoring
    Post images of each of these tabs into the thread:
    Overview tab
    Temperature
    SMART
    Disk performance
      My Computer


  6. Posts : 121
    Windows 10
    Thread Starter
       #6

    I started the tests but it's late here so I will continue tomorrow and post here the outcome.

    Most likely this is HD related so why do I need to run so many unrelated tests?

    Does the dump or other collected files report whether it is drive C or E?

    I read elsewhere that it might be related to HD overheating. If this is the case, as long as the heating is fine, the tests won't show anything, would they? and when the heating is not fine, it will be too late as I will get BSOD.

    I wonder why the error causes a BSOD instead of just popups an error...
    Thanks

    - - - Updated - - -

    1-10 (chkdsk of drive E you have in the original post, below is of drive c)

    Microsoft Windows [Version 10.0.18363.476]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.476

    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.476

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.

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

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

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    201385 data files processed.
    CHKDSK is verifying Usn Journal...
    40266816 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    487268581 KB total disk space.
    351857100 KB in 847163 files.
    478212 KB in 201386 indexes.
    0 KB in bad sectors.
    1649413 KB in use by the system.
    65536 KB occupied by the log file.
    133283856 KB available on disk.

    4096 bytes in each allocation unit.
    121817145 total allocation units on disk.
    33320964 allocation units available on disk.

    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-K0H9K1I\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\DESKTOP-K0H9K1I\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\WINDOWS\system32>
      My Computer


  7. Posts : 41,547
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    These tests can be run overnight:
    a) HD Tune full error scan
    b) Sea Tools for Windows long generic test.

    The tests have different algorithms.
    One of the tests will display current and maximum temperatures.

    Backup images are useful in case there is unexpected:

    malware
    ransomware
    corruption of the registry
    corruption of the operating system
    failure to boot
    drive failure
    etc.
      My Computer


  8. Posts : 121
    Windows 10
    Thread Starter
       #8

    Hi

    I still don't understand why it causes a BSOD and not a simple popup with the error. Also, does the dump say if the problem is drive C or drive E?

    I run the tests and post the results as they come... If you see a problem along the way let me know.
    I'm now waiting for the full error scan of Drive E to finish and I will post all the images of 14.
      My Computer


  9. Posts : 41,547
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    When there are BSOD dump files may be created.
    We use Microsoft Windbg for debugging the dump files.
    The debugging can find misbehaving software and hardware drivers and malfunctioning hardware.
    When there is malfunctioning hardware tests are ran to test the hardware components.

    So you are now testing each drive for SMART, error or surface scans, benchmarks, temperature, etc.

    All drives need to be tested.

    Some testing may need to be repeated.
      My Computer


  10. Posts : 121
    Windows 10
    Thread Starter
       #10

    Here are the images for point 14

    Attachment 256356

    - - - Updated - - -

    15

    --------------- SeaTools for Windows v1.4.0.7 ---------------
    Model Number: WDC WD5000AAKX-0
    Serial Number: WD-WCC2E1PHXLZK
    Firmware Revision: 1H19
    Long Generic - Started 23/11/2019 14:35:37
    Long Generic - Pass 23/11/2019 16:08:13

    --------------- SeaTools for Windows v1.4.0.7 ---------------
    Model: Elements 1023
    Serial: WXU1EA0KCDF2
    Firmware: 2005
    Long Generic - Started 23/11/2019 14:35:38
    Long Generic - FAIL 23/11/2019 17:17:31

    I didn't find a way to see a more generic log of the failure.

    - - - Updated - - -

    16

    Attachment 256382Attachment 256383Attachment 256384Attachment 256385

    Let me know if I forgot something
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:59.
Find Us




Windows 10 Forums