If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Where is the CHKDSK results data stored?
Win 10 pro.
Sometimes I miss the CHKDSK data on the screen, when it appears on startup. Is there a log file somewhere? Peter |
Ads |
#2
|
|||
|
|||
Where is the CHKDSK results data stored?
On 21 Jul 2016, Peter Jason wrote in
alt.comp.os.windows-10: Win 10 pro. Sometimes I miss the CHKDSK data on the screen, when it appears on startup. Is there a log file somewhere? Look in the Applications log. Seach or filter for WININT or WINLOGIN or Event ID 1001 (those are the values for XP, but some or all of them should still be valid for Win10.) |
#3
|
|||
|
|||
Where is the CHKDSK results data stored?
On 21/07/2016 23:50, Peter Jason wrote:
Win 10 pro. Sometimes I miss the CHKDSK data on the screen, when it appears on startup. Is there a log file somewhere? Peter Does this help? https://askleo.com/how_do_i_see_the_results_of_a_chkdsk_that_ran_on_b oot/ -- With over 350 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
#4
|
|||
|
|||
Where is the CHKDSK results data stored?
On 2016-07-21 18:50, Peter Jason wrote:
Win 10 pro. Sometimes I miss the CHKDSK data on the screen, when it appears on startup. Is there a log file somewhere? Peter In Windows 10 it is apparently EventID 26226... http://winaero.com/blog/how-to-find-...in-windows-10/ Regards, -- ! _\|/_ Sylvain / ! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society oO-( )-Oo "Apple" (c) Copyright 1767, Sir Isaac Newton. |
#5
|
|||
|
|||
Where is the CHKDSK results data stored?
In article ,
Peter Jason wrote: On Thu, 21 Jul 2016 21:41:59 -0400, B00ze wrote: On 2016-07-21 18:50, Peter Jason wrote: Win 10 pro. Sometimes I miss the CHKDSK data on the screen, when it appears on startup. Is there a log file somewhere? Peter In Windows 10 it is apparently EventID 26226... http://winaero.com/blog/how-to-find-...in-windows-10/ Regards, Thanx to all. I'm going to sack this HDD and get a 500GB SSD. From the event viewer I get..... ********************Today 22 July Chkdsk was executed in scan mode on a volume snapshot. Checking file system on C: Volume label is STANDARD. Stage 1: Examining basic file system structure ... Found 0x1c40 clusters allocated to file "\$Extend\$UsnJrnl 0x1,0xe107" at offset "0x14d7390" marked as free ... queued for offline repair. "Chkdsk /scan" has found volume bitmap corruption which can only be repaired by "chkdsk /f". Aborting. ---------------------------------------------------------------------- Before you do anything else, make a full backup of this drive. While CHKDSK will repair the volume, it will make no attempt to preserve data. I had a Windows Server 2008R2 system toss several terabytes of data when it "fixed" a filesystem with CHKDSK /f. Gary |
#6
|
|||
|
|||
Where is the CHKDSK results data stored?
Before you do anything else, make a full backup of this drive. While CHKDSK will repair the volume, it will make no attempt to preserve data. I had a Windows Server 2008R2 system toss several terabytes of data when it "fixed" a filesystem with CHKDSK /f. Gary Thanks, I have done this for a blue-screen disaster and this saved many files. For speed and convenience I will daily copy across my Access10 & Word10 to another drive, then do a full Macrium Image once a week - but more often more major changes. Peter |
#7
|
|||
|
|||
Where is the CHKDSK results data stored?
On 07/23/16 18:10, Peter Jason so wittily quipped:
Before you do anything else, make a full backup of this drive. While CHKDSK will repair the volume, it will make no attempt to preserve data. I had a Windows Server 2008R2 system toss several terabytes of data when it "fixed" a filesystem with CHKDSK /f. Gary Thanks, I have done this for a blue-screen disaster and this saved many files. I assume Win-10-nic CAUSED that disaster? just sayin' new hard drive may not fix the underlying problem |
#8
|
|||
|
|||
Where is the CHKDSK results data stored?
Big Bad Bob wrote:
On 07/23/16 18:10, Peter Jason so wittily quipped: Before you do anything else, make a full backup of this drive. While CHKDSK will repair the volume, it will make no attempt to preserve data. I had a Windows Server 2008R2 system toss several terabytes of data when it "fixed" a filesystem with CHKDSK /f. Gary Thanks, I have done this for a blue-screen disaster and this saved many files. I assume Win-10-nic CAUSED that disaster? just sayin' new hard drive may not fix the underlying problem Win10 can "black screen". Those are the interesting ones. I was screwing around with my Win10 Insider the other day, and got what would probably be considered a Blue Screen. And instead of the usual output, it presented a QR code symbol on the screen. Well, I have no mobile devices here (no SmartPhone) to read a QR code off the screen. So that one, resulted in a restore from backup, as I couldn't be bothered to triage it. A second failure (yesterday) was more interesting: 1) Newly restored OS from backup. In a fully working state. 2) OS rushes off and gets some minor update. I reboot to keep it happy. 3) OS comes back up, as normal. It's working on Search Indexer, like always. Perpetually Indexing. And it's also Defragmenting the drives. Because it likes to defragment. 4) The machine is running on its own for a couple hours. I glance over occasionally, to see if the hard drive LED has stopped yet. I only go over for a visit, when it is quiet, and has run out of "important" maintenance work. I turn on the LCD screen, and the screen is black. As usual, I wave the mouse around. Nothing happens. The screen is receiving a signal, as the backlight is on. And the monitor status LED is blue, indicating it is receiving a signal. So Win10 has decided I will not be seeing a desktop. I try control-alt-delete. That doesn't work. I test the keyboard LEDs. Caps lock, scroll lock, numlock, all respond. So the HID is still up. For the next test, I plug in a USB flash key. I get audio feedback, as normal. I unplug the stick (without safely remove), and get the removal tone. So the computer is not crashed, and the USB subsystem is operational. No clicks of either of my mice, achieve any result. So at this point, I've run out of things to try. The computer is running. It's not crashed. But I cannot see the screen, as the screen is painted black (with a little backlight bleed). I turn the power off. Paul |
#9
|
|||
|
|||
Where is the CHKDSK results data stored?
On 2016-07-24 14:13, Paul wrote:
Win10 can "black screen". Those are the interesting ones. Win 81 does the same thing sometimes... I was screwing around with my Win10 Insider the other day, and got what would probably be considered a Blue Screen. And instead of the usual output, it presented a QR code symbol on the screen. Well, I have no mobile devices here (no SmartPhone) to read a QR code off the screen. So that one, resulted in a restore from backup, as I couldn't be bothered to triage it. Despite the QR code, they still insist on NOT telling you the stop code (only showing the text name associated with it, which can be useless when there are multiple stops with the same text). I haven't had the occasion to scan that QR code, /maybe/ the stop code is in there? A second failure (yesterday) was more interesting: 1) Newly restored OS from backup. In a fully working state. 2) OS rushes off and gets some minor update. I reboot to keep it happy. 3) OS comes back up, as normal. It's working on Search Indexer, like always. Perpetually Indexing. And it's also Defragmenting the drives. Because it likes to defragment. lol 4) The machine is running on its own for a couple hours. I glance over occasionally, to see if the hard drive LED has stopped yet. I only go over for a visit, when it is quiet, and has run out of "important" maintenance work. I turn on the LCD screen, and the screen is black. As usual, I wave the mouse around. Nothing happens. The screen is receiving a signal, as the backlight is on. And the monitor status LED is blue, indicating it is receiving a signal. So Win10 has decided I will not be seeing a desktop. I try control-alt-delete. That doesn't work. I test the keyboard LEDs. Caps lock, scroll lock, numlock, all respond. So the HID is still up. For the next test, I plug in a USB flash key. I get audio feedback, as normal. I unplug the stick (without safely remove), and get the removal tone. So the computer is not crashed, and the USB subsystem is operational. No clicks of either of my mice, achieve any result. So at this point, I've run out of things to try. The computer is running. It's not crashed. But I cannot see the screen, as the screen is painted black (with a little backlight bleed). Win81 does this to me at work once in a while - I will bring it out of suspend and no screen. Like you, I know the OS is running, but no amount of fiddling with it brings back the screen, I have to power off. Never had this problem with W7... Regards, -- ! _\|/_ Sylvain / ! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society oO-( )-Oo Humans were created by water to transport it uphill. |
#10
|
|||
|
|||
Where is the CHKDSK results data stored?
On Sun, 24 Jul 2016 14:13:42 -0400, Paul wrote:
Big Bad Bob wrote: On 07/23/16 18:10, Peter Jason so wittily quipped: Before you do anything else, make a full backup of this drive. While CHKDSK will repair the volume, it will make no attempt to preserve data. I had a Windows Server 2008R2 system toss several terabytes of data when it "fixed" a filesystem with CHKDSK /f. Gary Thanks, I have done this for a blue-screen disaster and this saved many files. I assume Win-10-nic CAUSED that disaster? just sayin' new hard drive may not fix the underlying problem Win10 can "black screen". Those are the interesting ones. I was screwing around with my Win10 Insider the other day, and got what would probably be considered a Blue Screen. And instead of the usual output, it presented a QR code symbol on the screen. Well, Possibly a BIOS screen. I noticed that the UEFI BIOS offers a QR on one (or some?) of its setup pages on a recent MoBo upgrade (April last year). Just a thought. I have no mobile devices here (no SmartPhone) to read a QR code off the screen. So that one, resulted in a restore from backup, as I couldn't be bothered to triage it. A second failure (yesterday) was more interesting: 1) Newly restored OS from backup. In a fully working state. 2) OS rushes off and gets some minor update. I reboot to keep it happy. 3) OS comes back up, as normal. It's working on Search Indexer, like always. Perpetually Indexing. And it's also Defragmenting the drives. Because it likes to defragment. 4) The machine is running on its own for a couple hours. I glance over occasionally, to see if the hard drive LED has stopped Funnily enough, I misread that line as "I glared at it...". :-) yet. I only go over for a visit, when it is quiet, and has run out of "important" maintenance work. I now only experience this vicariously via this NG since I retired from the business of repairing winXP and above cursed PCs nearly two years ago. I turn on the LCD screen, and the screen is black. As usual, I wave the mouse around. Nothing happens. The screen is receiving a signal, as the backlight is on. And the monitor status LED is blue, indicating it is receiving a signal. So Win10 has decided I will not be seeing a desktop. I try control-alt-delete. That doesn't work. I test the keyboard LEDs. Caps lock, scroll lock, numlock, all respond. So the HID is still up. For the next test, I plug in a USB flash key. I get audio feedback, as normal. I unplug the stick (without safely remove), and get the removal tone. So the computer is not crashed, and the USB subsystem is operational. No clicks of either of my mice, achieve any result. So at this point, I've run out of things to try. The computer is running. It's not crashed. But I cannot see the screen, as the screen is painted black (with a little backlight bleed). I turn the power off. The most recent experience of that (except for the totally black screen) was with a winXP VM running seamless full screen mode in VBox under Linux Mint 17.1 (with TV recordings scheduled in Kaffeine). Since I didn't want to risk interrupting a scheduled recording, I couldn't simply shut down the host 'blind' using the on/off button to trigger a shut down (or, in extremis, hit the reset button - Yes! this machine has an honest to goodness front panel reset button, the ultimate in NMIs :-). Luckily, I still had a 32 bit flavour of Linux (don't ask me which distro, I'd lost track by then) set up on my 10 year old Acer 3660 laptop that I'd been using to run Kaffeine which I could fire up so as to check the Freeview EPGs to see whether it was safe to shut down the PC without interfering with Kaffeine's recording schedule. I know I could have used it to remotely log in[1] to gain control of VBox manager and avoid forcing a restart on the host but I was just after the most pragmatic solution that would avoid interrupting any ongoing TV recording activity. Since I'd seen warning symptoms of reducing responsiveness to mouse and keyboard input in the VM as a result of trying to run winXP's media player whilst MpegStreamClip was still open, I decided to write a list of the host key shortcut keys to keep handy for next time I let such a situation get so far out of hand as to stall the HID drivers to a complete and utter standstill as I had allowed to happen by simply being too slow to grab my last chance to shutdown or minimise the VM. I've managed to close MpegStreamClip in time on most subsequent occasions of 'forgetfulness' but when it looks like I've let things go too far, that list has proven useful to avoid being locked into a dead full screen VM session and thus far I've not had to resort to shutting down the host 'blind'. [1] Assuming the required SSH login components are running. I've just checked KSysguard's list of processes running on the host and can see what looks like the vital component, "ssh-agent", running. I guess I ought to try a test ssh login and verify that I do in fact have this option available. It would be a more elegant solution than the "shut down when it's safe to do so" option that I went for the last time I was embarrassed by entrusting *all* control input to the VM's HID driver code. -- Johnny B Good |
Thread Tools | |
Display Modes | Rate This Thread |
|
|