Junior Member
OK, it seems my W8 system is possibly in a bit of trouble...
I ran CHKDSK on my C: drive, and at the end saw this :
=============
Errors detected in the Boot File.
Windows has checked the file system and found problems.
Please run chkdsk /scan to find the problems and queue them for repair.
==============
Hmm, system boots just fine and I appear to have NO errors. I am on an SSD and it is quite possible that I did 'mess up' something in the boot record when I migrated a large partition that was bootable into the much smaller SSD.
So I ran CHKDSK /SCAN... BIG MISTAKE...
At the end it asked to cue it up to check the disk on boot. I allowed it. It ran and then started a troubleshooter, which ran PC Diagnostics and then a message that it could take up to 1 hour to fix. Almost instantly the system rebooted, AND ran chkdsk again. Off it went to the troubleshooter... and it just continued in this loop.
OK, I did break the loop and got an screen with options... one was to go into W8 directly, and again, the loop started up again. Argh... broke into it and I had other options, REFRESH, RESTORE, or shutdown. OK, Shutdown.... nope, power on started the loop again...
UGLY... so I did a REFRESH basically losing installed non-MS store programs. No problem, I've got an IMAGE.
When it was restored, it was OK on CHKDSK... and the few Store apps (Live Tiles) that didn't run before did... good.
I restored my image, and poof, CHKDSK shows the error again. However, this system has been booting for months with no problem and I assume the 'corruption' was present, and will now too with the 'problem'. I just can't run CHKDSK on it?
CAN NOT find anything about this on the web?
Thinking the MBR could be 'damaged'? There are programs to fix that and the boot record, but I'm not about to try this as it could break me?
HELP and SUGGESTIONS appreciated...
Windows 8 remember. Ran CHKNTFS and the FS is OK and the disk is NOT dirty....
I ran a program to check the MBR (MBRCheck.exe), it seems OK?
===============
\\.\C: --> \\.\PhysicalDrive0 at offset 0x00000000`00100000 (NTFS)
\\.\D: --> \\.\PhysicalDrive2 at offset 0x00000000`04700000 (NTFS)
\\.\K: --> \\.\PhysicalDrive2 at offset 0x0000002e`aae00000 (NTFS)
\\.\L: --> \\.\PhysicalDrive1 at offset 0x00000000`00100000 (NTFS)
\\.\X: --> \\.\PhysicalDrive2 at offset 0x00000003`c4700000 (NTFS)
PhysicalDrive0 Model Number: CorsairCSSD-F115GB2-A, Rev: 2.4
PhysicalDrive2 Model Number: WDCWD7501AALS-75J7B0, Rev: 05.00K05
PhysicalDrive1 Model Number: ST31000528AS, Rev: CC34
Size Device Name MBR Status
--------------------------------------------
107 GB \\.\PhysicalDrive0 Windows 7 MBR code detected
SHA1: 4379A3D43019B46FA357F7DD6A53B45A3CA8FB79
698 GB \\.\PhysicalDrive2 Windows 7 MBR code detected
SHA1: 4379A3D43019B46FA357F7DD6A53B45A3CA8FB79
931 GB \\.\PhysicalDrive1 Windows 98 MBR code detected
SHA1: 48F01D7E76A0F3C038D08611E3FDC0EE4EF9FD3E
==============
C: is the SSD that has the problem.
Senior Member
Could you attach a picture of your Disk Management picture on your next post. Use the Snipping tool and attach using the paperclip on the advanced reply?
I am not familiar with the utility you used to supply the info, so I cannot comment on that.
Did you modify the Windows 8 partitions prior to or during the move to the SSD?
Administrator
Check the SSD has all it's firmware updates ect. Same with the motherboard update to the latest bios.
Junior Member
Thread Starter Disk Management snapshot attached.Originally Posted by Saltgrass
No, the X: drive on DISK 2 was the original drive that was booted. System is a Dell, and D: is Dell's recovery, useless as it really is for Vista, but I don't need the space so I've left it. X: went from Vista (as shipped) to W7 and now W8. The SSD was cloned almost 2 years ago when it was W7.
I believe W8's CHKDSK was changed to work on UEFI BIOS's and since it is different, it might be part of the problem, but on a REFRESH of W8 it works fine?
Junior Member
Thread Starter Yeah, SSD has the lastest 2.4 firmware, first thing I checked. Computer is a Dell XPS 435T, almost 4 years old and the BIOS is the latest but hasn't been updated in a LONG time. Dell doesn't even provide W8 drivers for it. Luckily when I went to install W8 the network on the motherboard didn't work, but they had updated network drivers on the 8500 for W8 which is a follow-on XPS and that driver works fine.
No problems booting or running, just CHKDSK can't complete.
Senior Member
If I understand your post correctly, you ran chk dsk on the SSD?
This would have been a waste of time. SSDs do not have sectors, but chkdsk would see warn portions as "bad" sectors and report them as errors. The benefit of SSDs is that they automatically shut down any portions that show signs of error, so the chkdsk would be superfluous.
I understand, from experts, that it can actually be a bad idea to run chkdsk on an SSD.
For a general clean up, the Windows 8 defrag has a built in facility designed for SSDs. Have a look here:
10 hidden features in Windows 8 | ITworld
David
Junior Member
Thread Starter Thanks for your reply.
That reference is old and before W8 shipped. Some things might have changed?
For instance, the OPTIMIZER is different :
It does know about SSD's and DOES NOT support them. Trim is a function within the SSD.
I don't think there are any warnings about running CHKDSK on an SSD, but there are for DEFRAGMENTING one. CHKDSK repairs FILE SYSTEM errors, and they can occur on an SSD as well.
Junior Member
Thread Starter I have Wondershare LiveBoot 2012 - Wondershare Official which is a bootable CD and most functions are supported in W8 (Can Wondershare Liveboot 2012 support Win 8?| Wondershare support) and I booted it. Ran CHKDSK on C: from there, no problems found?
Is there a problem with CHKDSK on W8?
Senior Member
There were some changes to chkdsk in Windows 8, but I do not know if UEFI is related to the problem.
My system would run chkdsk all the time if I swapped the dual boot for the other OS. It did not find errors, but had some reason it wanted to run.
You might try turning off the Windows 8 Fast Startup in the Power Panel, Choose what the power buttons do, Shutdown settings, for testing.
Do you boot to anything other than the SSD?
If you want us to check, you might open an administrative command prompt and type the following:
bcdedit /enum all > %userprofile%\Desktop\bcdtext.txt
Then attach the text file from your desktop (hopefully) on your next post.
Edit: I also just noticed your Page File is on the second drive. I assume you moved it there? That might be related to the situation, but no evidence of it, so far.
Last edited by Saltgrass; 03-07-2013 at 10:31 AM.
Junior Member
Thread Starter Sorry, didn't see this post... never got notified it existed?
No need to make it a text file, just copied the output :
==========================
C:\WINDOWS\system32>bcdedit /enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {7b06eafc-c4c7-11de-b580-0023aee6d1ef}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {572bcd55-ffa7-11d9-aae0-0007e994107d}
device unknown
path \Windows\System32\boot\winload.exe
description Windows Recovery Environment
osdevice unknown
systemroot \Windows
nx OptIn
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {7b06eafa-c4c7-11de-b580-0023aee6d1ef}
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 8
locale en-US
inherit {bootloadersettings}
recoverysequence {7b06eafe-c4c7-11de-b580-0023aee6d1ef}
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {7b06eafc-c4c7-11de-b580-0023aee6d1ef}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
Windows Boot Loader
-------------------
identifier {7b06eafe-c4c7-11de-b580-0023aee6d1ef}
device ramdisk=[C:]\Recovery\7b06eafe-c4c7-11de-b580-0023aee6d1
ef\Winre.wim,{7b06eaff-c4c7-11de-b580-0023aee6d1ef}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
displaymessageoverride Recovery
osdevice ramdisk=[C:]\Recovery\7b06eafe-c4c7-11de-b580-0023aee6d1
ef\Winre.wim,{7b06eaff-c4c7-11de-b580-0023aee6d1ef}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
Resume from Hibernate
---------------------
identifier {5460d9d2-d391-11dc-9d9f-aba67a8797c5}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {7b06eafc-c4c7-11de-b580-0023aee6d1ef}
device partition=C:
path \WINDOWS\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {7b06eafe-c4c7-11de-b580-0023aee6d1ef}
recoveryenabled Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes
Windows Legacy OS Loader
------------------------
identifier {ntldr}
device unknown
path \ntldr
description Earlier Version of Windows
EMS Settings
------------
identifier {emssettings}
bootems No
Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200
RAM Defects
-----------
identifier {badmemory}
Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}
Device options
--------------
identifier {7b06eafb-c4c7-11de-b580-0023aee6d1ef}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\7b06eaf8-c4c7-11de-b580-0023aee6d1ef\boot.sdi
Device options
--------------
identifier {7b06eaff-c4c7-11de-b580-0023aee6d1ef}
description Windows Recovery
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\7b06eafe-c4c7-11de-b580-0023aee6d1ef\boot.sdi
C:\WINDOWS\system32>
=======================
I don't see anything unusual in the above?
Yes, PAGEFILE moved. I've got 8GB's of RAM, never swap, so why waste space on an SSD?
Other W8 system is also on an SSD with a PAGEFILE on the mechanical drive. CHKDSK works fine there?
I've already done the disable of fast start, first thing I did?
I also looked at SECTOR 0 on the first disk. Only ONE partition defined, I was wondering if 3 were from the clone of the original drive, but only 1. Nothing in sector 0 seems odd, but I can only locate up to W7 the contents of Sector 0, not Win8, but I wouldn't have suspected a change to it anyway.
I'm on the old BIOS anyway, as is the other computer, both Dell's...
Posting Permissions
Windows 8 Forums is an open discussion forum, and member of the Microsoft Partner Network. This website is not owned or operated by Microsoft Corporation. All trademarks are copyright their respective owners.
LinkBack URL
About LinkBacks
