Возникла неопределенная ошибка 6e74667363686b2e 1546

• Remove From My Forums

All replies

• I was having trouble with one of my 

  What trouble are you having?

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• Hi,

  A few days ago, I built a new physical WS2019 Data Center Edition, to run VEEAM on.

  The hardware in question was already running WS2019 with no problem, using a «regular» HDD and less memory. But in advance of installing VEEAM, I replaced the memory with larger memory and installed an SSD — a new 480GB SSD. I then re-installed
  WS2019 Data Ceneter and then VEEAM.

  I have been getting the following BSOD Bug Check once or twice a day (Source:BugCheck, Event ID 1001):

  «The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, bla, bla)»

  I ran sfc /scannow. It said it found and repaired errors. But after rebooting, running sfc gave the same message. In fact, I just posted here about the fact that running sfc /scannow reports problems on
  all my WS2019s, even if I then reboot and try again.

  I then ran chkdsk /f /x /r . Following are my results. Since no errors were found in User File Data, in theory the SSD should not be causing the problem. But the fact that there are so many errors in the Free Clusters of the SSD looks suspicious to me —
  this was a brand new SSD.

  Here are the results of the chkdsk:

  Checking file system on C:
  The type of the file system is NTFS.
  
  A disk check has been scheduled.
  Windows will now check the disk.                         
  
  Stage 1: Examining basic file system structure ...
    140800 file records processed.                                                         
  File verification completed.
    4613 large file records processed.                                    
    0 bad file records processed.                                      
  
  Stage 2: Examining file name linkage ...
    144 reparse records processed.                                       
    202134 index entries processed.                                                        
  Index verification completed.
    0 unindexed files scanned.                                         
    0 unindexed files recovered to lost and found.                     
    144 reparse records processed.                                       
  
  Stage 3: Examining security descriptors ...
  Cleaning up 155 unused index entries from index $SII of file 0x9.
  Cleaning up 155 unused index entries from index $SDH of file 0x9.
  Cleaning up 155 unused security descriptors.
  Security descriptor verification completed.
    30668 data files processed.                                            
  CHKDSK is verifying Usn Journal...
    35409328 USN bytes processed.                                                            
  Usn Journal verification completed.
  
  Stage 4: Looking for bad clusters in user file data ...
    140784 files processed.                                                                
  File data verification completed.
  
  Stage 5: Looking for bad, free clusters ...
  Read failure with status 0xc0000185 at offset 0x6fa68ec000 for 0x13000 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f5800 for 0x9800 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f5800 for 0x4c00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fa400 for 0x4c00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f7e00 for 0x2600 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fa400 for 0x2600 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fca00 for 0x2600 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f7e00 for 0x1200 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f9000 for 0x1400 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fa400 for 0x1200 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fb600 for 0x1400 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fca00 for 0x1200 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fdc00 for 0x1400 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f7e00 for 0x800 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f8600 for 0xa00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f9000 for 0xa00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f9a00 for 0xa00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fa400 for 0x800 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fac00 for 0xa00 bytes.
    109860444 free clusters processed.                                                        
  Free space verification is complete.
  Adding 8 bad clusters to the Bad Clusters File.
  Write failure with status 0xc0000185 at offset 0x6fa68ffe00 for 0x200 bytes.
  An unspecified error occurred (6e74667363686b2e 1546).
  
  Internal Info:
  00 26 02 00 8d 0e 02 00 00 2c 04 00 00 00 00 00  .&.......,......
  3c 00 00 00 54 00 00 00 00 00 00 00 00 00 00 00  <...T...........
  
  Windows has finished checking your disk.
  Please wait while your computer restarts.
  
  

  Should this be regarded as a bad SSD, and I should demand a replacement?

  Could this be causing the BSOD?

  How should I proceed to solve this BSOD?

  TIA,

  mlavie

  • Merged by

    Saturday, January 26, 2019 4:10 PM
    same issue

• Does not look good. What does the hardware manufacturer have to say?

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• Hi Dave,

  I was getting a BSOD on one my machines (but not on any of the others).

  I just posted about it a minute ago, so the details are there, but in short:

  I had a physical box running WS2019 Data Center Edition, with no problems. It had a regular HDD and little memory. I wanted to install VEEAM on it, and therefore replaced the old memory with new larger memory, and replaced the HDD with an SSD. I re-installed
  WS209 and installed VEEAM.

  Since then (3 days ago), I get a BSOD once or twice a day:
  «The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, …, …)»

   Any help would be appreciated. 

  TIA,

  mlavie

