Various BSOD errors on new build


  1. Posts : 1
    Windows 10 64bit
       #1

    Various BSOD errors on new build


    So since putting together my first Intel build I have been getting all sorts of BSOD errors when booting up my computer. They seem to change pretty often but some of the most common ones have been:

    MEMORY_MANAGEMENT
    BAD_POOL_HEADER
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    The errors only occur when booting up my computer; once it 'diagnoses' itself I don't seem to have any problems after that, and I never get BSOD on restarts. So far some of the things i've tried:

    - Updating all drivers numerous times
    - Uninstalling/reinstalling graphics driver in safe mode
    - Disabling start-up processes
    - Checking BIOS is up to date
    - Running disk checks
    - Running system file check
    - Running virus scans
    - Running Windows Memory Diagnostic
    - Uninstalling unnecessary software
    - Disconnecting external USB devices, as well as network adapter

    Then yesterday I noticed that the PC boots up fine with only one ram stick inserted, but I get BSOD when both are inserted. I tried the other stick on its own and again it booted up fine. Then I tried them both together again, but in a different configuration, and I got BSOD. So I ran memtest86 on one of the sticks overnight, and this was the result:

    Attachment 63462

    Am I right in thinking that this means the RAM stick is faulty? I am going to run memtest on the other stick tonight.

    In the meantime though, I was wondering if anyone could have a look at my logs (attached) and tell me if there's anything else causing the problem?
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #2

    3]Am I right in thinking that this means the RAM stick is faulty? I am going to run memtest on the other stick tonight.
    That is right yes, the 0x50 is a bit known for being there when memory problems occur
    Code:
    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.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ffffc0000290af28, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff803a952ac12, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000002, (reserved)
      My Computers


 

  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 07:46.
Find Us




Windows 10 Forums