Disappearing Hard Drive

[Tetramesh]

Hi
Hopefully someone here can help. I have a Dell Inspiron 6400 which I bought less than a year ago, it came with a 80GB hard drive, 1GB of RAM (I've since added an extra 1GB) and Vista Home Premium installed. I try to keep it uncluttered and uninstall any programs I don't need to free up disk space along with deleting restore points every now and then. Recently it has been a losing battle trying to free space, as I write this I have only 6.94GB left as shown on this image;


I installed and ran Treesize which showed that Windows is taking up a huge amount of space as shown in this image;



I opened the containing folder and found lots of TMP files as shown here;


Does anyone know what these are and are they responsible for my diminishing space?

Thanks.

[giradman]

Well, you may have to provide some more information concerning your 'activities' on this new LT computer? 'Dump' files are generated w/ major computer crashes that usually generate BSODs - have you been having a lot of crashes? If so, what are some of the potential reasons - installing, uninstalling, etc.?

Also, what are you storing on that hard drive, esp. audio, image, & video files? You may have nearly filled it up? Have you run any disk cleaning programs (VISTA & XP have 'cleanup' programs) or have you defragged the drive?

Please respond & maybe some more specific advise can be given - but good luck - BTW, I have a new Dell LT (almost a year old) w/ VISTA, and just have a third of the HD filled - not much help but just a comparison - think that I've had only a few 'freezes' while on the internet - had to re-boot, but no BSODs (nor any dump files) -

[Tetramesh]

Originally Posted by giradman

Well, you may have to provide some more information concerning your 'activities' on this new LT computer? 'Dump' files are generated w/ major computer crashes that usually generate BSODs - have you been having a lot of crashes? If so, what are some of the potential reasons - installing, uninstalling, etc.?

Also, what are you storing on that hard drive, esp. audio, image, & video files? You may have nearly filled it up? Have you run any disk cleaning programs (VISTA & XP have 'cleanup' programs) or have you defragged the drive?

Please respond & maybe some more specific advise can be given - but good luck - BTW, I have a new Dell LT (almost a year old) w/ VISTA, and just have a third of the HD filled - not much help but just a comparison - think that I've had only a few 'freezes' while on the internet - had to re-boot, but no BSODs (nor any dump files) -

Hi. I haven't had a BSOD for months, not since I reinstalled Vista.
I store about 4GB of audio on this laptop, most of my audio, all of my photos and all of my videos are stored on my XP desktop.
I've defragged and used Ccleaner regualarly.
An ongoing problem is that sometimes the computer will not shutdown, it hangs at the screen which says 'Shutting down...', I have no alternative other than to force it to shutdown by holding down the power button.

[AnnMarie]

Hi Tetramesh. You really need to sort out the shutdown problem. What you are looking at are complete memory dumps which have been created each time you have had a forced shutdown. See here for more information. Go to Control Panel > System > Advanced System Settings > Advanced and check your Startup and Recovery settings. What do you see under "Write debugging information"? Also is "Overwrite any existing file" checked?

[Tetramesh]

Hi. Under 'Write debugging information' it says 'Complete memory dump' and the 'Overwrite any existing file' is checked.

[AnnMarie]

Ok. Change your settings to the same as those you can see in the link I posted. Those dumps can also be deleted. No-one in their right mind is going to want to try and debug a 2 GB file. If I were you, I would bypass the Recycle Bin when you delete them just in case it chokes. To do this, select the file and then hold down the shift key and press delete.

The next time you have problems shutting down, a minidump should be created in the C:\Windows\Minidump folder. I would be happy to have a look at that for you but post here first.

[Tetramesh]

Hi. After deleting the TMP files and running Ccleaner I now have 35.6GB free space which is a great improvement. I changed the Startup and Recovery settings as advised and will let you know if I have more problems shutting down.

Thanks for your time and help.

[AnnMarie]

You are welcome Tetramesh.

[Tetramesh]

Hi, me again. I have had a couple of problems during shutdown recently, I've tried opening the Minidump file and found that I had to download the Windows Debugger first but I don't think it is working correctly. This is what it shows;


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini021308-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x82400000 PsLoadedModuleList = 0x82511e10
Debug session time: Wed Feb 13 14:40:15.345 2008 (GMT+1)
System Uptime: 0 days 5:08:52.659
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.................................................. .................................................. .................................................. ..
Loading User Symbols
Loading unloaded module list
.....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 84276030, 85955030, 8492ec48}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_IRP ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_DEVICE_OBJECT ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Probably caused by : ntkrnlpa.exe ( nt+d8681 )

Followup: MachineOwner

Any ideas?
---------

[AnnMarie]

Can you send me the file please Tetramesh. Also run a search for sysdata.xml and send me that too. Copy them to a new folder, zip it up (this is important) and email it to me (include a link to this thread) and title your email "Minidump". My address is anniefriday@xtra.co.nz. I will post back when I have checked them out.

[AnnMarie]

You didnt send me sysdata.xml which would have been useful.

The analysis identified bcmwl6.sys as causing the problem. This is apparently a Broadcom wireless driver and the version you have was last updated Nov, 2006. Try uninstalling and reinstalling the driver and also have a look on the Dell site and see if there are any updates for your model computer.

[Tetramesh]

Hi. After I put a search in for 'sysdata.xml' the result came up showing only the file I sent you, I couldn't see anything else. I'll take a look at reinstall the driver and take a look at the Dell site. I'll get back with more info.

Thanks.

[AnnMarie]

Ok. Good luck.