Blue screens: Bad_Header_Pool & Memory_Management

Similar Questions

• Blue screen Bad_Header_Pool

  I have a Dell Studio 1458 with windows 7, which is only six months old.  It blocks often resulting in a blue screen saying Bad_Header_Pool.  In the windows in safe mode provides the details of the following error:

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

  BCP1: 0000000000000020

  BCP2: FFFFFA800668F750

  BCP3: FFFFFA800668F770

  BCP4: 000000000402001E

  OS version: 6_1_7600

  Service Pack: 0_0

  Product:                                               768_1

  Files helping to describe the problem:

  C:\Windows\Minidump\030411-17362-01.dmp

  C:\Users\LeNoir\AppData\Local\Temp\WER-46488-0.SysData.XML

  Read our privacy statement online:

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

  You have any suggestions on how to fix this?

  Gerry,

  I spoke with someone at AOL technical support.  We have renamed the AOL ATWPKT264. Driver SYS 'ATWPKT264. SYS' at 'ATWPKT264. Bak' and then rebooted the system.  He solved the problem.

  LeNoir

• blue screen BAD_HEADER_POOL 0 x 00000019 (0x00000020, 0xe3498230, 0xe3498268, 0x0c070420)

  We started to have this blue screen with these error codes, can anyone help us with that?  We had a power surge, a loss of power, and the next blue screen this day began to appear.  Anyone got any ideas?

  If you had a power failure while XP worked and now, your system is bad, the first thing you should do is run a chkdsk with error correction.  These events can cause corruption in the file system then it would be the first thing to do.  Here's a way to do it:

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

  If it were me, I would run the chkdsk since the XP Recovery Console so I could watch it run...

  As the forums MS Answers does not prompt for any information system when a new question is asked, we don't know anything about your system.  Unless you want ideas for things to try (as opposed to things to do), please tell us more about your system:

  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?

  Your system have IDE or SATA disks?

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

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

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

  After running chkdsk with error correction (and clean), if you are still having the BSOD, follow these steps:

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

  Here's a BSOD example showing information you provide:

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

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

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

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

  Ignore the boring text unless it seems important to you.  We know what a BSOD looks like, we need to know what your BSOD looks like.

  Download BlueScreenView here:

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

• G7F08EA MEMORY_MANAGEMENT blue screen

  I got this phone 2 weeks ago, and the first day I had this... (BSOD, MEMORY_MANAGEMENT) Yesterday I did a restore of the operating system and I have yet to get it!

  Someone said I should update the drivers, but I don't know what are those who... Detecting device HP or something does not work I continue to press Scan but it does not!

  Hello NL_Alexxx, welcome to the Forums of HP.

  I see that you get a BSOD error. I will try to help you with this.

  I would like to direct you to this Microsoft document: resolution in Windows 7 stop errors (blue screen). (the steps can be done in Windows 8/8.1)

  If you use Windows 8/8.1 you might be looking at a refreshment or even recovery system. How to refresh, reset, or restore your PC

  I would like to know if it was able to help. Thanks for posting on the HP Forums.

