F5F Stay Refreshed Software Operating Systems Windows 10 Pro files are frequently experiencing corruption issues.

Windows 10 Pro files are frequently experiencing corruption issues.

Windows 10 Pro files are frequently experiencing corruption issues.

I
IkBenHetBram
Senior Member
735
07-18-2016, 10:08 AM
#1
Hey there, I bought a Workstation: HP Z620 with dual Xeon E5-2660 v2 20 cores from an electronics store. After a month, the system wouldn’t load properly. Even after cleaning and formatting the HDD, the issue persisted. They replaced the drive under warranty, but asked for an SSD instead. I reinstalled Windows, and it worked fine. After two months without issues, both Windows and repairs failed to start.

I tried a fresh install from Microsoft, but after about a month the problem returned. I switched to another version from softfamous.com, which also failed after a few weeks. After a month, I cleaned the system, reinstalled Windows, and ran MemTest—no errors found. Updated BIOS, downloaded new drivers, checked SSD and HDD with ADATA tools—they were all healthy.

Once a week Windows would boot, but then I encountered another failure. I followed some CMD commands (like chkcmd 6-2-2019.txt) and monitored Event Viewer, but the sfc /scannow command often couldn’t fix corruption. Now I’m facing the same issue again.

P.S. Whenever this happened, the machine shut down completely. I’ve searched many forums, but no solution came up. Thanks for your help!

Attached: Cmd commands used, DxDiag.txt, and the latest Event Viewer log (saved 11-2-2019.evtx cmd 6-2-2019.txt).
I
IkBenHetBram
07-18-2016, 10:08 AM #1

Hey there, I bought a Workstation: HP Z620 with dual Xeon E5-2660 v2 20 cores from an electronics store. After a month, the system wouldn’t load properly. Even after cleaning and formatting the HDD, the issue persisted. They replaced the drive under warranty, but asked for an SSD instead. I reinstalled Windows, and it worked fine. After two months without issues, both Windows and repairs failed to start.

I tried a fresh install from Microsoft, but after about a month the problem returned. I switched to another version from softfamous.com, which also failed after a few weeks. After a month, I cleaned the system, reinstalled Windows, and ran MemTest—no errors found. Updated BIOS, downloaded new drivers, checked SSD and HDD with ADATA tools—they were all healthy.

Once a week Windows would boot, but then I encountered another failure. I followed some CMD commands (like chkcmd 6-2-2019.txt) and monitored Event Viewer, but the sfc /scannow command often couldn’t fix corruption. Now I’m facing the same issue again.

P.S. Whenever this happened, the machine shut down completely. I’ve searched many forums, but no solution came up. Thanks for your help!

Attached: Cmd commands used, DxDiag.txt, and the latest Event Viewer log (saved 11-2-2019.evtx cmd 6-2-2019.txt).

G
GoMigs
Senior Member
614
07-18-2016, 10:43 AM
#2
Consider using Hard Disk Sentinel to verify drives. If everything looks fine, I suggest fixing the Windows image with DISM and then running SFC. I've created a script that automates this process for you. http://www.mediafire.com/file/4s31u10j42...8.bat/file
G
GoMigs
07-18-2016, 10:43 AM #2

Consider using Hard Disk Sentinel to verify drives. If everything looks fine, I suggest fixing the Windows image with DISM and then running SFC. I've created a script that automates this process for you. http://www.mediafire.com/file/4s31u10j42...8.bat/file

P
PhantomRazer
Member
186
07-23-2016, 07:18 AM
#3
I just tested Hard Disk Sentinel and everything seems okay. I ran DISM and after roughly an hour the sfc still detected corrupt files. I’ll use your script soon. Appreciate you avoiding integrity issues right now. But what triggers them is what bothers me—I’m pretty sure it will happen again.
P
PhantomRazer
07-23-2016, 07:18 AM #3

I just tested Hard Disk Sentinel and everything seems okay. I ran DISM and after roughly an hour the sfc still detected corrupt files. I’ll use your script soon. Appreciate you avoiding integrity issues right now. But what triggers them is what bothers me—I’m pretty sure it will happen again.

I
ISY_0815
Senior Member
566
07-28-2016, 05:06 PM
#4
Following the script execution as an admin, ensure no violations are detected by disabling hibernation via the command prompt and running powercfg -h off. Proceed with updating Windows afterward. Next, perform a disk cleanup using the built-in tool and then run a malware scan with HitmanPro or Malwarebytes Anti-Malware.
I
ISY_0815
07-28-2016, 05:06 PM #4

Following the script execution as an admin, ensure no violations are detected by disabling hibernation via the command prompt and running powercfg -h off. Proceed with updating Windows afterward. Next, perform a disk cleanup using the built-in tool and then run a malware scan with HitmanPro or Malwarebytes Anti-Malware.

G
guntaj800
Member
112
07-30-2016, 07:25 AM
#5
Thank you for your time and guidance. I reached out to the electronics store where I purchased the machine; they agreed to inspect it and either repair or replace it. I will remember your advice in case it becomes necessary.
G
guntaj800
07-30-2016, 07:25 AM #5

Thank you for your time and guidance. I reached out to the electronics store where I purchased the machine; they agreed to inspect it and either repair or replace it. I will remember your advice in case it becomes necessary.

L
LPTC1066
Junior Member
12
07-30-2016, 03:46 PM
#6
Sorry for the delay in sharing this. I wanted to tell you about my experience. The electronics shop reached out and said the machine was functioning correctly. They replaced the RAM just as a precaution and sent it back. When I tried to restart it, the issue repeated. I realized the main differences between my setup and theirs were the keyboard, mouse, and monitor. I swapped in an old PS/2 keyboard and a basic Dell mouse, which resolved the problem. Since then, everything is fine. I’m puzzled about why these two peripherals caused such trouble. Thanks again for your time. P.S. The mouse and keyboard came free with the machine purchase.
L
LPTC1066
07-30-2016, 03:46 PM #6

Sorry for the delay in sharing this. I wanted to tell you about my experience. The electronics shop reached out and said the machine was functioning correctly. They replaced the RAM just as a precaution and sent it back. When I tried to restart it, the issue repeated. I realized the main differences between my setup and theirs were the keyboard, mouse, and monitor. I swapped in an old PS/2 keyboard and a basic Dell mouse, which resolved the problem. Since then, everything is fine. I’m puzzled about why these two peripherals caused such trouble. Thanks again for your time. P.S. The mouse and keyboard came free with the machine purchase.