Pc Restarts, but no bsod While Playing Dota 2

Discussion in 'Win 7/Vista BSOD' started by DeX0303, Aug 3, 2012.


Thread Status:
Not open for further replies.
  1. DeX0303 Bronze Member

    Bronze
    Message Count:
    21
    Likes Received:
    1
    My System
    Loading...
    OK, i had the same issue months ago with dota 2 and a bsod, now the pc just freezes and restarts, but no bsod appears, just resets. i'll attach propers files and i hope to find a solution :s,



    pd: there are 2 dmp files, one is for the one just happened and the other from a few days ago, for better research, thanks a lot

    Attached Files:

  2. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,779
    Likes Received:
    384
    My System
    Loading...
    Hello.

    Bugchecks point to a hardware error
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: fffffa8007dc0038, 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.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`033c46f0 fffff800`02ecfcb9 : fffffa80`07dc0010 fffffa80`06a2b040 00000000`00000005 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`033c4c10 fffff800`02db0687 : fffffa80`07dc0010 fffff800`02e2a2b8 fffffa80`06a2b040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`033c4c40 fffff800`02d17a35 : fffff800`02e8bac0 00000000`00000001 fffffa80`07a12820 fffffa80`06a2b040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`033c4c80 fffff800`02c94471 : fffff880`011d5e00 fffff800`02d17a10 fffffa80`06a2b000 fffffa80`06a2b040 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`033c4cb0 fffff800`02f24f7a : 00000000`00000000 fffffa80`06a2b040 00000000`00000080 fffffa80`06a26040 : nt!ExpWorkerThread+0x111
    fffff880`033c4d40 fffff800`02c7b9c6 : fffff880`03164180 fffffa80`06a2b040 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033c4d80 00000000`00000000 : fffff880`033c5000 fffff880`033bf000 fffff880`039eb540 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    ---------
    Code:
    1: kd> !errrec fffffa8007dc0038
    ===============================================================================
    Common Platform Error Record @ fffffa8007dc0038
    -------------------------------------------------------------------------------
    Record Id     : 01cd71a5a771bd24
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 8/3/2012 18:27:43
    Flags         : 0x00000002 PreviousError
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007dc00b8
    Section       @ fffffa8007dc0190
    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   : 0x0000000000100f43
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007dc0100
    Section       @ fffffa8007dc0250
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : 43 0f 10 00 00 08 04 00 - 09 20 80 00 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  @ fffffa8007dc0250
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007dc0148
    Section       @ fffffa8007dc02d0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
      Status      : 0xfa00000000070f0f
    The problem is pointed out as a bus related error, which probably means there's something off with the processor or the motherboard.
    The usual steps include:
    - taking off the CPU cooler, cleaning both the heatsink and the ventilator
    - reseating the CPU
    - applying a fresh layer of thermal grease and reseating the cooler on the CPU
    - removing the memory modules and cleaning the memory slots
    - reseating memory modules

    If the error still reoccurs, you will need to do additional testing by using spare parts, like a compatible motherboard and a CPU.
  3. DeX0303 Bronze Member

    Bronze
    Message Count:
    21
    Likes Received:
    1
    My System
    Loading...
    i changed the RAM a few months ago, some RipJaws 8gb 4x2 1600mhz, and in this mobo i can't change the Command Rate to 2T, do you think this might be the problem with the Crashes? the thing is that this only happens with dota 2 :s
  4. Google Advertisement

  5. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,779
    Likes Received:
    384
    My System
    Loading...
    I don't know if the command rate issue is connected with this or it's RAM related.

    If you initiate some benchmark that will stress the CPU, you'll probably get more of this type of crashes. Usually things like this pop up under stress. Which usually means you can continue using a slightly damaged for a while after defects have been detected.
  6. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,779
    Likes Received:
    384
    My System
    Loading...
    Hello, have you managed to reach some conclusions?
  7. DeX0303 Bronze Member

    Bronze
    Message Count:
    21
    Likes Received:
    1
    My System
    Loading...
    well, i really don't know what's wrong with my pc, but im sure it only happens with dota 2, now i think i got a different error, i try to change memory timings and stuff but i can't still manage to get em running on 2T. here's new files.

    Attached Files:

  8. DeX0303 Bronze Member

    Bronze
    Message Count:
    21
    Likes Received:
    1
    My System
    Loading...
    now my pc restarts after i play 1 game of dota 2, 4 times today :s

    Attached Files:

  9. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,779
    Likes Received:
    384
    My System
    Loading...
  10. DeX0303 Bronze Member

    Bronze
    Message Count:
    21
    Likes Received:
    1
    My System
    Loading...
    the weird thing is that it only happens with Dota 2, after a game, I've played Skyrim and Starcraft 2 all day long and none a single crash

    btw, i hope the other test dont burn my **** down :S
  11. DeX0303 Bronze Member

    Bronze
    Message Count:
    21
    Likes Received:
    1
    My System
    Loading...
    burnitdown.jpg CoreTemp-Scr.png i Just got the test, i stoped the burn it down after a couple of minutes cause the temperature was getting way higher in my opinion, so, i got scared xD
  12. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,779
    Likes Received:
    384
    My System
    Loading...
    Both your CPU and GPU are extremely overheating, especially the CPU. I'm not an expert on this, but AFAIK safe temperatures for AMD processors should not go 62°C, 65° MAX. You're hitting 76°.
    GPU is doing moderately OK, but 92°C after a few minutes with a strong tendency to go up further is too much.

    You can follow Malnutrition's guide on cleaning on the inside of the PC case http://www.pchelpforum.com/xf/threads/all-browsers-are-using-too-much-cpu.136134/#post-862836
    Until you do, definitively do not stress your machine anymore.
    When you perform the cleaning, rerun the tests from post #8.
  13. DeX0303 Bronze Member

    Bronze
    Message Count:
    21
    Likes Received:
    1
    My System
    Loading...
    well, i used the pc temp level while playing and it never went beyond 60º, i'm really starting to think this problem is related with the Catalyst Control Center, because since the last update the crashes have been going more frequently, what do you think?

    Attached Files:

  14. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,779
    Likes Received:
    384
    My System
    Loading...
    Look mate, you PC is unstable as is now and if you need help fixing that you'll have to follow the procedure, this is simply not the moment for conjecture or speculation.

    This issue can be party related to CC if they changed something with the fan profiles. If that's the case, you can open CC and manually tune the fan speed under ATI overdrive. But you still need to handle the CPU overheating problem. Go back to post #11 and do as I instructed. If you aren't comfortable enough opening up your PC, you'll have to ask someone to look at it for you.
  15. DeX0303 Bronze Member

    Bronze
    Message Count:
    21
    Likes Received:
    1
    My System
    Loading...
    well... i dissasemble the whole thing, cleaned it, assemble it again, ieven try a different set of rams, still, after a while, it happened again, a couple of times. i think i'm done with it, something in dota 2 is causing this problem and i have no idea what it might be, this problem ONLY happens with this game, so, i guess no more dota 2 until this get fixed, the temps and everything even go higher with other games, and no crashes, lol... well thank you anyways
  16. mkey82 Je ne sais quois

    Tech Member
    Message Count:
    4,779
    Likes Received:
    384
    My System
    Loading...
    I still think dota isn't doing it, leave it alone with any benchmarks long enough and it will crash.
    User mode applications do not cause crashes on stable systems.

Pc Restarts, but no bsod While Playing Dota 2

Thread Status:
Not open for further replies.