• Cannot install windows - MEMORY_MANAGEMENT exception and blue screen

  Hello

  IM unable to install windows on my laptop computer, because whenever I try to install it, after installation there is exception MEMORY_MANAGEMENT and blue screen. It all started since a few exceptions on my previous windows which gives began several exceptions like DRIVER_IRQL_NOT_LESS_OR_EQUAL as errors and PC rebooted each time. Then I thought to install new windows and the problem started. I'll be very grateful if you look forward to my problem

  Thanks :)

  First run Memtest86 +:

  It runs from a floppy disk or CD and should eliminate or confirm if one or more of your memory
  sticks are bad or the values of the SPD in the BIOS are correct.
  Let it run for as long as you can: 2,4,6,8 or several hours (at least 3 full passes), so no errors at that time then your ram is OK.
  http://www.memtest.org/
  Memtest86 + Guide/How To (use the.) ISO to create a bootable CD)
  http://www.overclockers.com/forums/showthread.php?t=409152

  Hard drive test:
  (1) If you do not know your readers make / model number AND your computer is no longer able to load Windows:
  (a) Renmove the drive of your desktop and check the label for the serial number and model.
  (b) remove the bottom cover of your laptop, remove the disc and check the label for the serial number and model.

  (2) If Windows is still usable, install 'Speccy', it provides information of the computer/system in detail on your:
  OS, CPU, RAM, motherboard, graphics, Hard Drive, optical, Audio, peripherals, network.
  Note: Option RAM indicates number of slots, DRAM Timing.
  Works your memory speed (frequency). The nominal frequency of your memory.
  http://www.Piriform.com/Speccy

  Test drive - create a Bootable CD:
  (or connect the drive to anther PC and install the appropriate test software)

  Note: Reliability of the drive hard has come the way down over the last 24 months and improved a bit lately according to manufacturing.
  Ranging from 5 to 25% (depending on the make and model) new hard disks are defective.

  List the factory utilities, walk.
  If you have a new hard drive Seagate the very next thing would be to download Seagate Seatools
  (bootable CD) and check bad sectors.
  SeaTools for information: http://www.seagate.com/support/downloads/seatools/
  SeaTools for Windows download: http://www.seagate.com/support/internal-hard-drives/enterprise-hard-drives/saturn/seatools-win-master/
  SeaTools for DOS download:
  http://www.Seagate.com/support/internal-hard-drives/consumer-electronics/LD25-series/SeaTools-DOS-master/

  For Western Digital disks, download the file .iso from WdDiag:
  http://support.wdc.com/product/download.asp?GroupId=613&lang=en

  Samsung Estool: http://www.samsung.com/global/business/hdd/support/utilities/ES_Tool.html
  Samsung Disk Manager software: http://www.samsung.com/Products/HardDiskDrive/utilities/shdiag.htm

  Hitachi Drive Fitness Test Software: http://www.hgst.com/hdd/support/download.htm#DFT
  Diagnostic tool available for use by customers who believe that having a brand Toshiba Fujitsu hard drive:
  http://SDD.Toshiba.com/main.aspx?path=ServicesandSupport/WarrantySupport/SoftwareUtilities

  Notice of Fujitsu drive management utility: http://www.fujitsu.com/us/services/computing/storage/hdd/

  Toshiba CD bootable: (BACK Diagnostic Tool version 7.0 for IDE/ATA/SATA hard disks)
  http://SDD.Toshiba.com/main.aspx?path=ServicesSupport/FujitsuDrivesUSandCanada/SoftwareUtilities#diagnostic

  Also try Home Edition free Partition Wizard option "Test of disc surface":
  http://www.partitionwizard.com/free-partition-manager.html

  = Test SSD - modified software: 24/10/14 =.

  Intel® drive SSD Toolbox
  https://Downloadcenter.Intel.com/Detail_Desc.aspx?AGR=Y&DwnldID=18455

  Corsair SSD Toolbox:
  http://www.Corsair.com/en-us/blog/2013/may/the-Corsair-SSD-Toolbox

  Toolbox of Kingston:
  http://www.Kingston.com/us/support/technical/sandforce_ssd_toolbox.aspx

  OCZ Toolbox: http://ocz.com/consumer/download/firmware

  PNY support: http://www.pny.com/support/contact-us

  Samsung: http://www.samsung.com/global/business/semiconductor/minisite/SSD/global/html/about/whitepaper07.html
  Samsung Magican review:
  http://www.TweakTown.com/articles/5638/Samsung-magician-4-2-first-look-new-SSD-Toolkit-adds-rapid-mode/index.html

  SanDisk SSD Toolkit: http://kb.sandisk.com/app/answers/detail/a_id/9328/

  Seagate: http://www.seagate.com/support/internal-hard-drives/laptop-hard-drives/laptop-600-ssd/

  Life of the SSD: http://ssd-life.com/

  J W Stuart: http://www.pagestart.com