• Might try again with the original hardware. I’d also check here and with manufacturer about support for Server 2019.

  https://www.windowsservercatalog.com/

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• Hi Dave,

  I bought the SSD from the technician who handles computers. It’s a SAN-Disk. I’ll try to contact him tonight.

  Could this be causing the BSOD? What about the new memory? The computer is old, so the memory is DDR3 (please don’t laugh), and I suspect the memory he added was not new.

  With chkdsk results like these, could it likely cause the BSOD? Should I ask for a replacement for the SSD and/or memory?

  TIA,

  mlavie

• Hi Dave,

  There is no point in going back to my original hardware. The original disk as a 250 GB HDD — too slow and small for VEEAM. And I am sure my technician already ditched the old small DDR3s he took out.

  Again — I’d like to know if in your opinion that the results of chkdsk indicate that the SSD is likely causing the BSOD.

  And is there any way to get a more detailed analysis of exactly what is causing the «The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, bla, bla)»

  TIA,

  mlavie

• Does not sound good. The RAM should be ECC more info here.

  https://docs.microsoft.com/en-us/windows-server/get-started-19/sys-reqs-19

  If you’re building from unknown components then it doesn’t meant it can’t work but does mean all of the testing / vetting that server manufacturer’s normally do is left to the end user to do.

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• I have been getting the following BSOD Bug Check once or twice a day (Source:BugCheck, Event ID 1001):

  «The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, bla, bla)»

  hi,

  Could you please provide a link to your dumps?

  ---

  Avis de non-responsabilité:
  Mon opinion ne peut pas coïncider avec la position officielle de Microsoft.

  Bien cordialement, Andrei …
  
  MCP

• Dave,

  In case this helps, I also noticed these warning in the event log after all reboots (whether due to BSOD or an intentional reboot):

  Source:Disk, Event ID 153 «The IO operation at logical block address 0x37e477ff for Disk 0 (PDO name: DeviceIdeIdeDeviceP2T0L0-2) was retried.»

  • Edited by
    mlavie58
    Saturday, January 26, 2019 6:00 PM

• Cher Andrei,

  It appears that the dump files have disappeared — perhaps since I’ve done various multiple tests and reboots since the last BSOD.

  I’ll post a link as soon as this happens again.

  By the way, to which site should I upload dump files for use in this forum?

  Merci,

  mlavie

  • Edited by
    mlavie58
    Saturday, January 26, 2019 6:10 PM

• By the way, to which site should I upload dump files for use in this forum?

  Hi,

  Please upload them to Onedrive.

  ---

  Avis de non-responsabilité:
  Mon opinion ne peut pas coïncider avec la position officielle de Microsoft.

  Bien cordialement, Andrei …
  
  MCP

• In general you can put files up on OneDrive and share a link, but also note debugging stop errors is outside of scope of forums support. If you need help debugging I’d start a support case here.

  https://support.microsoft.com/en-us/gp/contactus81?forceorigin=esmc&audience=commercial&wa=wsignin1.0

  (please don’t forget to mark helpful replies as answer)

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• For posting into the thread please use share links:  one drive, drop box, or google drive

  1) Open administrative command prompt and type or copy and paste:

  a) sfc /scannow

  b) dism /online /cleanup-image /restorehealth

  c) 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

  2) Test the drive using:

  A) HD Tune

  https://www.hdtune.com/ (free edition)

  Post images into the thread for test results on these tabs:

  a) Health (SMART)

  b) Benchmark

  c) Full error scan

  B) HD Sentinel:

  https://www.hdsentinel.com/ (free or trial edition)

  https://www.hdsentinel.com/

  2) Repeat an evaluation of the drive file system running chkdsk /r /v

  This may take several hours so plan to run overnight

  3) Use the text and images in this link to find the chkdsk report in the event viewer > copy and paste > notepad > post a share link into the thread

  https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html

