42 posts in this topic

so how about a screenshot now showing its current state, then will have as reference when you say it changes.

As you wish :)

This is working (showing the label and hibernate works):

dsfz.png

The "photoshop" version of what happens is usually this (next time it happens Ill show you the official screenshot:

choppedu.png

Share this post


Link to post
Share on other sites

Here is the picture you asked of when it happens:

92988022.png

Share this post


Link to post
Share on other sites

Found this on hibernation issues- Seems as if in some systems it gets set 75 which is not enough for some systems causing random hibernation issues.

Change the registry setting HKLM\System\CurrentControlSet\Control\Power\HiberFileSizePercent to 100.

Rebooted. Now hiberfile size is 100% of RAM size. Hibernation now works.

Share this post


Link to post
Share on other sites

Here is the picture you asked of when it happens:

..

You don't happen to have any 3rd party boot managers or an antivirus that protects the boot partition, do you?

Also, what type of Windows install is this? OEM, Retail or Volume License?

Share this post


Link to post
Share on other sites

Found this on hibernation issues- Seems as if in some systems it gets set 75 which is not enough for some systems causing random hibernation issues.

Change the registry setting HKLM\System\CurrentControlSet\Control\Power\HiberFileSizePercent to 100.

Rebooted. Now hiberfile size is 100% of RAM size. Hibernation now works.

Done. Ill fix it like always and see if it does any difference...

You don't happen to have any 3rd party boot managers or an antivirus that protects the boot partition, do you?

Also, what type of Windows install is this? OEM, Retail or Volume License?

Nope.

This is VL.

Share this post


Link to post
Share on other sites

Nope.

This is VL.

Just a longshot, but can I assume you're activated normally and don't have a 3rd party bootloader? Some 3rd party bootloaders tend to overwrite partition tables.

Share this post


Link to post
Share on other sites

Just a longshot, but can I assume you're activated normally and don't have a 3rd party bootloader? Some 3rd party bootloaders tend to overwrite partition tables.

Yup :) This is normal standard activation.

Share this post


Link to post
Share on other sites

Who says it get removed? Looks to me like the disk just didn't get read correctly - since your file type is gone. If just label was removed you would still see that its a NTFS file system still.

Go to a command line and use disk part to see if you can view it that way. Elevated prompt!

C:\Windows\system32>diskpart

Microsoft DiskPart version 6.1.7601

Copyright

Share this post


Link to post
Share on other sites

Who says it get removed? Looks to me like the disk just didn't get read correctly - since your file type is gone. If just label was removed you would still see that its a NTFS file system still.

Go to a command line and use disk part to see if you can view it that way. Elevated prompt!

C:\Windows\system32>diskpart

Microsoft DiskPart version 6.1.7601

Copyright

Share this post


Link to post
Share on other sites

Here it is again broke:

Microsoft DiskPart version 6.1.7601

Copyright © 1999-2008 Microsoft Corporation.

On computer: SUM

DISKPART> sel disk 1

Disk 1 is now the selected disk.

DISKPART> list vol

Volume ### Ltr Label Fs Type Size Status Info

---------- --- ----------- ----- ---------- ------- --------- --------

Volume 0 E DVD-ROM 0 B No Media

Volume 1 F DVD-ROM 0 B No Media

Volume 2 Partition 100 MB Healthy Offline

Volume 3 C NTFS Partition 465 GB Healthy Boot

Volume 4 D NTFS Partition 8 TB Healthy

Volume 5 G Removable 0 B No Media

DISKPART>

Share this post


Link to post
Share on other sites

Shows offline for whatever reason - so yeah its not going to show you label or type. So there is NOTHING in your event log on why the volume was set offline?? I find that almost impossible to believe.

what do you get if you just set it back online

sel vol 2

online volume

Share this post


Link to post
Share on other sites

maybe the section of the hdd is dying?

Share this post


Link to post
Share on other sites

Shows offline for whatever reason - so yeah its not going to show you label or type. So there is NOTHING in your event log on why the volume was set offline?? I find that almost impossible to believe.

What and where do I look in my Event Log? Anything specific?

Share this post


