Freeze and BSOD sometime ..

Page 1 of 3 123 LastLast

  1. Posts : 10
    Win
       #1

    Freeze and BSOD sometime ..


    Hi ,
    my problem start before 5 months .

    laptop start to freeze ( can't Alt+Ctrl+Del or anything ) must to force restart
    1 time everyday
    and then start to be 2 , 3 times ..
    then after freeze sometime BSOD with WHEA_UNCORRECTABLE_ERROR
    i tried format my windows
    and the problem come again after 1 month
    and i tried format again .. and the problem come again

    i dont know whats the problem ..

    and sorry for my english

    this my 2V log collector .

    Thanks
      My Computer


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

    There are no dumps in either of the zip files you uploaded.

    The next BSOD you get, please run the V2 log collector immediately and upload the zip file here. Also see if there is a C:\Windows\MEMORY.DMP file. If there is, copy it to another location then zip it and upload to a file sharing site like OneDrive, then post a link to it so I can download it here.

    Thanks.

    Event log has a lot of these errors:

    Code:
    Event[5165]:
      Log Name: System
      Source: ACPI
      Date: 2019-06-13T14:10:49.393
      Event ID: 13
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-PEL9ITC
      Description: 
    : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.
    Google searches also turned up a few other possible fixes.

    1. Install the latest IME (Intel Management Engine).
    2. Test your RAM. One person had to remove half his ram. He had 16GB and as long as he ran with 8GB (either DIMM) he had no problems.
      My Computers


  3. Posts : 10
    Win
    Thread Starter
       #3

    Ztruker said:
    There are no dumps in either of the zip files you uploaded.

    The next BSOD you get, please run the V2 log collector immediately and upload the zip file here. Also see if there is a C:\Windows\MEMORY.DMP file. If there is, copy it to another location then zip it and upload to a file sharing site like OneDrive, then post a link to it so I can download it here.

    Thanks.

    Event log has a lot of these errors:

    Code:
    Event[5165]:
      Log Name: System
      Source: ACPI
      Date: 2019-06-13T14:10:49.393
      Event ID: 13
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-PEL9ITC
      Description: 
    : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.
    Google searches also turned up a few other possible fixes.

    1. Install the latest IME (Intel Management Engine).
    2. Test your RAM. One person had to remove half his ram. He had 16GB and as long as he ran with 8GB (either DIMM) he had no problems.
    Thanks for replay ..
    yes The BSOD did not show yet , but the freeze happen everyday .
    and i dont know where i can find IME , my processor is i7 8750H
      My Computer


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

    You have 16GB of RAM, try running with 8GB and see if that makes any difference.

    Is this a Gigabyte Aero 15 Laptop? There should be a label on the back of the laptop with the full model number. Please post that information so I can look at it on the Gigabyte web site.
      My Computers


  5. Posts : 10
    Win
    Thread Starter
       #5

    Yes its , I send pm 2 you , with all pics and videos , please check it ,
      My Computer


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

    Got them, still need the full model number as I can't read that from the pics.

    It will be a GIGABYTE AERO 15-X9-RT5P or something like that.

    As I mentioned, you have 16GB of ram so remove 8GB and try running with just 8GB, see if that makes a difference as it has for others. If it does then we'll proceed from there and figure out what to do next.

    The one blue screen you has a picture of was a WHEA UNCORRECTABLE ERROR which is a hardware error, usually a CPU failure but can also be caused by a bad driver.

    You can try to aggrivate the problem and force some BSODS that may give us the defective drive name by running Driver Verifier.
    ===================================================
    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 desired result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.

    Machines exposed to Driver Verifier may run 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   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 so you have a way to recover if it goes haywire. Seldom does but it can happen.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.
      My Computers


  7. Posts : 10
    Win
    Thread Starter
       #7

    Ztruker said:
    Got them, still need the full model number as I can't read that from the pics.

    It will be a GIGABYTE AERO 15-X9-RT5P or something like that.

    As I mentioned, you have 16GB of ram so remove 8GB and try running with just 8GB, see if that makes a difference as it has for others. If it does then we'll proceed from there and figure out what to do next.

    The one blue screen you has a picture of was a WHEA UNCORRECTABLE ERROR which is a hardware error, usually a CPU failure but can also be caused by a bad driver.

    You can try to aggrivate the problem and force some BSODS that may give us the defective drive name by running Driver Verifier.
    ===================================================
    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 desired result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.

    Machines exposed to Driver Verifier may run 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   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 so you have a way to recover if it goes haywire. Seldom does but it can happen.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.
    Thanks for replay ,

    I am afraid to void the warranty if I remove 8gb ram.

    So I will try Driver Verifier and we will see


    This my support ticket to gigabytes with no answer yet .
    Imgur: The magic of the Internet
      My Computer


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

    Removing 8GB of ram will not void the warranty. No different that replacing ram if it was defective.
      My Computers


  9. Posts : 10
    Win
    Thread Starter
       #9

    After I enable Driver Verifier ,
    Bsod coming when startup ( send this with my phone)
    Stop code:
    System_thread_exception_not_handled

    .. I will try remove ram tomorrow
      My Computer


  10. Posts : 1,538
    Windows 8.1 Enterprise x64
       #10

    Try this:
    1. Download Windows 10 SDK (https://developer.microsoft.com/pl-p...windows-10-sdk)
    2. In installer choose only "Debugging tools for Windows"
    3. After installation launch utility Global Flags
    4. In page "Kernel flags"
    5. Enable option "Stop on exception"
      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 09:18.
Find Us




Windows 10 Forums