What is Mini052111 - 01.dmp?

window of closes on me. It is the first time that this takes place which is Mini052111-01dmp?

It is a Minidump file that is where Windows stores information about the State of the system at the time where it crashed. Some of this information may be sent to Microsoft for use in reporting on problems and Solutions. More technical interest allows users the debugging tools for Windows with this file to try to diagnose the cause of the accident.

http://msdn.Microsoft.com/en-us/Windows/hardware/gg463009.aspx

Tags: Windows

Similar Questions

  • The file c:\Windows\MEMORY. DMP was removed, what will happen without it?

    Using antivirus software to remove the malware file c:\Windows\MEMORY. DMP has been removed.  If for any reason, the system crashes, the system will create a new c:\Windows\MEMORY. DMP file? If this is not what would happen without the said file? To what extent it is essential to restore the said file?

    However, there is no sequel. Memory dumps are created to help users to discover the cause of a system failure. If the problem oersist the system will create futher landfills.

    CCleaner and disk cleanup can be set to remove the dump files. Maybe it's what happened.

  • What MPEG4 - Part2 format supporting 4305 G DMP?

    Dear all,

    I would like to know what MPEG4 - Part2 format supporting the DMP 4305 G? Since I tried every codec

    for example.

    Standard MPEG4

    DivX

    XviD

    Can someone help me or give me an example file format so that I can get more information to convert the file to read in the DMP 4305 G.

    * I'm using DPM version 5.1

    Thanks in advance

    See below

  • Windows 7, get this blue screen error message, what should I do to remedy? C:\Windows\Minidump\100312-29827-01.dmp

    Need help, my computer hangs at this message

    Windows 7, get this blue screen error message, what should I do to remedy? C:\Windows\Minidump\100312-29827-01.dmp

    Hello

    1. when exactly do you get this error message?

    2 are you able to start in the Office?

    3 have there been recent changes to the computer before the show?

    I suggest you try the steps mentioned below and check if it helps.

    Method 1: Start your system in safe mode and check if the same problem occurs.

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

    Method 2: If the question does not exist in Mode safe mode then try to put your computer in a clean boot state.

    By setting your boot system minimum state helps determine if third-party applications or startup items are causing the problem.

    How to troubleshoot a problem by performing a clean boot in Windows Vista or Windows 7:
    http://support.Microsoft.com/kb/929135

    Note: After the boot minimum troubleshooting step, follow step 7 in the link provided to return the computer to a Normal startup mode.

    Method 3: Resolve stop (blue screen) errors in Windows 7: http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

    Hope this information is useful.

  • What are mini dmp files?, I can't open themm. How they are created?

    My pc stops whenever I have let in stanby, message "windows closed for serius problem. Error report... Details list 2 1 files? minidmp file newly created each time that? How does this affect pc? It's harmful.can I delete these files I can'topen them & can not find real estate of?

    .dmp files are memory dumps when you have a blue screen. You can consult with Nirsoft BlueScreenVIew or WhoCrashed. You can look at them yourself, but you should zip, upload to the sky by car or elsewhere and let someone take a look at them here.

  • How to read these .dmp files to figure out what made my computer crash?

    For some time now, I've been crashing when playing some games on my computer and I can't for the life of understand me how to read the dump of the computer files.

    http://www.sendspace.com/filegroup/8Gj9VzD2SKc7%2FIy4d%2BMmMbokVjIju92H
    These are the files to dump.

    Theres a problem with your nvidia driver & installation of DirectX

    BlueScreenView or WinDbg can help reading dmp files

  • Equium A110-276 - what is this BSOD average?

    I hope that someone help me by telling me what's causing all these blue screens, I got last week.

    I have analyzed dmp files and are in the posts below. I just be reformatted my hard drive and I was wondering if it was a specific driver, that I should be looking at, or if it was a hardware problem. I hope you can help!

    Hello

    I also suggest that you need to check the modules of RAM with Memtest86. You can download a CD image and burn it to a CD. Then you have a startup disk where you can start from.
    Memtest86 is really easy to use and find most of the problems of RAM.

    In my opinion it may be also due to drive HARD, maybe bad sectors. HARD drive you can test also, but that's why you should Drive Fitness Test or another test tool. Use Google to find, the test is also freeware and you can download an ISO image of a bootable disc.

    Good luck!

  • C:\Windows\Minidump\Mini082813-01.dmp C:\Users\Angel\AppData\Local\Temp\WER-496863-0.sysdata.xml C:\Users\Angel\AppData\Local\Temp\WERA939.tmp.version.txt

    C:\Windows\Minidump\Mini082813-01.dmp
    C:\Users\Angel\AppData\Local\Temp\WER-496863-0.SysData.XML
    C:\Users\Angel\AppData\Local\Temp\WERA939.tmp.version.txt

    Jane doe00

    We need the DMP file because it contains the single record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.

    WE NEED AT LEAST TWO FILES DMP TO SPOT TRENDS AND TO CONFIRM THE DIAGNOSIS.
    You may be able to get the DMP files without crashing by booting in SafeMode (F8) with networking.
    If you are overclocking stop.  (chances are that if you are unsure if you are, you are not)
    To allow us to help you with symptoms BSOD on your computer, download the contents of your folder "\Windows\Minidump".
    The procedure:
    * Copy the contents of \Windows\Minidump to another location (temporary) somewhere on your machine.
    * Zip up the copy (compress)
    * Please download to a service like Skydrive or "Rapidshare" to share files and put a link to them in your answer.
    Link to find out how to download below.
    To ensure the minidumps are enabled:
    * Click Start, in the search box, type: sysdm.cpl, press ENTER.
    * On the Advanced tab, click Startup and recovery... Settings button.
    * Make sure that automatically restart is unchecked.
    * Under the writing debugging information header, select image partial memory (256 KB) in the list box drop-down (varies from 256kb).
    * Ensure to that small Dump Directory is listed as % systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and download the output as well.
    To run MSinfo32 please go to start > run > MSinfo32
    Go to 'file', 'save' and download the PDF is saved with the DMP
    System specs are extremely useful then please include everything you know.

    Blue screen view and that crashed are often wrong and should only be used in case of emergency...

    You can learn more about BSOD here
    You will learn how to test your memory here 


    Team Zigzag3143.com  

  • What do the codes of the JIU 0 x 76 and 0 x 33

    What breaks down codes dump 0 x 76 0xf 0 x 33 average.

    We can help more if we know what OS you are using and if we have the DMP.  Without the DMP, it is what we can do.

    PROCESS_HAS_LOCKED_PAGES bug control has a value of 0 x 00000076. This bug check indicates that a driver failed to release the locked pages after an i/o operation, or that he tried to unlock pages that have already been released.

    Bug UNEXPECTED_INITIALIZATION_CALL control has a value of 0 x 00000033.

    This bug check appears very rarely.

  • What doesWhat is the cause of the msg blue screen error stop: 0 x 90909220, 0xBF94BAD1, 0 x 00000000, 0 x 00000000?

    Under XP SP3

    As the forums MS Answers does not prompt for any information system when a new question is asked, we know absolutely nothing about your system.

    Not knowing the basic information a problem prolongs the frustration and the agony of these issues.

    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?

    What is your Internet browser and version?

    Your system's disks IDE or SATA drives?

    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 question was preceded by a loss of power, aborted reboot or abnormal termination?  (this includes the plug pulling, buttons power, remove the battery, etc.)

    The afflicted system has a working CD/DVD (internal or external) drive?

    You have a genuine XP installation CD bootable, which is the same Service as your installed Service Pack (this is not the same as any recovery CD provided with your system)?

    Do you see that you think not you should see and when you see it?

    What do not you think that you should see?

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

    Your system seems to start OK and then crash or didn't he start not at all?
    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:
    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.
    Now provide more information about your system and data against more recent accidents.
    Click Start, run and enter in the box:
    Msinfo32
    Click on OK and when the system info summary appears, click on Edition, select all, copy, and then paste the information here.
    For information about video drivers, expand components, click view, click on edit, select all, copy and then paste the information here.
    There will be some personal information (such as the user name and the name of the system), and anything that turns information private for you, simply delete the pasted information.
    This will minimize back Q & A and eliminate guesswork.
    Download BlueScreenView here:
    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.

    Sometimes BlueScreenView will involve XP files as being the cause of the accident (ntoskrl.exe, win32k.sys, hal.dll etc.) but they are probably not the real cause of the accident (BSV is doing the best he can).  You will need to either pick up some example crashes over and look through them, or find somewhere the XP files are not the 'cause' or you can upload your files to your SkyDrive crash dump and someone with the windows debugging tools can help take a look at them more closely.

    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 Notepad, WordPad, etc.), select all (Ctrl-A), copy all the text in the Windows Clipboard (Ctrl-C) and paste the text to the Clipboard (Ctrl-V) back here 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: Mini102911 - 02.dmp
    Crash time: 2011-10-29 04:54:36
    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
    Plant address: ntoskrnl.exe + 22f43
    Stack address 1: i8042prt.sys + 27fb
    Stack address 2: i8042prt.sys + 2033
    Battery 3 address: ntoskrnl.exe + 6e715
    Computer name:
    Full path: C:\WINDOWS\Minidump\Mini102911-02.dmp
    Number of processors: 4
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 94 208
    ==================================================

    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.

  • That means the closing blue screen problem down in WinXP? DMP attached.

    Received the blue screen error and need help to interpret .dmp file. Having read the advice here and don't understand the error.

    DMP link here. Can someone please help?
    https://SkyDrive.live.com/redir.aspx?CID=5de3dc24cafcbc7c&RESID=5DE3DC24CAFCBC7C! 136 & authkey = TPC026azOCU % 24

    The dump file suggests that Hitman Pro is the culprit.  They just released a new version last week.

    Here's what the dump file has to say:

    ==================================================
    Dump file: Mini100311 - 01.dmp
    Crash time: 03/10/2011 15:38:19
    Bug Check String: KERNEL_MODE_EXCEPTION_NOT_HANDLED
    Bug check code: 0x1000008e
    Parameter 1: 0xc0000005
    Parameter 2: 0x806048f9
    Parameter 3: 0xa6d6baf0
    Parameter 4: 0x00000000
    Caused by the driver: hitmanpro35.sys
    Caused by the address: hitmanpro35.sys + 1ab5
    Description of the file:
    Product name:
    Company:
    Version of the file:
    Processor: 32-bit
    Computer name:
    Full path: C:\WINDOWS\Minidump\Mini100311-01.dmp
    Number of processors: 1
    Main version: 15
    Minor Version: 2600
    Size of the dump file: 65 536
    ==================================================

    You only install only recently?  You can uninstall, reboot and see what things look like.  If things look better without it, you can be sure that you use the latest version.

    I used BlueScreenView to interpret the dump file and so you can next time.

    Download BlueScreenView here:
    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.

    You can always put stuff on your SkyDrive of course if you need another set of eyeballs - BSV is not perfect - sometimes you have to dig deep with the windows debugging tools.

  • Need help with a DMP file. Windows XP

    Hello guys!

    Need your help impeccable with a dmp file? What is the problem causing blue screen?
    Thank you for the kind help!

    Hello Molphyr,

    The first discharge seems to have been caused by viahduaa.sys and it should be updated.  My comments on the discharge are in bold:

    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    100000 1 error checking, {a824a000, 2, 0, acc5e0d8}

    Probably caused by: viahduaa.sys (viahduaa + 280d 8)<-- debugger="" suspects="" this="">

    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: a824a000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: acc5e0d8, address memory

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

    READ_ADDRESS: a824a000

    CURRENT_IRQL: 2

    FAULTING_IP:
    viahduaa + 280d 8
    acc5e0d8 3b0f cmp ecx, dword ptr [edi]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0XD1

    LAST_CONTROL_TRANSFER: from acc6134c to acc5e0d8

    STACK_TEXT:
    WARNING: Information not available stack unwind. Sequence of images may be wrong.
    acc6134c 80551384 a8249fe0 00000020 a8249fe0 viahduaa + 0x280d8<---driver is="" at="" top="" of="">
    805513a 8 acd8d676 847bcd58 a8249fe0 a9abcc80 viahduaa + 0x2b34c
    805513d 0 80551401 00000020 80551400 portcls acd8d945! CPortPinWaveCyclic::Copy + 0 x 56
    80551410 acd877bf 00024fa0 8055c0c0 ffdff000 portcls! CPortPinWaveCyclic::RequestService + 0 x 298
    80551428 80545ebf 847 4238 4228 portcls 00000000 847c c! CServiceGroup::ServiceDpc + 0x2a
    8055be60 80551440 ffdffc50 00000000 8055be60 nt! KiRetireDpcList + 0x61
    80545da4 80551450 0000000e 00000000 00000000 nt! KiIdleThread0
    80551454 00000000 0000000e 00000000 00000000 nt! KiIdleLoop + 0 x 28

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    viahduaa + 280d 8
    acc5e0d8 3b0f cmp ecx, dword ptr [edi]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: viahduaa + 280d 8

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: viahduaa

    Nom_image: viahduaa.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a24e854

    FAILURE_BUCKET_ID: 0xD1_viahduaa + 280d 8

    BUCKET_ID: 0xD1_viahduaa + 280d 8

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

    0: kd > lmvm viahduaa
    start end module name
    acc36000 acd85900 viahduaa T (no symbol)
    Loaded symbol image file: viahduaa.sys
    Image path: viahduaa.sys
    Image name: viahduaa.sys
    Timestamp: Kills Jun 02 03:52:36 2009 (4A24E854)<--- driver="" from="" 2009-="" should="" be="">
    CheckSum: 00156D7B
    ImageSize: 0014F900
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Let us know if you have any questions.

    Best regards

    Matthew_Ha

  • 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:
    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:
    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.

  • c;windows\minidump\mini09513-09.dmp

    What is c? I have to crash on my computer

    We need the DMP file because it contains the single record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.

    WE NEED AT LEAST TWO FILES DMP TO SPOT TRENDS AND TO CONFIRM THE DIAGNOSIS.

    If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.
    You may be able to get the DMP files without crashing by booting in SafeMode (F8) with networking.
    If you are overclocking stop.  (chances are that if you are unsure if you are, you are not)
    To allow us to help you with symptoms BSOD on your computer, download the contents of your folder "\Windows\Minidump".
    The procedure:
    * Copy the contents of \Windows\Minidump to another location (temporary) somewhere on your machine.
    * Zip up the copy (compress)
    * Please download to a service like Skydrive or "Rapidshare" to share files and put a link to them in your answer.
    Link to find out how to download below.
    To ensure the minidumps are enabled:
    * Click Start, in the search box, type: sysdm.cpl, press ENTER.
    * On the Advanced tab, click Startup and recovery... Settings button.
    * Make sure that automatically restart is unchecked.
    * Under the writing debugging information header, select image partial memory (256 KB) in the list box drop-down (varies from 256kb).
    * Ensure to that small Dump Directory is listed as % systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and download the output as well.
    To run MSinfo32 please go to start > run > MSinfo32
    Go to 'file', 'save' and download the PDF is saved with the DMP
    System specs are extremely useful then please include everything you know.

    Blue screen view and that crashed are often wrong and should only be used in case of emergency...

    You can learn more about BSOD here
    You will learn how to test your memory here 
    An effective question gets help more quick read how here


    Team Zigzag3143.com  

  • Help..! I got the blue screen and other issues, do not know what to do...

    Signature of the problem:
    Problem event name: BlueScreen
    Please help me, I got the blue screen and this message today while I was trying to solve a problem with the backup of my pc...
    Don't know what to put here, if you need more make me know... Thank you

    The system version: 6.0.6002.2.2.0.768.3
    Locale ID: 1033

    More information about the problem:
    BCCode: 8086
    BCP1: 00000000
    BCP2: 00000000
    BCP3: 00000000
    BCP4: 00000000
    OS version: 6_0_6002
    Service Pack: 2_0
    Product: 768_1

    Files helping to describe the problem:
    C:\Windows\Minidump\Mini030513-01.dmp
    C:\Users\Andy\AppData\Local\Temp\WER-59483-0.SysData.XML
    C:\Users\Andy\AppData\Local\Temp\WERF871.tmp.version.txt

    Read our privacy statement:
    http://go.Microsoft.com/fwlink/?LinkId=50163&clcid=0x0409

    Hello

    Thanks for posting the question in the Microsoft Community!

    To help you better, we need more information.

    What is brand and model computer?

    To work with the issue, I suggest you check out the site:

    How to fix a blue screen stop errors that cause Windows Vista to shut down or restart unexpectedly

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

    Note: When you restore the system to a previous state, programs and updates installed later will be deleted.

    Note: When you format a disk, all data that it would disappear.

    It would be useful for us to identify the problem, if you could upload the dump file.

    You can use the Sky-drive to download the dump file. See the link for the steps on how to download Sky-Drive.

    Download pictures and files:

    http://Windows.Microsoft.com/en-in/SkyDrive/add-photos-files-FAQ

    The location of the dump file is C:\Windows\Minidump\.

    If the problem persists, or in the future if you face problems of Windows let us know and we would be happy to help you.

Maybe you are looking for