• Hi «questionsformicrosoftproducts»,

  I did sfc /scannow. It reported errors and said it fixed them. I rebooted, re-ran sfc, and got the same thing — over and over. In fact, I tried it on my 2 other physical and 3 other VM WS2019s, and they all suffered from the same phenomenon. The response
  is always:

  Beginning system scan.  This process will take some time.
  
  Beginning verification phase of system scan.
  Verification 100% complete.
  
  Windows Resource Protection found corrupt files and successfully repaired them.
  For online repairs, details are included in the CBS log file located at
  windirLogsCBSCBS.log. For example C:WindowsLogsCBSCBS.log. For offline
  repairs, details are included in the log file provided by the /OFFLOGFILE flag.

  «dism /online /cleanup-image /restorehealth» returned no errors:

  Deployment Image Servicing and Management tool
  Version: 10.0.17763.1
  
  Image Version: 10.0.17763.292
  
  [==========================100.0%==========================] The restore operation completed successfully.
  The operation completed successfully.

  I will run the other things you suggest. However, given all the errors chkdsk found in the SSD, I’m leaning towards that being the problem.

  In any case, thanks.

  mlavie

• The component store is without corruption as the restorehealth was fine.

  The scannow found problems that it was able to fix however the problems were recurrent.

  The problems were not permanently fixed by scannow.

  The drive has bad clusters.

  Running chkdsk /f or /r can allow you to use the drive without these sectors (the sections that were not able to be read).

  The bad clusters when they are logical bad clusters can be fixed by cleaning the drive. 

  They should disappear.

  See this link:

  https://www.howtogeek.com/173463/bad-sectors-explained-why-hard-drives-get-bad-sectors-and-what-you-can-do-about-it/

  When available please post the images of the test results for each HD Tune and HD Sentinel.

  Open the website for the computer or motherboard manufacturer > enter the product or serial number or model > select the operating system > view drivers and bios > post a url or hyperlink into the thread

  Some computers may have in the BIOS firmware to clean the drive.  For example:  disk sanitizer for HD or secure erase for SSD. 

  HP has a lot of government contracts and typically provides these firmware features so that drives can be repurposed

  Cleaning the drive may allow you to fix both problems with the drive file system and operating system.

  So this is a deeper clean than a clean install.

  After cleaning the drive> reinstall the operating system and drivers > perform Windows updates > retest the drive with scannow and chkdsk /r /v > confirm that it is normal. 

  Once you have confirmed that these are ok then you can use VM and reevaluate the operating system and drive file system.

  • Edited by
    questionsformicrosoftproducts
    Saturday, January 26, 2019 11:17 PM

• Remove From My Forums

All replies

• I was having trouble with one of my 

  What trouble are you having?

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• Hi,

  A few days ago, I built a new physical WS2019 Data Center Edition, to run VEEAM on.

  The hardware in question was already running WS2019 with no problem, using a «regular» HDD and less memory. But in advance of installing VEEAM, I replaced the memory with larger memory and installed an SSD — a new 480GB SSD. I then re-installed
  WS2019 Data Ceneter and then VEEAM.

  I have been getting the following BSOD Bug Check once or twice a day (Source:BugCheck, Event ID 1001):

  «The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, bla, bla)»

  I ran sfc /scannow. It said it found and repaired errors. But after rebooting, running sfc gave the same message. In fact, I just posted here about the fact that running sfc /scannow reports problems on
  all my WS2019s, even if I then reboot and try again.

  I then ran chkdsk /f /x /r . Following are my results. Since no errors were found in User File Data, in theory the SSD should not be causing the problem. But the fact that there are so many errors in the Free Clusters of the SSD looks suspicious to me —
  this was a brand new SSD.

  Here are the results of the chkdsk:

  Checking file system on C:
  The type of the file system is NTFS.
  
  A disk check has been scheduled.
  Windows will now check the disk.                         
  
  Stage 1: Examining basic file system structure ...
    140800 file records processed.                                                         
  File verification completed.
    4613 large file records processed.                                    
    0 bad file records processed.                                      
  
  Stage 2: Examining file name linkage ...
    144 reparse records processed.                                       
    202134 index entries processed.                                                        
  Index verification completed.
    0 unindexed files scanned.                                         
    0 unindexed files recovered to lost and found.                     
    144 reparse records processed.                                       
  
  Stage 3: Examining security descriptors ...
  Cleaning up 155 unused index entries from index $SII of file 0x9.
  Cleaning up 155 unused index entries from index $SDH of file 0x9.
  Cleaning up 155 unused security descriptors.
  Security descriptor verification completed.
    30668 data files processed.                                            
  CHKDSK is verifying Usn Journal...
    35409328 USN bytes processed.                                                            
  Usn Journal verification completed.
  
  Stage 4: Looking for bad clusters in user file data ...
    140784 files processed.                                                                
  File data verification completed.
  
  Stage 5: Looking for bad, free clusters ...
  Read failure with status 0xc0000185 at offset 0x6fa68ec000 for 0x13000 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f5800 for 0x9800 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f5800 for 0x4c00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fa400 for 0x4c00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f7e00 for 0x2600 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fa400 for 0x2600 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fca00 for 0x2600 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f7e00 for 0x1200 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f9000 for 0x1400 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fa400 for 0x1200 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fb600 for 0x1400 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fca00 for 0x1200 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fdc00 for 0x1400 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f7e00 for 0x800 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f8600 for 0xa00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f9000 for 0xa00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68f9a00 for 0xa00 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fa400 for 0x800 bytes.
  Read failure with status 0xc0000185 at offset 0x6fa68fac00 for 0xa00 bytes.
    109860444 free clusters processed.                                                        
  Free space verification is complete.
  Adding 8 bad clusters to the Bad Clusters File.
  Write failure with status 0xc0000185 at offset 0x6fa68ffe00 for 0x200 bytes.
  An unspecified error occurred (6e74667363686b2e 1546).
  
  Internal Info:
  00 26 02 00 8d 0e 02 00 00 2c 04 00 00 00 00 00  .&.......,......
  3c 00 00 00 54 00 00 00 00 00 00 00 00 00 00 00  <...T...........
  
  Windows has finished checking your disk.
  Please wait while your computer restarts.
  
  

  Should this be regarded as a bad SSD, and I should demand a replacement?

  Could this be causing the BSOD?

  How should I proceed to solve this BSOD?

  TIA,

  mlavie

  • Merged by

    Saturday, January 26, 2019 4:10 PM
    same issue