• How can I fix my computer of these blue screen of death error: KMODE_EXCEPTION_NOT_HANDLED BAD_POOL_HEADER & MEMORY_MANAGEMENT

  Last week, I updated my Windows 8 computer after that it had been updated to 8.1 because the computer was crashing so frequently. However, I continued to receive several blue screen error of death (KMODE_EXCEPTION_NOT_HANDLED, BAD_POOL_HEADER & MEMORY_MANAGEMENT).

  These have taken place when I watch movies via Amazon instant video or power video chat with my family. I guess I need to update a driver, but I don't know how to determine which driver to date.

  Is there an easy way to find out what the cause of the problem? What should I do?

  Here are my computer specs:

  HP Pavilion

  Windows 8

  Processor: AMD A8 - 5545 M APU with graphics HD Radeon (TM) 1.70 GHz

  RAM: 8.00 GB (7.22 GB usable)

  Operating system 64-bit, x 64 based processor

  I'm working on getting a shared online memory minidump file. I have problems with that.

  Yes, he did delete it. You can try a first auto repair (insert the installation DVD before the race) - http://www.bleepingcomputer.com/tutorials/http-wwwbleepingcomputercom-tutorials-automatically-repair-windows-8-with-automatic-repair-/

  Kind regards

  Patrick

• blue screen / memory_management/Restart - whenever I connect the external hard drive

  whenever I plug in the external that I get a screen blue with the message of management of the memory/500 GB, Ive done scan memory which was ok, booted in safe mode it still did. I did the sfc/scannow and message were found corrupted files that he couldn't fix it, tried to disable the antivirus then plug externally and he always has. It's windows 8 on a touchscreen ASUS all-in-one, is only 6 months and after 3 weeks, I was stuck with the constant blue screen at startup until it my tech had to wipe and reinstall windows and that day he said it was an update that he didn't like. When I plug a 32 GB key it works fine, but with external it restarts every time and on startup it sends a report to microsoft, so why microsoft will not send me a fix... Help

  whenever I plug in the external that I get a screen blue with the message of management of the memory/500 GB, Ive done scan memory which was ok, booted in safe mode it still did. I did the sfc/scannow and message were found corrupted files that he couldn't fix it, tried to disable the antivirus then plug externally and he always has. It's windows 8 on a touchscreen ASUS all-in-one, is only 6 months and after 3 weeks, I was stuck with the constant blue screen at startup until it my tech had to wipe and reinstall windows and that day he said it was an update that he didn't like. When I plug a 32 GB key it works fine, but with external it restarts every time and on startup it sends a report to microsoft, so why microsoft will not send me a fix... Help

  Thanx got fixed, had a boyfriend of work come and he found the answer on page 3, it was the USB driver had to be removed and reinstalled with the right pair on the ASUS website

