c;windows\minidump\mini09513-09.dmp

Similar Questions

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

  http://www.WikiHow.com/use-SkyDrive

  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  

• C:\Windows\Minidump\Mini060210-01.dmp

  I get this mess...

  "Windows has recovered from an unexpected shutdown.

  How can I get rid of this have looked for alternatives in the drop-down window and he says he can't fins questions?

  It was the first time that you got a crash/BSOD-blue screen bugcheck?  Were there of the last changes made to the system - a new hardware or software added or updated?

  You can download the contents of c:\windows\minidump on your SkyDrive?

  General to deal with the bluescreens indications:

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

  Also consider running SFC/scannow.

  It may be useful to use the driver verifier.  To activate the... Driver Verifier start-> verifier.exe-> OK-> create standard settings - > then-> the names of the drivers select in a list-> next-> sort by provider-> select all non-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 occur after you enable the auditor as described and then download it.

  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 (including video drivers), but also to ensure that you use the latest version of the BIOS.

• C:\Windows\Minidump\103010-19500-01.dmp

  Hello

  I'm running Windows 7 Ultimate 64 and I got an annoying problem. Whenever I play games online or use a program that has a high graphic content, for example: MS flight sim, after some time my PC blue screen. He says he performs a memory dump and gives a countdown. Once that the discharge has been completed and then restart Windows. Sometimes it just the program stops and tells me that it has stopped working. I tried to reinstall windows and even bought a new hard drive and it still does the same thing. I'm using 2 Gig of ram. I am told that Win 7 uses a lot of ram could be part of the problem? Here is the error message I receive after the blue screen. Any help you could give me would be greatly appreciated!

  BCCode: d1
  BCP1: 00000000FFFFFFFD
  BCP2: 0000000000000002
  BCP3: 0000000000000001
  BCP4: FFFFF8800F00D7E9
  OS version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1

  Locale ID: 2057

  Signature of the problem:
  Problem event name: BlueScreen
  The system version: 6.1.7600.2.0.0.256.1
  Locale ID: 2057

  More information about the problem:
  BCCode: d1
  BCP1: 00000000FFFFFFFD
  BCP2: 0000000000000002
  BCP3: 0000000000000001
  BCP4: FFFFF8800F00D7E9
  OS version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1

  Files helping to describe the problem:
  C:\Windows\Minidump\103010-19500-01.dmp
  C:\Users\my name\AppData\Local\Temp\WER-35303-0.sysdata.xml

  PAGE_FAULT_IN_NONPAGED_AREA (50) -invalid system memory was referenced.

  Nom_image: Unknown_Image

  DEBUG_FLR_IMAGE_TIMESTAMP: 0

  BUCKET_ID: CORRUPT_MODULELIST

  DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) - an attempt was made to access an address pageable (or completely invalid) at an interrupt request level (IRQL) that is too high.

  caused by the MS. directX driver So update your nVIDIA driver:

  Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
  Image name: nvlddmkm.sys
  Timestamp: Fri Jul 09 23:15:58 2010 (4C37918E)

  Error checking BAD_POOL_HEADER (19) , {3, fffff900c069cd80, fffff900c069cd7f, fffff900c069cd80}

  Probably caused by: Pool_Corruption

  The first and the last crash I come to the conclusion that you have a RAM problem.

  Please download memtest86 + [1] write a new bootable CD (use a CD - RW if possible) of ISO (download and use ImgBurn [2] for this), restart your PC and scan your RAM 4-5 h to find errors. If it detects errors, replace the faulty RAM.

  André

  [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
  [2] http://www.imgburn.com/index.php?act=download

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

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

• aid to the C:\Windows\Minidump\040413-14406-01.dmp

  I have a problem with Windows RT on the Surface, closing the table it restarts it self.
  can I open a session and get this.
  C:\Windows\Minidump\040413-14406-01.dmp
  C:\Users\bship_000\AppData\Local\Temp\WER-47265-0.SysData.XML
  C:\Windows\MEMORY. DMP

  Can someone help me with this problem?

  Hello

  Thanks for posting your question in the Microsoft Community forums.

  To provide the proper resolution, that I would need more information on your side.
  Did you the latest changes on the computer before this problem?

  Method 1:
  I suggest you to change the power plan settings and check if it helps.

  a. slide or press the Start button and click on Power Options.
  b. click "choose the power button.
  c. under parameters of start button / stop, expand the menu drop down.
  d. click stop.
  e. -press save changes.

  Check whether the problem is resolved.

  Method 2:
  If the problem persists, I suggest you run the disk check and check if it helps.

  drag to the right to go to the bar of charms.
  b. tap search and type command prompt.
  c. in the results left touch where it says guest and sweep upwards to bring up the options menu at the bottom of the screen.
  d. tap run as administrator.
  e. in the cursor flashing, type the following:

  Chkdsk /f /r

  See the article for more information.

  How stop (turn off) my PC?
  http://Windows.Microsoft.com/is-is/Windows-8/how-shut-down-turn-off-PC

  Hope this information helps you. If you need additional help or information on Windows, I'll be happy to help you.

• Difference between (minidump) and (memory.dmp)?

  Separated from this thread.

  is there a difference between (minidump) and (memory.dmp) I use windows 10

  The main difference is size. Memory dumps are larger and contain a bit more information.

  In most situations, it is best to configure the computer to produce a dump of memory the kernel in case of system failure. A complete memory dump is a very large file to manage so it is more convenient to work with kernel images of memory when you try to resolve the blue screen errors.

  I suggest that you change your dump file settings to produce an image kernel memory. Select the hotkey Win + X , Control Panel, system, advanced system settings, Advanced tab, and click the button settings to start recovery. Under system failure, select the checkboxes before to write an event to the system log and restart automatically. Change the option Write debugging information by using the scroll to the right for image kernel memory. Click OK , and in the next window, click apply and OK. Restart your computer to apply the changes.

• Help! read my windows minidump

  my windows xp sp3 pc restarts just trying to do a virus scan or other activities. It gives me a minidump and when it restarts itself, he said "my computer has recovered from a serious accident. Can someone please look at the attached here minidump and tell me what they think, what is the problem. Is there a tool to read the minidump? Thanks in advance for your help.

  I have provided the link to the minidump as I couldn't know how to attach a file here:

  www.Megaupload.com/?d=HCOA7ON4

  Thank you.

  Tharunam

  Hello

  If looked at the minidump - BSOD code bug 0x100000D1 check - file that is probably caused by:OAmon.sys (OAmon + 1415)
  OAmon.sys - is related to Online Armor Security Suite (11 / 01 / 2011)

  So first - try to uninstall this program.

  LC

• PAGE_FAULT_IN_NONPAGED_AREA (50) - Windows Server 2008

  Hi Microsoft supports the team.

  We have Windows server 2008 sp2 enterprise edition-32 bit, once a week, we started receive "PAGE_FAULT_IN_NONPAGED_AREA" error message on this subject. What error come server stops responding and blue screen came up with the error message above, after that, you need to restart the server to begin to work in!

  Please find below the log from the dump file:
  --------------------------------------------------------------------------------------------------------------------------------------------------

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

  Symbol search path is: D:\241 RND\Symbols\Extracted
  Executable search path is:
  Could not load the ntoskrnl.exe, 0n2 error Win32 image
  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 (8 procs) free x 86 compatible
  Product: LanManNt, suite: TerminalServer company
  Computer name:
  Kernel base = 0x82a18000 PsLoadedModuleList = 0x82b2fc70
  The debugging session: 23:11:57.714 on Thursday, August 2, 2012 (UTC + 01:00)
  System Uptime: 9 days 15:17:21.963
  Could not load the ntoskrnl.exe, 0n2 error Win32 image
  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 10000050, {f2a45048, 0, b 82, 94299, 0}

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

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

  MODULE_NAME: nt

  FAULTING_MODULE: 82a 18000 nt

  DEBUG_FLR_IMAGE_TIMESTAMP: 4f79a9be

  READ_ADDRESS: could not get nt! MmSpecialPoolStart
  Unable to get nt! MmSpecialPoolEnd
  Unable to get nt! MmPagedPoolEnd
  Unable to get nt! MmNonPagedPoolStart
  Unable to get nt! MmSizeOfNonPagedPoolInBytes
  f2a45048

  FAULTING_IP:
  NT + c 17 299
  82b 94299 394724 cmp dword ptr [edi + 24 h], eax

  MM_INTERNAL_CODE: 0

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT_SERVER

  BUGCHECK_STR: 0 X 50

  CURRENT_IRQL: 0

  LAST_CONTROL_TRANSFER: from 82b9a7f4 to b 82, 94299

  STACK_TEXT:
  WARNING: Information not available stack unwind. Sequence of images may be wrong.
  90e72a8c 82b9a7f4 01000001 4020 009c3f70 nt 009c + 0x17c299
  90e72abc 82b9ae22 c422da20 00000006 01000001 nt + 0x1827f4
  82b 95848 01000001 90e72c60 8000e8d0 nt 90e72b04 + 0x182e22
  90e72b60 82b97fb7 90e72bb4 00000000 00000005 nt + 0x17d848
  90e72bd8 82b9a257 90e72c60 90e72c4c 00000000 nt + 0x17ffb7
  90e72c18 82b9049f 90e72c60 90e72c7b 00000000 nt + 0 x 182257
  90e72d14 82b906d4 82b105a0 00000002 00000002 nt + 0x17849f
  90e72d38 82c6fb01 82b1a13c 8784e020 82abdda2 nt + 0x1786d4
  90e72d7c 82bedfe2 9b1e85b2 00000000 00000000 nt + 0x257b01
  90e72dc0 82a56f0e 82abdca5 00000000 00000001 nt + 0x1d5fe2
  00000000 00000000 00000000 00000000 00000000 nt + 0x3ef0e

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  NT + c 17 299
  82b 94299 394724 cmp dword ptr [edi + 24 h], eax

  SYMBOL_STACK_INDEX: 0

  SYMBOL_NAME: nt + 17 c 299

  FOLLOWUP_NAME: MachineOwner

  Nom_image: ntoskrnl.exe

  BUCKET_ID: WRONG_SYMBOLS

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

  --------------------------------------------------------------------------------------------------------------------

  Can you please review and guide us more as soon as POSSIBLE.

  Let me know if any other information required for the same thing.

  Kind regards

  Helen Shah

  Hello

  The question you posted would be better suited to the TechNet community. Please visit the link below to find a community that will provide the support you want.

  http://TechNet.Microsoft.com/en-us/WindowsServer/bb310558.aspx

  Hope this information is useful.

• Windows XP will only start in safe mode after Windows updated 09/02/2011

  We have seven Windows XP SP3 computers.  All are set to download/install automatic updates every day at 03:00.  Today, one of them does not start in normal mode.  When the user arrives at 08:30, screen was black and would not, if power to monitor and PC were in.  The user powered PC turned off/on.  He came normally too far that the screen blue, just before the login box appears, sucked to boot options.  Boot in safe mode and safe mode with networking mode.  Restart in safe mode after shows the same result.  The event log shows a SaveDump:

  Event type: Information
  Event source: Save Dump
  Event category: no
  Event ID: 1001
  Date: 09/02/2011
  Time: 08:30:01
  User: n/a
  Computer: TOTB-02
  Description:
  The computer was restarted after a bugcheck.  The bugcheck was: 0x1000007f (0 x 80042000, 0x00000000, 0x00000008, 0x00000000). A dump was saved in the: C:\WINDOWS\Minidump\Mini020911-01.dmp.

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  Installed updates: KB2393802, KB2476687, KB2478960, KB2478971, KB2479628, KB2483185, 2485376

  Word and Excel will not run.  The office is OpenLicense.  Says can not verify the license for this application.

  Thank you

  aDaniel

  A suggestion: as stated above, I thought I was wrong this posted in the Windows 7 Forum.  In fact, the link under XP for updates takes you to the Forum Windows 7 > Windows Update.  It seems that it would be less confusing, if questions update go to a forum, out of Windows 7 and Windows Update as a stand-alone speaker.

  Thank you for all your help,

  aDaniel

• BCCode error on blue screen 1 has in the Windows XP computer.

  Original title: BSOD on XP Pro.

  I recently started having BSOD on a computer running XP Pro, which had no material or changes in drivers or updates for some time.

  After re-booting, I get the following:

  BCCode 1A BCP1: 00000780 BCP2: C06D 4250 BCP3: CA 81 9898 BCP4: 000004CD OSver:5_1_2600 SP3_0 product 256_1

  Online it suggests incompatible drivers but the only change has recently been anti-virus and the problem predates this.

  Sometimes it happens on startup and the other time when in different programs or even idle.

  The computer is a Dell Vostro, who is just two years old.

  Yes - is not too much sense.

  You can see you are running SP3 from the information you have provided and it makes even less sense as the hotfixes in this section of the Microsoft Support Engineer are already included with SP3.  But, this is a link to an article.

  If/when it crashes again to follow this procedure in order to watch your own crash dump files for clues or download them to your SkyDrive so someone can help you to look at.  It's just a copy/paste that I send to anyone who needs help with a BSOD.

  If you have a few dumps already accumulated on your system before the new video card, they must remain on your system if you want to watch.

  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:

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

  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 information BleuScreenView of 5 last memory dumps (if you have 5 dumps memory yet, send the most recent, you).
  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.

  It is sometimes easier just to download the memory dump files since your last breaks down on your SkyDrive (everyone has a SkyDrive for file sharing).   So can someone who already has Windows debugging tools to look at things and understand what is happening.

  Dump memory of recent crashes and BSOD files are usually in this folder:

  c:\windows\minidump

  The files will be named something like this:

  Mini120311 - 01.dmp

  You need to download the latest... maybe 5-10 of the most recent crash dump files should be sufficient if you who have a lot.  If you do not have that much, send what you have.

  Getting started with SkyDrive:
  http://explore.live.com/SkyDrive-get-started

  Once you get your downloaded files and watch them on your SkyDrive, you need to 'share' your folders/files so that others can see them.

  Here is a link that tells you how to:
  http://explore.live.com/Windows-Live-SkyDrive-change-access-permissions-FAQ

  Then click on the button "insert a link".  When you click on that, a window opens that contains the link to your SkyDrive files.

  Copy the contents of the box "copy this link to share:" in selecting the content of the link (it will be all highlighted), press Ctrl + C (copy) and then come back to the forum and in your next message, press Ctrl + V to paste the contents of the link back here.

  What you paste the return will look something like this link on my SkyDrive:
  https://SkyDrive.live.com/redir.aspx?CID=6a7e789cab1d6f39&RESID=6A7E789CAB1D6F39! 311

• Blue screen of death (Minidump) - several stop codes.

  Hello

  ==================================================
  Dump file: Mini101911 - 02.dmp
  Crash time: 2011-10-19 14:22:12
  Bug Check String: KERNEL_MODE_EXCEPTION_NOT_HANDLED
  Bug check code: 0x1000008e
  Parameter 1: 0xc0000005
  Parameter 2: 0xbf80124b
  Parameter 3: 0xba127a48
  Parameter 4: 0x00000000
  Caused by the driver: win32k.sys
  Caused by the address: win32k.sys + 124 b
  Description of the file: multi-user Win32 Driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.6149 (xpsp_sp3_gdr.110906 - 1620)
  Processor: 32-bit
  Plant address: win32k.sys + 124 b
  Stack address 1: win32k.sys + 831d0
  Stack address 2: win32k.sys + b8fa7
  Battery 3 address: win32k.sys + 1142
  Computer name:
  Full path: C:\windows\Minidump\Mini101911-02.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  ==================================================
  Dump file: Mini101911 - 01.dmp
  Crash time: 19/10/2011-12:01:17
  Bug Check String: DRIVER_CORRUPTED_EXPOOL
  Bug check code: 0x100000c5
  Parameter 1: 0 x 00000004
  Parameter 2: 0x00000002
  Parameter 3: 0x00000001
  Parameter 4: 0x8054bfd2
  Caused by the driver: sr.sys
  Caused by the address: sr.sys + 4bbf
  Description of the file: System Restore filesystem filter 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 + 74fd2
  Stack address 1: ntoskrnl.exe + 19eb1
  Stack address 2: ntoskrnl.exe + aca58
  Battery 3 address: ntoskrnl.exe + e44aa
  Computer name:
  Full path: C:\windows\Minidump\Mini101911-01.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  ==================================================
  Dump file: Mini101811 - 02.dmp
  Crash time: 2011-10-18 12:45:15
  Bug Check String: DRIVER_CORRUPTED_EXPOOL
  Bug check code: 0x100000c5
  Parameter 1: 0x00076e14
  Parameter 2: 0x00000002
  Parameter 3: 0x00000001
  Parameter 4: 0x8054bfd2
  Caused by the driver: Ntfs.sys
  Caused by the address: Ntfs.sys + 575 b
  Description of the file: NT File System Driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.5512 (xpsp.080413 - 2111)
  Processor: 32-bit
  Plant address: ntoskrnl.exe + 74fd2
  Stack address 1: ntoskrnl.exe + 19eb1
  Stack address 2: ntoskrnl.exe + aca58
  Battery 3 address: ntoskrnl.exe + e44aa
  Computer name:
  Full path: C:\windows\Minidump\Mini101811-02.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  ==================================================
  Dump file: Mini101811 - 01.dmp
  Crash time: 2011-10-18 12:23:39
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x1000000a
  Parameter 1: 0x005c003a
  Parameter 2: 0x0000001c
  Parameter 3: 0x00000001
  Parameter 4: 0x80502cd6
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 2bcd6
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 5.1.2600.6055 (xpsp_sp3_gdr.101209 - 1647)
  Processor: 32-bit
  Plant address: ntoskrnl.exe + 2bcd6
  Stack address 1: ntoskrnl.exe + 2bf2f
  Stack address 2: ntoskrnl.exe + 230d9
  Battery 3 address: ntoskrnl.exe + 2316c
  Computer name:
  Full path: C:\windows\Minidump\Mini101811-01.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  So, I'm wondering for corrupted files, I can just remove or repair? For example, I got a blue screen of death before, so I remove the source of the blue screen of death which is

  ==================================================
  Dump file: Mini070811 - 01.dmp
  Crash time: 08/07/2011-18:28:31
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x1000000a
  Parameter 1: 0 x 00000016
  Parameter 2: 0x0000001c
  Parameter 3: 0x00000000
  Parameter 4: 0x80502eb4
  Caused by the driver: adasprot32.sys
  Caused by the address: adasprot32.sys + 1440
  Description of the file:
  Product name:
  Company:
  Version of the file:
  Processor: 32-bit
  Plant address: ntoskrnl.exe + 2beb4
  Stack address 1: ntoskrnl.exe + 2329e
  Stack address 2: adasprot32.sys + b31
  Battery 3 address: ntoskrnl.exe + 1819f
  Computer name:
  Full path: C:\WINDOWS\Minidump\Mini070811-01.dmp
  Number of processors: 2
  Main version: 15
  Minor Version: 2600
  Size of the dump file: 94 208
  ==================================================

  This is an example for you to understand the process. The essential 'Address', what is more important than 'address crash' and ' address 1-3' of the battery. I delete the corrupt of this show. So I wonder is that files that are displayed as blue screen of death appear as new files or has been corrupted (not new, but the changes) so that files is important, it is not good to remove it but just fix it? In this case, it is program file, so that files can be removed, but for above I'll list five blue screen of death (at the top of this page and recently), is files computer, more important than the program files. So I can delete files, but it would affect the entire computer? Or fix it? Another thing that is feature computer sank black and can't restart for some time. Thus, the program can cause corrupted files or delete files that is corrupt to become new and separate, which means that it can be? Are there two types of files? SE do not become like nine files can you repair files, but changes or files that become like new but bad files, it can therefore be removed. Thus, since the site Web who say it is the right program or files, but it is good to scan files that can cause of spyware, malware, virus or a program? So, do you know what could be cause of the last blue screen of death to connect to black on computer screen. It's as if I hard harddirve, but this isn't like that. This is exactly the same process of result with old hard drive causing the computer screen black, but this case is different departure process. If you tell me to use the cd, to solve the problem, tell me what cd and if it is a restore cd that say recovery on the cd for xp or more. It is large and clear a word that mean the recovery? If this is the case, I don't have it. Well, don't have no possible, but in case I did not.

  Hello Khalif Foster,

  It may be a problem with the Table of master files on the hard drive that does not, however, another option is to use the tool in the mentionted Knowledge Base article.

  Using Driver Verifier to identify issues with Windows drivers for users advanced

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

  To verify exactly which driver may be the cause of this problem. (if you don't believe the issue is the hard drive).

  Hope this information helps.

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

  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.

• A problem has been detected and windows has shut down to prevent damage to your computer.

  I was playing a game when the error occurred.

  Here's the Stop error message:

  The problem seems to be caused by the following file: nv4_disp

  STOP: 0X000000EA (0XFFB86980, 0XF9694CBC, 0XFFA9F318, 0 X 000000001)

  I have Windows XP Home Edition. Please do not hesitate to request additional information. Not really good at this. But I don't think that this problem can be with the video card.

  Please provide additional information on your system:

  What is your system brand and model?

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

  If your system works fine, what do you think might have changed since the last time it worked correctly?

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

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

• Error 0x0000008E (KERNEL_MODE_EXCEPTION_NOT_HANDLED) in the Windows XP machine code.

  Original title: KERNEL_MODE_EXCEPTION_NOT_HANDLED.

  Yes im receiving a blue error screen indicating the following:

  Mini033111 - 01.dmp

  31/03/2011-14:10:42

  KERNEL_MODE_EXCEPTION_NOT_HANDLED

  0x1000008E

  0xc0000047

  0x804fcf44

  0xb84e7a24

  0x00000000

  Ntoskrnl.exe

  Ntoskrnl.exe + 25f44

  NT kernel & system

  Microsoft® Windows® operating system

  Microsoft Corporation

  5.1.2600.6055 (xpsp_sp3_gdr.101209 - 1647)

  32 bit

  C:\WINDOWS\Minidump\Mini033111-01.dmp

  1

  15

  2600

  I havnt a clue what is causeing this help and all would be greatly appreciated

  Hello

  ·         You did it of any material changes or software on the computer before this problem?

  ·         Exactly when you receive this error message?

  You can follow this link and check if it helps.

  You receive a random "0x0000008E" error message on a blue screen in Windows XP

  Hope the helps of information.

  Please post back and we do know.