• Does not look good. What does the hardware manufacturer have to say?

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• Hi Dave,

  I was getting a BSOD on one my machines (but not on any of the others).

  I just posted about it a minute ago, so the details are there, but in short:

  I had a physical box running WS2019 Data Center Edition, with no problems. It had a regular HDD and little memory. I wanted to install VEEAM on it, and therefore replaced the old memory with new larger memory, and replaced the HDD with an SSD. I re-installed
  WS209 and installed VEEAM.

  Since then (3 days ago), I get a BSOD once or twice a day:
  «The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, …, …)»

   Any help would be appreciated. 

  TIA,

  mlavie

• Might try again with the original hardware. I’d also check here and with manufacturer about support for Server 2019.

  https://www.windowsservercatalog.com/

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• Hi Dave,

  I bought the SSD from the technician who handles computers. It’s a SAN-Disk. I’ll try to contact him tonight.

  Could this be causing the BSOD? What about the new memory? The computer is old, so the memory is DDR3 (please don’t laugh), and I suspect the memory he added was not new.

  With chkdsk results like these, could it likely cause the BSOD? Should I ask for a replacement for the SSD and/or memory?

  TIA,

  mlavie

• Hi Dave,

  There is no point in going back to my original hardware. The original disk as a 250 GB HDD — too slow and small for VEEAM. And I am sure my technician already ditched the old small DDR3s he took out.

  Again — I’d like to know if in your opinion that the results of chkdsk indicate that the SSD is likely causing the BSOD.

  And is there any way to get a more detailed analysis of exactly what is causing the «The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, bla, bla)»

  TIA,

  mlavie

• Does not sound good. The RAM should be ECC more info here.

  https://docs.microsoft.com/en-us/windows-server/get-started-19/sys-reqs-19

  If you’re building from unknown components then it doesn’t meant it can’t work but does mean all of the testing / vetting that server manufacturer’s normally do is left to the end user to do.

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• I have been getting the following BSOD Bug Check once or twice a day (Source:BugCheck, Event ID 1001):

  «The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, bla, bla)»

  hi,

  Could you please provide a link to your dumps?

  ---

  Avis de non-responsabilité:
  Mon opinion ne peut pas coïncider avec la position officielle de Microsoft.

  Bien cordialement, Andrei …
  
  MCP

• Dave,

  In case this helps, I also noticed these warning in the event log after all reboots (whether due to BSOD or an intentional reboot):

  Source:Disk, Event ID 153 «The IO operation at logical block address 0x37e477ff for Disk 0 (PDO name: DeviceIdeIdeDeviceP2T0L0-2) was retried.»

  • Edited by
    mlavie58
    Saturday, January 26, 2019 6:00 PM