• Blue screen in XP from DRIVER_FAULT and memory_corruption errors

  Hi people.  Had fun looking for a 45 BSOD for my Compact Win - XP Pro.  I get failures over the last 5 months once a week, ranging from A to Z in bugcodes.  About 10 have been 0 x 50.  I removed Norton360, ran all the tests system twice and three companies ESOT, Norton and the scan MSFT no virus, run Norton Regcleaner and was clean. I have part of the SDK installed and tried to get LMV? to work.  I have included the minidump.text.  I post the most recent dump just after you remove norton.  Any help finding drivers with the"LMV?" would be useful.  I have all the minidumps. I have updated NVIDIA.  It happens at any time, on the most part, any application.  You get the idea, things are a little tense.  I have knowledge of the central computer and a few PC, but dump and stack not debug stuff.

  Thank you, Jerry

  DUMP**********************************************************************************************************************************
  Debug version of Microsoft Windows (R) 6.12.0002.633 X 86
  Copyright (c) Microsoft Corporation. All rights reserved.

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

  Symbol search path is: srv * c:\mydir* http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows XP Kernel Version 2600 (Service Pack 3) MP (2 processors) free x 86 compatible
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 2600.xpsp_sp3_gdr.101209 - 1647
  Computer name:
  Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
  The debugging session: 16:41:37.234 Sun 9 Oct 2011 (UTC - 07:00)
  System Uptime: 0 days 1:58:58.968
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ..........
  Loading user symbols
  Loading unloaded module list
  ............
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Error checking 1 a, {41284, a 164, 9001, ef4, c0883000}

  Probably caused by: memory_corruption (nt! MiLocateWsle + c1)

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

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

  MEMORY_MANAGEMENT (1A)
  # All other values for parameter 1 must be examined individually.
  Arguments:
  Arg1: 00041284, A PTE or the work list is corrupted.
  Arg2: 164a 9001
  Arg3: 00000ef4
  Arg4: c0883000

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

  BUGCHECK_STR: 0x1a_41284

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: DRIVER_FAULT

  Nom_processus: explorer.exe

  LAST_CONTROL_TRANSFER: from 80523339 to 804f9f43

  STACK_TEXT:
  b1305be8 0000001 has 80523339 164a 9001 00041284 nt! KeBugCheckEx + 0x1b
  b1305c20 805b74f3 00000ef4 164 has 9000 c00b2548 nt! MiLocateWsle + 0xc1
  b1305c50 805b 8826 c00b2548 89ad45b0 00000000 nt! MiGetPageProtection + 0x13f
  b1305c88 805b90e5 00000000 89e8d608 89ad45b0 nt! MiQueryAddressState + 0xa4
  b1305d44 8054167c ffffffff 164a 1228 00000000 nt! NtQueryVirtualMemory + 0 x 477
  b1305d44 7c90e514 ffffffff 164a 1228 00000000 nt! KiFastCallEntry + 0xfc
  WARNING: Frame IP not in any known module. Sequence of images may be wrong.
  00000000 00000000 00000000 00000000 0x7c90e514 0238f78c

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  NT! MiLocateWsle + c1
  2b45f0 80523339 sub eax, dword ptr [ebp - 10 h]

  SYMBOL_STACK_INDEX: 1

  SYMBOL_NAME: nt! MiLocateWsle + c1

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nt

  DEBUG_FLR_IMAGE_TIMESTAMP: 4d00d46f

  Nom_image: memory_corruption

  FAILURE_BUCKET_ID: 0x1a_41284_nt! MiLocateWsle + c1

  BUCKET_ID: 0x1a_41284_nt! MiLocateWsle + c1

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

  Hello Elliottj,

  I would get the dumps uploaded to us.  If Please zip the contents of the c:\windows\minidump folder and place it in a public folder on http://skydrive.live.com.  Then post the link to us here.

  Let's start by cleaning the pagefile:

  1. Move the image to a different location on the hard drive.
  2. Move the paging file to another drive:
  3. Click Start.
  4. Right click on computer and select Properties.
  5. Click on Advanced system settings.
  6. Go to the Advanced tab if it is not already there.
  7. Click settings under performance.
  8. Click the Advanced tab.
  9. Click on 'change... '. »
  10. Uncheck "Automatically manage the size of pagefile for all readers."
  11. Select the drive where the pagefile is currently.
  12. Select "No paging file" below, and then click set.
  13. Select the drive where you move the file from the list of drives.
  14. Select the System managed size and then click set.
  15. Click OK and click OK again.
  16. Reset.
  17. I hope that we will now have a dumpster good blue screen.

  Once all this was done, we have a task:

  1. Click Start and type CMD
  2. Right click in the command line above and choose 'Run as administrator'.
  3. At the command prompt, type CHKDSK/r
  4. Let the full chkdsk.
  5. Close the command prompt.

  After that, we can look for another blue screen and I hope that this will give us a good image.

  Best regards

  Matthew_Ha

