Something is "devouring" my HD Space!

Something is "devouring" my HD Space!​

The Problem: Recently, I have noticed that almost immediately after boot up, my hard drive "space" starts to show "depletion" slowly running down and down from about 110.11 GB of space available; all the way down to around 90 - depending upon how long the computer is up and running. The lowest it has ever got to was 72 GB.

How I discovered this problem: I use a very small freeware tool called "Disk-Mem Panel" which places a small indicator on top of my screen which runs constantly, in order to view my Hard Drive space as well as memory usage. It starts up (at boot up) and runs while I'm working on the computer.

Things I have tried already: I have run my AVG antivirus, CCleaner (using both the cleaner and Issues section) Spyware Doctor, Adaware Professional and even went to the BitDefender Online virus scan and have found nothing.

The oddest thing about this is: Immediately after I reboot; there it is back at 110.11 GB but then the process starts up all over again with the space dwindling away.

Anyone have any ideas?

 

So we're dealing with upwards of 38 GB disk consumption...ouch.

Two things I can think of checking:

1. Pagefile settings - Is your pagefile system managed? Maybe the upper limit got unhooked somehow?!?!

2. Tracking file activity - recommend the excellent freeware, Filemon maybe this app will shed some light on what is robbing all your space!

 

There are a couple of nifty programs in this thread that will show disk usage graphically.

 

>> So we're dealing with upwards of 38 GB disk consumption...ouch. Two things I can think of checking: Pagefile settings and Tracking file activity <<

Thanks for the "rapid responses" Matt and Mada_Milty! I used an excellent freeware program called WinDirStat. I believe I found the "offending" file (using that handy WinDirStat):

C:\WINDOWS\system32\LogFiles\WMI\trace.log