• Cher Andrei,

  It appears that the dump files have disappeared — perhaps since I’ve done various multiple tests and reboots since the last BSOD.

  I’ll post a link as soon as this happens again.

  By the way, to which site should I upload dump files for use in this forum?

  Merci,

  mlavie

  • Edited by
    mlavie58
    Saturday, January 26, 2019 6:10 PM

• By the way, to which site should I upload dump files for use in this forum?

  Hi,

  Please upload them to Onedrive.

  ---

  Avis de non-responsabilité:
  Mon opinion ne peut pas coïncider avec la position officielle de Microsoft.

  Bien cordialement, Andrei …
  
  MCP

• In general you can put files up on OneDrive and share a link, but also note debugging stop errors is outside of scope of forums support. If you need help debugging I’d start a support case here.

  https://support.microsoft.com/en-us/gp/contactus81?forceorigin=esmc&audience=commercial&wa=wsignin1.0

  (please don’t forget to mark helpful replies as answer)

  ---

  Regards, Dave Patrick ….
  Microsoft Certified Professional
  Microsoft MVP [Windows Server] Datacenter Management

  Disclaimer: This posting is provided «AS IS» with no warranties or guarantees, and confers no rights.

• For posting into the thread please use share links:  one drive, drop box, or google drive

  1) Open administrative command prompt and type or copy and paste:

  a) sfc /scannow

  b) dism /online /cleanup-image /restorehealth

  c) 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

  2) Test the drive using:

  A) HD Tune

  https://www.hdtune.com/ (free edition)

  Post images into the thread for test results on these tabs:

  a) Health (SMART)

  b) Benchmark

  c) Full error scan

  B) HD Sentinel:

  https://www.hdsentinel.com/ (free or trial edition)

  https://www.hdsentinel.com/

  2) Repeat an evaluation of the drive file system running chkdsk /r /v

  This may take several hours so plan to run overnight

  3) Use the text and images in this link to find the chkdsk report in the event viewer > copy and paste > notepad > post a share link into the thread

  https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html

• Hi «questionsformicrosoftproducts»,

  I did sfc /scannow. It reported errors and said it fixed them. I rebooted, re-ran sfc, and got the same thing — over and over. In fact, I tried it on my 2 other physical and 3 other VM WS2019s, and they all suffered from the same phenomenon. The response
  is always:

  Beginning system scan.  This process will take some time.
  
  Beginning verification phase of system scan.
  Verification 100% complete.
  
  Windows Resource Protection found corrupt files and successfully repaired them.
  For online repairs, details are included in the CBS log file located at
  windirLogsCBSCBS.log. For example C:WindowsLogsCBSCBS.log. For offline
  repairs, details are included in the log file provided by the /OFFLOGFILE flag.

  «dism /online /cleanup-image /restorehealth» returned no errors:

  Deployment Image Servicing and Management tool
  Version: 10.0.17763.1
  
  Image Version: 10.0.17763.292
  
  [==========================100.0%==========================] The restore operation completed successfully.
  The operation completed successfully.

  I will run the other things you suggest. However, given all the errors chkdsk found in the SSD, I’m leaning towards that being the problem.

  In any case, thanks.

  mlavie

• The component store is without corruption as the restorehealth was fine.

  The scannow found problems that it was able to fix however the problems were recurrent.

  The problems were not permanently fixed by scannow.

  The drive has bad clusters.

  Running chkdsk /f or /r can allow you to use the drive without these sectors (the sections that were not able to be read).

  The bad clusters when they are logical bad clusters can be fixed by cleaning the drive. 

  They should disappear.

  See this link:

  https://www.howtogeek.com/173463/bad-sectors-explained-why-hard-drives-get-bad-sectors-and-what-you-can-do-about-it/

  When available please post the images of the test results for each HD Tune and HD Sentinel.

  Open the website for the computer or motherboard manufacturer > enter the product or serial number or model > select the operating system > view drivers and bios > post a url or hyperlink into the thread

  Some computers may have in the BIOS firmware to clean the drive.  For example:  disk sanitizer for HD or secure erase for SSD. 

  HP has a lot of government contracts and typically provides these firmware features so that drives can be repurposed

  Cleaning the drive may allow you to fix both problems with the drive file system and operating system.

  So this is a deeper clean than a clean install.

  After cleaning the drive> reinstall the operating system and drivers > perform Windows updates > retest the drive with scannow and chkdsk /r /v > confirm that it is normal. 

  Once you have confirmed that these are ok then you can use VM and reevaluate the operating system and drive file system.

  • Edited by
    questionsformicrosoftproducts
    Saturday, January 26, 2019 11:17 PM

