BSOD While Using Laptop Normally, error UNEXPECTED_STORE_EXCEPTION  


  1. Posts : 3
    Windows 10
       #1

    BSOD While Using Laptop Normally, error UNEXPECTED_STORE_EXCEPTION


    Hello, I'm using windows 10 64 bit version and my laptop is Micro Star (MSI) GL63 8RC.
    After upgrade ssd (nvme) to Adata SX8200 256GB around 2-3 month my laptop often to get BSOD UNEXPECTED_STORE_EXCEPTION. I already try to fix it from the other forum (fixing registry file, turn off fast start up, etc.) but still encounter this error almost every day. I'll add the log, thank you.
      My Computer


  2. Posts : 14,890
    Windows 10 Pro
       #2

    Could you link to this other forum so we can see the fixes you tried.
      My Computers


  3. Posts : 3
    Windows 10
    Thread Starter
       #3

    axe0 said:
    Could you link to this other forum so we can see the fixes you tried.
    Hello, thanks for your response. Here is the link SOLVED: Unexpected Store Exception in Windows 10 - Appuals.com.
      My Computer


  4. Posts : 14,890
    Windows 10 Pro
       #4

    When you mentioned 'forum', I assumed you meant a site like this one. That site looks more like a blog.
    From the looks of the content of the article, it looks like they're just random suggestions collected by looking at what worked for others, and these suggestions are typically just common things that actually don't work that often for many. I'm not really surprised it didn't help you to be honest.

    There is one suggestion in that article that should have pointed you to the right direction. The 0x154 crash you have is typically accompanied by the system having issues generating the necessary files to allow debugging, which does make sense given that it often is related to issues with the memory or drive.

    Because there are no dump files, I looked into the events and here's what I found related to this issue.
    Code:
    2019-06-01T16:30:47.845		Checking file system on C:
    The type of the file system is NTFS.
    One of your disks needs to be checked for consistency. You
    may cancel the disk check, but it is strongly recommended
    that you continue.
    Windows will now check the disk.                         
    Stage 1: Examining basic file system structure ...
      410880 file records processed.                                                        
    File verification completed.
    Deleting orphan file record segment 30EBC.
    Deleting orphan file record segment 30EBD.
    Deleting orphan file record segment 30EBE.
    Deleting orphan file record segment 30EBF.
    Deleting orphan file record segment 351BC.
    Deleting orphan file record segment 351BD.
    Deleting orphan file record segment 351BE.
    Deleting orphan file record segment 351BF.
    Deleting orphan file record segment 5AFBC.
    Deleting orphan file record segment 5AFBD.
    Deleting orphan file record segment 5AFBE.
    Deleting orphan file record segment 5AFBF.
      4343 large file records processed.                                   
      0 bad file records processed.                                     
    Stage 2: Examining file name linkage ...
      206 reparse records processed.                                      
      530380 index entries processed.                                                       
    Index verification completed.
      0 unindexed files scanned.                                        
      0 unindexed files recovered to lost and found.                    
      206 reparse records processed.                                      
    Stage 3: Examining security descriptors ...
    Cleaning up 179 unused index entries from index $SII of file 0x9.
    Cleaning up 179 unused index entries from index $SDH of file 0x9.
    Cleaning up 179 unused security descriptors.
    Security descriptor verification completed.
      59751 data files processed.                                           
    CHKDSK is verifying Usn Journal...
      36507536 USN bytes processed.                                                           
    Usn Journal verification completed.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    Windows has made corrections to the file system.
    No further action is required.
     249427967 KB total disk space.
      55978304 KB in 344934 files.
        205164 KB in 59752 indexes.
            12 KB in bad sectors.
        524019 KB in use by the system.
         65536 KB occupied by the log file.
     192720468 KB available on disk.
          4096 bytes in each allocation unit.
      62356991 total allocation units on disk.
      48180117 allocation units available on disk.
    Internal Info:
    00 45 06 00 da 2c 06 00 0c c0 0b 00 00 00 00 00  .E...,..........
    65 00 00 00 69 00 00 00 00 00 00 00 00 00 00 00  e...i...........
    Windows has finished checking your disk.
    Please wait while your computer restarts.
    2019-06-01T12:26:30.571		Chkdsk was executed in scan mode on a volume snapshot.  
    Checking file system on \Device\HarddiskVolume5
    Stage 1: Examining basic file system structure ...
    The USA check value, 0x0, at block 0x1 is incorrect.
    The expected value is 0x2.
        Found corrupt basic file structure for "<0x2,0x2e81d>"
            ... repaired online.
    The USA check value, 0x0, at block 0x1 is incorrect.
    The expected value is 0x2.
        Found corrupt basic file structure for "<0x2,0x2e81e>"
            ... repaired online.
    The USA check value, 0x0, at block 0x1 is incorrect.
    The expected value is 0x2.
        Found corrupt basic file structure for "<0x2,0x2e81f>"
            ... repaired online.
                                                                                           
      410880 file records processed.                                                        
    File verification completed.
                                                                                           
      4342 large file records processed.                                   
        Found unused file metadata marked as used
            ... queued for offline repair.
                                                                                           
      0 bad file records processed.                                     
    Stage 2: Examining file name linkage ...
                                                                                           
      206 reparse records processed.                                      
        Found an unneeded link ($FILE_NAME: "290~1.0-R") in index "$I30" of directory "\Users\feriy\AppData\Local\Android\Sdk\build-tools <0x5,0xee3d>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "GE2DF2~1.EXP") in index "$I30" of directory "\src\flutter\.pub-cache\hosted\pub.dartlang.org\front_end-0.1.11\testcases\inference <0x1,0x1ac0a>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "GEBB3E~1.EXP") in index "$I30" of directory "\src\flutter\.pub-cache\hosted\pub.dartlang.org\front_end-0.1.11\testcases\inference <0x1,0x1ac0a>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "GEF4EC~1.EXP") in index "$I30" of directory "\src\flutter\.pub-cache\hosted\pub.dartlang.org\front_end-0.1.11\testcases\inference <0x1,0x1ac0a>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "GENERI~4.EXP") in index "$I30" of directory "\src\flutter\.pub-cache\hosted\pub.dartlang.org\front_end-0.1.11\testcases\inference <0x1,0x1ac0a>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "306633a263fb04df_0") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "306633~1") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "3d1a8e4939f65d4e_0") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "3D1A8E~1") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "add6e63e6cd74e9f_0") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "ADD6E6~1") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "instagram-bccebd657e[1].svg") in index "$I30" of directory "\Users\feriy\AppData\Local\Packages\Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe\AC\INetCache\C10MUJEV <0x5,0x30d89>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "INSTAG~1.SVG") in index "$I30" of directory "\Users\feriy\AppData\Local\Packages\Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe\AC\INetCache\C10MUJEV <0x5,0x30d89>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "index.txt") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544 <0x10,0x31361>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "f7d99f271d4df9a2aaa205ce696a1895.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\f7 <0x1,0x351e2>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "F7D99F~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\f7 <0x1,0x351e2>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "a15344c4b65458d508db64b8feff5ce2.unlinked") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\a1 <0x1,0x35212>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "A15344~1.UNL") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\a1 <0x1,0x35212>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "61c97d0ffbc7ee105a44ea6933b8ce7d.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\61 <0x1,0x35226>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "61C97D~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\61 <0x1,0x35226>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "3ef524824023f9cada800cb4369a76ea.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\3e <0x1,0x35282>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "3EF524~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\3e <0x1,0x35282>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "168882b3a0b2a2b9b141cdd36949da27.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\16 <0x1,0x352b6>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "168882~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\16 <0x1,0x352b6>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "1f6dccc25952b647cd1a2492d2f1d8a7.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\1f <0x1,0x353b6>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "1F6DCC~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\1f <0x1,0x353b6>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "14") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Mozilla\Firefox\Profiles\aku1tt5g.default-release\storage\default\moz-extension+++fcc0451e-bd0b-455c-872c-3f51f93c3071^userContextId=4294967295\idb\3647222921wleabcEoxlt-eengsairo.files <0x2,0x3ccfa>"
            ... repaired online.
                                                                                           
      530516 index entries processed.                                                       
    Index verification completed.
                                                                                           
                                                                                           
        Found 31 lost files (...\package.xml <0x4,0x2e801>, ...\mainDexClasses <0x2,0x2e820>, ...); requesting reconnection to index "$I30" of directory "\Device\HarddiskVolume5\found.000"
            ... repaired online.
                                                                                           
      206 reparse records processed.                                      
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
                                                                                           
      59819 data files processed.                                           
    CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.
    Windows has found problems and some were fixed online;
    the remaining problems must be fixed offline.
    Please run "chkdsk /spotfix" to fix the issues.
     249427967 KB total disk space.
      56435740 KB in 346142 files.
        205488 KB in 59822 indexes.
        488183 KB in use by the system.
         65536 KB occupied by the log file.
     192298544 KB available on disk.
          4096 bytes in each allocation unit.
      62356991 total allocation units on disk.
      48074636 allocation units available on disk.
    ----------------------------------------------------------------------
    Stage 1: Examining basic file system structure ...
    The multi-sector header signature in file 0x2e81d is incorrect.
    42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ??  BAAD0...........
    Deleting corrupt file record segment 2E81D.
    The multi-sector header signature in file 0x2e81e is incorrect.
    42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ??  BAAD0...........
    Deleting corrupt file record segment 2E81E.
    The multi-sector header signature in file 0x2e81f is incorrect.
    42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ??  BAAD0...........
    Deleting corrupt file record segment 2E81F.
    Deleting orphan file record segment 30EBC.
    Deleting orphan file record segment 30EBD.
    Deleting orphan file record segment 30EBE.
    Deleting orphan file record segment 30EBF.
    Deleting orphan file record segment 351BC.
    Deleting orphan file record segment 351BD.
    Deleting orphan file record segment 351BE.
    Deleting orphan file record segment 351BF.
    Deleting orphan file record segment 5AFBC.
    Deleting orphan file record segment 5AFBD.
    Deleting orphan file record segment 5AFBE.
    Deleting orphan file record segment 5AFBF.
    Stage 2: Examining file name linkage ...
    The file reference 0x200000002e81c of index entry 290~1.0-R of index $I30
    with parent 0xee3d is not the same as 0x400000002e81c.
    Deleting index entry 290~1.0-R in index $I30 of file EE3D.
    The file reference 0x100000001af9e of index entry GE2DF2~1.EXP of index $I30
    with parent 0x1ac0a is not the same as 0xb00000001af9e.
    Deleting index entry GE2DF2~1.EXP in index $I30 of file 1AC0A.
    The file reference 0x100000001af9d of index entry GEBB3E~1.EXP of index $I30
    with parent 0x1ac0a is not the same as 0x300000001af9d.
    Deleting index entry GEBB3E~1.EXP in index $I30 of file 1AC0A.
    The file reference 0x100000001af9f of index entry GEF4EC~1.EXP of index $I30
    with parent 0x1ac0a is not the same as 0xa00000001af9f.
    Deleting index entry GEF4EC~1.EXP in index $I30 of file 1AC0A.
    The file reference 0x100000001af9c of index entry GENERI~4.EXP of index $I30
    with parent 0x1ac0a is not the same as 0xa00000001af9c.
    Deleting index entry GENERI~4.EXP in index $I30 of file 1AC0A.
    Index entry 306633a263fb04df_0 of index $I30 in file 0x30d3b points to unused file 0x30ebd.
    Deleting index entry 306633a263fb04df_0 in index $I30 of file 30D3B.
    Index entry 306633~1 of index $I30 in file 0x30d3b points to unused file 0x30ebd.
    Deleting index entry 306633~1 in index $I30 of file 30D3B.
    Index entry 3d1a8e4939f65d4e_0 of index $I30 in file 0x30d3b points to unused file 0x30ebe.
    Deleting index entry 3d1a8e4939f65d4e_0 in index $I30 of file 30D3B.
    Index entry 3D1A8E~1 of index $I30 in file 0x30d3b points to unused file 0x30ebe.
    Deleting index entry 3D1A8E~1 in index $I30 of file 30D3B.
    Index entry add6e63e6cd74e9f_0 of index $I30 in file 0x30d3b points to unused file 0x30ebf.
    Deleting index entry add6e63e6cd74e9f_0 in index $I30 of file 30D3B.
    Index entry ADD6E6~1 of index $I30 in file 0x30d3b points to unused file 0x30ebf.
    Deleting index entry ADD6E6~1 in index $I30 of file 30D3B.
    Index entry instagram-bccebd657e[1].svg of index $I30 in file 0x30d89 points to unused file 0x30ebc.
    Deleting index entry instagram-bccebd657e[1].svg in index $I30 of file 30D89.
    Index entry INSTAG~1.SVG of index $I30 in file 0x30d89 points to unused file 0x30ebc.
    Deleting index entry INSTAG~1.SVG in index $I30 of file 30D89.
    Index entry index.txt of index $I30 in file 0x31361 points to unused file 0x5afbe.
    Deleting index entry index.txt in index $I30 of file 31361.
    Index entry f7d99f271d4df9a2aaa205ce696a1895.resolved of index $I30 in file 0x351e2 points to unused file 0x351be.
    Deleting index entry f7d99f271d4df9a2aaa205ce696a1895.resolved in index $I30 of file 351E2.
    Index entry F7D99F~1.RES of index $I30 in file 0x351e2 points to unused file 0x351be.
    Deleting index entry F7D99F~1.RES in index $I30 of file 351E2.
    Index entry a15344c4b65458d508db64b8feff5ce2.unlinked of index $I30 in file 0x35212 points to unused file 0x5afbc.
    Deleting index entry a15344c4b65458d508db64b8feff5ce2.unlinked in index $I30 of file 35212.
    Index entry A15344~1.UNL of index $I30 in file 0x35212 points to unused file 0x5afbc.
    Deleting index entry A15344~1.UNL in index $I30 of file 35212.
    Index entry 61c97d0ffbc7ee105a44ea6933b8ce7d.resolved of index $I30 in file 0x35226 points to unused file 0x5afbd.
    Deleting index entry 61c97d0ffbc7ee105a44ea6933b8ce7d.resolved in index $I30 of file 35226.
    Index entry 61C97D~1.RES of index $I30 in file 0x35226 points to unused file 0x5afbd.
    Deleting index entry 61C97D~1.RES in index $I30 of file 35226.
    Index entry 3ef524824023f9cada800cb4369a76ea.resolved of index $I30 in file 0x35282 points to unused file 0x351bd.
    Deleting index entry 3ef524824023f9cada800cb4369a76ea.resolved in index $I30 of file 35282.
    Index entry 3EF524~1.RES of index $I30 in file 0x35282 points to unused file 0x351bd.
    Deleting index entry 3EF524~1.RES in index $I30 of file 35282.
    Index entry 168882b3a0b2a2b9b141cdd36949da27.resolved of index $I30 in file 0x352b6 points to unused file 0x351bc.
    Deleting index entry 168882b3a0b2a2b9b141cdd36949da27.resolved in index $I30 of file 352B6.
    Index entry 168882~1.RES of index $I30 in file 0x352b6 points to unused file 0x351bc.
    Deleting index entry 168882~1.RES in index $I30 of file 352B6.
    Index entry 1f6dccc25952b647cd1a2492d2f1d8a7.resolved of index $I30 in file 0x353b6 points to unused file 0x351bf.
    Deleting index entry 1f6dccc25952b647cd1a2492d2f1d8a7.resolved in index $I30 of file 353B6.
    Index entry 1F6DCC~1.RES of index $I30 in file 0x353b6 points to unused file 0x351bf.
    Deleting index entry 1F6DCC~1.RES in index $I30 of file 353B6.
    Index entry 14 of index $I30 in file 0x3ccfa points to unused file 0x5afbf.
    Deleting index entry 14 in index $I30 of file 3CCFA.
    CHKDSK is scanning unindexed files for reconnect to their original directory.
      0 unindexed files recovered to original directory.
    CHKDSK is recovering remaining unindexed files.
        Lost and found is located at \found.000
    Stage 3: Examining security descriptors ...
    2019-06-01T12:26:16.217		A corruption was discovered in the file system structure on volume C:.
    The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1000000000000.  The name of the file is "<unable to determine file name>".
    2019-06-01T12:13:15.661		Chkdsk was executed in verify mode on a volume snapshot.  
    Checking file system on \Device\HarddiskVolume5
    Examining 1 corruption record ...
    Record 1 of 1: Corrupt File "<0x9,0x5afbf>" ... no corruption found.
    1 corruption record processed in 0.1 seconds.
    Windows has examined the list of previously identified potential issues and found no problems.
    No further action is required.
    2019-06-01T12:09:21.156		Dump file creation failed due to error during dump creation.
    2019-06-01T11:55:58.041		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T11:17:32.422		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T11:15:44.685		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T11:01:08.599		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:50:00.069		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:50:00.067		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:50:00.063		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:59.987		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:41.367		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.837		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.835		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.832		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.830		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.828		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.826		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.824		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.821		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.816		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.340		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.338		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.336		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.329		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.327		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.324		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.322		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.320		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.287		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.174		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.172		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.168		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.166		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:55.865		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:55.863		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:55.861		The device, \Device\Harddisk0\DR0, has a bad block.
    It comes down to the file system on your drive having severe issues. I would recommend you run chkdsk again, but this time an off-line scan, meaning you won't be able to use your pc for a while.

    Please open an admin command prompt or admin powershell and enter the following command
    Code:
    chkdsk /r
    It will ask you to schedule the task on a reboot, press Y to allow it and then reboot your pc.
    It may take some time for chkdsk to finish, depending on how much it has to do, please do NOT interrupt it and let it run. The time it needs varies and can take about 20 minutes up to several hours.
    It may also appear as if it is freezing, this is NOT the case, just let it run and it will reboot automatically.

    Once chkdsk is finished, upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
      My Computers


  5. Posts : 3
    Windows 10
    Thread Starter
       #5

    axe0 said:
    When you mentioned 'forum', I assumed you meant a site like this one. That site looks more like a blog.
    From the looks of the content of the article, it looks like they're just random suggestions collected by looking at what worked for others, and these suggestions are typically just common things that actually don't work that often for many. I'm not really surprised it didn't help you to be honest.

    There is one suggestion in that article that should have pointed you to the right direction. The 0x154 crash you have is typically accompanied by the system having issues generating the necessary files to allow debugging, which does make sense given that it often is related to issues with the memory or drive.

    Because there are no dump files, I looked into the events and here's what I found related to this issue.
    Code:
    2019-06-01T16:30:47.845		Checking file system on C:
    The type of the file system is NTFS.
    One of your disks needs to be checked for consistency. You
    may cancel the disk check, but it is strongly recommended
    that you continue.
    Windows will now check the disk.                         
    Stage 1: Examining basic file system structure ...
      410880 file records processed.                                                        
    File verification completed.
    Deleting orphan file record segment 30EBC.
    Deleting orphan file record segment 30EBD.
    Deleting orphan file record segment 30EBE.
    Deleting orphan file record segment 30EBF.
    Deleting orphan file record segment 351BC.
    Deleting orphan file record segment 351BD.
    Deleting orphan file record segment 351BE.
    Deleting orphan file record segment 351BF.
    Deleting orphan file record segment 5AFBC.
    Deleting orphan file record segment 5AFBD.
    Deleting orphan file record segment 5AFBE.
    Deleting orphan file record segment 5AFBF.
      4343 large file records processed.                                   
      0 bad file records processed.                                     
    Stage 2: Examining file name linkage ...
      206 reparse records processed.                                      
      530380 index entries processed.                                                       
    Index verification completed.
      0 unindexed files scanned.                                        
      0 unindexed files recovered to lost and found.                    
      206 reparse records processed.                                      
    Stage 3: Examining security descriptors ...
    Cleaning up 179 unused index entries from index $SII of file 0x9.
    Cleaning up 179 unused index entries from index $SDH of file 0x9.
    Cleaning up 179 unused security descriptors.
    Security descriptor verification completed.
      59751 data files processed.                                           
    CHKDSK is verifying Usn Journal...
      36507536 USN bytes processed.                                                           
    Usn Journal verification completed.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    Windows has made corrections to the file system.
    No further action is required.
     249427967 KB total disk space.
      55978304 KB in 344934 files.
        205164 KB in 59752 indexes.
            12 KB in bad sectors.
        524019 KB in use by the system.
         65536 KB occupied by the log file.
     192720468 KB available on disk.
          4096 bytes in each allocation unit.
      62356991 total allocation units on disk.
      48180117 allocation units available on disk.
    Internal Info:
    00 45 06 00 da 2c 06 00 0c c0 0b 00 00 00 00 00  .E...,..........
    65 00 00 00 69 00 00 00 00 00 00 00 00 00 00 00  e...i...........
    Windows has finished checking your disk.
    Please wait while your computer restarts.
    2019-06-01T12:26:30.571		Chkdsk was executed in scan mode on a volume snapshot.  
    Checking file system on \Device\HarddiskVolume5
    Stage 1: Examining basic file system structure ...
    The USA check value, 0x0, at block 0x1 is incorrect.
    The expected value is 0x2.
        Found corrupt basic file structure for "<0x2,0x2e81d>"
            ... repaired online.
    The USA check value, 0x0, at block 0x1 is incorrect.
    The expected value is 0x2.
        Found corrupt basic file structure for "<0x2,0x2e81e>"
            ... repaired online.
    The USA check value, 0x0, at block 0x1 is incorrect.
    The expected value is 0x2.
        Found corrupt basic file structure for "<0x2,0x2e81f>"
            ... repaired online.
                                                                                           
      410880 file records processed.                                                        
    File verification completed.
                                                                                           
      4342 large file records processed.                                   
        Found unused file metadata marked as used
            ... queued for offline repair.
                                                                                           
      0 bad file records processed.                                     
    Stage 2: Examining file name linkage ...
                                                                                           
      206 reparse records processed.                                      
        Found an unneeded link ($FILE_NAME: "290~1.0-R") in index "$I30" of directory "\Users\feriy\AppData\Local\Android\Sdk\build-tools <0x5,0xee3d>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "GE2DF2~1.EXP") in index "$I30" of directory "\src\flutter\.pub-cache\hosted\pub.dartlang.org\front_end-0.1.11\testcases\inference <0x1,0x1ac0a>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "GEBB3E~1.EXP") in index "$I30" of directory "\src\flutter\.pub-cache\hosted\pub.dartlang.org\front_end-0.1.11\testcases\inference <0x1,0x1ac0a>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "GEF4EC~1.EXP") in index "$I30" of directory "\src\flutter\.pub-cache\hosted\pub.dartlang.org\front_end-0.1.11\testcases\inference <0x1,0x1ac0a>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "GENERI~4.EXP") in index "$I30" of directory "\src\flutter\.pub-cache\hosted\pub.dartlang.org\front_end-0.1.11\testcases\inference <0x1,0x1ac0a>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "306633a263fb04df_0") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "306633~1") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "3d1a8e4939f65d4e_0") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "3D1A8E~1") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "add6e63e6cd74e9f_0") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "ADD6E6~1") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544\9009eff8-6cb4-4419-b50f-25ceecd0ff6d <0xe,0x30d3b>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "instagram-bccebd657e[1].svg") in index "$I30" of directory "\Users\feriy\AppData\Local\Packages\Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe\AC\INetCache\C10MUJEV <0x5,0x30d89>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "INSTAG~1.SVG") in index "$I30" of directory "\Users\feriy\AppData\Local\Packages\Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe\AC\INetCache\C10MUJEV <0x5,0x30d89>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "index.txt") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Franz\Partitions\service-82785ef8-4f1f-4c5b-835c-4942a989e701\Service Worker\CacheStorage\0bf6ab7f94a21cdc9c1649f884333ec20f40a544 <0x10,0x31361>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "f7d99f271d4df9a2aaa205ce696a1895.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\f7 <0x1,0x351e2>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "F7D99F~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\f7 <0x1,0x351e2>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "a15344c4b65458d508db64b8feff5ce2.unlinked") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\a1 <0x1,0x35212>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "A15344~1.UNL") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\a1 <0x1,0x35212>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "61c97d0ffbc7ee105a44ea6933b8ce7d.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\61 <0x1,0x35226>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "61C97D~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\61 <0x1,0x35226>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "3ef524824023f9cada800cb4369a76ea.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\3e <0x1,0x35282>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "3EF524~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\3e <0x1,0x35282>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "168882b3a0b2a2b9b141cdd36949da27.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\16 <0x1,0x352b6>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "168882~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\16 <0x1,0x352b6>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "1f6dccc25952b647cd1a2492d2f1d8a7.resolved") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\1f <0x1,0x353b6>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "1F6DCC~1.RES") in index "$I30" of directory "\Users\feriy\AppData\Local\.dartServer\.analysis-driver\1f <0x1,0x353b6>"
            ... repaired online.
        Found an unneeded link ($FILE_NAME: "14") in index "$I30" of directory "\Users\feriy\AppData\Roaming\Mozilla\Firefox\Profiles\aku1tt5g.default-release\storage\default\moz-extension+++fcc0451e-bd0b-455c-872c-3f51f93c3071^userContextId=4294967295\idb\3647222921wleabcEoxlt-eengsairo.files <0x2,0x3ccfa>"
            ... repaired online.
                                                                                           
      530516 index entries processed.                                                       
    Index verification completed.
                                                                                           
                                                                                           
        Found 31 lost files (...\package.xml <0x4,0x2e801>, ...\mainDexClasses <0x2,0x2e820>, ...); requesting reconnection to index "$I30" of directory "\Device\HarddiskVolume5\found.000"
            ... repaired online.
                                                                                           
      206 reparse records processed.                                      
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
                                                                                           
      59819 data files processed.                                           
    CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.
    Windows has found problems and some were fixed online;
    the remaining problems must be fixed offline.
    Please run "chkdsk /spotfix" to fix the issues.
     249427967 KB total disk space.
      56435740 KB in 346142 files.
        205488 KB in 59822 indexes.
        488183 KB in use by the system.
         65536 KB occupied by the log file.
     192298544 KB available on disk.
          4096 bytes in each allocation unit.
      62356991 total allocation units on disk.
      48074636 allocation units available on disk.
    ----------------------------------------------------------------------
    Stage 1: Examining basic file system structure ...
    The multi-sector header signature in file 0x2e81d is incorrect.
    42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ??  BAAD0...........
    Deleting corrupt file record segment 2E81D.
    The multi-sector header signature in file 0x2e81e is incorrect.
    42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ??  BAAD0...........
    Deleting corrupt file record segment 2E81E.
    The multi-sector header signature in file 0x2e81f is incorrect.
    42 41 41 44 30 00 03 00 ?? ?? ?? ?? ?? ?? ?? ??  BAAD0...........
    Deleting corrupt file record segment 2E81F.
    Deleting orphan file record segment 30EBC.
    Deleting orphan file record segment 30EBD.
    Deleting orphan file record segment 30EBE.
    Deleting orphan file record segment 30EBF.
    Deleting orphan file record segment 351BC.
    Deleting orphan file record segment 351BD.
    Deleting orphan file record segment 351BE.
    Deleting orphan file record segment 351BF.
    Deleting orphan file record segment 5AFBC.
    Deleting orphan file record segment 5AFBD.
    Deleting orphan file record segment 5AFBE.
    Deleting orphan file record segment 5AFBF.
    Stage 2: Examining file name linkage ...
    The file reference 0x200000002e81c of index entry 290~1.0-R of index $I30
    with parent 0xee3d is not the same as 0x400000002e81c.
    Deleting index entry 290~1.0-R in index $I30 of file EE3D.
    The file reference 0x100000001af9e of index entry GE2DF2~1.EXP of index $I30
    with parent 0x1ac0a is not the same as 0xb00000001af9e.
    Deleting index entry GE2DF2~1.EXP in index $I30 of file 1AC0A.
    The file reference 0x100000001af9d of index entry GEBB3E~1.EXP of index $I30
    with parent 0x1ac0a is not the same as 0x300000001af9d.
    Deleting index entry GEBB3E~1.EXP in index $I30 of file 1AC0A.
    The file reference 0x100000001af9f of index entry GEF4EC~1.EXP of index $I30
    with parent 0x1ac0a is not the same as 0xa00000001af9f.
    Deleting index entry GEF4EC~1.EXP in index $I30 of file 1AC0A.
    The file reference 0x100000001af9c of index entry GENERI~4.EXP of index $I30
    with parent 0x1ac0a is not the same as 0xa00000001af9c.
    Deleting index entry GENERI~4.EXP in index $I30 of file 1AC0A.
    Index entry 306633a263fb04df_0 of index $I30 in file 0x30d3b points to unused file 0x30ebd.
    Deleting index entry 306633a263fb04df_0 in index $I30 of file 30D3B.
    Index entry 306633~1 of index $I30 in file 0x30d3b points to unused file 0x30ebd.
    Deleting index entry 306633~1 in index $I30 of file 30D3B.
    Index entry 3d1a8e4939f65d4e_0 of index $I30 in file 0x30d3b points to unused file 0x30ebe.
    Deleting index entry 3d1a8e4939f65d4e_0 in index $I30 of file 30D3B.
    Index entry 3D1A8E~1 of index $I30 in file 0x30d3b points to unused file 0x30ebe.
    Deleting index entry 3D1A8E~1 in index $I30 of file 30D3B.
    Index entry add6e63e6cd74e9f_0 of index $I30 in file 0x30d3b points to unused file 0x30ebf.
    Deleting index entry add6e63e6cd74e9f_0 in index $I30 of file 30D3B.
    Index entry ADD6E6~1 of index $I30 in file 0x30d3b points to unused file 0x30ebf.
    Deleting index entry ADD6E6~1 in index $I30 of file 30D3B.
    Index entry instagram-bccebd657e[1].svg of index $I30 in file 0x30d89 points to unused file 0x30ebc.
    Deleting index entry instagram-bccebd657e[1].svg in index $I30 of file 30D89.
    Index entry INSTAG~1.SVG of index $I30 in file 0x30d89 points to unused file 0x30ebc.
    Deleting index entry INSTAG~1.SVG in index $I30 of file 30D89.
    Index entry index.txt of index $I30 in file 0x31361 points to unused file 0x5afbe.
    Deleting index entry index.txt in index $I30 of file 31361.
    Index entry f7d99f271d4df9a2aaa205ce696a1895.resolved of index $I30 in file 0x351e2 points to unused file 0x351be.
    Deleting index entry f7d99f271d4df9a2aaa205ce696a1895.resolved in index $I30 of file 351E2.
    Index entry F7D99F~1.RES of index $I30 in file 0x351e2 points to unused file 0x351be.
    Deleting index entry F7D99F~1.RES in index $I30 of file 351E2.
    Index entry a15344c4b65458d508db64b8feff5ce2.unlinked of index $I30 in file 0x35212 points to unused file 0x5afbc.
    Deleting index entry a15344c4b65458d508db64b8feff5ce2.unlinked in index $I30 of file 35212.
    Index entry A15344~1.UNL of index $I30 in file 0x35212 points to unused file 0x5afbc.
    Deleting index entry A15344~1.UNL in index $I30 of file 35212.
    Index entry 61c97d0ffbc7ee105a44ea6933b8ce7d.resolved of index $I30 in file 0x35226 points to unused file 0x5afbd.
    Deleting index entry 61c97d0ffbc7ee105a44ea6933b8ce7d.resolved in index $I30 of file 35226.
    Index entry 61C97D~1.RES of index $I30 in file 0x35226 points to unused file 0x5afbd.
    Deleting index entry 61C97D~1.RES in index $I30 of file 35226.
    Index entry 3ef524824023f9cada800cb4369a76ea.resolved of index $I30 in file 0x35282 points to unused file 0x351bd.
    Deleting index entry 3ef524824023f9cada800cb4369a76ea.resolved in index $I30 of file 35282.
    Index entry 3EF524~1.RES of index $I30 in file 0x35282 points to unused file 0x351bd.
    Deleting index entry 3EF524~1.RES in index $I30 of file 35282.
    Index entry 168882b3a0b2a2b9b141cdd36949da27.resolved of index $I30 in file 0x352b6 points to unused file 0x351bc.
    Deleting index entry 168882b3a0b2a2b9b141cdd36949da27.resolved in index $I30 of file 352B6.
    Index entry 168882~1.RES of index $I30 in file 0x352b6 points to unused file 0x351bc.
    Deleting index entry 168882~1.RES in index $I30 of file 352B6.
    Index entry 1f6dccc25952b647cd1a2492d2f1d8a7.resolved of index $I30 in file 0x353b6 points to unused file 0x351bf.
    Deleting index entry 1f6dccc25952b647cd1a2492d2f1d8a7.resolved in index $I30 of file 353B6.
    Index entry 1F6DCC~1.RES of index $I30 in file 0x353b6 points to unused file 0x351bf.
    Deleting index entry 1F6DCC~1.RES in index $I30 of file 353B6.
    Index entry 14 of index $I30 in file 0x3ccfa points to unused file 0x5afbf.
    Deleting index entry 14 in index $I30 of file 3CCFA.
    CHKDSK is scanning unindexed files for reconnect to their original directory.
      0 unindexed files recovered to original directory.
    CHKDSK is recovering remaining unindexed files.
        Lost and found is located at \found.000
    Stage 3: Examining security descriptors ...
    2019-06-01T12:26:16.217		A corruption was discovered in the file system structure on volume C:.
    The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1000000000000.  The name of the file is "<unable to determine file name>".
    2019-06-01T12:13:15.661		Chkdsk was executed in verify mode on a volume snapshot.  
    Checking file system on \Device\HarddiskVolume5
    Examining 1 corruption record ...
    Record 1 of 1: Corrupt File "<0x9,0x5afbf>" ... no corruption found.
    1 corruption record processed in 0.1 seconds.
    Windows has examined the list of previously identified potential issues and found no problems.
    No further action is required.
    2019-06-01T12:09:21.156		Dump file creation failed due to error during dump creation.
    2019-06-01T11:55:58.041		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T11:17:32.422		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T11:15:44.685		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T11:01:08.599		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:50:00.069		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:50:00.067		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:50:00.063		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:59.987		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:41.367		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.837		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.835		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.832		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.830		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.828		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.826		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.824		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.821		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:49:05.816		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.340		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.338		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.336		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.329		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.327		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.324		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.322		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.320		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.287		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.174		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.172		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.168		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:56.166		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:55.865		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:55.863		The device, \Device\Harddisk0\DR0, has a bad block.
    2019-06-01T10:48:55.861		The device, \Device\Harddisk0\DR0, has a bad block.
    It comes down to the file system on your drive having severe issues. I would recommend you run chkdsk again, but this time an off-line scan, meaning you won't be able to use your pc for a while.

    Please open an admin command prompt or admin powershell and enter the following command
    Code:
    chkdsk /r
    It will ask you to schedule the task on a reboot, press Y to allow it and then reboot your pc.
    It may take some time for chkdsk to finish, depending on how much it has to do, please do NOT interrupt it and let it run. The time it needs varies and can take about 20 minutes up to several hours.
    It may also appear as if it is freezing, this is NOT the case, just let it run and it will reboot automatically.

    Once chkdsk is finished, upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
    Ah sorry, i forgot it's a blog. I'll try chkdsk and see the log after it done. Thank you for your help, i really appreciate it.
      My Computer


  6. Posts : 14,890
    Windows 10 Pro
       #6

    Some extra information, because chkdsk was already run a few times and had to do quite a few things, if the log shows that chkdsk again had to do quite a few things it is a sign that the drive may be failing.
      My Computers


 

  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 03:02.
Find Us




Windows 10 Forums