Dump files

Similar Questions

• Create the command line for the Dump file without having to install additional tools

  I should automate the creation of dump files. It must to be command line and without installing tools such as ProcDumpTechNet.Microsoft.com/Sysinternals/dd996900, minidump or similar. I think that it is not a solution but if someone can help me.

  This issue is beyond the scope of this site (for consumers) and to be sure, you get the best (and fastest) reply, we have to ask either on Technet (for IT Pro) or MSDN (for developers)

  *

  http://social.technet.Microsoft.com/forums/en-us/home s/fr-U.S./Accueil
  http://social.msdn.Microsoft.com/Forum

• How can I free up space on my C drive without dumping files I need to power my computer? Windows XP 2002

  How can I free up space on my C drive without dumping files I need to power my computer? I have currently 40,4 GB used and I don't know how or what is out there that I don't need? I have a backup of system restore that takes a lot of space, but Im saying that I can not remove it by a pop-up box that says access denied even though I have since transferred it on my external backup hard drive. Can someone please help? Thank you

  {You can remove C:\{folder-name with lots of letters and numbers like this: 2b4892ncf73d63db37db37}------(these files are temporary and have been created by installers)
  C:\Temp
  C:\Documents and Settings\\temp
  C:\Documents andSettings\Temp Settings\
  C:\Documents and Settings\\Local Settings\Temporary Internet Files\ (all the folders inside this folder)

  To remove manually restore points, you will need to login to safe mode and change the permissions in the Security tab of the restore point. However, I do not recommend this.

  Read this article on how to remove safely restore points:
  http://support.Microsoft.com/kb/555367

  If your computer is slow too, I can check for you and let you know what you have running, you know not everything in the background with a newspaper.

  -Alex

• What causes BSOD? I have the dump file for those interested

  DUMP_HEADER32:
  MajorVersion 0000000f
  MinorVersion 00000 has 28
  DirectoryTableBase 0adc05a0
  PfnDataBase 81 b 46000
  Kernel 8055d 720
  PsActiveProcessHead 805638 b 8
  MachineImageType c 0000014
  NumberProcessors 00000002
  BugCheckCode 10000050
  BugCheckParameter1 e62a7d05
  BugCheckParameter2 00000000
  BugCheckParameter3 bf26e8b7
  BugCheckParameter4 00000001
  PaeEnabled 00000001
  KdDebuggerDataBlock 8054d2e0
  MiniDumpFields 00000dff

  TRIAGE_DUMP32:
  00000300 ServicePackBuild
  SizeOfDump 00010000
  ValidOffset 0000fffc
  ContextOffset 00000320
  ExceptionOffset 000007d0
  MmOffset 00001068
  UnloadedDriversOffset 000010 has 0
  PrcbOffset 00001878
  ProcessOffset 000024c 8
  ThreadOffset 00002728
  CallStackOffset 00002980
  SizeOfCallStack 0000052c
  DriverListOffset 00003140
  DriverCount 00000074
  StringPoolOffset 000053 b 0
  StringPoolSize 00000ff0
  BrokenDriverOffset 00000000
  TriageOptions 00000041
  TopOfStack b5ea9ad4
  DebuggerDataOffset 00002eb0
  DebuggerDataSize 00000290
  DataBlocksOffset 000063 has 0
  DataBlocksCount 00000006

  Windows XP Kernel Version 2600 (Service Pack 3) MP (2 processors) free x 86 compatible

  Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
  The debugging session: Sun May 08 20:00:09 2011
  System Uptime: 0 days 08:59:41
  start end module name
  804 d 7000 806e5000 nt Checksum: 001FA054 Timestamp: Thu Dec 09 05:
  06:55 2010 (4D00D46F)

  Unloaded modules:
  aec31000 aec3e000 DMusic.sys Timestamp: unavailable (00000000)
  aecb1000 aecbf000 c:\windows\system32\drivers\swmidi.sys Timestamp: unavailable (00000000)
  ae1f8000 ae21b000 aec.sys Timestamp: unavailable (00000000)
  ba636000 ba638000 splitter.sys Timestamp: unavailable (00000000)
  b18a8000 b18d3000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b58bd000 b58c9000 cfwids.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b18a4000 b18cf000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b1919000 b1944000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b248a000 b24b5000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  b50fe000 b5129000 c:\windows\system32\drivers\kmixer.sys Timestamp: unavailable (00000000)
  ba729000 ba72a000 drmkaud.sys Timestamp: unavailable (00000000)
  b51c9000 b51ec000 aec.sys Timestamp: unavailable (00000000)
  b55e5000 b55f2000 DMusic.sys Timestamp: unavailable (00000000)
  b5675000 b5683000 c:\windows\system32\drivers\swmidi.sys Timestamp: unavailable (00000000)
  ba63c000 ba63e000 splitter.sys Timestamp: unavailable (00000000)
  b5571000 b5595000 mfeavfk01.sy Timestamp: unavailable (00000000)
  b5e0a000 b5e1a000 Serial.SYS Timestamp: unavailable (00000000)
  b58f9000 b590d000 Parport.SYS Timestamp: unavailable (00000000)
  ba1f8000 ba201000 processr.sys Timestamp: unavailable (00000000)
  ba448000 ba44d000 Cdaudio.SYS Timestamp: unavailable (00000000)
  b8ae5000 b8ae8000 Sfloppy.SYS Timestamp: unavailable (00000000)
  ba440000 ba445000 Flpydisk.SYS Timestamp: unavailable (00000000)
  ba438000 ba43f000 Fdc.SYS Timestamp: unavailable (00000000)

  Finish the dump check

  Unfortunately, even after the recent updates and updates the Microsoft Answers forum still does not prompt for any kind of information system when a new question is asked if we know anything about your system.  Not knowing the basic information a problem prolongs the frustration and the agony of these issues.

  Maybe someday the dialog box 'ask a question' forums XP will ask these questions automatically when a new thread is started so I don't have to ask every time.  It might even be possible to solve a problem in a single response when enough information is provided.

  Provide information on your system, the better you can:

  What is your system brand and model?

  What is your Version of XP and the Service Pack?

  Describe your current antivirus and software anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc..

  The afflicted system has a CD/DVD drive work?

  You have a true bootable XP installation CD (it is not the same as any recovery CD provided with your system)?

  If the system works, what do you think might have changed since the last time it did not work properly?

  Can you make the system crash when you want
  ?  For example, you would say that there is no specific system activity that coincides with the accidents (like watching videos, playing games, etc.).

  The next time your system crashes, provide more information on what you see.

  Here's a BSOD example showing information you provide:

  http://TechRepublic.com.com/i/tr/downloads/images/bsod_a.jpg

  Send for the nose and the Red arrows (3 to 4 lines total).

  Send all * line STOP message since there are clues in the 4 parameters.

  If there is a name of the file listed in the STOP message, don't forget to include this information too.

  Ignore the boring text unless it seems important to you.  We know what a BSOD looks like, we need to know what your BSOD looks like.
  Download BlueScreenView here:
  http://www.NirSoft.NET/utils/blue_screen_view.html
  Unzip it and run it (BSV installs nothing) and let him complete the digitization of all your crash dump files.
  If you double-click on depressed, you will get information on it (including the field caused by the driver) and you should be able to spot the problem right away - especially if you see a model in landfills where Caused by field pilot is the same (beginning with this driver).
  BlueScreenView tries to find the right driver or module that caused the blue screen by looking inside the stack of the accident. However, be aware that the driver detection mechanism is not 100% reliable, and you should also look in the lower pane, that display all drivers/modules found in the stack.
  Select (highlight) one or more of the most recent dump files by clicking on them and hold down the CTRL key to select multiple files.  Try to select only the most recent links that relate to your problem (perhaps five or six to start dump files).
  Click on file, save selected items and save information from the dumps to a text file on your desktop called BSOD.txt
  .  Open BSOD.txt with a text editor, copy the text and paste it in your next reply.
  Here's an example of report ASB to a single BSOD I initiated on purpose that indicates the cause of the accident as the pilot i8042prt.sys belonging to Microsoft Corporation:
  ==================================================
  Dump file: Mini062110 - 01.dmp
  Crash time: 21/06/2010-11:51:31
  Bug Check String: MANUALLY_INITIATED_CRASH
  Bug check code: 0x000000e2
  Parameter 1: 0x00000000
  Parameter 2: 0x00000000
  Parameter 3: 0x00000000
  Parameter 4: 0x00000000
  Caused by the driver: i8042prt.sys
  Caused by the address: i8042prt.sys + 27fb
  Description of the file: i8042 Port driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2108)
  Processor: 32-bit
  Computer name:
  Full path: C:\WINDOWS\minidump\Mini062110-01.dmp
  ==================================================
  Send the information of the last 5 memory dumps (if you don't have 5 memory dumps yet, send the newest, you have).
  While you wait, please follow these steps:
  Perform scans for malware, and then fix any problems:

  Download, install, update and do a full scan with these free malware detection programs:

  Malwarebytes (MMFA): http://malwarebytes.org/

  SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

  They can be uninstalled later if you wish.

  Restart your computer and solve the outstanding issues.

• System error memory dump files

  Is it safe to delete system error memory dump files after you run a cleaning disc?  Also what are system error memory dump files?

  Hi Cookie5354,

  Basically, error, say a blue screen of death (BSOD) Windows gathers all available information stored in memory at the time of the incident and that she "pours" in a file. The file can then be used by a support technician to determine what could perhaps have the error in the first place. Sometimes, when an error occurs on Windows will ask you if it can information additional NMCS to Microsoft. If you press the Yes button on the request message that appears, then Windows will download the dump to Microsoft Server files.

  Dump files are useful "but" they have the bad habit of taking a lot of space, so it is beneficial remove files to recover the space they occupy. Personally, I use a freeware thrid party application called CCleaner (www.piriform.com) If you use this and look at the bottom of the left side of the window of CCleaner, you will see a list of options what it removes. "Remove Windows error reports" is not checked by default, but I it check every few weeks or so, so that it clears the resports old error that are no longer needed.

  So, in answer to your question, yes they can be deleted.

  This forum post is my own opinion and does not necessarily reflect the opinion or the opinion of Microsoft, its employees or other MVPS.

  John Barnett MVP: Windows XP Expert associated with: Windows Desktop Experience: www.winuser.co.uk | vistasupport.mvps.org | xphelpandsupport.mvps.org | www.silversurfer-Guide.com

• Cannot get rid of "debug dump files.

  When I 'disk cleanup' results show a list of files to delete and "debug dump files" is unchecked. I then check the debug dump files, but when files are deleted, the debug dump files do not disappear.

  Hello

  Thanks for posting in the Microsoft Community Forum. Rest assured that we would do our best to help you.

  Save files, previously called crash dumps, allows you to save the information on the program for debugging later. Dump files can be especially useful when you are testing a program on a computer that does not have source files or a symbol. When an incident occurs, you can save a dump file and later, debug on the build computer or on another computer on which the source files and debugging symbols.

  Try these steps and check:

  Step 1:

  Run the disk cleanup utility should delete these files. You can remove the files if you want to save space on the hard disk.

  Try to delete the files as an administrator. To do this, try the following steps.
  a. Click Start, type disk cleanup, click with the right button on disk cleanup and click Run as administrator.
  b. place a checkmark on "System error memory dump files"
  c. click ok and check if the files are deleted successfully.

  See , delete files using disk cleanup

  Step 2:

  Try to remove the dump files manually and check:

  To do this, follow these steps:

  a. Click Start, type or copy the following command in the start search box and click on enter.

  %SystemRoot%\Minidump

  b. press on ctrl + a to select all files in the minidump and do right click and select Remove, or hit delete key on the keyboard.

  Hope this information helps. If you have any questions do not hesitate to answer, we would be happy to help.

• Can someone please read my mini dump files?

  Ive been making these mistakes to fall frequently ARREST, but I haven't changed anything on my 32 bit Vista computer. I'm not very tech savvy but I have done enough research to know that someone can solve this problem to my analysis of these files 'mini '. I was wondering if someone can help out me?

  dump files:

  https://onedrive.live.com/ * address email is removed from the privacy *.

  Thank you very much

  -Lucas

  Run the tool to remove the links below, Norton to remove these modules apparently remains.

  Norton Removal Tool.

  https://support.Norton.com/SP/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us

  Then find and uninstall Hotspot shield module below.

  Image path: \SystemRoot\system32\DRIVERS\taphss6.sys
  Image name: taphss6.sys
  Timestamp: Thu Jun 20 21:08:54 2013 (51C3A7A6)

  Note: If you want to make sure they are gone, download "autoruns" and it allows to locate and delete after checking that all the entries in Microsoft have been hidden, in order to eliminate the possibility of error. (instructions in the link below youtube video)

  Autoruns for Windows

  v13.01

  This utility, which has a knowledge of auto-starting locations of any startup monitor, shows you what programs configured to run at system startup or login and that the entries in the order of processing windows. These programs include those in your startup folder, Run, RunOnce, and other registry keys. You can configure Autoruns to show other locations, including Explorer shell, toolbar extensions, helper objects to the browser, Winlogon notifications, auto and many start-up services even more. Autoruns goes way beyond the MSConfig utility bundled with Windows Me and XP.

  The Autoruns hide signed Microsoft entries allows you to zoom in on images of automatic start of third parties who have been added to your system and it has support for looking at images of Autostart configured for other accounts configured on a system

  https://TechNet.Microsoft.com/en-us/sysinternals/bb963902.aspx

  How to use Autoruns.

  https://www.YouTube.com/watch?v=HhtSDsQYi28

  Download, install, update ad run a complete scan with Microsoft Security Essentials.

  Microsoft Security Essentials.

  http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download

• BSOD, klim6.sys, tdx.sys - dump file

  OS: Windows Vista Home Premium (32 bit)
  Cell phone brand / model: Acer Aspire 4930
  Processor: Intel Core 2 Duo 2 GHz
  RAM: 3 GB
  Anti Virus: Kaspersky AntiVirus 2009 (8.0.0.506)

  Problem: BSOD a few times (at random times) - pointing to tdx.sys problem

  Troubleshooting done so far:

  Follow-up http://support.microsoft.com/kb/315263 to use WinDBG to read crash dump files. The analysis of dump in WinDBG output is displayed under my immediate questions - thanks in advance! :

  1. is the problem because tdx.sys (legacy driver problem) or klim6.sys (Kaspersky)?
  2. If it is due to klim6.sys - should I uninstall Kaspersky?
  3. If it is due to tdx.sys - which of the following hotfix should I apply?
  (a) http://support.microsoft.com/default.aspx/kb/967891
  (b) http://support.microsoft.com/kb/934611
  4. the patch will present other bugs?

  Output of WinDBG Crash Dump Analysis:
  Debug version of Microsoft Windows (R) 6.11.0001.404 X 86
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading file Dump [c:\windows\minidump\Mini050209-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  ATTENTION: Inaccessible path: "c:\windows\i386".
  Symbol search path is: srv * c:\symbols* http://msdl.microsoft.com/download/symbols
  Executable search path is: c:\windows\i386
  Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 processors) free x 86 compatible
  Product: WinNt, suite: TerminalServer personal TerminalServer
  By: 6001.18226.x86fre.vistasp1_gdr.090302 - 1506
  Computer name:
  Kernel base = 0x82c38000 PsLoadedModuleList = 0x82d4fc70
  The debugging session: 19:19:44.274 Saturday, may 2, 2009 (GMT + 8)
  System Uptime: 2 days 6:33:50.154
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ...................................
  Loading user symbols
  Loading unloaded module list
  ........
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  BugCheck D1, {38, 2, 1, 9230855d}

  Cannot load the image \SystemRoot\system32\DRIVERS\klim6.sys, 0n2 error Win32
  WARNING: Unable to verify timestamp for klim6.sys
  ERROR: Module load completed but symbols can be loaded for klim6.sys
  Probably caused by: tdx.sys (tdx! TdxSendConnectionTlRequestComplete + 59)

  Follow-up: MachineOwner
  ---------

  0: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
  An attempt was made to access an address pageable (or completely invalid) to a
  application interrupt level (IRQL) that is too high.  It is usually
  caused by drivers using a wrong address.
  If the kernel debugger is available, get a stack backtrace.
  Arguments:
  Arg1: 00000038, referenced memory
  Arg2: 00000002, IRQL
  Arg3: 00000001, value 0 = read operation, 1 = write operation
  Arg4: 9230855d, address which referenced memory

  Debugging information:
  ------------------

  WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d6f868
  Cannot read MiSystemVaType memory at 82d4f420
  00000038

  CURRENT_IRQL: 2

  FAULTING_IP:
  TDX! TdxSendConnectionTlRequestComplete + 59
  8701 xchg eax, dword ptr [ecx] 9230855d

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

  BUGCHECK_STR: 0XD1

  Nom_processus: System

  TRAP_FRAME: 82d2d358-(.trap 0xffffffff82d2d358)
  ErrCode = 00000002
  EAX = 00000000 ebx = 92311d ecx 16 = 00000038 edx = 00000000 esi = 00000000 edi = 9 c 665760
  EIP = d 9230855 esp = 82d2d3cc ebp = 82d2d3dc iopl = 0 nv up ei pl zr pe nc
  CS = 0008 ss = 0010 ds = 0023're = 0023 fs = 0030 gs = 0000 efl = 00010246
  TDX! TdxSendConnectionTlRequestComplete + 0 x 59:
  9230855d 8701 xchg eax, dword ptr [ecx] ds:0023:00000038 is?
  Reset the default scope

  LAST_CONTROL_TRANSFER: from 9230855d to 82c92d24

  STACK_TEXT:
  82d2d358 badb0d00 d 9230855 82d2d37c 00000000 nt! KiTrap0E + 0x2ac
  82d2d3dc 92247d 84 021d0ac0 00000000 00000065 tdx! TdxSendConnectionTlRequestComplete + 0 x 59
  82d2d3fc 922455 has 7 9c7a80b0 9241b 598 d 922 4850 tcpip! TcpCompleteTcbSend + 0x2e
  82d2d454 92244f1b b 9241, 518 0063ba48 82d2d4b8 tcpip! TcpTcbReceive + 0 x 287
  82d2d4ac 92244d 14 9241b 518 00000000 and 00000000 tcpip! TcpMatchReceive + 0x1ec
  82d2d4f4 9241b 518 92245310 92425000 92425010 tcpip! TcpPreValidatedReceive + 0x2b0
  82d2d510 9241b 518 92245913 82d2d54c 92425000 tcpip! TcpReceive + 0x32
  82d2d520 9226ffef 82d2d534 c000023e 00000000 tcpip! TcpNlClientReceiveDatagrams + 0x12
  82d2d54c 9226fdb2 922c6e50 82d2d5a0 c000023e tcpip! IppDeliverListToProtocol + 0 x 49
  82d2d56c 9226fcd9 922c6c68 82d2d5a0 00000006 tcpip! IppProcessDeliverList + 0x2a
  82d2d5c4 9226f4cc 922c6c68 00000000 00000006 tcpip! IppReceiveHeaderBatch + 0x1eb
  82d2d654 9226dfc6 993fd270 82d1b401 00000000 tcpip! IpFlcReceivePackets + 0xbe1
  82d2d6d0 9226e50e 9c63ad70 ac5b46f0 00000000 tcpip! FlpReceiveNonPreValidatedNetBufferListChain + 0x6e3
  82d2d6f8 833520b 0 9c63ad70 ac5b46f0 00000000 tcpip! FlReceiveNetBufferListChain + 0 x 104
  82d2d72c 83344919 0063a9b8 ac5b46f0 00000000 ndis! ndisMIndicateNetBufferListsToOpen + 0xab
  82d2d754 83344890 00000000 9c64b240 9f7d4148 ndis! ndisIndicateSortedNetBufferLists + 0x4a
  82d2d8d0 8328557f 00000000 00000000 ndis 85f22438! ndisMDispatchReceiveNetBufferLists + 0 x 129
  82d2d8ec 832b0d88 85f22438 ac5b46f0 00000000 ndis! ndisMTopReceiveNetBufferLists + 0x2c
  82d2d908 832b0d5f 9c64bc10 ac5b46f0 00000000 ndis! ndisFilterIndicateReceiveNetBufferLists + 0x20
  82d2d924 92bca003 9c64bc10 ac5b46f0 00000000 ndis! NdisFIndicateReceiveNetBufferLists + 0x1b
  WARNING: Information not available stack unwind. Sequence of images may be wrong.
  00000000 00000000 00000000 00000000 00000000 klim6 + 0 x 2003

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  TDX! TdxSendConnectionTlRequestComplete + 59
  8701 xchg eax, dword ptr [ecx] 9230855d

  SYMBOL_STACK_INDEX: 1

  SYMBOL_NAME: tdx! TdxSendConnectionTlRequestComplete + 59

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: tdx

  Nom_image: tdx.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 479190ee

  FAILURE_BUCKET_ID: 0xD1_tdx! TdxSendConnectionTlRequestComplete + 59

  BUCKET_ID: 0xD1_tdx! TdxSendConnectionTlRequestComplete + 59

  Follow-up: MachineOwner
  ---------

  Hello Hanning,

  Windows allows to fix corrupt or missing files it finds. If the information of the installation CD is required to fix the problem, you may be asked to insert your Windows Vista CD. You can get the well-known files from your dvd to the BONE. Have you this? If this is not the case, try a system restore. If it does not always help let us know that you can download and ISO of here: http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ but the use of this software to burn your ISO. Link: http://download.cnet.com/Active-ISO-Burner/3000-2646_4-10602452.html?tag=mncol, let us know if this allows you to get your drive. Follow the instructions. Let us know whether, if that helps you. Make it a great day!

  "In the end, the love you take, is equal to the Love You Make"

• Cleaning disc does not remove "debug dump and system error memory dump files".

  Original title: clean windows vista disk

  on my drive clean I have 112 mb on the debug dump files and 112 mb on system error memory dump files. My problem is when I try to delete these files from my cleaning disc will not remove these files. could help me with this problem?

  Hello

  1. what happens when you try to delete the files of debugging bump?

  2. do you get any error code or error message?

  3. have you made changes on the computer before this problem?

  I would suggest trying the following methods and check if it helps.

  Method 1:

  Start in safe mode and then try to perform a disk cleanup and check if it works.

  Step 1: Start Windows Vista in safe mode:

  http://Windows.Microsoft.com/en-us/Windows-Vista/start-your-computer-in-safe-mode

  Step 2: Delete files using Disk Cleanup:

  http://Windows.Microsoft.com/en-us/Windows-Vista/delete-files-using-disk-cleanup

  Method 2:

  Run the scan tool (SFC) System File Checker and check if it helps.

  How to use the tool File Checker system to troubleshoot missing or corrupted on Windows Vista system files: http://support.microsoft.com/kb/929833

  Also check the event viewer on the program that is causing the problem.

  Event Viewer is a tool that displays detailed information about important events on your computer.

  http://Windows.Microsoft.com/en-us/Windows-Vista/open-Event-Viewer

  Hope the information is useful.

• What is error in system memory dump files and is it ok to delete

  can someone tell me what are the system error memory dump files and mini dump files and is it OK to remove them to give me more memory hard drive

  They are for when your computer blue screens, it exports the files of the ram disk for troubleshooting.  Yes, it is safe to remove them if you do disk cleanup.

• When I click on dump debugging, system, thumbnails and files dump files memory system archive of windows error reporting

  When I click on dump debugging, system, thumbnails and files dump files memory system archive of windows error reporting
  They does not clear my cleaning disc on my computer at home. If someone could help
  deal with this problem?

  * original title - disc clean up problem *.

  You are welcome.

• What is a debug dump file, and do I need?

  When I go to disk cleanup, debugging dump files is one of the options, are files created by windows, will be permanently deleted and do I need?

  Hello

  Those are to help if you are experiencing operating system problems. If there is no
  real problems under Windows and then delete as they will not help in the future
  News and events will be created if a major problem comes up.

  I hope this helps.

• Disk Cleanup is not showing me the ability to clean the system error memory dump files

  Hello. When I run the disk cleanup utility in Vista, it does not show the option of cleaning the system error memory dump files. It is a very serious problem. I had to delete files that I really wanted to keep, because I thought they were taking too much space. He did not make a particle of difference. I have only two GB on my C drive now. How to fix this problem?

  Kim

  You must use the scroll bar on the right disk cleanup in the window that appears after checking for space to scroll to check the boxes before these items.

  Deleting the less important system restore points allows you to earn useful free disk space.

  A better program of disk cleanup is cCleaner. Delete System Restore points may be important if you have little free disk space. The ability to delete them is one of the tools options. You can selectively remove those created in less important moments.

  cCleaner also comes with a registry tool. Do not use this tool as any registry cleaner could lead to the creation of very difficult to resolve system errors.

  http://www.CCleaner.com/download

  You have free disk space in another partition on the drive or any other drive internal on your computer?

• Why the system error memory dump files create everytime in vista

  Why the system error memory dump files create everytime in vista

  Please help me find

  Hi ashwin_amb,

  System error memory dump files contain dump files created by Windows because of a stop error. They are created when an application crashes and creates an exception code. The dump file indicates which line or an area of memory the program crashed at and is used for troubleshooting.

  For more information, see the KB article:

  How read partial memory dump files that Windows creates for debugging

  http://support.Microsoft.com/kb/315263

  Hope the helps of information.

• HP EliteBook 8470p: need HP EliteBook Notebook PC Bios Dump file 16 MB 8470p

  Anyone have HP EliteBook Notebook PC Bios Dump file 16 MB 8470p?

  I got 1 of French Forum but when I reprogram the bios chip which, bios everything ok work and windows works very well, but when every time you start the laptop gives these errors

  1:

  warning machine not be State

  2:

  Council OOA product invalid information system
  Name of the product
  Configuration
  Serial number
  Product number

  Please share if anyone has the other suggestions or bios dump file?

  Now all Ok Guy

  Put in touch with Hp Support.

  they sent the files and the instructions, as they provide guidance and now everything is ok.

  Thank you all for Guide.