Author Topic: System Restore points silently disappear (Read 66975 times)

Shane · « **Reply #25 on:** August 11, 2015, 11:33:11 am »

It sounds like the chkdsk froze up, which happens if it hits a bad sector OR if there is bad memory. Chkdsk uses a lot of memory. I have had chkdsk lock up on me before from it.

So if chkdsk did at least make it to the end then if it found any bad sectors it would have marked them, so you should be able to run chkdsk in read only mode and we can make sure it still says 0 KB in bad sectors.

So just run
chkdsk C:

Also if you havent yet, running a memory test would be a good idea, and we should make sure you have the latest chipset drivers installed as well

Shane

Steevo · « **Reply #26 on:** August 11, 2015, 11:56:43 am »

It did make it to the end and said it was going to reboot, that's where the hang was.

It mentioned fixing things. Too bad the logs didn't get written.

I'll try it again in read only.

I'll have to make a bootable memtest86 disk, unless you have another suggestion.

Shane · « **Reply #27 on:** August 11, 2015, 12:12:24 pm »

memtest should be good, I actually saved the Microsoft memory tester, it did a good job, not sure why they removed it off their site.

Shane

Steevo · « **Reply #28 on:** August 11, 2015, 01:34:52 pm »

I ran chkdsk on my system drive in read only, and it passed with no errors.
Is your preferred memory test from ms uploaded somewhere?
Should I use that? I'd like to try it.

Shane · « **Reply #29 on:** August 11, 2015, 01:48:52 pm »

Did the chkdsk show 0 KB in bad sectors at the end of the scan when it was done?

https://technet.microsoft.com/en-us/magazine/2008.09.utilityspotlight.aspx
Which points to
http://www.softpedia.com/progDownload/Microsoft-Windows-Memory-Diagnostic-Download-3648.html

Shane

Steevo · « **Reply #30 on:** August 11, 2015, 01:51:33 pm »

Yes. Seems to be fine.

Quote

Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:

CHKDSK is verifying files (stage 1 of 3)...
568576 file records processed. File verification completed.
1361 large file records processed. 0 bad file records processed. 2 EA records processed. 63 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
667324 index entries processed. Index verification completed.

CHKDSK is verifying security descriptors (stage 3 of 3)...
568576 file SDs/SIDs processed. Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
Security descriptor verification completed.
49375 data files processed. CHKDSK is verifying Usn Journal...
33756200 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
370548896 KB in 431464 files.
219536 KB in 49376 indexes.
700871 KB in use by the system.
65536 KB occupied by the log file.
604087268 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
151021817 allocation units available on disk.

Shane · « **Reply #31 on:** August 11, 2015, 01:55:54 pm »

Thats odd, its not even listing the 0kb in bad sectors.

It should like this

Code: [Select]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Shane>chkdsk c:
The type of the file system is NTFS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
  711680 file records processed.
File verification completed.
  588 large file records processed.
  0 bad file records processed.
  2 EA records processed.
  44 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
  782782 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
  711680 file SDs/SIDs processed.
Security descriptor verification completed.
  35552 data files processed.
CHKDSK is verifying Usn Journal...
  34184384 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

 233293823 KB total disk space.
 138088888 KB in 222446 files.
     85016 KB in 35553 indexes.
         0 KB in bad sectors.
    821547 KB in use by the system.
     65536 KB occupied by the log file.
  94298372 KB available on disk.

      4096 bytes in each allocation unit.
  58323455 total allocation units on disk.
  23574593 allocation units available on disk.

C:\Users\Shane>

Shane

Steevo · « **Reply #32 on:** August 11, 2015, 08:05:48 pm »

Well, I pasted that from the windows application event log.

Your event log entry for a read only chkdsk differs from that?

Here's the event log from the chkdsk I ran on one of my external usb drives.

Chkdsk was executed in read/write mode.

Checking file system on G:
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is 300 GB.

CHKDSK is verifying files (stage 1 of 5)...
179968 file records processed. File verification completed.
13 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
215404 index entries processed. Index verification completed.

CHKDSK is verifying security descriptors (stage 3 of 5)...
179968 file SDs/SIDs processed. Security descriptor verification completed.
17719 data files processed. CHKDSK is verifying Usn Journal...
708696 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
179952 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
50078104 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

293033600 KB total disk space.
92410196 KB in 162016 files.
55072 KB in 17720 indexes.
255916 KB in use by the system.
65536 KB occupied by the log file.
200312416 KB available on disk.

4096 bytes in each allocation unit.
73258400 total allocation units on disk.
50078104 allocation units available on disk.

Steevo · « **Reply #33 on:** August 11, 2015, 08:28:13 pm »

I have a new automatic restore point created by windows update tonight. Cool.

Boggin · « **Reply #34 on:** August 12, 2015, 02:08:30 am »

Are you using a SSD or a HDD ?

Steevo · « **Reply #35 on:** August 12, 2015, 06:27:03 am »

A 1 tb ordinary hdd.

Shane · « **Reply #36 on:** August 12, 2015, 06:39:29 am »

I just opened a cmd.exe window as administrator and put in
chkdsk c:

when it was done I right click on the cmd.exe window and click select all, then when I right click again it will unselect, that is because it just copied all the text to the clip board and you can paste it

Shane

Steevo · « **Reply #37 on:** August 12, 2015, 06:47:00 am »

I didn't do it that way.
I went to my computer, clicked the disk and rt-clicked properties, and told it to check and repair the disk.
It asked to schedule on restart, I told it to and when I restarted it ran.

The USB 300 gb, I did that one while the system was running, no restart. No system on that one.

Julian · « **Reply #38 on:** August 12, 2015, 06:40:04 pm »

Quote from: Steevo on August 12, 2015, 06:47:00 am