• blue screen with the error of MEMORY MANAGEMENT. 0x0000001A

  Separated from this thread.

  Hello

  I have a toshiba satellite c870. When I turned on my computer, I got a blue screen by reading the following:

  (blue screen)

  : (

  Your PC has encountered a problem and needs to restart. We are only collecting the error information, and then we'll restart for you. (100% complete)

  If you want more information, you can later search online for this error: MEMORY_MANAGEMENT.

  Then it restarts and I get these 2 following errors of switching back and forth between the two sound tempting to prepare auto repair. See below:

  (blue screen)

  : (

  Your PC has encountered a problem and needs to restart. We will provide for you.

  If you want to learn more, you can search online later to this error: NTFS_FILE_SYSTEM

  Then he goes to the black Toshiba Logo screen as usual and reads the following:

  preparation auto repair...

  And then it goes to another screen blue read the following error message:

  (blue screen)

  : (

  Your PC has encountered a problem and needs to restart. We will provide for you.

  If you want to learn more, you can search online later to this error: FAT_FILE_SYSTEM

  He'll then return to the Logo of Toshiba screen, then the Blue error screen (NTFS_FILE_SYSTEM), then return to the Logo of Toshiba screen and then the Blue error screen (FAT_FILE_SYSTEM). It just keeps it again and again and does nothing else. I removed the battery, removed all caps, deleted all devices USB (mouse) and pressed the power button for 60 seconds. Then I put the battery in place, pluged in the power cord and it turned on. I got the same results, as shown above. NO CHANGE! HELP PLEASE!

  Well Vista and before "XP", usually, do not use the FAT32 file system, they use, as do the new OS NTFS.

  Vista/XP can read FAT32, & can / could use, but its outdated... Memory is not really in this case, but

  you too extended the hardware capabilities of the pc.

  From this point, try to start the BIOS, the value 'advanced settings' once this done, change BIOS for any add-on

  material, save & exit.

• Computer crashes frequently with errors of "Blue Screen of Death" as shown below. These occur usually (but not always) after that the PC has been in sleep/wake.

  Here is the blue screen errors

  IRQL_NOT_LESS_OR_EQUAL

  MEMORY_MANAGEMENT

  PFN_LIST_CORRUPT

  -------------------------
  Bought PC in Nov 2008
  Q6600
  Vista SP2
  ATI 4850 graphics card
  4 GB of RAM
  500 GB HD

  Hello

  Probably either a (most likely) driver error or faulty memory. First run the internal memory diagnosis (just "type diagnosis memory" in the start/search to start line). If it passes, then we will have to analyze the dump file is created.

  If the error messages are compatible - even verbiage and error code, it is more likely to be a driver problem. If they are constantly changing, so the problem is more likely to be a faulty hardware. Start by memory, then maybe a hard drive diagnostic. If they pass, then the next step is exchanging materials well known from the power supply. Good luck, Rick Rogers, aka "Crazy" - Microsoft MVP http://mvp.support.microsoft.com Windows help - www.rickrogers.org

• File blue screen screenshot, which is the cause of this blue screen

  My younger brother is using Sony VAIO laptop, Model: VGN-CR353 and Windows Vista Home Premium. Here's the DMP file for bluescreen.

  Download the dmp file: here

  What could cause this blue screen and how can it be solved?
  If you are unable to download the file, please let me know where to download for you.

  Best regards
  S.

  Looks like it's an error stop 0x0000001a MEMORY_MANAGEMENT. I would like to get rid of Symantec AV. And install something better to start. WHEN it crash? At any time? When you use a particular program? Looks like virtual clonedrive can also crash a system. If it is installed

• The matching blue screens and random reboots/crashes.

  Greetings. A year ago, I built a new computer, including the following parts:

  AMD Athlon 64 Dual Core 89W

  Motherboard ASUS M3A78 Pro

  Seagate Barracuda 7200.10 250 GB Sata internal HD

  4 GB of Ram DDR2 (not sure of the speed/brand)

  Since installing windows, I started getting blue screens of various types. Here are some blue screens I have met:

  Interrupt Unhandled Exception, failure of Page in the paginated, computer space made an attempt to write to read only memory, Memory_Management, IRQL not less or equal and Driver IRQL not less or equal. When these blue screens occur, some remain on the screen, while other flick on briefly and the computer begins to restart.

  On top of these blue screens, I also sound experience breaks down in loop in games. These experiences are breakers occur anywhere from 5 minutes to more than two hours of play.

  In the first dealing with this issue, I decided to test the memory with memtest86. A test actually froze on me. A second test showed no problems. Because of the freeze, I took a bit of ram to see if there could be a problem with some of the sticks is bad. Low and here are the problems disappeared. For a period of time. Some games have kept crashing on me, while others have worked without a hitch. I will mention that a game (World of Warcraft) seems to have more memory than others still ran without encountering any problem later.

  Because of all the questions, I decided to reformat/reinstall windows to make sure that everything has been installed correctly. Right out of the door, it began freezing at all normal intervals.

  I have this post is because I am curious about how of course, I can be that these problems are caused by a single hardware issue (I think I'm the ram). I ask because DDR2 Ram is cheaper and my motherboard will not support DDR3. However, if I buy the overvalued price DDR2 and it does not solve the problem, then it ends up being a pretty big money sink.

  Any guidance would be greatly appreciated.

  Hello

  Check this thread for more information on using BlueScreenView, MyEventViewer and other methods
  to troubleshoot the BlueScreens - first two responses.

  http://social.answers.Microsoft.com/forums/en-us/vistahardware/thread/8cd8362e-7d06-46FB-afd7-84d54b6a8ea7

  I hope this helps.

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

• MANY blue screens - no. Dumps and for different reasons

  I am running Windows 7 Ultimate SP1 - x 64

  My startup and recovery settings are set up right:

  Write an event to the log system - verified

  Automatically - restart disabled

  Image partial memory (256 KB)

  Directory: %SystemRoot%\Minidump

  Error Reporting Service - running and set to automatic

  I got all blue screens under the Sun, Ntfs.sys does not, LeAPC_INDEX_MISMATCHErreur, IRQL_NOT_LESS_OR_EQUAL, BAD_POOL_HEADER, MEMORY_MANAGEMENT (the most common), REFERENCE_BY_POINTER, PFN_LIST_CORRUPT, and more, it's just at a glance down the list Bug Check Code reference

  Whenever this happens, no minidumps are created in C:\Windows\Minidump, even after reinstalling Windows. Almost all parts of my PC has been replaced since it started, except the hard drive, CPU, optical drive Bay hard drive and 2 sticks of ram on 4.

  I'm sure that it is not overheating, that my temperature control it ever close to overheating, even when it bluescreens. And I replaced the power supply with no luck, so I guess this isn't a power failure.

  I made the disk, the controller memory, and System File Checker check without operating

  It makes me crazy, any help would be appreciated, thanks

  If the minidumps are still not created, check these reasons as to why that may happen

  For discharges to be product what follows must be correct

  Paging file must be on the same drive as your operating system

  The basic file size must be greater than the physical RAM installed

  Windows Error Reporting (WER) system service must be set to MANUAL

  Value file system run on the operating system drive

  The value of options/crash recovery system "kernel memory dump".

  User account control must be running.

  Sometimes the SSDS with an older firmware are not DMP (firmware update)

  Applications like Ccleaner cleaner remove DMP files to avoid them until you're fixed.

  Please read this wiki to know how to find and download your Event Viewer logs

• Blue screen of PC tailor-made

  I built a custom a little pc back, but it hangs at random times, gives me the blue screen. How can I find out what's wrong with it.

  Here's the file dump of the last fall.

  042515-17706 - 01.dmp 25/04/2015 15:41:47 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 0x000000c1 0xb0752fe8 0x00001f18 00000018 0 x 0 x 00000021 ntkrnlpa.exe ntkrnlpa.exe + dcb3c NT Kernel & System Microsoft® Windows® operating system Microsoft Corporation 6.1.7600.17273 (win7_gdr.130318 - 1532) 32-bit ntkrnlpa.exe + dcb3c ntkrnlpa.exe + e6a05 ntkrnlpa.exe + 11f0db ntkrnlpa.exe + 330f90 C:\Windows\Minidump\042515-17706-01.dmp 3 15 7600 143 360 4/25/2015 15:42:35

  Here is an another dump file:

  23758 042415 - 01.dmp 0x0000001a MEMORY_MANAGEMENT 24/04/2015-19:52:19 0 x 00041790 0xc0802066 0x0000ffff 0 x 00000000 halmacpi.dll halmacpi.dll + 5ba9 Hardware Abstraction Layer DLL Microsoft® Windows® operating system Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713 - 1255) 32-bit ntkrnlpa.exe + b9be0 ntkrnlpa.exe + b34c1 ntkrnlpa.exe + a8f7d ntkrnlpa.exe + 27acb0 C:\Windows\Minidump\042415-23758-01.dmp 3 15 7600 143 360 4/24/2015-19:53:16

  So the problem seems to be memory. Should I get the new ram sticks?

  Here's the last minidump: https://onedrive.live.com/redir?resid=8880d745468b7e67%21229

  Sorry for the delay.

  Run the version of Windows 7 tool linked below.

  Fix corruption of Windows errors by using the DISM or System Update Readiness Tool.

  https://support.Microsoft.com/en-us/KB/947821

  Then...

  It would certainly benefit upgrade your system to the latest service pack (SP1) available, if you haven't done so already.

  Steps to take before installing Windows 7 SP1 and Windows Server 2008 R2 SP1 starting from Microsoft Download Center.

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

  Learn how to install Windows 7 Service Pack 1 (SP1).

  http://Windows.Microsoft.com/en-us/Windows7/install-Windows-7-Service-Pack-1

  Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932)

  http://www.Microsoft.com/en-US/Download/details.aspx?ID=5842

  Troubleshoot installation of Service Pack 1 (SP1) for Windows 7 or Windows Server 2008 R2

  http://Windows.Microsoft.com/en-us/Windows7/troubleshoot-problems-installing-Service-Pack

  If you are still experiencing blockages of the system after the update, please download a share a link to the last. DMP files.

• Various blue screen of death windows 7, Asus laptop

  Experts/dear Microsoft community,

  Recently I had some problems with my laptop. I tried reformatting and everything but nothing seems to solve the problem long term, brief (2-3 days)

  My computer crashes (blue screen of death), whenever I play big games online. Games such as Company of Heroes, or Dota 2, etc. If I don't play these games solo (offline) I have no problems. Also all other programs work perfectly.

  I have a feeling that it has to do with my Asus laptop drivers, I tried to update, restore and re - install, but without result.

  To tell you that as the scenario for the crash: I start the game, I log on online, join a game. Then after 20 to 25 minutes of play online with no loss of FPS, it auto-shutsdown the game with absolutely no message, followed with an accident soon after, sometimes immediately.

  Here's the accident report I got the program: Whocrashed

  Look forward to hearing your suggestions.

  Concerning

  computer name: ICRASHEVERYWEEK
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  Material: N61Ja, ASUSTeK Computer Inc..
  CPU: GenuineIntel Intel (r) Core i5 CPU M 430 @ 2.27 GHz Intel586, level: 6
  4 logical processors, active mask: 15
  RAM: 4140355584 total
  VM: 2147352576, free: 1929850880

  --------------------------------------------------------------------------------
  Crash Dump Analysis
  --------------------------------------------------------------------------------

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Friday, November 7, 2014 22:01:49 this computer crashed
  crash dump file: C:\Windows\Minidump\110714-44912-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x5996A0)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003BF56A0, 0xFFFFF880035AEE88, 0xFFFFF880035AE6E0)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  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 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 the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, November 7, 2014 22:01:49 this computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80003BF56A0, 0xFFFFF880035AEE88, 0xFFFFF880035AE6E0)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  Bug control description: this bug check indicates that a system thread threw an exception that the error handler did not.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, November 7, 2014 18:29:29 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110714-17737-01.dmp
  This was probably caused by the following module: athrx.sys (athrx + 0x1C4F76)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88005E67F76, 0xFFFFF880035A7438, 0xFFFFF880035A6C90)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\athrx.sys
  product: Atheros CB42/CB43/MB42/MB43 network card driver
  company: Atheros Communications, Inc.
  Description: Atheros Extensible wireless device driver
  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.
  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: athrx.sys (pilot device wireless Atheros Extensible, Atheros Communications, Inc.).
  Google search: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

  Friday, November 7, 2014 18:27:43 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110714-14570-01.dmp
  This was probably caused by the following module: atikmdag.sys (atikmdag + 0x1421E5)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005B4A1E5, 0xFFFFF88003E795E0, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: ATI Technologies Inc.
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
  Google search: ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION

  Friday, November 7, 2014 6:26:57 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110714-15194-01.dmp
  This was probably caused by the following module: atikmdag.sys (0xFFFFF88005B20B5B)
  Verification of error code: 0 x 50 (0x0, 0xFFFFF88005B20B5B, 0xFFFFF8A0024CF000, 0x0)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: ATI Technologies Inc.
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: This indicates that invalid system memory was referenced.
  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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
  Google search: ATI Technologies Inc. PAGE_FAULT_IN_NONPAGED_AREA

  Friday, November 7, 2014 17:57:41 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\110714-49280-01.dmp
  This was probably caused by the following module: atikmdag.sys (atikmdag + 0x899D90)
  Bugcheck code: 0xBE (0x12F9A6860, 0xFFFFF880035BC560, 0xFFFFF880062ACD90, 0xE)
  Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: ATI Technologies Inc.
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: sounds if a driver attempts to write to a memory segment read-only.
  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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
  Google search: ATI Technologies Inc. ATTEMPTED_WRITE_TO_READONLY_MEMORY

  Friday, November 7, 2014 17:55:49 this computer crashed
  crash dump file: C:\Windows\Minidump\110714-16692-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000395AA49, 0xFFFFF8800AB310C0, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  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 exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  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.

  Saturday, November 1, 2014 8:24:12 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110114-17550-01.dmp
  This was probably caused by the following module: rdyboost.sys (rdyboost + 0x2C476)
  Bug check code: 0x1000007E (0x0, 0xFFFFF880035248B8, 0xFFFFFFFFC0000005, 0xFFFFF88003524110)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\rdyboost.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: driver for ReadyBoost
  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.

  Saturday, November 1, 2014 8:22:52 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\110114-18142-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B90)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  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 a kernel-mode program generated an exception which 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 the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, October 15, 2014 9:09:56 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\101514-50856-01.dmp
  This was probably caused by the following module: athrx.sys (athrx + 0xF9D77)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880051BED77, 0xFFFFF880033A7708, 0xFFFFF880033A6F60)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\athrx.sys
  product: Atheros CB42/CB43/MB42/MB43 network card driver
  company: Atheros Communications, Inc.
  Description: Atheros Extensible wireless device driver
  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.
  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: athrx.sys (pilot device wireless Atheros Extensible, Atheros Communications, Inc.).
  Google search: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

  --------------------------------------------------------------------------------
  Conclusion
  --------------------------------------------------------------------------------

  13 dumps were found and analysed. Only 10 are included in this report. 2 third party drivers have been identified 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:

  athrx.sys (Atheros Extensible, Atheros Communications, Inc. wireless device driver.)
  atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)

  If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

  Read the WARNINGS GENERAL topic for troubleshooting failures of the system for more information.

  Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

  Analysis of Dump 1Crash
  --------------------------------------------------------------------------------

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Monday, October 13, 2014 5:41:45 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\101314-17004-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B90)
  Verification of error code: 0 x 17 (0x0, 0x0, 0x0 0 x 0)
  Error: CID_HANDLE_DELETION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug control appears very rarely.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 5:41:45 PM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheck + 0x0)
  Verification of error code: 0 x 17 (0x0, 0x0, 0x0 0 x 0)
  Error: CID_HANDLE_DELETION
  Bug control description: this bug control appears very rarely.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 12:15:52 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\101314-17784-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x2EDF95)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003145F95, 0xFFFFF88004650448, 0xFFFFF8800464FCA0)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  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 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 the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 11:09:34 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\101314-14320-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0xA (28, 0 x 2, 0 x 0 x 0, 0xFFFFF80002F21D80)
  Error: IRQL_NOT_LESS_OR_EQUAL
  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 Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  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.

  Monday, October 13, 2014 2:53:45 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\101314-46987-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x3B (0xC0000005, 0x0, 0x0, 0xFFFFF88002DA2910)
  Error: SYSTEM_SERVICE_EXCEPTION
  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 exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  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.

  Sunday, September 28, 2014 17:57:12 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\092814-16926-01.dmp
  This was probably caused by the following module: dxgmms1.sys (dxgmms1 + 0xC0A1)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  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 kernel-mode program generated an exception which 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.
  Google search: Microsoft Corporation KMODE_EXCEPTION_NOT_HANDLED

  Monday, September 22, 2014 6:50:05 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092214-42525-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1A (0xFFFFF780C0000000, 0x1DEE, 0 x 5003, 0x420700003BD8)
  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.

  --------------------------------------------------------------------------------
  Conclusion
  --------------------------------------------------------------------------------

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

  dxgmms1.sys (DirectX Graphics MMS, Microsoft Corporation)

  If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

  Read the WARNINGS GENERAL topic for troubleshooting failures of the system for more information.

  Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

  PC! PK

  These two were related to the material.  Specifically of the RAM.  Please run memtest