Blue Screen Randomly while idle-ly watching youtube


  1. Posts : 113
    Win10 Pro 64bit
       #1

    Blue Screen Randomly while idle-ly watching youtube


    very first occourence for me personally. in all my years of owning this PC 6 years to be exact its never bluescreened. anyways quick run down. was pretty much just watching youtube and that was it. audio and everything became unresponsive. i know that cause the audio was constantly repeating and stuttering of a milisecond of audio indicating something bad has happened.

    event viewer shows: Event ID 18: WHEA-Logger

    A fatal hardware error has occurred.Reported by component: Processor CoreError Source: Machine Check ExceptionError Type: Internal Timer ErrorProcessor APIC ID: 0The details view of this entry contains further information.

    looked into it a bit and found a ton of stuff it could be related to, but needing assistance in order to narrow down the problem more.

    the PC as a whole is 6 years old maybe even 7. PSU is at least 2-3 maybe and GPU is 2-3 (got it at the same time of the PSU)

    and hard drive.. well i had HDD problems previous but this is a new HDD. had it around 1 month 3 weeks now. cause no problems thus far.

    any help would be greatly appreciated, as this just happened out of no where and was a shockingly unexpected event.

    Ps. How do i get rid of TFdebugfiles folder thats left over from the DM_Log Collector on my desktop ???

    Attachment 120665
      My Computer


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

    Hi Dibbz,

    Unfortunately, with a single 0x124 crash and not much else to go on there is no course if action that could be suggested, because to troubleshoot 0x124 crashes multiple dumps are required for a proper course.
    This is simply because a 0x124 usually has not enough information when it's lonely. Multiple dumps are used to get a pattern.

    The 0x124 occured, because the CPU reported an internal timer error. If one would research it, you may get results that say the CPU is the cause. Normally there is a good chance the CPU would be the cause, but with a single crash I honestly doubt it.
    Code:
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffde00f83e8138
    Section       @ ffffde00f83e82c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : Internal timer (Proc 0 Bank 5)
      Status      : 0xbe00000000800400
      Address     : 0x00003fff1ab4b52e
      Misc.       : 0x0000000000000001
      My Computers


  3. Posts : 113
    Win10 Pro 64bit
    Thread Starter
       #3

    axe0 said:
    Hi Dibbz,

    Unfortunately, with a single 0x124 crash and not much else to go on there is no course if action that could be suggested, because to troubleshoot 0x124 crashes multiple dumps are required for a proper course.
    This is simply because a 0x124 usually has not enough information when it's lonely. Multiple dumps are used to get a pattern.

    The 0x124 occured, because the CPU reported an internal timer error. If one would research it, you may get results that say the CPU is the cause. Normally there is a good chance the CPU would be the cause, but with a single crash I honestly doubt it.
    Code:
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffde00f83e8138
    Section       @ ffffde00f83e82c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : Internal timer (Proc 0 Bank 5)
      Status      : 0xbe00000000800400
      Address     : 0x00003fff1ab4b52e
      Misc.       : 0x0000000000000001
    ah i see. well currently after the crash i had the PC running for around another 2-3 hours with no issues. and during that time it was majority research and testing temp's (currently not tested under heavy load) to see if that might have been the cause but highly doubt it.

    if another crash happens il make sure to keep giving the dumps. and if this happens on a regular occurrence witch i hope does not happen. then it should be pretty evident at that point that it might be a hardware related issue!
      My Computer


 

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




Windows 10 Forums