BSOD playing playing Tom Clancy's Division


  1. Posts : 4
    Windows 10
       #1

    BSOD playing playing Tom Clancy's Division


    happens when im play division and when coping files from one HDD to another
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    Dxdiag output says you have a AMD Radeon R9 200 Series which I guess is your Asus r9270x.

    The first dump, 7/27 11:13 says AuthenticAMD is the cause.
    Code:
    BugCheck 124, {0, ffffe001d181b678, 0, 0}
    Probably caused by : AuthenticAMD
    !analyze -V showed this was a
    Code:
    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: ffffe001d181b678, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    The error record shows:
    Code:
    4: kd> !errrec ffffe001d181b678
    ===============================================================================
    Common Platform Error Record @ ffffe001d181b678
    -------------------------------------------------------------------------------
    Record Id     : 01d1e819692b649c
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 7/27/2016 15:13:30 (UTC)
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe001d181b6f8
    Section       @ ffffe001d181b7d0
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 3
    CPU Version   : 0x0000000000600f12
    Processor ID  : 0x0000000000000006
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe001d181b740
    Section       @ ffffe001d181b890
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000006
    CPU Id        : 12 0f 60 00 00 08 08 06 - 0b 22 98 1e ff fb 8b 17
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ ffffe001d181b890
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe001d181b788
    Section       @ ffffe001d181b910
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_GENERIC_ERR_*_NOTIMEOUT_ERR (Proc 6 Bank 5)
      Status      : 0xb0800000000c0e0f
    My first question is, are you overclocking anything? If yes, reset all clocks and voltages to default and test, see what happens.

    If not, lets check RAM. If that doesn't show any problems then let's stress the CPU and GPU, see what that shows. Lastly we'll turn on Driver Verifier and see if that gives us any clue.

    ===================================================
    RAM:


    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    Information


    MemTest86+
    is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
    If none of these help then this could well be a CPU problem.

    ===================================================
    Follow this tutorial to stress test your CPU:
    Prime95 - Stress Test Your CPU - Windows 10 Forums

    ===================================================
    Follow this tutorials to stress test your GPU:
    FurMark - GPU Stress Test - Windows 10 Forums

    If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..

    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to
    PART TWO
    and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My Computers


  3. Posts : 4
    Windows 10
    Thread Starter
       #3

    Okay yeah I will thank you
      My Computer


  4. Posts : 4
    Windows 10
    Thread Starter
       #4

    photo share ram test okay running prime 95 I think my overclock was unstable
      My Computer


  5. Posts : 4
    Windows 10
    Thread Starter
       #5

    upload gambar Im going to mark the thread as solved I found out my i was getting BSODs had quiet and cool on in the bios with Asus Ai overclocker on .... silly me
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    Thanks for letting me know. Glad you are running again.
      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 18:08.
Find Us




Windows 10 Forums