Link to post
Share on other sites

What and where do I look in my Event Log? Anything specific?

generally what I do is let it load up-- then sort by type-- look for anything red -

When you sort by type depending on the sort they will either be at the top or bottom of the list.

I would start there... usually those will tell you if there are serious issues.

Share this post


Link to post
Share on other sites

Found something! :) Finally. I just don't know how the **** this arrived like this. And how the **** do I remove it?

Encrypted volume check: Volume information on \\?\Volume{b692cea4-1ccd-11e2-80c8-806e6f6e6963} cannot be read.

Source: BitLocker-Driver

User: SYSTEM

The thing is I have never used Bitshit in my life. How the **** do I nuke this piece of ****?

Share this post


Link to post
Share on other sites

And now even stranger: I used to be able to assign it a letter (therefore recovering the label), deassign it the letter and then hibernate. Now I do the same process but when I hibernate it, the display goes black but the PC keeps running and it never hibernates.

Share this post


Link to post
Share on other sites

I don't think that error is related to drive being encrypted or using bitlocker, just think that is a generic type error that that volume can not be read in general. While your bitlocker driver checked to see if it was encrypted.

Seems you have issues with that disk if you ask me... You ran checkdisk against that specific partition?

Does that guid for that volume match up with your system reserved partition? A quick way to list all volumes by guid is mountvol

example


C:\>mountvol

Creates, deletes, or lists a volume mount point.


MOUNTVOL [drive:]path VolumeName

MOUNTVOL [drive:]path /D

MOUNTVOL [drive:]path /L

MOUNTVOL [drive:]path /P

MOUNTVOL /R

MOUNTVOL /N

MOUNTVOL /E


	path		Specifies the existing NTFS directory where the mount

				point will reside.

	VolumeName  Specifies the volume name that is the target of the mount

				point.

	/D		  Removes the volume mount point from the specified directory.

	/L		  Lists the mounted volume name for the specified directory.

	/P		  Removes the volume mount point from the specified directory,

				dismounts the volume, and makes the volume not mountable.

				You can make the volume mountable again by creating a volume

				mount point.

	/R		  Removes volume mount point directories and registry settings

				for volumes that are no longer in the system.

	/N		  Disables automatic mounting of new volumes.

	/E		  Re-enables automatic mounting of new volumes.


Possible values for VolumeName along with current mount points are:


	\\?\Volume{2964090a-db60-11e0-ba2f-806e6f6e6963}\

		*** NO MOUNT POINTS ***


	\\?\Volume{594c943c-dbb1-11e0-a78d-180373b10dd3}\

		D:\


	\\?\Volume{2964090b-db60-11e0-ba2f-806e6f6e6963}\

		C:\


	\\?\Volume{2964091f-db60-11e0-ba2f-806e6f6e6963}\

		*** NO MOUNT POINTS ***


	\\?\Volume{29640920-db60-11e0-ba2f-806e6f6e6963}\

		*** NO MOUNT POINTS ***


	\\?\Volume{29640921-db60-11e0-ba2f-806e6f6e6963}\

		*** NO MOUNT POINTS ***


	\\?\Volume{29640922-db60-11e0-ba2f-806e6f6e6963}\

		*** NO MOUNT POINTS ***


	\\?\Volume{6cc911ca-db53-11e0-80fa-806e6f6e6963}\

		E:\


	\\?\Volume{6cc91246-db53-11e0-80fa-180373b10dd3}\

		I:\

Now that first one is my reserved volume - and I can real simple verify that with just opening it

post-14624-0-79922100-1356360838.png

If while system reserved partition is listed, not a drive letter can you open it with that volume guid listed? If not it might be some other mount point that is no longer even connected to your drive and could be a red herring in your quest for the cause of the problem.

I would run a chkdsk against that system reserved partition. This thread has been going on for a while - you did run a FULL drive test with the tools from your drive maker??

I don't believe you can run a check disk with say

C:\>chkdsk \\?\Volume{2964090a-db60-11e0-ba2f-806e6f6e6963}\

The specified volume name does not have a mount point or drive letter.

So give it a drive letter and then run chkdsk against that drive letter.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.