1.    07 May 2015 #1
    Join Date : May 2015
    Netherlands
    Posts : 3
    Windows 10 Build 10074

    MEMORY_MANAGEMENT / 0x8000200000000002 errors since build 10074


    Hello everyone,

    I just registered here, so please don't blame me if I'm at the wrong forum. :P

    So, the last few days my ASUS N56VB notebook keeps getting BSODs saying theres an MEMORY_MANAGEMENT error. I performed a Windows Memory Diagnostics check. And yes, strangely enough it does say there is a problem with my memory. However, to me that sounds ridiculous. And this is why: prior to build 10074, which I installed last Monday, I NEVER EVER had this, nor any related problem. And I replaced my memory like a few months ago. Again, never had problems. Has been working like a charm! Also have been using the Windows 10 Technical Preview since its initial release.

    I would be pleased to have some suggestions about what the actual problem could be, and of course any other potential solutions. If any other data could be helpful in finding the problem, please let me know.

    Here is the log from the Event Viewer, which might be a little helpful:


    Code:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
      <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
      <EventID>41</EventID> 
      <Version>3</Version> 
      <Level>1</Level> 
      <Task>63</Task> 
      <Opcode>0</Opcode> 
      <Keywords>0x8000200000000002</Keywords> 
      <TimeCreated SystemTime="2015-05-07T18:03:18.572334600Z" /> 
      <EventRecordID>3691</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="4" ThreadID="8" /> 
      <Channel>System</Channel> 
      <Computer>TOMB</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="BugcheckCode">0</Data> 
      <Data Name="BugcheckParameter1">0x0</Data> 
      <Data Name="BugcheckParameter2">0x0</Data> 
      <Data Name="BugcheckParameter3">0x0</Data> 
      <Data Name="BugcheckParameter4">0x0</Data> 
      <Data Name="SleepInProgress">0</Data> 
      <Data Name="PowerButtonTimestamp">130754953750637438</Data> 
      <Data Name="BootAppStatus">0</Data> 
      </EventData>
      </Event>
    
    
      My ComputerSystem Spec
  2.    07 May 2015 #2
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,207
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    I am sorry but it does not sound ridiculous to me. Your RAM was good yesterday, it does not mean it is good today and it does not matter how new it is either.

    If the memtest stated that you have a bad memory then chances you have a bad stick. I suggest to open the case/laptop and re-seat the RAM tightly and try again. If it does not work, re-run memtest: Memtest86+ - Advanced Memory Diagnostic Tool. Let it run for 4-6 hours unless errors occur earlier.
      My ComputerSystem Spec
  3.    07 May 2015 #3
    Join Date : May 2015
    Netherlands
    Posts : 3
    Windows 10 Build 10074
    Thread Starter

    Quote Originally Posted by topgundcp View Post
    I am sorry but it does not sound ridiculous to me. Your RAM was good yesterday, it does not mean it is good today and it does not matter how new it is either.

    If the memtest stated that you have a bad memory then chances you have a bad stick. I suggest to open the case/laptop and re-seat the RAM tightly and try again. If it does not work, re-run memtest: Memtest86+ - Advanced Memory Diagnostic Tool. Let it run for 4-6 hours unless errors occur earlier.
    Do understand it doesn't have to be ridiculous. I just find it very strange that the problems occur RIGHT AFTER installation of a new build. That's quite a coincidence, isn't it?

    Anyway, will check the physical modules then, and check whether it works again or not, if they don't sit well or something.

    EDIT: So I have checked the modules. One of them seemed a little loose to me, though I don't expect that to be the (main) cause of the BSODs. Decided to switch the modules (not with other modules, but just from one slot to another). After rebooting everything seems double as fast. Not sure if that's because of the modules I switched. But anyway, I'll have to see whether the error will show up again or not.
      My ComputerSystem Spec
  4.    07 May 2015 #4
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,207
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    If one of the stick is loose, that will also cause the memory to fail. By switching the sticks around and it works, it also does not guarantee that all sticks are good, Windows got loaded into the good part of the RAM until one/some bad spots on the stick get used then you'll run into the problem again. It is best to re-run the memory test to ensure all sticks are good.

    Cheers !!!
      My ComputerSystem Spec
  5.    07 May 2015 #5
    Join Date : Oct 2013
    Wolves, England
    Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM

    Quote Originally Posted by topgundcp View Post
    If the memtest stated that you have a bad memory then chances you have a bad stick. I suggest to open the case/laptop and re-seat the RAM tightly and try again. If it does not work, re-run memtest: Memtest86+ - Advanced Memory Diagnostic Tool. Let it run for 4-6 hours unless errors occur earlier.
    Just a note; MemTest86+ should be run for a minimum of eight passes for more conclusive results, this can take several hours depending on how much RAM is installed. 4-6 hours isn't long enough in most cases to complete eight full passes.
      My ComputerSystem Spec
  6.    09 May 2015 #6
    Join Date : Oct 2014
    Posts : 230
    10

    Should the BSOD's return (after running the memory diagnostics) please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum): Solved BSOD - Posting Instructions - Windows 10 Forums
      My ComputerSystem Spec
  7.    09 May 2015 #7
    Join Date : May 2015
    Netherlands
    Posts : 3
    Windows 10 Build 10074
    Thread Starter

    Added the ZIP file
      My ComputerSystem Spec
  8.    09 May 2015 #8
    Join Date : Oct 2013
    Penns Forrest
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3

    Side note: 10.074 has been giving me occasional memory errors on shutdown. This occurred back in an earlier release as well (don't recall the rls #). It appears as though there is a memory leak in 10.074 (not unexpected in preview code).

    It's possible that the RAM was not seated correctly and it's possible that the memory leak kept flooding that area of RAM.

    I only stopped in to post what I observed as a memory leak on my HP laptop.

    Run the long memory test as suggested to see fully test your RAM condition.
    You have some of the best minds for troubleshooting BSODs already on your thread,
      My ComputerSystem Spec
  9.    10 May 2015 #9
    Join Date : Oct 2014
    Posts : 230
    10

    Your BIOS/UEFI dates from 2013 - I would strongly suggest updating it (if available from the manufacturer's support website):
    BIOS Version: American Megatrends Inc. N56VB.202, 21-1-2013
    Lot's of Windows Updates failures in the WER section of the MSINFO32 report. If the problems continue, please post over in the Windows Updates Activation - Windows 8 Forums for further expert assistance with this issue.

    The WER section of MSINFO32 shows 6 BSOD's with 3 different error codes - this is often a sign of a hardware or low-level driver error. This is consistent with the memory stick problems that you described earlier. Have you done the memory diagnostics that were suggested earlier?

    You have Avast and BitDefender installed. Please uninstall one of them. DO NOT run more than one antivirus and one firewall at a time. They will compete with each other - which can lead to errors (to include BSOD's) or could even allow malware onto your system.

    You also have MalwareBytes installed - please uninstall it. The next time that you choose to install it, please remember to uncheck the offer for the Pro version during installation - that will ensure that it's components don't run in memory alongside other antivirus programs.

    Overall this is a clean system that most likely has RAM problems. I'd expect that the other things that I've cited would cause the problems to occur more frequently, so I'd suggest fixing them no matter what the state of the RAM testing.

    Should the BSOD's continue (after running the RAM tests and after fixing the things that I've suggested) then post back with the latest memory dumps and we'll move on from there.

    Good luck!

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sat May  9 05:11:37.147 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\050915-51937-01.dmp]
    Windows 8 Kernel Version 10074 MP (8 procs) Free x64
    Built by: 10074.1.amd64fre.fbl_impressive_cxe.150425-1755
    System Uptime:0 days 18:10:52.942
    Probably caused by :ntkrnlmp.exe ( nt!KiSwapThread+68d )
    BugCheck A, {ffffe021b145c8c8, 2, 0, fffff8019f0c6abd}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
    Arguments: 
    Arg1: ffffe021b145c8c8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8019f0c6abd, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  bdagent.exe
    FAILURE_BUCKET_ID: AV_nt!KiSwapThread
    CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2395
      BIOS Version                  N56VB.202
      BIOS Release Date             01/21/2013
      Manufacturer                  ASUSTeK COMPUTER INC.
      Product Name                  N56VB
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Sat May  9 05:11:37.147 2015 (UTC - 4:00)**************************
    GEARAspiWDM.sys              Thu May  3 15:56:17 2012 (4FA2E2E1)
    IntcDAud.sys                 Tue Jun 19 10:40:51 2012 (4FE08F73)
    HECIx64.sys                  Mon Jul  2 18:14:58 2012 (4FF21D62)
    kbfiltr.sys                  Wed Aug  1 23:22:22 2012 (5019F26E)
    iaStorA.sys                  Mon Nov 19 15:09:40 2012 (50AA9204)
    npf.sys                      Thu Feb 28 20:31:24 2013 (513004EC)
    L1C63x64.sys                 Sun Mar 31 23:15:17 2013 (5158FBC5)
    AsusTP.sys                   Thu May  9 05:23:42 2013 (518B6B1E)
    vmci.sys                     Fri May 17 21:19:18 2013 (5196D716)
    athwbx.sys                   Mon Jul 15 03:29:50 2013 (51E3A4EE)
    iwdbus.sys                   Wed Jul 24 21:06:12 2013 (51F07A04)
    vstor2-mntapi20-shared.sys   Wed Aug 28 06:25:49 2013 (521DD02D)
    igdkmd64.sys                 Mon Sep 16 20:08:54 2013 (52379D96)
    AsHIDSwitch64.sys            Mon Oct  7 21:45:17 2013 (525363AD)
    btfilter.sys                 Thu Jan  2 00:24:20 2014 (52C4F804)
    mwac.sys                     Tue Jun 17 22:07:00 2014 (53A0F444)
    vsock.sys                    Sun Jun 29 20:37:03 2014 (53B0B12F)
    VMNET.SYS                    Sun Jul 27 09:30:27 2014 (53D4FEF3)
    vmnetadapter.sys             Sun Jul 27 09:30:30 2014 (53D4FEF6)
    vmnetbridge.sys              Sun Jul 27 09:30:32 2014 (53D4FEF8)
    mbam.sys                     Wed Sep  3 13:50:25 2014 (540754E1)
    trufos.sys                   Sat Oct 11 05:01:08 2014 (5438F1D4)
    gzflt.sys                    Wed Oct 22 03:29:01 2014 (54475CBD)
    hcmon.sys                    Wed Jan  7 11:02:45 2015 (54AD58A5)
    MBAMSwissArmy.sys            Thu Jan  8 21:45:43 2015 (54AF40D7)
    avc3.sys                     Wed Jan 14 04:58:21 2015 (54B63DBD)
    avchv.sys                    Fri Jan 23 08:52:58 2015 (54C2523A)
    vmnetuserif.sys              Fri Feb  6 19:51:47 2015 (54D561A3)
    vmx86.sys                    Fri Feb  6 21:29:47 2015 (54D5789B)
    RTKVHD64.sys                 Mon Mar  2 04:57:24 2015 (54F43404)
    nvpciflt.sys                 Wed Mar 11 15:42:26 2015 (55009AA2)
    nvlddmkm.sys                 Wed Mar 11 15:48:01 2015 (55009BF1)
    intelppm.sys                 Fri Apr 24 19:13:05 2015 (553ACE01)
    WindowsTrustedRTProxy.sys    Fri Apr 24 19:14:48 2015 (553ACE68)
    WindowsTrustedRT.sys         Fri Apr 24 19:14:50 2015 (553ACE6A)
    mirahid.sys                  Fri Apr 24 19:23:34 2015 (553AD076)
    storqosflt.sys               Fri Apr 24 19:25:38 2015 (553AD0F2)
    filecrypt.sys                Sat Apr 25 23:20:23 2015 (553C5977)
    
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=kbfiltr.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=npf.sys
    http://www.carrona.org/drivers/driver.php?id=L1C63x64.sys
    http://www.carrona.org/drivers/driver.php?id=AsusTP.sys
    http://www.carrona.org/drivers/driver.php?id=vmci.sys
    http://www.carrona.org/drivers/driver.php?id=athwbx.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=vstor2-mntapi20-shared.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=AsHIDSwitch64.sys
    http://www.carrona.org/drivers/driver.php?id=btfilter.sys
    http://www.carrona.org/drivers/driver.php?id=mwac.sys
    http://www.carrona.org/drivers/driver.php?id=vsock.sys
    http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
    http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
    http://www.carrona.org/drivers/driver.php?id=mbam.sys
    http://www.carrona.org/drivers/driver.php?id=trufos.sys
    http://www.carrona.org/drivers/driver.php?id=gzflt.sys
    http://www.carrona.org/drivers/driver.php?id=hcmon.sys
    http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
    http://www.carrona.org/drivers/driver.php?id=avc3.sys
    http://www.carrona.org/drivers/driver.php?id=avchv.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
    http://www.carrona.org/drivers/driver.php?id=vmx86.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    WindowsTrustedRTProxy.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    WindowsTrustedRT.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    mirahid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    storqosflt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    filecrypt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
Solved build 10074
I had build 10074 and was having problems with the mail app. I refreshed and went back to windows 8 and then 8.1. I decided to download build 10122 but when I down loaded I was only given build 10074. After downloading I was only getting windows 7,...
Windows Insider
should I reinstall build 10074
All was working well with build 10074, then for some reason, I lost the start screen, Cortana and the ability to personalize the display. I can right click the start icon (greyed out) and I can click on the 'search' option , but nothing happens. ...
Installation and Upgrade
Any idea when build the next build AFTER 10074 comes out?
hi guys, seen the video of Build 10114 (if i am correct). so when will this come out. Since Build 10074 blocked my internal network, i had to go back to Build 10061. Numbers.....numbers
Windows Insider
Build 10074 not working as should
hi guys, my network and/or homegroup no longer work. After searching and trying to fix this (a couple of hours) i gave up, gave feedback to MS and returnde to Build 10061. Hate to do a fresh install, although i have burned the ISO. So i...
Network and Sharing
Windows 10 Build 10074 Expected at BUILD 2015
Source UPDATE: https://www.tenforums.com/windows-10-news/5698-new-windows-10-insider-preview-build-10074-now-available.html
Windows 10 News
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 14:51.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums