minidump file

Similar Questions

• where can I obtain the necessary tools to control a minidump file?

  I try to install the Windows SDK in order to check the minidump file.

  The computer running Windows XP Professional.

  Although, when I check the Windows development kit Web site, it says it's for Windows 7.
  Where can I download Windows SDK for Windows XP Professional, 32-bit.

  Thank you

  MSDN is the place of those tools, however this is not an SDK for windows xp, go to

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

  In addition, xp has a tool that you can use, its called 'AUDITOR '.

  Type it in the race, for info, go to

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

  Read the instructions 1...

• How to read minidump files?

  My question is small, but has a large influence on the detection of the windows error.

  I have a question, how to read minidump files?

  This is the default location is "C:\WINDOWS\Minidump.

  Specifically, I have no problem in real-time, but I want to know about it.

  I have also noticed that some MVP suggest that you download the minidump & they inspect it. But how do?

  Do not hesitate to make the technical content, I will try to understand that also.

  I have no OS dependencies so here you can chat on any OS (XP, Vista, win 7).

  It would be good if you give me an example. As an example you can quote all the minidump pre inspected which is uploaded to skydrive files.

  S.Chatterjee

  http://support.Microsoft.com/kb/315263 MS - MVP - Elephant Boy computers - don't panic!

• Windows Vista-used to get the blue screen with the error on it. Re-installed Vista and the programs one by one w/restorations. Now, I get the blank screen minidump file blue w/error after reboot and...

  I find the minidump files and tried opening them and could not. Files and downloaded programs of debugging appear in the program. When I try to open them I get "you must be an administrator to open" insofar as I know that I am the administrator because supposedly everything I need is another administrator account. Also my restore will pass in a few days, and the box is no longer available. Also had an error on my printer files so I removed them, but as I (after) that I pressed the firm PC, the blue screen appeared and had to turn it off manually and of course got the minidump error message when I started again. If at this point, I'm still waiting to see if deleting the files printer helped. Any information would be appreciated.

  OK, I'll look for your next post with minidump files.

• Driver power state failure; BSOD; Cannot open the minidump files

  Two weeks, my computer with Vista has started giving me a BSOD with status message driver failure.  I found the minidump files, but cannot open them.  The BSOD usually occurs after the computer has entered a sleep or hibernation.  I have not added any equipment to the computer and Norton 360 when I scan computer everything seems OK.  It is August 10, 19, then 23, also.  Don't know what the cause of the problem. Is there general reasons that could cause this or is - associated virus or what?

  Thank you

  Hello

  Check this thread for more information using BlueScreenView, MyEventViewer and other methods
  to troubleshoot the BlueScreens - top 3 answers (now 4).

  http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

  You can use BlueScreenView to stick the BSOD info in a message here.

  NOTICE - report HTML all THE ELEMENTS or right-click on a BSOD line and select the same. Then, copy and
  Paste the lines in a message here. Make sure and check the file name section. Also check the time
  in MyEventViewer for more information as possible.

  ===========================================================

  Check out these utilities to see if information may be collected:

  It is an excellent tool for displaying the blue screen error information

  -Free - BlueScreenView scans all your minidump files created during "blue screen of death," collisions
  and displays information about all accidents of a table.
  http://www.NirSoft.NET/utils/blue_screen_view.html

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

  MyEventViewer can be verified at the time of the blue screen (BSOD) within a second or so of the
  time of the BSOD to provide more information about the possible cause - see TIP.

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the whole of the record-
  Set it for a bit before and after the time of the BSOD.
  http://www.NirSoft.NET/utils/my_event_viewer.html

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

  AppCrashView - free - a small utility for Windows Vista and Windows 7 that displays the details of all the
  application goes down has occurred in your system. The information breaks down is extracted from the .wer
  the files created by the Windows Error Reporting (WER) of the operating system component of each
  time that an accident has occurred. AppCrashView also allows you to easily record the list of accidents to
  text/html/csv/xml file.
  http://www.NirSoft.NET/utils/app_crash_view.html

  I hope this helps.

  Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

