So, I checked my free hard drive space, turns out I only had like 250 MB left on my 32GB SSD. Ha! So, I deleted some excess stuff on there and now I have about 3 gigs free.
That is a big problem. Even 3 GB free (~10.3% in your case) is not enough for Windows to function in an optimal state.
In 2009, I tested Windows (either Vista SP2 or Windows 7 - don't recall which ATM) for about 30 days running with extreme low space (just a few GB free space - similar to the amount that you currently have free) and watched as Windows applied space conservation measures such as deletion, movement, compression of files deemed non OS-critical & much more. There is a Microsoft KB on this; if I locate it, I'll post a link to it.
More free space is needed - please look through these KBs; run cleanmgr
Strategies for freeing disk space
Delete files using Disk Cleanup
Is Windows System Restore running? Are there restore points?
Run this batch script, please. Extract batch script from the zip; save to Documents. RIGHT-click on the batch script, "Run as Administrator"
A CMD screen will appear with status; upon completion, a Notepad will open. Attach the Notepad to your next post.
The restore points may already be gone -
Microsoft kb301224 said:
The deletion of restore points may be caused by any one of the following by-design conditions:
• You run out of disk space on the system drive or on any one of the available non-system drives, and System Restore stops responding and stops monitoring your system.
This behavior causes the system to delete all restore points in an attempt to free up disk space. However, you have probably already received a warning about running low in disk space prior to this point. In this case, when sufficient disk space is freed, System Restore starts to monitor the system again. At this point, it creates an automatic System Checkpoint.
--> System Restore "restore points" are missing or deleted
Where did you get the 3 GB free number from? Check Disk management -
START | type diskmgmt.msc
- What is the total size of the SSD?
- What is the current free space?
A 32 GB SSD is seen by Windows as ~29 GB -
Microsoft Support said:
The advertised local disk size is shown using the decimal system, while Windows displays the disk size using the binary system. As a result, 1 GB (in decimal) appears as about 0.93 GB (in binary). The storage capacity is the same, it's just shown differently depending on the how you measure a GB (decimal or binary).
- Binary is used by the hard drive manufacturers; 1 GB = 1024 MB
- Decimal is used by Windows; 1 GB = 1000 MB
Please run the WMI EXE I mentioned in POST #33
Download & save to Desktop. RIGHT-click on EXE, "Run as Administrator" -
..Now, I have 7 drivers that are not signed by Microsoft. I turned on the first 4 in Driver Verifier in safe mode and then booted into normal mode. The best that I'm getting there is a hard lock upon signing in, or loading up Chrome. I do get a couple blue screens but only right after entering in my password and hitting enter. Unfortunately, for some reason, it's not creating any dump files in the Minidumps folder! Is it because it's happening before Windows is fully loaded up?
7 unsigned drivers? What are they?
If you have gotten to logon screen, Windows has in fact loaded and should be able to produce a dump file. At this point, two reasons come to mind for "no dump" condition -
- Catastrophic hardware failure brings the system down so fast there is no time for a dump (tantamount to pulling the plug)
- Conditions are not right - Page File, WERCON, etc...
#2 - https://www.sysnative.com/forums/bs...-information/325-bsods-but-no-dump-files.html
When I go back to Safe Mode and turn on the last 3 drivers in Driver Verifier, I get a hard lock upon entering my password in normal mode Windows boot up. Again, no dump files of course.
A long shot, but let's make sure the user account is not corrupted.
Get into Windows - normal or safe mode & activate the Hidden Administrator user account -
Try and log on to it & see if same result - freezing.
I'm doing my best here to get you guys a dump file so you can see which driver is causing this mess. Should I just delete every single driver that wasn't signed by Windows and boot into normal mode to see if I still get hard locks/blue screens? Then, I can slowly reintroduce all my necessary drivers and see which one is the culprit?
NO -- Please do not delete any drivers!! We need to know which drivers are involved.
Regards. . .