Random, intermittent BSOD on bootup 0x00000109 and 0x00000050


  1. Posts : 10
    Win7 Ultimate x64
       #1

    Random, intermittent BSOD on bootup 0x00000109 and 0x00000050


    Hello,
    Ive got a machine here that is giving random BSOD messages during bootup, I have no idea if its fixed, because it could be OK from now on for a month or more, last time it happened was over 2 weeks ago, but I can only find the 2 most recent logs or memory dumps (probably due to Ccleaner)

    Ive disconnected hardware i suspect may be the cause but Ill wait and see.

    I have not experienced any BSOD while the machine is running, only has done it a handful of times when booting the computer.

    Memory tests OK
    Hard drive tests perfect, no bad sectors, SMART reports all good, etc.
    Ran every malware scan, jrt, combofix etc in the book and system comes clean.

    Below are the logs of the two BSOD's
    Attached are the memory dumps.

    0x00000109 can be related to bad memory, but 0x00000050 is often related to HDD communication errors etc.

    Anyway, i expect any subsequent BSOD's could potentially give different error codes, which makes it hard to diagnose.
    Usually random ones indicate faulty memory, but memtest86 is all clear on several passes, i may need to run for 24 hours or more perhaps, but im lost to what it could be.

    Ntoskrnl is the only thing they have in common, but if i get any more BSOD's I will update this thread...

    TIA


    Dump File 112116-18828-01.dmp
    Crash Time
    21/11/2016 6:38:00 a.m.
    Bug Check String
    Bug Check Code 0x00000109
    Parameter 1 a3a039d8`95e5d550
    Parameter 2 b3b7465e`e862a4a6
    Parameter 3
    fffff800`0326c760
    Parameter 4
    00000000`00000001
    Caused By Driver ntoskrnl.exe
    Caused By Address ntoskrnl.exe+70180
    File Description
    NT Kernel & System
    Product Name Microsoft® Windows® Operating System
    Company Microsoft Corporation
    File Version 6.1.7601.23539 (win7sp1_ldr.160902-0600)
    Processor
    x64
    Crash Address
    ntoskrnl.exe+70180
    Computer Name Full Path C:\Windows\Minidump\112116-18828-01.dmp
    Processors Count
    4
    Major Version
    15
    Minor Version
    7601
    Dump File Size
    282,776
    Dump File Time
    21/11/2016 10:39:26 a.m.


    Dump File 111916-23187-01.dmp
    Crash Time 19/11/2016 10:39:55 p.m.
    Bug Check String
    PAGE_FAULT_IN_NONPAGED_AREA
    Bug Check Code
    0x00000050
    Parameter 1
    ffffffff`fffffff8
    Parameter 2 00000000`00000001
    Parameter 3 fffff800`0d9d6763
    Parameter 4
    00000000`00000000
    Caused By Driver
    ntoskrnl.exe
    Caused By Address ntoskrnl.exe+70180
    File Description
    NT Kernel & System
    Product Name Microsoft® Windows® Operating System
    Company Microsoft Corporation
    File Version
    6.1.7601.23539 (win7sp1_ldr.160902-0600)
    Processor
    x64
    Crash Address
    ntoskrnl.exe+70180
    Computer Name Full Path C:\Windows\Minidump\111916-23187-01.dmp
    Processors Count
    4
    Major Version
    15
    Minor Version
    7601
    Dump File Size 284,520
    Dump File Time
    19/11/2016 10:41:18 p.m.
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    Hi nzoomed,

    Welcome to the 7forums and apologies for the delay.

    Are you still in need of help?
      My Computer


  3. Posts : 10
    Win7 Ultimate x64
    Thread Starter
       #3

    Thanks for your reply.

    If its possible to analyse those memory dumps, it might be able to help me, if it points to any particular piece of hardware.

    I still dont know if its fixed, because it might be fine for another week or more before i see another BSOD.

    So far, its behaving itself but only time will tell.
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #4
      My Computer


  5. Posts : 10
    Win7 Ultimate x64
    Thread Starter
       #5

    Are the minidumps not enough?
    I dont have access to the computer for a while. Will be in touch.
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #6

    A single dump is not enough
      My Computer


  7. Posts : 10
    Win7 Ultimate x64
    Thread Starter
       #7

    OK, well ill try and get more dumps when I get access to the computer, but those dumps uploaded were the only ones there.
      My Computer


  8. Posts : 7,050
    Windows 10 Pro
       #8

    There is more addition information required to properly troubleshoot, this information can be provided by following the BSOD Posting Instructions.
      My Computer


  9. Posts : 10
    Win7 Ultimate x64
    Thread Starter
       #9

    axe0 said:
    There is more addition information required to properly troubleshoot, this information can be provided by following the BSOD Posting Instructions.
    Yes Ive read those, will try it when i get back.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:23.
Find Us