• How to submit the minidump file to microsoft for analysis...

  My win7 gives me a Disconnections. I have a little the minidump files how to send this file to microsoft and analyze findout my PC problem.

  My win7 gives me a Disconnections. I have a little the minidump files how to send this file to microsoft and analyze findout my PC problem.

  Hello

  There is no official way to do this. That's what a technical support technician may ask you to do as part of a normal support call.

  What you can do is zip the minidump files and download the file to a file such as the sharing site
  Microsoft Windows Live SkyDrive.

  Place the file in the Public folder, and make it accessible to all the world.  After return here with as much detail about the errors you can include the URL to this public folder.

  Some Members here can download the file and run a scan in order to let you know what can be the cause of error.

  I hope this helps.

  Thank you for using Windows 7

  Ronnie Vernon MVP

• Need help to understand the last string on my Win 7 BSOD. The Minidump files are attached.

  Hello

  Since last week, I've known several BSOD. Some have referred to a memory problem, but after you run a memory diagnostic seveal times, I still have to find the problem.

  Since last week, here is the link to the minidump files.

  https://onedrive.live.com/redir?RESID=2FA3EA1D7C87B0CD! 471 & authkey =! AA05X_X_DXaEOgc & ithint = % 2cdmp

  Thanks in advance for any help you can give.

  These accidents were related to the corruption of memory (probably caused by a driver).

  Please run these tests to check your memory and find which driver is causing the problem.

  
  

  If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

  
  

  Since then, it is more likely to be a pilot run everything first.

  1-Driver Verifier (for full instructions, see our wiki here)

  
  

  If the auditor does not have the issue we move to it.

  2-Memtest. (You can learn more about running memtest here)

  
  

  If you cannot start after you have enabled the auditor reboot in safe mode

  In Vista & victory (F8)

  When win 8 http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-Windows-8-the-easy-way/

  
  

  Co-written by JMH3143

  .

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

  Loading file Dump [C:\Users\Ken\Desktop\New folder\080714-32011 - 01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol of validation of the path summary *.
  Location of response time (ms)
  Deferred srv * C:\Symbols* http://msdl.microsoft.com/download/symbols
  Symbol search path is: srv * C:\Symbols* http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) free x 64
  Product: WinNt, suite: TerminalServer personal TerminalServer
  By: 7601.18409.amd64fre.win7sp1_gdr.140303 - 2144
  Computer name:
  Kernel base = 0xfffff800'03660000 PsLoadedModuleList = 0xfffff800'038 has 3890
  The debugging session: Thu Aug 7 14:15:03.891 2014 (UTC - 04:00)
  System Uptime: 0 days 4:02:55.202
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ........................
  Loading user symbols
  Loading unloaded module list
  .......
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck 50, {fffff6e400084040, 0, fffff800036e7f42, 5}

  Could not read the name of the problem driver
  Probably caused by: memory_corruption (nt! MiUpdateWsle + 122)

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

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

  PAGE_FAULT_IN_NONPAGED_AREA (50)
  Invalid system memory was referenced.  This cannot be protected by try-except,
  It must be protected by a probe.  In general, the address is simple bad or it
  pointing to freed memory.
  Arguments:
  Arg1: fffff6e400084040, memory referenced.
  Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
  Arg3: fffff800036e7f42, if not zero, the address of the instruction that refers to bad memory
  address.
  Arg4: 0000000000000005, (reserved)

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

  Could not read the name of the problem driver

  READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000390d100
  GetUlongFromAddress: cannot read fffff8000390d1c0
  fffff6e400084040 non paged pool

  FAULTING_IP:
  NT! MiUpdateWsle + 122
  fffff800'036e7f42 498b 00 mov rax, qword ptr [r8]

  MM_INTERNAL_CODE: 5

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

  BUGCHECK_STR: 0 X 50

  Nom_processus: vsserv.exe

  CURRENT_IRQL: 0

  ANALYSIS_VERSION: 6.3.9600.17029 (debuggers (dbg). 140219-1702) amd64fre

  TRAP_FRAME: fffff8800970b550-(.trap 0xfffff8800970b550)
  NOTE: The frame trap does contain not all registers.
  Some registry values can be set to zero or incorrect.
  Rax = 0000098000000000 rbx = 0000000000000000 rcx = 0000000000000a0f
  RDX = 0000c 80010808009 rsi = 0000000000000000 rdi = 0000000000000000
  RIP = fffff800036e7f42 rsp = fffff8800970b6e0 rbp = 0000000000000c 70
  R8 = fffff6e400084040 r9 = 0000000fffffffff r10 = fffff70001080488
  R11 = 000000000000116e r12 = 0000000000000000 r13 = 0000000000000000
  R14 = 0000000000000000 r15 = 0000000000000000
  iopl = 0 nv in pe of na EI ng nz cy
  NT! MiUpdateWsle + 0 x 122:
  fffff800'036e7f42 498b 00 mov rax, qword ptr [r8] ds:fffff6e4'00084040 =?
  Reset the default scope

  LAST_CONTROL_TRANSFER: from fffff800037525b3 to fffff800036d5bc0

  STACK_TEXT:
  "fffff880 '0970b3e8 fffff800' 037525b 3: 00000000'00000050 fffff6e4 ' 00084040 00000000 00000000' fffff880 ' 0970b 550: nt! KeBugCheckEx
  fffff880 '0970b3f0 fffff800' 036d3cee: 00000000 00000000' fffff6e4 ' 00084040 fffffa80' 04122600 fffffa80'00000028: nt! : FNODOBFM: 'chain' + 0 x 43801
  fffff880 '0970b 550 fffff800' 036e7f42: fffffa80'00000028 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiPageFault + 0x16e
  fffff880 '0970b6e0 fffff800' 036f41bd: 00000000' 00000a0f 00000000' 23ba4548 fffff700 ' 01080000 fffff700' 01080000: nt! MiUpdateWsle + 0 x 122
  fffff880 '0970b 750 fffff800' 036f39df: 20f00001 '63eb7025 00000001' 63eb7121 fffffa80' 04e10200 00000000' 00000000: nt! MiCompleteProtoPteFault + 0x2cd
  fffff880 '0970b7e0 fffff800' 036f24f3: 00000000' 0016bd60 000007fe'fbef34ac fffff683 'ff7df798 fffffa80' 07f6cd08: nt! MiResolveProtoPteFault + 0x1cf
  fffff880 '0970b 870 fffff800' 036e2179: 00000001 00000000' 000007fe 'fbef34ac fffffa80' 09a44af0 00000000' 00000000: nt! MiDispatchFault + 0x1c3
  "fffff880 '0970b 980 fffff800' 036d3cee: 00000000 ' 00000008 000007fe ' fbef34ac fffff880'00000001 00000000' 0863fe50: nt! MmAccessFault + 0 x 359
  fffff880 '0970bae0 000007fe' fbef34ac: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiPageFault + 0x16e
  00000000' 0863fb68 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x000007fe'fbef34ac

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  NT! MiUpdateWsle + 122
  fffff800'036e7f42 498b 00 mov rax, qword ptr [r8]

  SYMBOL_STACK_INDEX: 3

  SYMBOL_NAME: nt! MiUpdateWsle + 122

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nt

  DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb

  IMAGE_VERSION: 6.1.7601.18409

  Nom_image: memory_corruption

  FAILURE_BUCKET_ID: X64_0x50_nt! MiUpdateWsle + 122

  BUCKET_ID: X64_0x50_nt! MiUpdateWsle + 122

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:x64_0x50_nt! miupdatewsle + 122

  FAILURE_ID_HASH: {adc90a39-f60f-e57a-aeeb-d2a428d2eb03}

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