As you can see, the file was in the WMI directory which; as many of you may know, is actually a "hidden" folder. It is quite obviously the "cause" of the problem because I kept refreshing it using WinDirStat and it grew each time I checked it (the file is currently 3.4 GB - exactly the difference between the starting HD space amount 110.11 GB and what is currently showing on the "Disk-Mem Panel."

The WMI folder's trace.log appears as a "text file" which apparently cannot be "manually" deleted. The "growth" spurt is fairly rapid at approximately 3/4 GB per half an hour (and sometimes even faster than that). However, I'm not quite sure what to do next... At least I know which file it is. Now if I could only uncover the "cure" to this problem!

Any more ideas?

 

Hi Chas,
does resetting the value from verbose to disabled mean that the problem will still be there, but you just won't have to read about it anymore? Or does it suggest the logging IS the problem?
abri

 

After reading the posts to this thread, I did a search using *.log.

The search found 166 files on my PC.

The largest is 10 megs and is tvDebug.log in C:\Windows\Internet logs\

What is this? What program causes this? Do I need it?

Does CCleaner, Cleanup!, or whatever, remove it?

I can check it out later when I logoff and run my housekeeping programs, but thought I'd ask here to help out others. Bazza

 

It is a debugging log for the True Vector service installed by Zone Alarm. You don't need it; zone alarm will re-create it if it goes missing. CCleaner will not remove it, unless explicitly configured to do so.

 

Thanks, Mada_Milty for the info. Ah, Zone Alarm, eh
The tv bit had me thinking of television not True Vector.

Didn't think CCleaner would auto remove it as I have 100+ other log files dating back quite a while. Log files are usually created when you install a program, aren't they?

Most are small and not worth the trrouble of deleting them. Bazza

===

 

I would say so! They're VERY helpful to a programmer... it lets you see exactly where in the program you might have problems. I have my Windows configured so that when I create a new VBScript, it already has my logging function written out for me, and I just have to specify where I want to keep it.

 

M_M, are they any help to us mere mortal users?

I guess if a tech / programmer / help desk, asks us to recount to them the contents of a log file it would help in troubleshooting. That is why they are there? Bazza

===

 

Check your PMs... we gots to stop hijacking this thread!

 

Today is just NOT my day, (computerwise) folks...​

I just rebooted my machine and ALL of the different "program icons" suddenly changed to very odd looking PINK and Purple colored SQUARE SHAPED icons! ALL of the SHORTCUT icons as well! Using system restore did NOT fix this...

"CALGON... Take me awwwwway!" lol​

Any suggestions?

 

>> Re: I just rebooted my machine and ALL of the different "program icons" suddenly changed to very odd looking PINK and Purple colored SQUARE SHAPED icons! <<

Well... at least THAT icon problem was a relatively "easy" fix. I just fired up tweak UI and clicked:

Repair > Rebuild Icons and *Bingo* the icons went back to normal...

Yahoooooo! <lol>

 

Sure sounds like a nasty got through your defences COMPUABLE, wonder if chaslang or the other folks in Malware might have a take on it. Just a side note on deleteing "Protected Files" I have found that "Eraser 5.8" will get rid of just about anything available here at MG here http://www.majorgeeks.com/download4221.html Good Luck (yea kinda lame I know)

 

>> Sure sounds like a nasty got through your defences... BCGray <<

Well if it is actually MALWARE or some type of viral problem; it must be something "brand new" because I ran just about every malware, adware, HD cleaner and trojan program as well as every 'online scanner' I could think of and absolutely nothing "unusual" showed up on any of these scans.

I tried the "bootvis" fix; followed the instructions to the letter and was able to remove the offensive WMI\trace.log file; however upon reboot that trace.log file just kept growing again! Even after I rebooted (and then uninstalled bootvis); that dang trace.log file just keeps, growing, and growing...

Thanks for the Eraser suggestion BCGray; however in this case it does not apply because the file deletes itself upon each reboot automatically anyway (just like Eraser would).

Back to the drawing board, I guess! Thanks again, for keeping the suggestions coming everyone!

Good Luck!

 

I am certain you did, but just in case chaslang's first post had a link that has a option to place a limiter on the WMI\trace.log file did that do anything???

 

>>> I am certain you did, but just in case chaslang's first post had a link that has a option to place a limiter on the WMI\trace.log file did that do anything??? BCGray <<<

Hi BCGrey, thanks for the advice ("good eye" there!) - It worked... Problem SOLVED! (Yee-haa!)​

===========================================================================
Since your suggestion re: chaslang's first post's link suggestion actually WORKED (so far at least > fingers crossed here! lol) I thought I would post this just in case anyone else out there runs into this exact same nasty problem regarding the apparently "Bulimic" WMI\trace.log file that gets FAT (because of running BootVis previously) while the computer is running and then "purges" the mega-gigabyte file after it reboots...

===========================================================================​

Here is the solution: I just went to the following: Start > Run > Regedit... and then changed:

HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\WBEM\CIMOM\Logging = 1
to
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\WBEM\CIMOM\Logging = 0

Just so you all know...

Changes to the logging level registry value take effect immediately.
No restart of the WMI service is necessary.

Logging level Description

0 No Logging
1 Log only errors
2 Verbose Logging (default) ​

===========================================================================​

The really amazing/scary thing about this; is that many people may actually have this problem and they’d never in a million years know it. Why? Because it has absolutely no visible effect upon the system's performance - nothing runs slow or acts erratically. Had I not been running that Disk-Mem Panel program 24/7 like I usually do - I'd never have found out about it either!

I just set it to ZERO - Wish me luck! Once again THANK YOU ALL so much for helping me put my space gobbling WMI\trace.log file on a "diet"

 

>> I knew if I pointed you guys in the right direction that you would figure it out while I kept busy in the Malware Forum. Good job! chaslang <<

Well chaslang, I certainly appreciate the fact that you had the time stop by the "Software Forum" yesterday! I know that the folks in the Malware Forum keep you very busy with requests for your expertise and assistance.

Additionally, although I had posted that I'd already checked out that first link which you offered; I appreciate the fact that BC Gray took the time to look over the information provided there, as well (far more thoroughly than I did). The fact that he was able to "catch" the answer and point me back in the direction of the original link; which offered the actual answer - an option to place a limiter on the WMI\trace.log file - was a big help to me as well!

Unfortunately, sometimes when we’re faced with some nasty that's causing a nagging problem; in our haste, it becomes very easy to overlook something that might actually be helpful. It’s great to know that folks like you and BC Gray are available in this forum to point us all in the right direction and “have our backs” in such situations!

Thanks again to all who contributed to helping me to resolve my problem yesterday!

Good Luck