Got the zip file with the logs, also formatted the HDD using the Low Level Format Tool so the HDD currently has no partitions or a partition style (Disk Management prompted to select MBR or GPT but I left it unattended, so no changes at all). Should I run Chkdsk now or not since the HDD isn't assigned to a drive letter?
Beta log
Open device manager > click view > click show > hidden devices > manually expand all rows > look for any row with a yellow triangle and a black exclamation mark or unknown device > post images into the thread
For the ST drive chkdsk generally requires ntfs.Code:Intel(R) HD Graphics 4600 PCI\VEN_8086&DEV_0412&SUBSYS_D0001458&REV_06\3&11583659&0&10 This device is disabled.
diskpart
list disk
list volume
select disk 1
(make sure it is the applicable drive)
create partition primary size=5000
list volume
format fs=ntfs
assign
active
exit
copy the files to the new partition
run chkdsk /r /v
By the files, are you specifying the ones I've backed-up onto the recovery? I ran the codes but isn't 5000 too small? The partition is only 4.88 GB big which isn't enough for the files. Should it be 50000 instead of 5000? Also, I've disabled the Intel HD 4600 driver too see if it would fix video stuttering issues on the computer. It doesn't, so I'll turn it back on.
The partition can be MBR or GPT.
Any size can be chosen and the modified as it is a storage drive.
50,000 MB =5 GB is fine.
The last BSOD in the logs were on 3/23/2018.
If there any BSOD run the BETA log collector and post a new zip into the thread.
On disk management the prior partition file size before modification was approximately 930 GB.
The used space was approximately 200 GB.
To test chkdsk any size partition can be used.
The partition size can be 500,000 to start and then modified as needed.
Last edited by zbook; 28 Mar 2019 at 16:18.
I have ran BSOD's into a few BSOD's the past weeks but they aren't common, I guess the 23rd was the last time I ran into one.
I can't copy 187 GB of files onto a 4.88 GB partition, shouldn't I increase the partition size?
The chkdsk had failed with error insufficient space.
If chkdsk works with a small partition it should be a quick test.
Then you can modify the partition, restore all files, and run the chkdsk overnight.
Modify the startup and recovery setting with adinistrative command prompt:
wmic recoveros set autoreboot = false
Got the chkdsk results and also executed the code.
CHKDSKResults
Nice.
Ckdsk had completed.
There were no reported problems.
To extend the partition download and install minitool partition partition wizard:
MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download.com
How to Extend Partition | MiniTool Partition Wizard Tutorial
Restore all files and then run chkdsk /r /v overnight.
After the chkdsk results are posted plan to monitor the computer for several days.
Report into thread if there are hangs, freezes, unexpected shutdowns or BSOD.
Then post a new BETA log collector zip.
Last edited by zbook; 31 Mar 2019 at 19:51.
Chkdsk ran without problems and there were no problems detected.
Please run the BETA log collector and post a new zip into thread.
Quote