• My computer has crashed with BSOD - I have miniDump file link

  Sony Vaio

  Windows 7
  Intel Core 2 Duo T6600 CPU 2.20 GHz
  4 GB OF RAM
  Crucial SSD - M4-ct128m4ssd2cca
  Norton
  My computer went to bsod last week - tried cleaning registry and dskchk and pilot - I went through the drivers and found one in need of an update - update has been blocked by norton.  No problem for a while, then was crushed this evening - also previous accidents create minidump files - but this one did - here's the link (((CORRECTED)))
  https://SkyDrive.live.com/redir?RESID=B19C18E006620FEE! 109 & authkey =! AGMr2-pOWW1-sR8&ithint=file%2c.zip
  Thank you

  Hello

  The attached file of the DMP is (7A) KERNEL_DATA_INPAGE_ERROR bug check.

  This bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.

  Error checking 7 a, {fffff6fc40007f08, ffffffffc000000e, 4c4f8860, fffff88000fe1630}

  The 2nd parameter of the bug check is 0xc000000e = DISK_HARDWARE_ERROR: there is error with hardware disk.

  0xC000000E or STATUS_NO_SUCH_DEVICE, usually indicates a hardware failure or an incorrect drive configuration. Check your cables and check the disk with the available from the manufacturer of your drive diagnostic utility. If you use old PATA (IDE) disks, this status code may indicate a bad master/subordinate drive configuration.

  It is also possible that a driver is causing corruption.

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

  1. uninstall ArcSoft Magic - i Visual effect.

  2 remove and replace Norton with Microsoft Security Essentials for purposes of troubleshooting temporary, as it is probably cause conflicts:

  Removal of Norton- https://support.Norton.com/SP/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;JSESSIONID=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&PVID=f-home

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

  3. SFEP.sys - Fri Aug 03 01:35:53 2007

  ^^ Sony Firmware Extension parser - 2007 pilot version has problems BSOD in Win7 (yours is 2007).

  Update ASAP - http://esupport.sony.com/perl/select-system.pl

  4 uninstall InterVideo, it seems to be linked to Corel - http://www.corel.com/corel/pages/index.jsp?pgid=800034

  If you still crash after all the foregoing, we probably hard drive failure which we will then move on diagnostics.

  Kind regards

  Patrick

