• Hello,

    I have just recently built a shiny new computer, but it seems that it has a habit of getting a blue screen error 0x0000000a IRQL_NOT_LESS_OR_EQUAL. It has happened three times som far, and I think I can safely assume that it's not a fluke.

    In most 0x0000000a cases it's faulty RAM or RAM slots, but I have just run a 10.5 hours memtest86 test and it reported no errors.

    Debug of the latest coredump you can see here
    It says "Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )"

    I've already established the problem is not due to faulty RAM chips or faulty RAM slots, what can it be?

    Any help is greatly appreciated. Thank you.

    Sunday, June 26, 2011 9:40 AM


  • For future reference, Driver verifier (built in to win 7) will "watch" for mis-behaving drivers and then put it into the DMP when it crashes the system.  It crashes the system when it finds misbehaving drivers so it can write them to the DMP on reboot.
    Wednesday, April 11, 2012 11:40 PM

All replies

  • Update,

    I have experienced another BSOD but with different error message this time.


    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )


    I have googled the problem and I've seen several posts suggesting it might either be the BIOS, Intel Chipset driver or Nvidia drivers causing this problem.
    Does anyone with more experience in reading crashdumps see anything useful in there that can pinpoint the problem? 

    Sunday, June 26, 2011 10:50 AM
  • Bug Check Code 0xA:

    Try what is mentioned in the article I gave.

    If this does not help, uninstall all programs that you don't use and perform a full scan on your disks to delete all malware programs.

    Also, install SP1.

    It will be better to use Microsoft Skydrive and upload the dump here.

    You can also contact Microsoft CSS.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    Sunday, June 26, 2011 11:21 AM
  • Thanks for you reply.

    I have shared the crashdumps here!152


    1. Download and install updates and device drivers for your computer from Windows Update.
    2. Scan your computer for computer viruses.
    3. Check your hard disk for errors.

    I have downloaded all updates from Windows Update, as well as scanned my computer for virues. Nothing was found.
    Error check of hard disk is in progress.

    Chipset drivers and BIOS is up to date with the latest drivers (the motherboard is brand new, so the supplied drivers and BIOS version were the latest ones available for these devices).

    Other things I have done is I rolled back the NVIDIA driver to the driver that came with my card (Asus GeForce GTX580 DCU II), and I found an oddity in the BIOS which had the RAM chips running at 1333MHz even though these chips are designed for 1600MHz (and the motherboard supports 1066/1333/1600). I then set the BIOS to enforce 1600MHz speed on the RAM modules.

    After these two changes I have not experienced another BSOD, but I have had the system freeze/lock up on two occasions. These incidents do not show up in the event log, the only entry that is logged is the power failure when I shut down the computer (to get out of the freeze/lock up). 

    Sunday, June 26, 2011 3:36 PM
  • Couple things....

    IRQL_NOT_LESS_OR_EQUAL is frequently a driver problem, but it sounds like you've been updating, so let's look at some other possibilities


    Make sure you have a sufficient power supply.  If you don't, you can get weird issues that don't show up in software.

    The other thing is that your hard drive could have some bad sectors, which, if the bad sector is in your page file, could show up as a memory corruption error.  Try running a chkdsk /r


    Are you doing anything in particular when this happens?  Is it just idling, or are you gaming/watching videos/etc?

    Sunday, June 26, 2011 9:38 PM
  • Thank you both for your replies.

    Notice: I've experienced another BSOD (MEMORY_MANAGEMENT error message this time), I've added the log to my SkyDrive share (it's called 062611-9079-01.dmp).


    @Zac Lockard:

    My power supply is at 800w capacity, this should be more than enough for my setup. Reference the list I'm providing further down this post.

    I will try to run a chkdisk /r, thanks for the tip.

    The BSODs I have experienced both while idling and while gaming. The first occurence (IRQL_NOT_LESS_OR_EQUAL) happened when I was trying out World of Warcraft on this new system (first time I ran it). I was also testing the performance of the capture tool FRAPS ( at the time, recording to disk at 30fps 1920x1200. The second and third BSOD (MEMORY_MANAGEMENT) I had while idling at the desktop. I only had the mIRC client running at the time.

    The system seems to run fine otherwise. I have been benchmarking the system with 3Dmark Vantage, Cinebench and Unigine Heaven without experiencing any problems. The BSODs seems very random to me.


    @Vegan Fanatic:

    The hardware specifics are the following:


    ASUS P8Z68 Deluxe, Socket-1155
    Intel Core™ i7 2600K 3.4 GHz Quad Processor
    Fractal Design Define XL Black Pearl Computer Case
    Fractal Design Newton R2 800W PSU
    Noctua NH-D14 CPU Cooler
    Samsung 1 TB 7200RPM S-ATA2 32MB
    ASUS GeForce GTX 580 1536MB PhysX CUDA
    Samsung SH-B123L/BSBP DVD±RW BD-ROM Drive
    Corsair XMS3 DDR3 1600MHz 16GB CL9 (4 × 4 GB kit)
    Kingston SSDNow! V+100 256 GB

    (Relevant?) drivers:

    BIOS: P8Z68 DELUXE 0501 BIOS with IRST (latest)
    Chipset: Intel Chipset Inf V9.2.0.1021, for Z68 chipsets (latest)
    NVIDIA: 263.09, I have also tried version 275.33 but experienced the same problem (BSOD) with this one. Currently rolled back to 263.09 (which was on the driver CD) 

    All the components except the SSD unit are brand new. The SSD unit I 'scavenged' from my laptop, formatted it, and installed Windows 7 on in the new system.

    The Windows install is brand new (clean). I built this system on friday/saturday.



    I'm planning to run another Memtest86 test (while I'm asleep and at work tomorrow) that I will let run for at least 10 passes, perhaps it will show anything new?

    Another theory I got is that reusing the SSD might be a problem? I have no extensive experience in pinpointing the problem in a matter like this, and it's pure speculation from my side.
    I fear that it might be the motherboard (I've read on some forums that faulty chipsets or RAM slots can cause errors like these), but I'm trying to exhaust any other option before I settle for that.

    Again, thank you for helping, I really appreciate it. 

    Sunday, June 26, 2011 11:36 PM
  • Addition:

    Latest memtest86+ run stopped.

    From what I've gathered, this may be a faulty RAM stick or faulty motherboard.

    Gonna try and run each stick through memtest86+ to see if I can find out more. If it's the motherboard, I'm not sure how exactly to prove that.

    Monday, June 27, 2011 2:13 PM
  • Please refer to the following article to analyze your mini dump file and see if there is any clues.

    How to read the small memory dump files that Windows creates for debugging

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Tuesday, June 28, 2011 7:33 AM
  • I have been testing a bit more and seem to have pinpointed the cause. I believe the system crashes when both memory channels are accessed at the same time. System runs smooth with memory modules in only one channel, but as soon as both channels are populated, I got a system crash on my hands.

    Thank you for your help and suggestions, I think I'll just return my motherboard to the shop now.

    Tuesday, June 28, 2011 4:19 PM
  • Update:

    Put in all memory modules, reset CMOs, applied XMP for my mem modules, reinstalled Windows, did not install all motherboard and graphics card extra utilities (bloatware) from ASUS.

    System works 100% now, no BSOD or errors over 30 hours use.

    Problem solved - bad software and/or drivers!

    Thursday, June 30, 2011 9:01 AM
  • For future reference, Driver verifier (built in to win 7) will "watch" for mis-behaving drivers and then put it into the DMP when it crashes the system.  It crashes the system when it finds misbehaving drivers so it can write them to the DMP on reboot.
    Wednesday, April 11, 2012 11:40 PM