Windows 10: Repairing USB error (6e74667363686b2e 1546)

Discus and support Repairing USB error (6e74667363686b2e 1546) in Windows 10 Network and Sharing to solve the problem; I have been trying to use a USB to play videos on a TV but it only plays a very select few.

The USB has plenty of size and the TV plays most formats…
Discussion in ‘Windows 10 Network and Sharing’ started by DanielAllen__, Feb 22, 2019.

Repairing USB error (6e74667363686b2e 1546)

1. Repairing USB error (6e74667363686b2e 1546) — Similar Threads — Repairing USB error

2. An unspecified error occurred 6e74667363686b2e 15bc.

   in Windows 10 Network and Sharing

   An unspecified error occurred 6e74667363686b2e 15bc.: Chkdsk was executed in read/write mode. Checking file system on H:Stage 1: Examining basic file system structure … 256 file records processed. &nb…

3. An unspecified error occurred 6e74667363686b2e 17b4

   in Windows 10 Network and Sharing

   An unspecified error occurred 6e74667363686b2e 17b4: After running chkdsk in /x /r mode from windows 10 powershell at stage 5 the message: Correcting errors in the Master File Table MFT mirror.Insufficient disk space to repair master file table MFT mirror.CHKDSK aborted.An unspecified error occurred 6e74667363686b2e 17b4The HDD…

4. An unspecified error occurred 6e74667363686b2e 17b4

   in Windows 10 Gaming

   An unspecified error occurred 6e74667363686b2e 17b4: After running chkdsk in /x /r mode from windows 10 powershell at stage 5 the message: Correcting errors in the Master File Table MFT mirror.Insufficient disk space to repair master file table MFT mirror.CHKDSK aborted.An unspecified error occurred 6e74667363686b2e 17b4The HDD…

5. An unspecified error occurred 6e74667363686b2e 17b4

   in Windows 10 Software and Apps

   An unspecified error occurred 6e74667363686b2e 17b4: After running chkdsk in /x /r mode from windows 10 powershell at stage 5 the message: Correcting errors in the Master File Table MFT mirror.Insufficient disk space to repair master file table MFT mirror.CHKDSK aborted.An unspecified error occurred 6e74667363686b2e 17b4The HDD…

6. An unspecified error occurred 6e74667363686b2e 17b4.

   in Windows 10 Network and Sharing

   An unspecified error occurred 6e74667363686b2e 17b4.: What’s the meaning of this error?

   https://answers.microsoft.com/en-us/windows/forum/all/an-unspecified-error-occurred-6e74667363686b2e/c625011a-9fd7-44d7-90d8-d2a6ad840f61

7. An unspecified error occurred 6e74667363686b2e 17b4.

   in Windows 10 Gaming

   An unspecified error occurred 6e74667363686b2e 17b4.: What’s the meaning of this error?

   https://answers.microsoft.com/en-us/windows/forum/all/an-unspecified-error-occurred-6e74667363686b2e/c625011a-9fd7-44d7-90d8-d2a6ad840f61

8. An unspecified error occurred 6e74667363686b2e 17b4.

   in Windows 10 Software and Apps

   An unspecified error occurred 6e74667363686b2e 17b4.: What’s the meaning of this error?

   https://answers.microsoft.com/en-us/windows/forum/all/an-unspecified-error-occurred-6e74667363686b2e/c625011a-9fd7-44d7-90d8-d2a6ad840f61

9. CHKDSK error 6e74667363686b2e 13d7

   in Windows 10 BSOD Crashes and Debugging

   CHKDSK error 6e74667363686b2e 13d7: After doing a factory reset on my Windows 10 Dell, I attempted to perform windows updates. Was unable to successfully update and when attempting to restart, I got stuck in continuous boot loop. I performed CHKDSK and it came up with the following error at stage 5:…

10. Error 6e74667363686b2e 7e3

    in Windows 10 Network and Sharing

    Error 6e74667363686b2e 7e3: I get this error while trying to repair the drive

    https://answers.microsoft.com/en-us/windows/forum/all/error-6e74667363686b2e-7e3/ccb44797-df02-4e13-85e4-92379b904b8d