• Bad Pool Caller error (Windows 8) - including the link to my Minidump file

  Hello!

  I recently received 4 blue screens; the first three were probably related to Avast, so I uninstalled ( Memory_managementerror)

  Later, says error Bad_Pool_Caller

  I have already travelled through further discussion, so here is the link to my Minidump file

  https://www.dropbox.com/s/sinr1qwyjjj43qw/dump.zip

  Also, here are the results of WhoCrashed

  
  

  Thank you very much!

  
  

  (Local) information system
  computer name: KISS
  Windows version: Windows 8, 6.2, build: 9200
  Windows dir: C:\Windows
  CPU: GenuineIntel Intel (r) Core i7-3630QM CPU @ 2.40 GHz Intel586, level: 6
  8 logical processors, active mask: 255
  RAM: 21425922048 total
  VM: 2147352576, free: 1917325312

  Crash Dump Analysis
  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Wednesday, October 29, 13 16:57:33 this computer crashed
  crash dump file: C:\Windows\Minidump\102913-8937-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7A040)
  Bugcheck code: 0xC2 (0x7, 0x11C1, 0x11AC6DA0, 0xFFFFFA8011AC6DB0)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the current thread is doing a bad pool request.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, October 29, 13 16:57:33 this computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: gdi32.sys (GDI32! D3DKMTPresent + 0xA)
  Bugcheck code: 0xC2 (0x7, 0x11C1, 0x11AC6DA0, 0xFFFFFA8011AC6DB0)
  Error: BAD_POOL_CALLER
  Bug control description: This indicates that the current thread is doing a bad pool request.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: gdi32.sys.
  Google search: gdi32.sys BAD_POOL_CALLER

  Wednesday, October 29, 13 12:15:41 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\102913-13828-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7A040)
  Bugcheck code: 0x1A (0xFFFFF70001080000, 0x1C03, 0 x 5003, 0x1C0400003846)
  Error: MEMORY_MANAGEMENT
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an error occurred serious memory management.
  This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.

  
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, October 29, 13 11:42:59 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\102913-23578-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x40C90)
  Verification of error code: 0 x 24 (0xFFFFF8800ACAE0C8, 0xFFFFF8800ACAD900, 0xB50019060B, 0xFFFFF8800197C552)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Tuesday, October 28, 13 18:22:31 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\102813-13562-01.dmp
  This was probably caused by the following module: dxgmms1.sys (dxgmms1 + 0x263E7)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880049B53E7, 0xFFFFF8800975A4E8, 0xFFFFF88009759D20)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\dxgmms1.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics MMS
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Conclusion
  5 dumps were found and analysed. A third-party driver has been designated to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

  Gdi32.sys

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.

  If you are overclocking anything reset by default before running these tests.
  In other words STOP!  
  If you don't know what it means that you're probably not

  1-Memtest. (You can learn more about running memtest here)
  Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Get it here
  Boot from the CD and let it run at least 5 or 6 passes.
  Remember, anytime Memtest reports errors, it can be bad RAM or a bad motherboard slot.
  Test the sticks individually and if you find a good, test it in all slots.

  If a well-known stick fails in a card mother slot but not an another is probably the slot.
  
  
  2-Driver Verifier (for full instructions, see our wiki here)
  Using Driver Verifier is a dubious proposition.
  Most of the time it will crash and it will tell you what is the driver, but sometimes, it will crash and will not tell you the driver.
  Sometimes it will crash until you can connect to Windows. If you can't mode without failure, then you will have to resort to editing the registry offline to disable driver verifier.

  I suggest that you first back up your data and make sure you have access to another computer so you can contact us in case of problems.
  Then do a system restore point (so you can restore the system using the functionality of Vista/Win7 Startup Repair).
  
  Here is the procedure:
  Go to Start and type "auditor" (without the quotes) and press enter
  Select "create of the custom settings (for code developers)" and click "Next".

  Select "Select individual settings from the list complete" and click "next".
  Select all elements EXCEPT FOR "Low Resource Simulation"
  Do not check to win 8 Concurrency stress test and the verification of the conformity of DDI, click "next".
  Select "Select the driver names from a list", then click on "next".
  Select all drivers NOT supplied by Microsoft, and then click "Next".
  Select 'Finish' on the next page.
  
  Restart the system and wait as he crashed to blue screen.
  Continue to use your system normally and if you know what are the causes of the crash, do it several times.
  The objective here is to get the system crash because Driver Verifier is stressing out the drivers.
  If it is not planted for you, then let it run for at least 36 hours of continuous operation.
  
  If you are unable to Windows because it crashes too early, try safe mode.
  If you can't mode without fail, try to use the system from the installation DVD restore to bring the system back to the previous point of restoration that you created.

