Multiple BDOS in the last few days, all different error messages.

Page 1 of 2 12 LastLast

  1. Posts : 9
    10
       #1

    Multiple BDOS in the last few days, all different error messages.


    Hello guys, these past couple weeks ive had frequent BSOD, 0-2 a day.
    The thing with these BSOD is that the last couple that I had, all had different error messages.
    Here are some of the most recent ones below.

    IRQL_NOT_LESS_OR_EQUAL
    ATTEMPTED_WRITE_TO_READONLY_MEMORY
    IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    MEMORY_MANAGEMENT
    PFN_LIST_CORRUPT

    Ive been thinking about just taking my computer apart and rebuild it and then do a fresh install of Windows wiping everything. Hoping that it might fix the problem, but before going to that length I thought id seek help to see if i can resolve this issue without doing that. So here I am.
    Any help are very much appreciated.
      My Computer

  2. axe0's Avatar
    Posts : 14,784
    Windows 10 Pro
       #2

    Hi krislin,

    Welcome to the 10forums :)

    Different error codes usually suggest hardware problems, sometimes specifically the RAM.

    Please update the BIOS to version 3103
    MAXIMUS VII HERO | Motherboards | ASUS Global
      My Computers


  3. Posts : 9
    10
    Thread Starter
       #3

    ive ran a memtest on both my ram and foud out one of them had errors so im using just 1 8gb stick atm. Haven't had a BSOD yet. I'll keep this updated if i do encounter a BSOD.
      My Computer

  4. axe0's Avatar
    Posts : 14,784
    Windows 10 Pro
       #4

    What memory test did you ran?
      My Computers


  5. Posts : 9
    10
    Thread Starter
       #5

    memtest86+
      My Computer

  6. axe0's Avatar
    Posts : 14,784
    Windows 10 Pro
       #6

      My Computers


  7. Posts : 9
    10
    Thread Starter
       #7

    Well the bad ram was definitely causing me BSOD, but now im back to my old BSOD problems. problems that ive had since i first build my pc. the one i just got was whea_uncorrectable_error which is one i've seen plenty of times before. These BSOD arent like frequent. maybe like once a month, once a week, at worst maybe couple times a week. But over the 2 years its gotten to the point where when i get a BSOD , im just like meh, another blue screen. wait for it to restart and wonder how long it'll be for the next BSOD.

    Not sure if you can help, but if you can that be great.
      My Computer


  8. Posts : 9
    10
    Thread Starter
       #8

    this was the minidump analyst

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************


    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe00163148028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.


    Debugging Details:
    ------------------




    BUGCHECK_STR: 0x124_GenuineIntel


    CUSTOMER_CRASH_COUNT: 1


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


    PROCESS_NAME: Overwatch.exe


    CURRENT_IRQL: f


    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre


    STACK_TEXT:
    fffff800`d0f21a38 fffff800`cf811f1f : 00000000`00000124 00000000`00000000 ffffe001`63148028 00000000`be000000 : nt!KeBugCheckEx
    fffff800`d0f21a40 fffff800`cf2228bc : ffffe001`63148028 ffffe001`631b7c00 ffffe001`631b7c00 ffffe001`631b7c00 : hal!HalBugCheckSystem+0xcf
    fffff800`d0f21a80 fffff800`cf81240c : 00000000`00000728 00000000`00000000 fffff800`d0f21e70 00000000`00000000 : nt!WheaReportHwError+0x258
    fffff800`d0f21ae0 fffff800`cf812764 : ffffe001`00000010 ffffe001`631b7c00 fffff800`d0f21c88 ffffe001`631b7c00 : hal!HalpMcaReportError+0x50
    fffff800`d0f21c30 fffff800`cf81264e : ffffe001`622d7b40 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
    fffff800`d0f21c80 fffff800`cf81288e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
    fffff800`d0f21cc0 fffff800`cf812a10 : ffffe001`622d7b40 fffff800`d0f21ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
    fffff800`d0f21cf0 fffff800`cf15e47b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`d0f21d20 fffff800`cf15e231 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    fffff800`d0f21e60 fffff800`cf0e4a45 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    ffffd000`4023ca50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeDelayExecutionThread+0x45




    STACK_COMMAND: kb


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: GenuineIntel


    IMAGE_NAME: GenuineIntel


    DEBUG_FLR_IMAGE_TIMESTAMP: 0


    IMAGE_VERSION:


    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE


    BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE


    ANALYSIS_SOURCE: KM


    FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache


    FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}
      My Computer

  9. axe0's Avatar
    Posts : 14,784
    Windows 10 Pro
       #9

    It only says that there was a problem in executing something, but nothing else. Basically useless because this analysis is the same with all 0x124 CPU type crashes.

    You need to provide a dump using the DM Log Collector so it can be analyzed further.
      My Computers


  10. Posts : 9
    10
    Thread Starter
       #10

    will this do?
      My Computer


 
Page 1 of 2 12 LastLast

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




Windows 10 Forums