New
#41
/f is a parameter that is already included twice....
I am wondering zbook, what is the reason for suggesting /f /r and /x whilst I've been trying to explain this a few times.
Just run chkdsk G: /r /x
/f is a parameter that is already included twice....
I am wondering zbook, what is the reason for suggesting /f /r and /x whilst I've been trying to explain this a few times.
Just run chkdsk G: /r /x
The syntax allow both to be used to get the same result. It's out of habit.
If /r has it disregard the /f switch then its the same. If /f makes it run the same process again that its consuming unnecessary time. I was not able to find that information and understand your comment.
/r Locates bad sectors and recovers readable information. The disk must be locked. /r includes the functionality of /f, with the additional analysis of physical disk errors.
/x Forces the volume to dismount first, if necessary. All open handles to the drive are invalidated. /x also includes the functionality of /f.
Hi guys
Have run memtest again so that will be about 12 passes with both memtests and 0 errors.
Attachment 139586
I have took both seagate drives out of the system for now to see if it is ok for a while as i was transfering a couple of files from the one of them drives to my 4tb hitachi one and it bsod again twice.
Ive updated system spec also.
updated logs below.
Thanks again Axe0,Zbook.
Hally.
Last edited by Hally; 15 Jun 2017 at 06:36.
Memtest test result shouldn't be added to another test result.
What happens is that you test a certain part a few times, whilst another part of the memory isn't being tested.
Hi Axe0
I see i will run it over night so it does 8 passes.
Did the logs have anything different or were they the same errors.
Hally
Pretty much the same, at this stage information like below is useless. The only thing it says is that a memory access violation occured due to corruption in the memory mechanisms of Windows, ffffffffc0000005 = memory violation, nothing more.
Code:BugCheck 1000007E, {ffffffffc0000005, fffff800f8cb3730, ffffb780def8a678, ffffb780def89ec0} Probably caused by : memory_corruption
Hi Axe0,Zbook
Ran memtest 86+ again but only could do 7 passes as needed to use the comp for work.
Attachment 139810
Thanks Axe0 yeah those errors don't give much away and they are so random when it bsod
I think it could be the windows 1703 update as my system was running fine not had problem or bsod for about a year and soon as this update was on nothing but problems even the asmedia usb 3 drivers went on ok in the other versions of windows now it says cant fined usb 3 controller even though it's enabled in bios.
Hi Axe0,Zbook,Spectrum just like to say thank you for all the help you gave me.
Axe0 where would i get the windows version before this 1703 one and will rufus convert the iso to usb boot drive.
Thanks again really appreciated the help.
Kind regards.
Hally
Hally,
Before going back to windows 7 or 8.1 consider an in place upgrade with windows 10. That way if there was any operating system/registry problem not found by scannow or restorehealth you will have the option to continue using windows 10 after the repair.
When you make an iso from the Microsoft web site they are made bootable and you should not need rufus.
This is a link for an in place upgrade or repair install of windows 10:
Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials
This is a link to create a bootable windows 10 iso: Download Windows 10
This is a link to create a bootable windows 7 iso: Download Windows 7 Disc Images (ISO Files)
This is a link to a dual boot option: How to Dual-Boot Windows 10 with Windows 7 or 8
This is a link about windows 7 VM: How to uninstall Windows 10 and go back to Windows 7 or 8 | PCWorld
Some other links:
How to uninstall Windows 10 and restore Windows 7 - Microsoft Community
How to: Rollback to a previous version of Windows from Windows 10 | Teching It Easy: with Windows
How to Uninstall Windows 10 and Downgrade to Windows 7 or 8.1
Each tool that is used can be modified.
Now that we have eliminated memory RAM/dim and HD issues the bsod troubleshooting can be approached by testing every non-Microsoft driver with these customized settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
If bsod are produced we can analyze the minidump.
If there are no more bsod then we can call it a day.