• Several bsod, nothing seems to work? [with minidump files]

  Hello, I got a new laptop yesterday and it is already not working properly.   I bought it refurbished online manufacturer and I rather not return.  It's a Lenovo z580.  I have neen having multiple problems with it, and again I tried to fix it more it seems to get worse.

  Some errors are:
  MANY BSODs, including bad_pool_header, kern security check failure, etc.  I must have got more than 10 different ones, my computer restarts almost every 5 minutes.
  Windows updates will not download/install.
  When attempting to auto repair, it says it failed, because srttrail.txt.
  What I did:
  Resfreshed the computer,
  Reset the computer
  Discovery System of onekey to reset the computer
  Perform maintenance on the updates of Windows,
  Used the option such as chkdsk cmd: of and such.
  At this point, I wiped my computer clean to a point where I have literally no apps, no office, and I had to re-activate Windows.  Now, it gives me a different error long complicated.
  Can someone help me?  I feel like I did worse it when I do the things recommended to me from the Microsoft forums.  I am a student and it is extremely annoying.   : (I used my phone and a Windows 7 laptop in the meantime.
  My Lenovo z580 was supplied with Windows 8, so I do not have the disc.
  Please get back to me.  : (
  https://SkyDrive.live.com/redir?RESID=55A089856625D95B! 107 & authkey =! AORaUHOB_eRSChE&ithint=file%2c.zip

  Here's my minidump files.

  Oqqa

  These accidents were related to the corruption of memory (probably caused by your McAfee)

  Please run these tests to check your memory and find which driver is causing the problem.  I would start by driver verifier because it doesn't seem to be the RAM
  

  
  

  If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

  1-Memtest. (You can learn more about running memtest here)

  2-Driver Verifier (for full instructions, see our wiki here)

  Co-written by JMH3143

  .

• Difficulty to read minidump files

  Summer work computer crashing a lot lately.  I think that relatively new facility?  Computer us, anyway move me work and try to understand how use the windows to read files in dump posing more of a challenge than I expected.  I don't have a computer at home to do more research on how to do it and it's been almost a week now.  I'm not looking for someone debug this show so much as me how if possible.  I post a link to the .rar file and I'll post the error message I receive, I am using the command line: SRV * C:\symbols* http://msdl.microsoft.com/download/symbols under the user and system variables, I in c:\Symbols folder (empty)

  A screenshot of environmental variables m, rar file with crash dumps on the text file and the week when I try to open the file for debugging.

  https://onedrive.live.com/redir?RESID=F2E22D3677057E11%21216.

  You can't debug it to me (unless you have nothing else to do and I would be very grateful), but it would be great if I can understand how it works.  Thank you

  David

  LS

  First you must update asacpi.sys (yours is 2005) at least 2009

  Pre 2009 this driver version is a known cause of BSOD.
  
  Please visit Asus tek computer Inc. - support - drivers and download p7p55d the
  http://support.ASUS.com/download.aspx?SLanguage=en&m=P7P55D%20Le&p=1&s=32&OS=29&hashedid=e7zic83pvqsr80lm

  Scroll to the utility category, then scroll down to the "atk0110 driver for Windows XP/vista/windows 7 32 & 64-bit" (it is about 12 down).
  Download and install it.

  Go to c:\windows\system32\drivers to check and make sure that the file asacpi.sys is stamped 2009 or 2010 (not before).  If you are using Win 8 there are at least a 2012 version that is needed for this.  If you can't find it on the site of ASUS you can download using windows update.  Read about it here

  These accidents were related to the corruption of memory (probably caused by a driver).

  Please run these tests to check your memory and find which driver is causing the problem.

  
  

  If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

  
  

  Since then, it is more likely to be a pilot run everything first.

  1-Driver Verifier (for full instructions, see our wiki here)

  
  

  If the auditor does not have the issue we move to it.

  2-Memtest. (You can learn more about running memtest here)
  
  
  If you cannot start after you have enabled the auditor reboot in safe mode
  In Vista & win 7 (F8)
  In 8 victory & Win 10 http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-Windows-8-the-easy-way/
  
  
  Co-written by JMH3143

  .

• Blue screen, included minidump file

  https://SkyDrive.live.com/redir?RESID=313C73EFD01E0E70! 201

  Please help, the message says pilot less than or equal to, but I don't have the name of the driver.

  This occurred shortly after a windows update.

  I also started to get this error:
  The system firmware has changed the registers of the processor memory type range (MTRR) through a transition from sleep state (S4). This can result in reduced recovery performance.

  Russell

  This accident was related to athrx.sys stretch of Atheros Communications, Inc. wireless device driver.  Your's is about a year.  I would like to re - install the latest driver available.

  If you continue to plant I delete AVG and use the built in Defender

  Download new DMP files if they occur.

• Windows 8 won't let me copy or zip a minidump file

  What can I do so that I can copy or zip up a dump file memory without a notice of approval?

  William %

  You slide & on your desktop, and try to zip?

  You may need to 'ownership' of the DMP file
  http://www.eightforums.com/tutorials/2814-take-ownership-add-context-menu-Windows-8-a.html

• Please, hoping to help BSOD: link to file included :) - Minidump IRQL_NOT_LESS_OR_EQUAL

  Hello world

  I have never actually solved a BSOD problem, and I hope that this will be my first time! :)

  Here is the link to my Minidump file: http://1drv.ms/1eGOvpv

  My utility BlueScreenView says that ntoskml.exe is somehow involved - but other threads on this site of questions and answers suggest that this is probably just a symptom, not the cause, of my BSOD.

  All of your help, input and advice is much appreciated!

  Jay

  Hi Patrick,

  Well, my problem is SOLVED and you played a huge role to solve.  But... it has not been resolved as we both waited.  Unfortunately, the new external hard drive enclosure did not prevent the BSOD little once the drive has been removed safely.  But! :)   Helped you eliminate so many root causes (AVG, Norton...) and you had raised the possibility of a pilot did not cooperate, so I was wondering what (s) may be involved in my external hard drive is disconnected.  By chance, when I searched on Google, I've included a search term that I never thought about you: eSATA!  My external hard drive is connected via eSATA.  So when I search Google Dell, BSOD and eSATA, I soon saw a page which seems to indicate that I should check that I had the last pilot technology Intel Rapid Storage Technology.  And sure as heck, I had not installed at all!  Then, installed this driver and - bingo! -everything works perfectly now!

  But I NEVER would have gotten there if you had not encouraged me before and help narrow my focus on the external hard drive and drivers.  Yes, thank you Patrick!  So far as I am concerned you have solved this mystery, more than any!  And I am eternally grateful!

  Jay

• Windows 7 blue screen (file uploaded to SkyDrive minidump)

  I am running Windows 7 Ultimate 32-bit, updated since Vista. I get a blue screen every 1-3 days with no special action takes place.  Minidump file is available at:

  http://CID-f669dc5583876d16.SkyDrive.live.com/self.aspx/Windows%207%20Blue%20Screen%20Issue/010610-25781-01.dmp

  Any help is appreciated!

  Ron

  Just a final note to all those who might find this thread. I have finally saved my entire system, reinstalled Windows 7 from scratch and re-installed everything being of course to only load Windows 7 approved drivers and programs.  It was a good exercise, but the blue of the system proposed once more with the same error. The next step was to download Microsoft Memory Diagnostic program and place it on a bootable CD. I ran the tests extended for several hours, and it turns out a number of memory errors. I bought a set of replacement of memory, test it too (no error after 10 full hours of testing). So I hope I've chased it away.

  IMPORTANT: Before you spend hours (days, months) looking for a software solution, be sure to carefully check your memory before you do!