Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

EVENT LOG ERROR !


  • Please log in to reply
3 replies to this topic

#1 MaDDeSS

MaDDeSS

  • Members
  • 2 posts
  • OFFLINE
  •  

Posted 07 November 2015 - 03:40 AM

Hello guys , i have a win 7 32 bits and sometimes it just random restart so i googled my problem and i was sent to see some event log error and i got this message, can you please help me fix it ? 

 

Log Name:      Application
Source:        Microsoft-Windows-WMI
Date:          07.11.2015 10:28:41
Event ID:      10
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      USSER-PC
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Event Xml:
  <System>
    <Provider Name="Microsoft-Windows-WMI" Guid="{1edeee53-0afe-4609-b846-d8c0b2075b1f}" EventSourceName="WinMgmt" />
    <EventID Qualifiers="49152">10</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-11-07T08:28:41.000000000Z" />
    <EventRecordID>73619</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>USSER-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>//./root/CIMV2</Data>
    <Data>SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage &gt; 99</Data>
    <Data>0x80041003</Data>
  </EventData>
</Event>


BC AdBot (Login to Remove)

 


#2 MaDDeSS

MaDDeSS
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  

Posted 07 November 2015 - 07:02 AM

help pls? 



#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,563 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:29 AM

Posted 07 November 2015 - 04:41 PM

Please download MiniToolBox  , save it to your desktop and run it.
 
Checkmark the following checkboxes:
  List last 10 Event Viewer log
  List Installed Programs
  List Users, Partitions and Memory size.
 
Click Go and paste the content into your next post.
 
Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link of the snapshot in your next post.
 
Louis



#4 gniyps_si_ftosorcim

gniyps_si_ftosorcim

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:10:29 AM

Posted 08 November 2015 - 11:20 AM

This is a common yet benign error, Microsoft has a fix-it for this: https://support.microsoft.com/en-us/kb/2545227

 

Cause

This originated in the Windows 7 SP1 DVD/ISO creation process. There was an issue in the creation process that caused a WMI registration to remain in the DVD/ISO. Since the registration is designed to work only during the DVD/ISO creation process, it fails to run on a live system and causes these events. These events are not indicative of any issue in the system and can be safely ignored. If however you want to prevent these events from getting generated and want to remove this specific WMI registration manually, please follow the steps mentioned in this article for running the workaround script.

 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users