1. #1

    EVENT ID 136 and 137 started to appear in Event Log - Please do not close !!!

    Hello All,


    I open this thread for a second time, because the first thread was closed with an answer that I simply don't understand:


    "
    You are using a crack.
    Please remove it, then reboot and re-post your log.
    "


    Can you please explain what do you mean by this ?




    Below is the text of my original thread.


    ***** Please don't close this thread before letting me answer ! ***************


    Thanks a lot & Best Regards,
    Iudith Mentzel




    ---------------------
    My original thread
    ---------------------


    On my AMD machine with Windows 7 Professional 64 bit suddenly started to appear many pairs of Warning (EventID=136) + Error (EventID=137)
    repeating almost every minute.


    I read another thread Help with an error from event viewer
    by which the following was supposed to solve this problem:


    fsutl resource setautoreset true c:\


    I tried it but it DID NOT HELP in my case.


    So, I followed the instructions on that same thread and got a file VEW.TXT containing the last 20 events,
    which I attach to this post.


    On the first occurrence of these errors the message was the following:


    The default transaction resource manager on volume \Device\HarddiskVolumeShadowCopy17 encountered an error while starting
    and its metadata was reset. The data contains the error code.


    The subsequent errors are similar, but for either \Device\HarddiskVolume2 or C:




    I also do have another thread open for assistance with a Windows Update problem,


    Windows 7 Pro 64 (AMD) does NOT receive last updates KB4088881, KB4100480


    so I don't know whether the two problems are related, but the EventViewer problem only started today, while the Windows Update problem is older.




    Thanks a lot in advance for your help on this issue.


    Best Regards,
    Iudith Mentzel
    Attached Files Attached Files


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Tekno Venus's Avatar
    Join Date
    Jul 2012
    Location
    UK
    Age
    20
    Posts
    5,873
    • specs System Specs
      • Manufacturer:
        Custom Built
      • Motherboard:
        ASUS Z170I ITX
      • CPU:
        Intel Core i7 6700K
      • Memory:
        16GB DDR4
      • Hard Drives:
        500GB Samsung 850 EVO, 2TB Seagate HDD
      • Power Supply:
        450W Corsair SFX
      • Case:
        Silverstone SG13 ITX
      • Cooling:
        Corsair H60i
      • Display:
        Dell U2715H - 2160x1440 27 inch
      • Operating System:
        Windows 10 Pro x64

    Re: EVENT ID 136 and 137 started to appear in Event Log - Please do not close !!!

    Hi,

    Your original thread was closed because some of the events in your Event Viewer logs indicate that you are currently running a non-genuine version of Windows. The events show the presence of a program called AutoKMS, which activates Windows without needing to pay for a licence key. For more information, see here: https://support.microsoft.com/en-us/...indows-genuine

    If you were not aware that your Windows was Non-Genuine, contact your seller or the company that provided the computer and file a complaint. Also let Microsoft know of the problem: How to Tell – Report Piracy


  3. #3

    Re: EVENT ID 136 and 137 started to appear in Event Log - Please do not close !!!

    Hello,

    I think that I know what is the problem.

    My Windows7 is an OEM installation and it is completely genuine.


    What probably is not genuine is the MS Office, so I disabled the problematic program and I will contact the seller about it,
    since it is not my fault in any way.


    I attach a new log file, just created now.

    In the meantime I tried to perform a System Restore back to the point when the 2 events 136 and 137 started to appear,
    but the restore failed with error 0x80071a91.

    This is probably the same error due to which the new Windows Update is unable to finish installation.


    As background info for the entire issue:

    Microsoft's buggy Monthly update of month 2018-MAR caused corruption of the Automatic Update mechanism on my machine,
    and now no additional updates are able to install !!!


    As by my understanding, it looks like there are some more registry problems ...


    I will highly appreciate your help in trying to fix these issues, if possible.



    Thanks a lot & Best Regards,
    Iudith Mentzel
    Attached Files Attached Files

  4. #4
    Tekno Venus's Avatar
    Join Date
    Jul 2012
    Location
    UK
    Age
    20
    Posts
    5,873
    • specs System Specs
      • Manufacturer:
        Custom Built
      • Motherboard:
        ASUS Z170I ITX
      • CPU:
        Intel Core i7 6700K
      • Memory:
        16GB DDR4
      • Hard Drives:
        500GB Samsung 850 EVO, 2TB Seagate HDD
      • Power Supply:
        450W Corsair SFX
      • Case:
        Silverstone SG13 ITX
      • Cooling:
        Corsair H60i
      • Display:
        Dell U2715H - 2160x1440 27 inch
      • Operating System:
        Windows 10 Pro x64

    Re: EVENT ID 136 and 137 started to appear in Event Log - Please do not close !!!

    Hi,

    Thanks for the clarification.

    To avoid any confusion, lets wait until you have finished working with Brian in your Windows Update thread before proceeding further with this one.

    -Stephen


  5. #5

    Re: EVENT ID 136 and 137 started to appear in Event Log - Please do not close !!!

    Just as a matter of interest did the Updates/Event Viewer problem start after installing Office 2010.
    If he sold it to you with the AutoKMS included it begs the question what else was changed?

    Roy

  6. #6

    Re: EVENT ID 136 and 137 started to appear in Event Log - Please do not close !!!

    Hello All,

    No, definitely NOT !!!

    To make it short, the initial problem was that applying the Microsoft Monthly Rollup Update for 2018-MAR ( KB4088875 )
    caused my AMD machine to get stuck on the reboot after installation !

    This was a HUGE FLAW from Microsoft's side, and later on this issue of the flawed MS updates was widely discussed on many web sites !

    It looks like ALL the Monthly updates for JAN-MAR 2018 ( which unsuccessfully attempted to correct the Meltdown security issue )
    were buggy and caused many machines to be bricked or to crash, including AMD machines for which this security "fix" should NOT have been applied
    in the first place !


    So, I had to force a reboot of my machine through PowerOff/PowerOn, then perform several CHKDSK-s, until I got my machine working again.

    At this point, my machine worked normally and there were NO WARNINGS OR ERRORS OF ANY KIND in the EventViewer System log !


    I only remarked that the subsequent updates released by MS for Windows 7 64 bit machines DID NOT appear on my AMD machine,
    but they DID appear on other (Intel) machines having the same OS.

    For this issue I opened my other thread on this forum
    Windows 7 Pro 64 (AMD) does NOT receive last updates KB4088881, KB4100480
    Ultimately, MS released a new Monthly update for 2018-APR ( KB4093118 ),
    which did arrive on the Intel machines the next day after its first release (on Apr 11)
    and finally it also appeared on my AMD machine, but only 2 days later ( on Apr 13), after Microsoft probably modified it in some way,
    as its current release date on the MS catalog is Apr 12.


    When this last update attempted to be installed and DID NOT succeed, then the Events 136-137 started to appear in the EventViewer log.


    Meanwhile, before this last update arrived, I also performed some backups on my machine,
    and I have also seen many web sites where a backup is considered a possible culprit for the appearance of these events.

    But anyway, at this moment, these events whose meaning is that the "Default Transaction Resource Manager" is NOT working
    are probably those which prevent the last update to install and also prevent other actions, like performing a System Restore.

    It is not clear whether these events were caused by:

    1. applying the MAR-2018 update, which caused the machine to be blocked on reboot

    2. performing an image backup

    3. attempting to install the APR-2018 update ( the first OS update after the problematic MAR-2018 update )


    Anyway, the events only started to appear AFTER all these actions.


    The AutoKMS is NOT running any more, so the whole issue is purely OS-related, and more specifically Windows Update-related,
    it has nothing to do with any other software that runs on my machine.


    I hold Microsoft 100% responsible for all this buggy situation that they caused totally irresponsibly and unprofessionally to so many users !


    Thanks a lot & Best Regards,
    Iudith

Similar Threads

  1. Event ID 136-137 started to appear in EventLog
    By iudith in forum Windows 7 | Windows Vista
    Replies: 1
    Last Post: 04-14-2018, 06:23 AM
  2. master file table corrupt Event ID 55 and WMI error event 24
    By edge in forum Windows 8 | Windows RT
    Replies: 10
    Last Post: 07-20-2017, 03:24 PM
  3. Replies: 1
    Last Post: 12-12-2016, 09:24 PM
  4. Event logs
    By Jared in forum Windows 10
    Replies: 5
    Last Post: 08-03-2015, 05:31 AM
  5. Event ID 41 troubleshooting
    By usasma in forum BSOD Kernel Dump Analysis Debugging Information
    Replies: 1
    Last Post: 04-12-2013, 11:55 AM

Log in

Log in