Download of dumps

Hey Microsoft:

I was informed by a Microsoft technology to download a crashdump.  From a previous post, it's about a specific piece of software the BSOD caused.   In any case... Who should I send the image file and the address where I could send.  (As this is not a site where you can view copies of graphics).  In addition, currently I don't have the software to read the file.  I have to make another copy of "crashed".

Thank you

stanulg

Please see if these instructions on downloading files on your OneDrive help.

1 copy all the files to download in one place or the folder in Windows Explorer.

2. click on this link: https://onedrive.live.com/

3. click on download.

4. navigate in Windows Explorer to the location where you have placed the file (s).

5. place the cursor on the downloaded file and click the Open button.

6. you will need to repeat steps 3 through 5 for each file you download several files.

7 move the cursor over each file to be shared, check the box in the upper right of the file and click on part.

8. click on get a link and use the scroll to change the entry under Select an option to view only to change.

9. click on the Create link button.

10. click on link shorten.

11 place the cursor on the link in the box under the Publicand right click. Selectfrom the drop down menu,select all , and then select copy to place the address to your Clipboard.

12 place the cursor in an open here message, right click and select Paste.

13. When you paste links into a message here please go to end of the link, press the SPACEBAR , then the key ENTRY . It helps another person open the link more easily. The link in the message of change and blue.

Tags: Windows