I didn't do it that way.
I went to my computer, clicked the disk and rt-clicked properties, and told it to check and repair the disk.
It asked to schedule on restart, I told it to and when I restarted it ran.

The USB 300 gb, I did that one while the system was running, no restart. No system on that one.

that will run chkdsk.exe via explorer.exe instead of via chkdsk.exe and it won't show kb in bad sector that way.

plus it's harder to kill because it can cause explorer to crash in middle of it lol.

Steevo · « **Reply #39 on:** August 14, 2015, 07:11:47 am »

I still have an automatically created restore point from 3 days ago!
I am going to create a manual one. And watch it.

Steevo · « **Reply #40 on:** August 14, 2015, 09:14:16 am »

I found out why the Microsoft memory test was discontinued, it only tests up to 4 GB.
It gave a message that this was a limitation of that program, not the computer. So they knew.

I ran memtest86 for a while, it progressed through test 5 and part of 6 before I stopped it. No errors. I have 24 GB of ram.
The test was not exhaustive, but I will let it run overnight tonight.

So I have no memory problems, or no big ones so far.
No disk problems, I think.

Julian · « **Reply #41 on:** August 16, 2015, 09:33:51 am »

Yep Max that windows handles with x86 is 4gb lol so that sounds about right

Steevo · « **Reply #42 on:** August 16, 2015, 09:47:03 am »

Quote from: Julian on August 16, 2015, 09:33:51 am

Yep Max that windows handles with x86 is 4gb lol so that sounds about right

Well, that's not exactly true. 32 bit windows, yes.
64 bit windows, not at all true. 64 bit windows is not at all new.

I have windows 7 64 bit and 24 gb of ram.

Back to the topic:

As of this morning, I have no restore points.
All gone.

So I just don't know.

Julian · « **Reply #43 on:** August 16, 2015, 04:47:34 pm »

X86 is 32 bit so x86 programs are 32 bit Windows mem test is a 32 bit application

Steevo · « **Reply #44 on:** August 16, 2015, 05:19:55 pm »

Which is why I used memtest86, which does not have that limitation.

It works pretty well, I think.

Julian · « **Reply #45 on:** August 16, 2015, 05:21:51 pm »

can you open up cmd and type in

Code: [Select]

vssadmin list shadowstorage and post what it tells you

Julian · « **Reply #46 on:** August 16, 2015, 05:23:44 pm »

Quote from: Julian on August 16, 2015, 05:21:51 pm

can you open up cmd and type in
Code: [Select]
vssadmin list shadowstorage and post what it tells you

also use this command as well and post the results

Code: [Select]

vssadmin list writers

Steevo · « **Reply #47 on:** August 16, 2015, 05:39:40 pm »

Here is the response.
I've never heard of that. This is deep down.

Code: [Select]

C:\Windows\system32>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Shadow Copy Storage association
   For volume: (F:)\\?\Volume{512b7507-ef71-11e3-b3eb-0019b91ef004}\
   Shadow Copy Storage volume: (F:)\\?\Volume{512b7507-ef71-11e3-b3eb-0019b91ef0
04}\
   Used Shadow Copy Storage space: 2.141 GB (0%)
   Allocated Shadow Copy Storage space: 4.975 GB (0%)
   Maximum Shadow Copy Storage space: 111.781 GB (12%)

Shadow Copy Storage association
   For volume: (G:)\\?\Volume{adbb1ba6-bff5-11e3-834c-0019b91ef004}\
   Shadow Copy Storage volume: (G:)\\?\Volume{adbb1ba6-bff5-11e3-834c-0019b91ef0
04}\
   Used Shadow Copy Storage space: 502.391 MB (0%)
   Allocated Shadow Copy Storage space: 1.107 GB (0%)
   Maximum Shadow Copy Storage space: 13.973 GB (5%)

Shadow Copy Storage association
   For volume: (C:)\\?\Volume{f63cfb61-baea-11e3-b701-806e6f6e6963}\
   Shadow Copy Storage volume: (C:)\\?\Volume{f63cfb61-baea-11e3-b701-806e6f6e69
63}\
   Used Shadow Copy Storage space: 768.891 MB (0%)
   Allocated Shadow Copy Storage space: 3.06 GB (0%)
   Maximum Shadow Copy Storage space: 93.141 GB (10%)


C:\Windows\system32>

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {b2c85219-a35e-4ec7-b24e-955f9d6181df}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {be633e73-ac1f-44bb-8d3b-be7ad506c141}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {02089769-8662-4ca8-93a4-d208aa4f79dd}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {74299e55-ee57-48dd-923d-b5a71aa2c88e}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {306478e0-266c-461c-9541-b6fd1e5029fa}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {1baa4918-b835-4348-b1a1-e58cc487c07d}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {92e589ee-5362-47da-a564-f801494593ba}
   State: [5] Waiting for completion
   Last error: No error


C:\Windows\system32>

Julian · « **Reply #48 on:** August 16, 2015, 06:13:43 pm »

hmmm can you show me

Code: [Select]

vssadmin list shadows

Julian · « **Reply #49 on:** August 16, 2015, 06:24:30 pm »

Code: [Select]

[quote author=Steevo link=topic=3457.msg25031#msg25031 date=1439771980]

Shadow Copy Storage association
   For volume: (C:)\\?\Volume{f63cfb61-baea-11e3-b701-806e6f6e6963}\
   Shadow Copy Storage volume: (C:)\\?\Volume{f63cfb61-baea-11e3-b701-806e6f6e69
63}\
   Used Shadow Copy Storage space: 768.891 MB (0%)
   Allocated Shadow Copy Storage space: 3.06 GB (0%)
   Maximum Shadow Copy Storage space: 93.141 GB (10%)

[/quote]

the allocated shadow copy has me curious hmmm looks like it's disabled...