BSoD Memory Management at Desktop + Ingame

Page 1 of 3 123 LastLast

  1. Posts : 13
    Windows 10 Pro
       #1

    BSoD Memory Management at Desktop + Ingame


    Hey guys,

    I built a new PC and now I have some troubles getting it to work.
    I get so many bluescreens, most of them appear when I am on the desktop a few minutes after the PC starts (sometimes I can start playing games, but after a few minutes the PC crashes). I am not even able to save the dumpfiles because the PC crashes so fast after rebooting, but fortunately I was able to save some on my memory stick so I can provide them now (I am posting this from another PC). I am sorry that I cannot provide any more information.

    I will attach the dumps and hopefully you guys can help me out... would really appreciate that:)

    PC Specs:
    Windows 10 Pro
    Intel Core i7 6700k
    ASRock Z170 Extreme 6+
    32GB HyperX 2800 MHz CL14
    EVGA GeForce GTX 980 TI Superclocked ACX 2.0
    Corsair RM750i
    Corsair H110 for CPU water cooling
      My Computer


  2. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #2
      My Computer


  3. Posts : 13
    Windows 10 Pro
    Thread Starter
       #3

    Sorry for being stupid, here we go again.

    Hopefully it is okay this time.

    Thanks in advance
      My Computer


  4. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #4

    Your Intel Pro/1000 Network Adapter driver has been flagged. Check your motherboard manufacturer's support page or the Intel site for an updated version.

    Code:
    *** WARNING: Unable to verify timestamp for e1d65x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1d65x64.sys
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    0: kd> lmvm e1d65x64
    start             end                 module name
    fffff800`d8c00000 fffff800`d8c85000   e1d65x64 T (no symbols)           
        Loaded symbol image file: e1d65x64.sys
        Image path: \SystemRoot\system32\DRIVERS\e1d65x64.sys
        Image name: e1d65x64.sys
        Timestamp:        Thu Jun 18 17:37:56 2015 (5582F3E4)
        CheckSum:         0008FF35
        ImageSize:        00085000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  5. Posts : 13
    Windows 10 Pro
    Thread Starter
       #5

    Hey,

    I'm still getting bluescreens...

    I got the first one when I was ingame for about 30 minutes
    and the other ones right after the PC restarted after the previous bluescreens.

    I updated the driver you mentioned (hope I did it right).

    I attached some new dumpfiles, could anyone analyze them, please ?

    Thank you so much.
    Last edited by EnRage95; 05 Sep 2015 at 14:01.
      My Computer


  6. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #6

    Sorry for the late reply, I've been a bit under the weather the last few days.

    The latest dumps aren't pinpointing anything particular, but a couple of things worth checking out are listed in the code below. Razer Game Scanner has shown in a couple of the dumps (listed below) and while it could be a false positive it's worth eliminating it as a possible cause. Try disabling it in Services or uninstall the Razer software completely for testing purposes.

    It may also be worth testing the RAM to rule it out.

    Download and run MemTest86+ to test your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

    Code:
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41792, fffff6800002b1a0, 8000, 0}
    
    Probably caused by : memory_corruption ( ONE_BIT )
    
    Followup: MachineOwner
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
        the PTE. Parameters 3/4 contain the low/high parts of the PTE.
    Arg2: fffff6800002b1a0
    Arg3: 0000000000008000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    MEMORY_CORRUPTOR:  ONE_BIT
    
    BUGCHECK_STR:  0x1a_41792
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  GameScannerSer
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    STACK_TEXT:  
    ffffd000`21d4f5a8 fffff803`d57f17ee : 00000000`0000001a 00000000`00041792 fffff680`0002b1a0 00000000`00008000 : nt!KeBugCheckEx
    ffffd000`21d4f5b0 fffff803`d56a0df0 : 00000000`00000001 fffff803`d59baa80 ffffe000`8d2dcd38 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x209ee
    ffffd000`21d4f7b0 fffff803`d5a802ac : ffffe000`8dd61b20 ffffe000`8dd61b20 00000000`00000000 00000000`052c0000 : nt!MiDeleteVad+0x4b0
    ffffd000`21d4f8e0 fffff803`d5a80967 : 00000000`00000000 00000000`00000008 00000000`052c0000 00000000`04f7fd01 : nt!MiUnmapViewOfSection+0xec
    ffffd000`21d4f9b0 fffff803`d57cc863 : ffffe000`8bf37080 00000000`00000000 ffffe000`8bf37001 ffffe000`8d2dc840 : nt!NtUnmapViewOfSectionEx+0x77
    ffffd000`21d4fa00 00007ffc`a68e379a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`04f7e9a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`a68e379a
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ONE_BIT
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    
    BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit
    
    FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}
      My Computer


  7. Posts : 13
    Windows 10 Pro
    Thread Starter
       #7

    Thank you for responding.

    I disabled Razer Game Scanner and was able to play for about 20 minutes, then my game crashed again. After the first Bluescreen, my PC restarted and I got more Bluescreens right after I got on the Desktop.

    I will run memtest overnight and inform you about the result asap.

    I will attach new dumpfiles...it is getting frustrating, because I keep getting new bluescreens all the time, which I assume is not a good thing...

    And again, thank you for your help and patience.
      My Computer


  8. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #8

    You're welcome, I'll check on these tonight when I get home from work as I don't have access to WinDBG at the moment. We could do with the MemTest86+ results as well really to rule that out before we go digging anywhere else.
      My Computer


  9. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #9

    All of the latest dumps are still showing memory corruption, we need the results from MemTest86+ to be able to rule out RAM. Have you run it yet?

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41792, fffff68056971b60, 8, 0}
    
    Probably caused by : memory_corruption ( ONE_BIT )
    
    Followup: MachineOwner
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ONE_BIT
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    Code:
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff80067aa31c6, ffffd001144470f8, ffffd00114446910}
    
    Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+3e )
    
    Followup: MachineOwner
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  Origin.exe
    
    CURRENT_IRQL:  2
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
      My Computer


  10. Posts : 13
    Windows 10 Pro
    Thread Starter
       #10

    I've been running memtest for about 30 hours now, when I woke up today it finished 9 passes without any errors. Memtest is still running, but I can't give you an Update because I am at work atm. Will stop the Test this evening.
      My Computer


 

  Related Discussions
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 13:13.
Find Us




Windows 10 Forums