Similar Questions

  • 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

  • Update of Internet Explorer 9 and crash to get instant dumping errors blue screen for nvidia

    Cannot run any hardware nvidia screen when starting explore 9 or by a service pak, without a computer by launching a "crashdump" blue towards the top and windows not start correctly and trying to 'settle' which may not

    Hello

    1. What is the exact error message and the error code that you get in the blue screen?

    Download the dump file for us to analyze the issue.

    The dump file location: my computer > C drive > Windows folder > Minidump folder > Minidump files.

    For the procedure on how to upload the dump files so that we can use them, open the site mentioned below:

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65.

    Method 1: update the driver

    If you are able to boot to the desktop then update the graphics card.

    For instructions on how to update driver, please see the site mentioned below:

    http://windows.microsoft.com/en-US/windows7/Update-a-driver-for-hardware-that-isn ' t-work correctly.

    Method 2: Reinstall the driver

    a. click Start, type devmgmt.msc in the start search box and press enter

    b. right-click on the device and click on uninstall. Restart the computer and allow the driver to install.

     

    You can also consult the site mentioned below:

    http://windows.microsoft.com/en-US/windows-vista/Picking-up-the-pieces-after-a-computer-crash.

  • SBS 2011 BSOD - installation of Hyper V.

    Hi, I'm under SBS 2011 STD in a Hyper-V environment (host operating system: Windows 2008 R2 enterprise Core), after installation, activation & update completely I seem to be getting the BSOD. This problem only resides on the VM not the kernel.

    I ran the file minidump via the debugger tools and found that the module that has been failing: nt, name of the image: ntkrnlnp.exe, so the Windows kernel. The bug check is: the bugcheck was: 0 x 00000018 (0xfffffa800ad803f0, 0 x 0000000000000002, 0 x 0000000000000000, 0xffffffffffffffff). A dump was saved in the: C:\Windows\MEMORY. DMP. Report ID: 010912-12625-01
    The results of the minidump are:
    Debugging information:
    ------------------
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
    BUGCHECK_STR: 0 X 18
    Nom_processus: svchost.exe
    CURRENT_IRQL: 0
    LAST_CONTROL_TRANSFER: from fffff80001624944 to fffff80001683c40
    STACK_TEXT:
    fffff880'03dd2428 fffff800'01624944: fffffa80 00000000'00000018 00000000'00000000 ' 0ad803f0 00000000'00000002: nt! KeBugCheckEx
    fffff880 '03dd2430 fffff800' 0197a7b9: fffff880 '03dd2ca0 fffff880' 03dd27f0 00000000' 0000001 has 00000006' 00000000: nt! : FNODOBFM: 'string' + 0x49d71
    fffff880 '03dd2490 fffff800' 0197aaee: 00000000'00000001 00000000'00000000 00000000'00000001 00000000'00000001: nt! ObpWaitForMultipleObjects + 0x2d3
    fffff880 '03dd2960 fffff800' 01682ed3: fffffa80 '09d9e590 00000000' 00d6fb18 fffff880 '03dd2bc8 fffff880' 03dd2c00: nt! NtWaitForMultipleObjects + 0xe5
    fffff880 '03dd2bb0 00000000' 775c18ca: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSystemServiceCopyEnd + 0x13
    00000000' 00d6faf8 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x775c18ca
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    NT! : FNODOBFM: 'string' d + 49 71
    fffff800'01624944 cc int 3
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: nt! : FNODOBFM: 'string' d + 49 71
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    Nom_image: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
    FAILURE_BUCKET_ID: X64_0x18_OVER_DEREFERENCE_nt! _ ?? _::FNODOBFM:_string_ + 49 d 71
    BUCKET_ID: X64_0x18_OVER_DEREFERENCE_nt! _ ?? _::FNODOBFM:_string_ + 49 d 71
    Follow-up: MachineOwner
    ---------
    No details of idDebugging:
    ------------------
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
    BUGCHECK_STR: 0 X 18
    Nom_processus: svchost.exe
    CURRENT_IRQL: 0
    LAST_CONTROL_TRANSFER: from fffff80001624944 to fffff80001683c40
    STACK_TEXT:
    fffff880'03dd2428 fffff800'01624944: fffffa80 00000000'00000018 00000000'00000000 ' 0ad803f0 00000000'00000002: nt! KeBugCheckEx
    fffff880 '03dd2430 fffff800' 0197a7b9: fffff880 '03dd2ca0 fffff880' 03dd27f0 00000000' 0000001 has 00000006' 00000000: nt! : FNODOBFM: 'string' + 0x49d71
    fffff880 '03dd2490 fffff800' 0197aaee: 00000000'00000001 00000000'00000000 00000000'00000001 00000000'00000001: nt! ObpWaitForMultipleObjects + 0x2d3
    fffff880 '03dd2960 fffff800' 01682ed3: fffffa80 '09d9e590 00000000' 00d6fb18 fffff880 '03dd2bc8 fffff880' 03dd2c00: nt! NtWaitForMultipleObjects + 0xe5
    fffff880 '03dd2bb0 00000000' 775c18ca: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt
    ! KiSystemServiceCopyEnd + 0x13
    00000000' 00d6faf8 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x775c18ca
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    NT!
    ? : FNODOBFM: 'string' d + 49 71
    fffff800'01624944 cc int 3
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: nt! : FNODOBFM: 'string' d + 49 71
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    Nom_image: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
    FAILURE_BUCKET_ID: X64_0x18_OVER_DEREFERENCE_nt! _ ?? _::FNODOBFM:_string_ + 49 d 71
    BUCKET_ID: X64_0x18_OVER_DEREFERENCE_nt! _ ?? _::FNODOBFM:_string_ + 49 d 71
    Follow-up: MachineOwner
    ---------
    I can't find a reason as any for what is originally to failure.

    Hello

    I am happy to have a look at this, you can download the dump,

    http://mikemstech.blogspot.com/2010/08/SkyDrive-uploading-files-for-community.html

  • Problem with MS flight Simulator & acceleration. __Problem signature: problem event name: BlueScreen__ OS Version: 6.1.7600.2.0.0.768.3__ locale ID: 1033

    Signature of the problem:
    Problem event name: BlueScreen
    OS version: 6.1.7600.2.0.0.768.3
    Locale ID: 1033

    More information about the problem:
    BCCode: d1
    BCP1: FFFFF80003BA6F4A
    BCP2: 0000000000000002
    BCP3: 0000000000000008
    BCP4: FFFFF80003BA6F4A
    OS version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Files helping to describe the problem:
    C:\Windows\Minidump\061410-12448-01.dmp
    C:\Users\Joseph\AppData\Local\Temp\WER-21777-0.SysData.XML

    Read our privacy statement online:
    http://go.Microsoft.com/fwlink/?LinkId=104...MP;clcid=0x0409

    If the online privacy statement is not available, please read our offline privacy statement:
    C:\Windows\system32\en-US\erofflps.txt

    Joseph Blair

    System Specs:
    Mobo: Asus P6x58d Premium
    Processor: Refrigerated by an Intel i7 980 x (4.5 oc) liquid
    6 GB of DD3 RAM
    Intel SSD boot drive 40 GB W7 Home
    2 x 300 GB WD Velociraptor (dedicated FSX drive)
    HIS ATI Radeon 5870 GPU (oc of factory)
    PSU Corsair TX950W (7 fans)
    NZXT fan controller
    Corsair 800 d case

    Hi Joseph,.

    (a) when exactly you get this error message?

    (b) was your game works well before?

    Error messages on blue screen are normally related to the material, the following steps are worth a try:

    Step 1: Disconnect all external devices (printers, scanner, USB(universal serial bus) readers, etc...) Except the keyboard and mouse, then do a test

    Step 2: Put the computer to clean and test start

    Follow step 1 in the link below,

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

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

    Important: n ' forget not the computer to start normal follow step 7 in the link.

    If the problem persists, please download the dump on Sky Drive file and share the link with us for analysis

    SkyDrive.live.com

    Available at the location file

    C:\Windows\Minidump\061410-12448-01.dmp

    You might want to know

    How read partial memory dump files that Windows creates for debugging

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

    Thank you, and in what concerns:

    Ajay K

    Microsoft Answers Support Engineer

    Visit our Microsoft answers feedback Forum and let us know what you think.

  • Blue screen when you unplug the power of the computer dell laptop XP

    I have a dell latitude E6500... problems with blue screen when I unplug the laptop.  his past about 5 out of 10 times now.  Ive updated all recommended microsoft updates and it is still the case?  is there a driver for xp needed to solve this problem?  It only happens when I unplug the power cord and it happens as soon as I unplug

    Hello suncoastsrq,

    Usually, when we see problems during shutdown, the cause is something that loads at startup.

    To this end, I would recommend mode startup minimum troubleshooting as seen in the following articles:

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

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

    Please note that after refine us the cause, it is important that we return to a normal startup and manually delete the startup program.

    In addition, if we can get downloaded discharge, the community has access to them and will probably be able to determine the cause.

    You can download the dump Auggy's previous suggestion?

    Let us know.

    Best regards

    Matthew_Ha

  • Laptop crashes when you use an external monitor

    Hi, my laptop still crashes when using an external monitor. So far ive tried s-video and vga, but still no joy. This can happen after a few minutes or sometimes after a good few hours, and it seems to crash more frequently during playback of movies, games etc... There are a few signatures of different problem most to come including this one:

    Signature of the problem:

    Problem event name: BlueScreen

    The system version: 6.0.6002.2.2.0.768.3

    Locale ID: 2057

    More information about the problem:

    BCCode:                                              116

    BCP1:                                                   8688F510

    BCP2:                                                   8E01FB5A

    BCP3:                                                   00000000

    BCP4:                                                   0000000D

    OS version: 6_0_6002

    Service Pack: 2_0

    Product:                                              768_1

    Files helping to describe the problem:

    C:\Windows\Minidump\Mini012710-01.dmp

    C:\Users\Jack\AppData\Local\Temp\WER-62384-0.SysData.XML

    C:\Users\Jack\AppData\Local\Temp\WERF852.tmp.version.txt

    Read our privacy statement:

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

    Maybe a problem with my graphics card drivers? This is my first post and I'm not sure if this is really anything that someone would be able to help me with that I don't really know anything about the wiretap, but tips are very much appreciated.

    Vista 32 bit

    ATI Mobility Radeon HD 2600 graphics card

    Thank you

    Hello j.d.1882,

    1. you have the latest drivers installed for your graphics card?

    I suggest that you update the drivers for the graphics card and check if the computer continues to crash.

    In addition, I suggest that you download the dump files to check exactly what may cause the problem.

    Athttp://skydrive.live.com using your Live ID and I will check:

    a. Click Start, select run, type '% SystemRoot%\Minidump' (without the quotes) in the search box and press ENTER.

    b go to your desktop, right-click on it and create a new folder named "Dump".

    c. copy all the files in memory dump (it looks like Mini092003 - 01.DMP) in Minidump in this folder.

    d. right click on the folder of the image, click on "send to" and click on "compressed file (zipped).

    e. Please download the ZIP file.

    You can check the link for more information below:

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

    Thank you
    Irfan H, Engineer Support Microsoft Answers. Visit ourMicrosoft answers feedback Forum and let us know what you think.

  • Windows XP - what is this BSOD code meaning? And how to solve?

    BAD_POOL_CALLER * STOP: 0X000000C2 (0X00000CD4, 0X8175A2E8, 0 X 0000007, 0XB8A6B448)

    The details of the error checking (double free) suggest memory corruption occurs.  This may be due to a hardware failure (defective RAM, for example), or a bad/buggy driver or a driver that is not designed for the version of Windows you are using. Consider using driver verifier as described below, to determine which driver is corrupting the memory.

    General to deal with the bluescreens indications:

    Consider running chkdsk on all partitions.  Leave complete chkdsk on each partition and see if that helps.

    It may be useful to use the driver verifier.  To activate the... Driver Verifier start-> verifier.exe-> OK-> create standard settings-> next-> driver select the names to a list-> next-> sort by provider-> select all other Microsoft drivers-> finish and OK your way out of the dialog box.

    Then restart and use the system as you normally and wait for a problem.  In case the system does not completely start after activation of the Verifier, boot mode safe and run driver verifier and tell him to remove the changes.

    Wait for an error checking to happen after you have enabled the auditor as described and then download the dump on your SkyDriveand provide a link.

    Also consider running SFC/scannow.

    If you start in safe mode, do you still feel bugs? What if you do a clean boot, or boot device?

    Consider the memory with memtest86 or Windows Memory Diagnostic test. Note that memory that pass the tests isn't necessarily good memory - he not only failed a review.  Examine systematically to eliminate the system RAM - run with a few modules for awhile and see how things are going. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date, but also to ensure that you use the latest version of the BIOS.

  • Crash on the screen of Microsoft Corporation

    Screen kick upward and crashed to the 'Microsoft Corporation '. Power off then again, chose that recommended such startup repair. Asked and chose to restore. Computer seems to be working fine now but this accident shows everything what should I be concerned about?

    X 64 Vista Home Premium.

    Thank you.

    Thanks for the reply.

    I had no problem since the accident. I suspect she had to with a game that requires plug above me. During playback, I got a lot of slowdown and other problems and I uninstalled. If I hire this problem once again I locate and download the dump files and post in this thread again.

    I see two other people have had this problem and I hope that they have been able to resolve things.

    Thanks again.

    VFNNJ

  • BUGCHECK_STR: 0X7E

    Microsoft (R) Windows debug 6.2.9200.20512 AMD64 Version
    Copyright (c) Microsoft Corporation. All rights reserved.

    Command line: C:\Windows\Minidump\Mini081113-01.dmp
    Cannot run 'C:\Windows\Minidump\Mini081113-01.dmp', 0n193 error Win32
    "%1 is not a valid Win32 application".

    Loading dump file [C:\Windows\Minidump\Mini081113-01.dmp]
    The mini kernel dump file: only registers and the trace of the stack are available

    Symbol search path is: * invalid *.
    ****************************************************************************
    * Loading of the symbol may be unreliable without a symbol search path.           *
    * Use .symfix to get the debugger to choose a symbol path.                   *
    * After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols cannot be loaded because the path is not initialized. *
    *                                                                   *
    * The symbol path can be defined: *.
    * using the _NT_SYMBOL_PATH environment variable.                 *
    * with the help of the there when you start the debugger argument. *.
    * using the .sympath and .sympath + *.
    *********************************************************************
    Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
    WARNING: Unable to verify timestamp for ntoskrnl.exe
    ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack2) MP (2 processors) free x 64
    Product: WinNt, suite: TerminalServer personal TerminalServer
    Computer name:
    Kernel base = 0xfffff800 '02257000 PsLoadedModuleList = 0xfffff800' 0241bdd0
    The debugging session: Sun Aug 11 21:26:06.348 2013 (UTC - 04:00)
    System Uptime: 0 days 0:00:46.144
    *********************************************************************
    * Symbols cannot be loaded because the path is not initialized. *
    *                                                                   *
    * The symbol path can be defined: *.
    * using the _NT_SYMBOL_PATH environment variable.                 *
    * with the help of the there when you start the debugger argument. *.
    * using the .sympath and .sympath + *.
    *********************************************************************
    Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
    WARNING: Unable to verify timestamp for ntoskrnl.exe
    ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
    Loading the kernel symbols
    ...............................................................
    ................................................................
    .....
    Loading user symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    Bugcheck 1000007E, {ffffffffc0000005, fffff800024f5609, fffffa6001bd94d8, fffffa6001bd8eb0}

    The kernel symbols are FALSE. Correct symbols to do the analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Either you have specified an absolute symbol, or your debugger *.
    has no information complete symbol.  Absolute symbol *.
    resolution is disabled by default. Please specify a *.
    complete symbol module! NomSymbole, or activate the resolution *.
    symbols unskilled by typing '.symopt 100 '. Note that *.
    allowing unqualified symbol with the network symbol resolution *.
    shares of server in the symbol path can cause the debugger to *.
    appear to hang for long periods of time when an incorrect *.
    symbol name is typed or the symbol of the network server is down.     ***
    ***                                                                   ***
    For some commands work properly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Either you have specified an absolute symbol, or your debugger *.
    has no information complete symbol.  Absolute symbol *.
    resolution is disabled by default. Please specify a *.
    complete symbol module! NomSymbole, or activate the resolution *.
    symbols unskilled by typing '.symopt 100 '. Note that *.
    allowing unqualified symbol with the network symbol resolution *.
    shares of server in the symbol path can cause the debugger to *.
    appear to hang for long periods of time when an incorrect *.
    symbol name is typed or the symbol of the network server is down.     ***
    ***                                                                   ***
    For some commands work properly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Either you have specified an absolute symbol, or your debugger *.
    has no information complete symbol.  Absolute symbol *.
    resolution is disabled by default. Please specify a *.
    complete symbol module! NomSymbole, or activate the resolution *.
    symbols unskilled by typing '.symopt 100 '. Note that *.
    allowing unqualified symbol with the network symbol resolution *.
    shares of server in the symbol path can cause the debugger to *.
    appear to hang for long periods of time when an incorrect *.
    symbol name is typed or the symbol of the network server is down.     ***
    ***                                                                   ***
    For some commands work properly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    Probably caused by: ntoskrnl.exe (nt + 29e609)

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

    0: kd > g
    ^ No executable debuggees error in 'g '.
    0: kd >! analyze - v
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    It is a very common bugcheck.  Usually the PIN address of exception
    the driver/function that caused the problem.  Always note this address
    and the date of the picture link / driver that contains this address.
    Some common problems are the exception code 0 x 80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system has been started
    / /NODEBUG.  It is not supposed to happen as developers should never have
    breakpoints coded hard in retail code, but...
    In this case, make sure a debugger must be connected and the
    system startup/DEBUG.  This will we will see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, unhandled exception code
    Arg2: fffff800024f5609, the address that the exception occurred at
    Arg3: fffffa6001bd94d8, address of Exception report
    Arg4: fffffa6001bd8eb0, address of the context record

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

    The kernel symbols are FALSE. Correct symbols to do the analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Either you have specified an absolute symbol, or your debugger *.
    has no information complete symbol.  Absolute symbol *.
    resolution is disabled by default. Please specify a *.
    complete symbol module! NomSymbole, or activate the resolution *.
    symbols unskilled by typing '.symopt 100 '. Note that *.
    allowing unqualified symbol with the network symbol resolution *.
    shares of server in the symbol path can cause the debugger to *.
    appear to hang for long periods of time when an incorrect *.
    symbol name is typed or the symbol of the network server is down.     ***
    ***                                                                   ***
    For some commands work properly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Either you have specified an absolute symbol, or your debugger *.
    has no information complete symbol.  Absolute symbol *.
    resolution is disabled by default. Please specify a *.
    complete symbol module! NomSymbole, or activate the resolution *.
    symbols unskilled by typing '.symopt 100 '. Note that *.
    allowing unqualified symbol with the network symbol resolution *.
    shares of server in the symbol path can cause the debugger to *.
    appear to hang for long periods of time when an incorrect *.
    symbol name is typed or the symbol of the network server is down.     ***
    ***                                                                   ***
    For some commands work properly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    Either you have specified an absolute symbol, or your debugger *.
    has no information complete symbol.  Absolute symbol *.
    resolution is disabled by default. Please specify a *.
    complete symbol module! NomSymbole, or activate the resolution *.
    symbols unskilled by typing '.symopt 100 '. Note that *.
    allowing unqualified symbol with the network symbol resolution *.
    shares of server in the symbol path can cause the debugger to *.
    appear to hang for long periods of time when an incorrect *.
    symbol name is typed or the symbol of the network server is down.     ***
    ***                                                                   ***
    For some commands work properly, your symbol path *.
    should point to .pdb files have the type information complete.      ***
    ***                                                                   ***
    Some (such as the public OS symbols) .pdb files are not *.
    contain the required information.  The contact group that *.
    you provided with these symbols, if you need this command for *.
    work.                                                          ***
    ***                                                                   ***
    Type referenced: nt! _KPRCB *.
    ***                                                                   ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:
    You can run '.symfix; .reload' to try to fix the symbols path and of loading symbol.

    MODULE_NAME: nt

    FAULTING_MODULE: fffff80002257000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 513a94a9

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - the instruction at 0 x % lx 08 referenced memory at 0 x % 08 lx. The memory could not be %s.

    FAULTING_IP:
    NT + 29e609
    fffff800'024f5609 430fb70c11 movzx ecx, word ptr [r9 + r10]

    EXCEPTION_RECORD: fffffa6001bd94d8-(.exr 0xfffffa6001bd94d8)
    Can not read the Exception record @ fffffa6001bd94d8

    CONTEXT: fffffa6001bd8eb0-(.cxr 0xfffffa6001bd8eb0)
    Cannot read the context, Win32 error 0n30

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0X7E

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff800024c885a to fffff800024f5609

    STACK_TEXT:
    "fffffa60 '01bd9718 fffff800' 024c885a: fffff800'024528 b 0 fffffa80 ' 036 c 8800 00000000 00000000' fffffa80 ' 07b604c0: nt + 0x29e609
    "fffffa60 '01bd9720 fffff800' 024528b 0: fffffa80 ' 036 c 8800 00000000 00000000' fffffa80 ' 07b604c0 00000000' 00000000: nt + 0x27185a
    fffffa60'01bd9728 fffffa80'036 c 8800: 00000000 00000000' fffffa80 '07b604c0 00000000 00000000' fffffa60' 01bd97f0: nt + 0x1fb8b0
    fffffa60'01bd9730 00000000' 00000000: fffffa80'07b604c0 00000000 00000000' fffffa60 '01bd97f0 fffffa60' 02af5b01: 0xfffffa80'036 c 8800

    FOLLOWUP_IP:
    NT + 29e609
    fffff800'024f5609 430fb70c11 movzx ecx, word ptr [r9 + r10]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt + 29e609

    FOLLOWUP_NAME: MachineOwner

    Nom_image: ntoskrnl.exe

    STACK_COMMAND: .cxr 0xfffffa6001bd8eb0; Ko

    BUCKET_ID: WRONG_SYMBOLS

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

    0: kd > .exr 0xfffffa6001bd94d8
    Can not read the Exception record @ fffffa6001bd94d8
    0: kd > .cxr 0xfffffa6001bd8eb0
    Cannot read the context, Win32 error 0n30
    0: kd > .cxr 0xfffffa6001bd8eb0
    Cannot read the context, Win32 error 0n30

    Hello

    Please download the dump, as requested by zig - zag file. In the meantime, let us know exactly when you get the error message and also refer to the following article explains the generally why a control bug 0x7E occurs and what can be tried to solve the problem.

    http://msdn.Microsoft.com/en-us/library/Windows/hardware/ff559239 (v = VS. 85) .aspx

    Hoping to hear from you soon.

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

  • Irql_not_less_or_equal blue help screen / / / 0x0000000A

    Hello! Recently I was making a few different blue screens. After a few different system restores, I only get 1 now. It's the irql_not_less_or_equal.

    For a few months now, I was not using my computer until within the last few days, because for a while, I need new RAM. And I thought I needed a new graphics card, because I had problems with my monitor (it became very pixelated/signs of him dying). Although, I don't have my installed latest graphics card.

    My computer will last between 5-15 minutes until I get this blue screen.

    I went from 2 GB of RAM DDR2 up to 8 GB DDR3 (2 of 4 GB each). Recently, I was not able to boot my computer. After hours of trying to figure out why, I watched my RAM and 1 of them had burnt/burned some how. I don't know when or why. POM I have removed that one and I kept the right thing and put it on the opposite side of where the other burned. Because I had removed the charred/burnt RAM, I am now able to boot my computer very well.

    I am currently using my old graphics (NVIDIA Geforce 8500 GT)
    My system specs are:

    Windows Vista Edition Home Premium
    Service Pack 2
    Processor: Intel (r) Pentium (r) D CPU 3.73 GHz
    (Vivid RAM) memory: 4.00 GB
    System type: 32-bit

    Windows Update is current. Each update it can find, I installed. My graphics card is up-to-date as well. I ran a memtest86 + on my 1 stick of 4 GB of RAM, and it found no problem. I also used Rkill, MalwareBytes, and MSE to see if it was virus/etc. related. No problem.

    I wrote down the info, when I saw a blue screen. This was also the last blue screen, I'm currently in Mode safe mode w / Networking:
    Irql_not_less_or_equal
    STOP: 0X0000000A (0X0000001B, 0X00000000, 0X00A20BA4, 0X830B8352)

    I'm not too familiar with the system logs/event viewer. So, I downloaded Blue Screen Viewer, (just in case). I'd appreciate any help!

    Thank you very much
    Cody

    Hi Cody,

     

    Please join Microsoft Community where you can find the necessary information on Microsoft products!

     

    You get bluescreen error Irql_not_less_or_equal STOP: 0x0000000A (0x0000001B, 0x00000000, 0x00A20BA4, 0x830B8352).

    The problem may occur if any of the hardware devices are defective or the drivers are corrupt.

    What is brand and model computer?

    To check if the problem is with a malfunction of the devices or drivers, I suggest you follow the steps described in the mentioned 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.

    WARNING: If you restore Windows from disk from the manufacturer, you will lose all the programs and data.

    Note: This article is also applicable to the Vista Service pack 2.

    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. Check the link for the steps on how to download Sky-Drive.

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65.

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

    I hope this helps. If the problem persists, let know us and we would be happy to help you.

  • Kodak ESP 3200 printer stops spool error and will not print. Tried many times from print print spooler. Following other instructions as starting all over. Nothing seems to work. Help

    Spooler subsystem App stopped working

    Event problem APPCRASH

    application name spoolsv.exe

    6.0.6002.18294

    exception code c0000374

    exception code c0000374

    This means that the heap corruption took place.

    Try installing the latest for your Kodak printer driver.

    If this doesn't fix it, please download this reg from my SkyDrive file:

    http://CID-128fc518635be2dc.Office.live.com/self.aspx/.public/Ms%20Foren/registry/LocalDumps.reg

    and double click on the file to import.

    When an application crashes, Windows Error Reporting Service [1] creates a dmp under C:\Localdumps. Please download the dump (zip it first) to your public Skydrive folder [2] and post the link here. I take a look at the discharge with the debugger, maybe that I can see the cause.

    André

    [1] http://msdn.microsoft.com/en-us/library/bb787181%28VS.85%29.aspx
    http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 [2]

    "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

  • Taskeng error (Vista Ultimate). PC will not properly shutdown

    Hey Microsoft board gurus,

    (Running Vista Ultimate on a Dell Optiplex 330)

    SHUTDOWN PROBLEM, here is what happens:

    1. I use start menu & off the pc.
    2. PC seems to turn off (but a few small red lights twinkling near the power button / at the front of the Tower & the rest of button IT turned on.)
    3. After about 10 minutes, the PC then restarts by itself
    4. He can complain about "an unscheduled stop.
    5. Then
    6. I stopped again, and finally, it shuts

    Sometimes to get it off, I have to make a hold in the power button.  I know that regularly isn't good for the computer.

    At some point after the pc auto-entrée back, he sent this taskeng error, so maybe this is a hint on the cause of the problem.

    • I tried to do a restore from the registry to May 7 (a date the pc was ok), tried ending taskeng before stopping, and I let a Windows system/repair/recovery Volume and still have the problem.
    • Thinking maybe the computer was in the middle of the installation of Windows updates when I turn me off my PC at night, I have reviewed the updates of Windows 'Important' that were pending / CCEd would be / available, and they are useless for me (Office 2007 and IE) and should not have been install.
    • I tried a few other things, and the problem happens even about half time or more when I turned off the PC for the night.
    • I spoke to Microsoft; they don't help me without paying because my license code Vista is OEM, meaning that Dell is responsible for helping me.  Dell will not help me without paying because they say that it is a software problem and those who are not included in no charge technical support and was told to talk to Microsoft.

    Any advice to get my computer to close normally again?  It is very annoying because it takes TWO stops in about 10 min. OR a hold-in button stop making my PC actually turn off.  The text of the error below.  Thank you.

    Signature of the problem:
    Problem event name: BlueScreen ((registry of means files are corrupt MATERIAL ts rep sales; AFTER this error if I post in the community))
    OS version: 6.0.6002.2.2.0.256.1
    Locale ID: 1033

    More information about the problem:
    BCCode: 9f
    BCP1: 00000003
    BCP2: 86DDA430
    BCP3: 86DE1348
    BCP4: 8460BE28
    OS version: 6_0_6002
    Service Pack: 2_0
    Product: 256_1

    Files helping to describe the problem:
    C:\Windows\Minidump\Mini050910-02.dmp
    C:\Users\Kurt Kirton\AppData\Local\Temp\WER-40029-0.sysdata.xml
    C:\Users\Kurt Kirton\AppData\Local\Temp\WERCAAD.tmp.version.txt

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

    You said Details of the bugcheck 0x9f - DRIVER_POWER_STATE_FAILURE. "This bug check indicates that the driver is in an inconsistent or invalid power state." The problem is that "a device object has been blocking an IRP for too long."

    You can download the contents of the c:\windows\minidump on SkyDrive and provide a link?

    Consider the following general guidelines for dealing with bluescreens.

    Consider running chkdsk on all partitions.  Leave complete chkdsk on each partition and see if that helps.

    Also consider running SFC/scannow.

    If you start in safe mode, do you still feel bugs? What if you do a clean boot, or boot device?

    Consider the memory with memtest86 or Windows Memory Diagnostic test. Note that memory that pass the tests isn't necessarily good memory - he not only failed a review.  Examine systematically to eliminate the system RAM - run with a few modules for awhile and see how things are going. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date, but also to ensure that you use the latest version of the BIOS.

    It may be useful to use the driver verifier.  To activate the... Driver Verifier start-> verifier.exe-> OK-> create standard settings-> next-> driver select the names to a list-> next-> sort by provider-> select all other Microsoft drivers-> finish and OK your way out of the dialog box.

    Then restart and use the system as you normally and wait for a problem.  In case the system does not completely start after activation of the Verifier, boot mode safe and run driver verifier and tell him to remove the changes.

    Wait for a bugcheck occurs after you have enabled the auditor as described, and then download the dump on your SkyDrive and provide a link.

  • Unexpected stops when the cd player is ejected

    Unexpected shutdown takes place if the cd player is ejected and a blue screen appears.

    Signature of the problem:
    Problem event name: BlueScreen
    OS version: 6.0.6002.2.2.0.768.2
    Locale ID: 16393

    More information about the problem:
    BCCode: d1
    BCP1: 00000000
    BCP2: 0000000 A
    BCP3: 00000000
    BCP4: 822A 7289
    OS version: 6_0_6002
    Service Pack: 2_0
    Product: 768_1

    Files helping to describe the problem:
    C:\Windows\Minidump\Mini070510-01.dmp
    C:\Users\Nireeksha\AppData\Local\Temp\WER-53477-0.SysData.XML
    C:\Users\Nireeksha\AppData\Local\Temp\WERF797.tmp.version.txt

    even bury them and cd playback is not possible.

    hardware problem is not detected.

    So can I please get acquainted with the appropriate problem I have and the clear solution for him...

    When the behavior started? Did you recently add or remove any hardware or software?

    , Start here: you can download the c:\windows\minidump content to SkyDrive and provide a link?  If you have trouble downloading the files, copy them to the c:\windows\minidump folder in a new folder on your desktop and upload them from there.  

    Consider the following general guidelines for dealing with bluescreens.

    Consider running chkdsk on all partitions.  Leave complete chkdsk on each partition and see if that helps.

    Also consider running SFC/scannow.

    If you start in safe mode, do you still feel bugs? What if you do a clean boot, or boot device?

    Consider the memory with memtest86 or Windows Memory Diagnostic test. Note that memory that pass the tests isn't necessarily good memory - he not only failed a review.  Examine systematically to eliminate the system RAM - run with a few modules for awhile and see how things are going. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date, but also to ensure that you use the latest version of the BIOS.

    It may be useful to use the driver verifier.  To activate the... Driver Verifier start-> verifier.exe-> OK-> create standard settings-> next-> driver select the names to a list-> next-> sort by provider-> select all other Microsoft drivers-> finish and OK your way out of the dialog box.

    Then restart and use the system as you normally and wait for a problem.  In case the system does not completely start after activation of the Verifier, boot mode safe and run driver verifier and tell him to remove the changes.

    Wait for a bugcheck occurs after you have enabled the auditor as described, and then download the dump on your SkyDrive and provide a link.

Maybe you are looking for