Application Error wintab32.dll

I am getting this Application Error while working in Flash Adobe CS5 Professional version.
The error occurs at different times either while I am attempting to generate a SWF for testing or when I am in ActionScript.
From EventViewer>Application Error:
Faulting application flash.exe, version 11.0.2.489, faulting module wintab32.dll, version 2.1.1.8, fault address 0x00001c00.
I am running WinXP Professional. ServicePack3
Has anyone experienced this?

Hi,
Just a thought, as I had seen errors like these due to an anti-virus software running on the host.
Perhaps could try disabling the AV for sometime and see if this still happens.
Regards,
Srikishan

Similar Messages

  • DIAdem Application Error (mfc71u.dll)

    Hi, I'm working with an application in DIAdem who analize some data that LABview acquire and save the result in one file ("BRAKE_#.TDM") every test.
    I've got some error saving this files:
    23   19:15:34 Error:
         Error while executing "DATASAVE("Brake_1231")" command
         Error type: ACCESS VIOLATION
         Error address: 00009E81
         Module name:kernel32.dll
    24   19:15:34 Error:
         Error in <Rumore.VBS> (Line: 234, Column: 5):
         Error while executing "DATASAVE("Brake_1231")" command
         Error type: ACCESS VIOLATION
         Error address: 00009E81
         Module name:kernel32.dll
    25   19:16:08 Error:
         Error while executing "" command
         Error type: ACCESS VIOLATION
         Error address: 000631BA
         Module name:gfsdesk.DLL
    Sometimes also DIAdem crash and in the EventViewer there are this errors (the PC where run the program is in spanish):
    Aplicación con errores: diadem.exe, versión: 10.0.0.2658, módulo con error:
    mfc71u.dll, versión 7.10.3077.0, dirección de error 0x00023fee.
    or
    Aplicación con errores: diadem.exe, versión: 10.0.0.2541, módulo con error:
    mfc71u.dll, versión 7.10.3077.0, dirección de error 0x00023fee.
    Someone can help me ?
    Thanks

    Hello MicheleS! Hello Brad!
    In the past I ran several times into the same strange error messages. The DATASAVE AV was never the reason, but it was always the symptom for a corrupt memory content. In my case it was caused by extension DLLs (GPI) I used (and developed).
    I recommend to find the reason for the 'mfc71u.dll' AV.
    Matthias
    Matthias Alleweldt
    Project Engineer / Projektingenieur
    Twigeater?  

  • Application Error - Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385

    Hi,
    we have one Visual C++ application and this application also using few external dlls. while exiting from application, getting following error. This
    is happened in Windows 7.
    Please help us to resolve this issue.
    Log Name:     
    Application
    Source:       
    Application Error
    Date:         
    28/07/2010 11:44:16 AM
    Event ID:     
    1000
    Task Category: (100)
    Level:        
    Error
    Keywords:     
    Classic
    User:         
    N/A
    Computer:     
    CRIWKS12.crillylaw.local
    Description:
    Faulting application name: WinTest.exe, version: 2.7.1.0, time stamp: 0x4b78d5b8
    Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdaae
    Exception code: 0x0eedfade
    Fault offset: 0x00009617
    Faulting process id: 0x10b8
    Faulting application start time: 0x01cb2df647dfd847
    Faulting application path: C:\Program Files\xxx\xxx\xxx\ WinTest.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: a17377fd-99e9-11df-8941-90fba60d7539
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-07-28T01:44:16.000000000Z" />
    <EventRecordID>3773</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CRIWKS12.crillylaw.local</Computer>
    <Security />
    </System>
    <EventData>
    <Data> WinTest.exe</Data>
    <Data>2.7.1.0</Data>
    <Data>4b78d5b8</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7600.16385</Data>
    <Data>4a5bdaae</Data>
    <Data>0eedfade</Data>
    <Data>00009617</Data>
    <Data>10b8</Data>
    <Data>01cb2df647dfd847</Data>
    <Data>C:\Program Files\xxx\xxx\xxx\ WinTest.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>a17377fd-99e9-11df-8941-90fba60d7539</Data>
    </EventData>
    </Event>
    PS. I apologise for not being able to provide the application's name.

    Hi Jesse ,
    I am pasting the entire module where the code fails:
    /// <summary>
    /// Pool the job execution status
    /// </summary>
    private void PoolJobExecutionStatus()
    int waitIndex = 0;
    while (true)
    try
    lock (this.lockingObject)
    this.ReOpenRegistryConnection();
    currentJob = SR.Job.Load(this.currentJobId, this.poolingConnection);
    JobStatusEventArgs jobStatusArg = (currentJob.Status == SR.JobStatus.Aborted) ?
    new JobStatusEventArgs(currentJob.Name, currentJob.Status, currentJob.ErrorMessage) :
    new JobStatusEventArgs(currentJob.Name, currentJob.Status);
    this.dispatcher.BeginInvoke(new EventHandler<JobStatusEventArgs>(RaiseUpdateStatus), DispatcherPriority.Normal, new object[] { this, jobStatusArg });
    if (currentJob.Status == JobStatus.Aborted || currentJob.Status == JobStatus.Completed)
    this.PoolJobThread.Abort();
    break;
    catch (ThreadAbortException)
    catch (ConnectionFailure ex)
    TridentErrorHandler.HandleUIException(ex);
    // If reconnection fails more than the max reconnection value then exit.
    if (this.connectionAttempts >= this.maxConnectionAttempts)
    break;
    this.connectionAttempts++;
    catch (BackendStorageException ex)
    TridentErrorHandler.HandleUIException(ex);
    // If reconnection fails 5 times then exit.
    if (this.connectionAttempts >= this.maxConnectionAttempts)
    break;
    this.connectionAttempts++;
    catch (Exception ex)
    TridentErrorHandler.HandleUIException(ex);
    break;
    try
    Thread.Sleep(500);
    // If job is in waiting state, every 3 min show the user retry message.
    // (waitIndex == 360) Specifes 3 min.
    if (currentJob.Status == JobStatus.Waiting && waitIndex == 360)
    waitIndex = 0;
    JobStatusEventArgs jobStatusArg = new JobStatusEventArgs(this.currentJob.Name, this.currentJob.Status, TridentResourceManager.GetString("JobTerminatedByUserMessage"));
    this.dispatcher.BeginInvoke(new EventHandler<JobStatusEventArgs>(RaiseUpdateStatus), DispatcherPriority.Normal, new object[] { this, jobStatusArg });
    catch (Exception ex)
    TridentErrorHandler.HandleUIException(ex);
    waitIndex++;
    public void StartDataProductService(Guid jobId, Connection poolConnection)
    this.currentJobId = jobId;
    this.poolingConnection = poolConnection;
    this.ClearTempData();
    this.HaltService();
    this.PoolJobThread = new Thread(this.PoolJobExecutionStatus);
    this.PoolJobThread.Start();
    Hope this helps
    Regards,
    Rahul

  • I tried to download the latest upgrade and got the following: "iTunes was not installed correctly. Please reinstall iTunes. Error 7 (Windows error 193).  Program Files/Common Files/Apple/Apple Application Support\ApplePushService.dll

    I tried to download the latest upgrade and I got a message telling me "The application or DLL ProgramFiles/CommonFiles/Apple/Applie Application Support\ApplePushService.dll is not a valid Windows image. Please check this against your installation diskette." and then below that another message "iTunes was no installed correctly. Please reinstall iTunes. Error 7 (Windows error 193).  I tried reinstalling and it still will not work.

    Taken at face value, you're having trouble with an Apple Application Support program file there. (Apple Application Support is where single copies of program files used by multiple different Apple programs are kept.)
    Let's try something relatively simple first. Restart the PC. If you're using Vista or 7,now head into your Uninstall a program control panel, select "Apple Application Support" and then click "Repair". If you're using XP,head into your Add or Remove Programs control panel, select "Apple Application Support", click "Change" and then click "Repair".
    If no joy after that, try the more rigorous uninstall/reinstall procedure from the following post. (If you've got XP, although the procedure is for Vista and 7, just read "Computer" as "My Computer", read "Uninstall a program control panel" as "Add or Remove programs control panel" and assume the system is 32-bit, and you'll be doing the right things.)
    Re: I recently updated to vista service pack 2 and I updated to itunes 10.2.1 and ever

  • Event 1000, Application Error (Faulting application name: w3wp.exe - Faulting module name: KERNELBASE.dll)

    Hello Guys,
    While running a web application am getting an error like: Remote server not responding. Below are the details of event viewers which been captured at the same time when this error happened:
    Event 1000, Application Error
    Faulting application name: w3wp.exe, version: 7.5.7600.16385, time stamp: 0x4a5bd0eb
    Faulting module name: KERNELBASE.dll, version: 6.1.7600.16850, time stamp: 0x4e211da1
    Exception code: 0xe053534f
    Fault offset: 0x000000000000a88d
    Faulting process id: 0x%9
    Faulting application start time: 0x%10
    Faulting application path: %11
    Faulting module path: %12
    Report Id: %13
    Event 1001, Windows Error Reporting
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: w3wp.exe
    P2: 7.5.7600.16385
    P3: 4a5bd0eb
    P4: KERNELBASE.dll
    P5: 6.1.7600.16850
    P6: 4e211da1
    P7: e053534f
    P8: 000000000000a88d
    P9: 
    P10: 
    Attached files:
    C:\Windows\Temp\WERC9CD.tmp.WERInternalMetadata.xml
    C:\Windows\Temp\WERC9CE.tmp.hdmp
    C:\Windows\Temp\WEREE30.tmp.mdmp
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_w3wp.exe_30877924d6b2c607fe88a8718915f25fb79093_cab_e905f2b0
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d46a6849-8f6a-11e1-98af-00215e6e4855
    Report Status: 4
    This is an priority issue which we are facing in IIS. IIS is configured for Framework 2.0 and underlying OS is - Windows
    Server 2008 R2 Standard.This issue is replicable and occurring frequently Please suggest how to resolve it. Any input related to above issue is appreciable.

    Please refer similar discussions and see if they help
    Faulting application name: w3wp.exe 
    http://telligent.com/support/communityserver/community_server_2008/f/288/t/1067447.aspx 
    Event ID: 1000, Faulting application w3wp.exe, faulting module unknown, 
    http://social.msdn.microsoft.com/forums/en-US/clr/thread/9be88a2f-c8cc-4a73-9371-45ab73982123
    For IIS related queries, please post them in IIS forum - http://forums.iis.net/
    A UNIVERSE without WINDOWS is CHAOS !
    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
    About Me !!!

  • Firefox.exe application error, tried uninstalling firefox but will not delete Scriptff.dll says access is denied. so i can't make a complete clean reinstall. how do i fix this?? thanks!

    saw in previous questions that to fix this application error, i need to uninstall and do a clean install of firefox. however, Scriptff.dll says that access is denied and can not be deleted from the program files. how can i fix this so i can run a clean install?

    Hello cor-el, thanks for your reply. I changed my settings for downloads to desktop and it has appeared on there. When I double click I am asked which program I want to open file. I click firefox and another box "opening install" says I have chosen to open the file which is an application and do I want to save it. This is the only real option so I press save file. I get a box saying this is an executable file which may contain viruses - do you want to run. I press ok and the final box showing C drive file name and desktop appears stating application not found.
    This happens the same whenever I try to install.
    To my untrained eye the application is not being recognised as an application and I cannot work out how to get it to do that.
    My plugin is still showing as out of date.
    Is there anything you could suggest. Thanks for your time.

  • TS1717 On Windows Vista and tried several times to start up my iTunes, but keep getting 'application failed MSVCR80.dll error-7 (windows 126) is this an easy fix ...?

    On Windows Vista and tried several times to start up my iTunes, but keep getting 'application failed MSVCR80.dll error-7 (windows 126) is this an easy fix ...?

    Click here and follow the instructions. You may need to completely remove and reinstall iTunes and all related components, or run the process multiple times; this won't normally affect its library, but that should be backed up anyway.
    (99442)

  • Directory server 5.1 application error - faulting module libslapd.dll

    we are running directory server 5.1 (build 2001.326.2045) on windows nt, with multi-master replication on two servers. one server went down. there are no clues as to why in the access or error logs.
    the windows event viewer shows an application error. the faulting application is slapd.exe, faulting module is libslapd.dll, and fault address is 0x0003edb0
    any help would be appreciated. any questions please ask. thanks!
    Edited by: amlefty on Aug 26, 2009 8:12 PM

    we are running directory server 5.1 (build 2001.326.2045) on windows nt, with multi-master replication on two servers. one server went down. there are no clues as to why in the access or error logs.
    the windows event viewer shows an application error. the faulting application is slapd.exe, faulting module is libslapd.dll, and fault address is 0x0003edb0
    any help would be appreciated. any questions please ask. thanks!
    Edited by: amlefty on Aug 26, 2009 8:12 PM

  • I continually get this: Application Error 1000_(100)_"Faulting application name: MyAppName.exe Faulting module name: MSVBVM60.DLL

    I have a VB6 application which connects to a SQL Server.  I am running my exe on a Windows Server Terminal Server.  I frequently have my EXE crash and close at random.  My EXE doesn't log any error because the crash occurred outside of my
    application. 
    Here is the Windows event error:
    07/17/14 4:59:49 PM    Application Error    1000    (100)    "Faulting application name: MyApp.exe, version: 8.0.0.0, time stamp: 0x53adc042
    Faulting module name: MSVBVM60.DLL, version: 6.0.98.15, time stamp: 0x4a5bda6c
    Exception code: 0xc0000006
    Fault offset: 0x00054948
    Faulting process id: 0x24d4
    Faulting application start time: 0x01cfa1fe336df3db
    Faulting application path: N:\MyApp\MyApp.exe
    Faulting module path: C:\Windows\system32\MSVBVM60.DLL
    Report Id: 498ee913-0df5-11e4-a940-000c29a03ae8"
    I have tried to search the internet but I have yet to find a solution.  Any help or explanation would be greatly appreciated.

    Hello,
    Thank you for your post.
    I’m afraid that it is not the correct forum for this issue, since this forum is to
    discusses the usage of Visual Studio IDE such as
    WPF & SL designer, Visual Studio Guidance Automation Toolkit,
    Developer Documentation and Help System and
    Visual Studio Editor.
    Since you are working with VB6 application, I suggest that you can consult on these popular third-party forums which support Visual Basic 6for better solutions:
    VB Forums
    VB City
    Best regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Ntdll.dll application error makes itunes crash

    Itunes keeps crashing every 30 minutes to 2 hours since more than 2 years now (!!)
    according to the event log of XP there's an application error in module ntdll.dll
    I have searched the internet for quite some time for a fix for this problem but there doesn't seem to be a clear one.
    Help would be really appreciated!
    Message was edited by: marcbolan
    Message was edited by: marcbolan

    Okay ... not the malware thing that was causing trouble at the beginning of the year. (On the other hand, as well as citing ntdll.dll, that used to always stop people from launching iTunes and quicktime.)
    It's relatively rare to see ntdll.dll show up in this context (and probably even rarer to see it only cropping up sometimes), so we'll proceed on a basic principles troubleshooting basis.
    ntdll.dll is one of the core Windows operating system files related to handling drivers, so we'd better check on driver, firmware and so forth.
    If you've got a name-brand PC, check first at the Manufacturer's website for drivers, firmware and BIOS for your system. If you've added third-party components to the system since then, check for driver updates for those components at the component-manufacturer's website.
    If you've got a custom/homw-built system, check at the manufacturer's webpages for drivers/firmware/BIOS for the various components. There's some advice in the following document:
    [Updating the drivers on your Windows PC|http://support.apple.com/kb/HT1768]
    If you update, does iTunes seem more stable for you? (A bit tricky to tell, of course, given that it doesn't happen right away.

  • Application crash with error ntdll.dll 00018fea

    Hi,
    I have a problem with my app.exe build.
    I attach a simple code; the Vi open and close a TDM file.
    If I run this Vi in Labview works fine.
    If I build the application.exe on a notebook and I run it I got "Application crash with error ntdll.dll 00018fea".
    I've tried to build the Vi on another Pc Desktop with Labview and here if I run the exe it works fine.
    On the two PC I have LV8.5; the build options are the same.
    On the notebook I've try also to reinstall LV8.5 but I got the same error.
    Can you help me?
    Thanks a lot
    Attachments:
    open tdm.vi ‏33 KB

    MicheleS wrote:
    This morning I've try to put the ntdll.dll of the other PC in the notebook but the problem remain.
    Never ever do that! You were very lucky that both ntdll.dll files were probably the same version so the exchange didn't do much but ntdll.dll is one of the core Windows DLLs were everything goes through that normal applications may access in Windows. A mixup in such a part because of incompatitible ntdll.dll with other system API DLLs might prevent your computer entirely from starting up even in safe mode.
    You should not attempt to ever switch system DLLs between different computers. In such behaviour lays insanity. If you expect a system DLL to be corrupt attempt to do a repair installation instead. Also Windows nowadays has techniques to detect if a system DLL got corrupt and will attempt to repair it, though I guess if ntdll.dll would go belly up it's likely your computer won't even start up.
    Rolf Kalbermatter
    Message Edited by rolfk on 01-14-2008 08:05 AM
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Application Error (gwpoa.exe & GWWWW1.dll)

    Hi everyone,
    We are having the POA on one of our GroupWise 2012 (Windows) servers crashing.
    Here are the general information:
    Faulting application name: gwpoa.exe, version: 12.0.0.8586, time stamp: 0x4f153311
    Faulting module name: GWWWW1.dll, version: 12.0.0.8586, time stamp: 0x4f1531c9
    Exception code: 0xc0000005
    Fault offset: 0x001679df
    Faulting process id: 0x2344
    Faulting application start time: 0x01cf48970a4ea082
    Faulting application path: C:\Program Files (x86)\Novell\GroupWise Server\Agents\gwpoa.exe
    Faulting module path: C:\Program Files (x86)\Novell\GroupWise Server\Agents\GWWWW1.dll
    Report Id: 6b68533f-b48a-11e3-964a-00505692208f
    THE FOLLOWING IS THE XML RESULTS:
    - System
    - Provider
    [ Name] Application Error
    - EventID 1000
    [ Qualifiers] 0
    Level 2
    Task 100
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2014-03-26T02:00:36.000000000Z
    EventRecordID 16602
    Channel Application
    Computer mta-gw03.mta.qld.edu.au
    Security
    - EventData
    gwpoa.exe
    12.0.0.8586
    4f153311
    GWWWW1.dll
    12.0.0.8586
    4f1531c9
    c0000005
    001679df
    2344
    01cf48970a4ea082
    C:\Program Files (x86)\Novell\GroupWise Server\Agents\gwpoa.exe
    C:\Program Files (x86)\Novell\GroupWise Server\Agents\GWWWW1.dll
    6b68533f-b48a-11e3-964a-00505692208f
    Does anyone have any ideas why this has started doing this? (About two three weeks now).
    There have been no updates to the Server (Windows, Novell, e.t.c.)
    Thanks.
    Cheers,
    Ant

    Hi Ant,
    Is DEP (Data Execution Prevention) turned OFF on the server in question?
    Cheers,

  • Windows Server 2008 R2 - Multiple application errors in module MSVCR90.DLL

    I'm having some trouble with one of the terminal servers that I administrate, lately there have been a large number of application errors reported by users. Looking at the logs they all have in common that they report MSVCR90.DLL as the faulty module, with
    some of the applications throwing errors being fixmapi.exe, iexplore.exe & acrord32.exe.
    I did some searching around and tried the usual things of uninstalling and reinstalling the mvc redist, however it doesn't appear to have made much of a difference. I configured capture of user-mode dumps as mentioned in http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/repeated-appcrash-errors-across-many-applications/18ee194c-56dd-4909-abed-e563de11713b
    which seems to be recommended as a way to find the real faulty module that is behind all the problems, so far I've generated one dumpfile at least for a fixmapi.exe but I am not sure how to parse it, does anyone have any idea?

    Hi DialectEmil,
    Would you please let me know whether install all necessary updates on the problem computer? Please run
    sfc /scannow command to scan all protected system files. In addition, please perform a
    clean boot and check if this issue still exist.
    Please also refer to following article and check if help you to troubleshoot application crashes.
    Basic Debugging of an Application Crash
    If any update, please feel free to let me know.
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • **SOLUTION** DLLML.exe Fails to load at startup (application error)

    Hello everyone!
    I purchased the SB X-Fi Fatalty Champion Edition soon after release, and think this is the best card I have ever used to date. Absolutely love it, unbelievable sound.
    Now a year or two ago I noticed a certain file failing to load when I started windows.
    This file, DLLML.exe. To my understanding this file is used to load EAX emulation support into older games/modules (essential loads a "middle-man" file between the game's sound files/.dll's, and the hardware SPU [Sound Processing Unit, not a real acronym, but that's what I call it since GPU and CPU are similar distincti've acronyms so if you see it used anywhere, it came from me ] to allow EAX support in non-EAX enabled games), and/or to add EAX effects in your audio files using the Wave Studio app.
    I've pinpointed this issue to either a Windows Update, or the Creative auto-update (which could mean it is an error caused by an installaion combination of multiple apps at once) because this issue did not arise until I did these two things (did Windows Update, then Creative Auto-Update, then restarted computer).
    Now I've primarily had this issue with Windows XP x64 but I have had this issue at times with Windows XP x86 as well.
    After you install the software suite, it adds an entry in your Windows Startup to load the module (Start/Run. msconfig. Startup tab. Look for STARTUP ITEM: DLLML). The entry looks like this:
    WinXPx86 looks like: "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
    WinXPx64 looks like: "C:\Program Files (x86)\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
    Under most circumstances this module loads fine, but because Creative, for reasons why I have not delved into, loads some of their DLL files differently than the Windows standard, which may also be a cause of this issue (extremely unlikely, I believe it is one of the 2 things i mentioned above).
    Either way, after I did those 2 things, the DLLML.exe startup entry failed to load every time.
    But I fixed it.
    Now what you have to do to resolve this issue, involves editing the startup entry in the Windows Registry.
    If you are scared to go into it, have no idea what I am talking about, or never edited the Registry before, don't worry. If you follow these steps EXACTLY, you have nothing to fear.
    I will be using default installation parameters for file pathing, so if your Operating System is installed in a different dri've letter other than C:\, then just change the letter to the one your OS is installed onto.
    Capitals used for emphesis on actions to take:
    -Hit the START button, then select RUN
    --------If RUN is not in your start menu, you need to enable it by right-clicking and open area of your TASKBAR, select PROPERTIES. --------Click the START MENU tab, then the CUSTOMIZE button. Click the ADVANCED tab. In the START MENU ITEMS box, scroll down to the entry that says SHOW RUN. Check the checkbox to fill it. Then OK/APPLY/OK, and you should be back to the desktop. Then go to START/RUN
    -type the word REGEDIT
    --------This opens the Windows Registry.
    --------DO NOT change ANYTHING in this other than the exact directions I specify or you may corrupt your registry or even worse, corrupt your system, which means F&R time (Format & Reinstall). Treat it like a stripper. You can look all you want but don't touch or there could be dire consequences.
    --------Now the fastest way to find this is to manually navigate to the specific "key" or "entry" you need to modify. Mouse-click the +'s to navitage further into the "hi've" following these maps:
    -FOR WINDOWS XP x86 USERS NAVIGATE TO: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run
    -FOR WINDOWS XP x64 USERS NAVITAGE TO: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432\Microsoft\Wind ows\CurrentVersion\Run
    --------Now you are looking for a specific entry NAME called RCSYSTEM. Depending on which version you are running. They are:
    -FOR WINDOWS XP x86 USERS: "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
    -FOR WINDOWS XP x64 USERS: "C:\Program Files (x86)\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
    -------Now we are going to edit the entry. What we need to do is get rid of that * (asterix) character in the name. I don't know why it is there, I'm thinking it may be a coding error. But in my WinXPx64, this was the culprit.
    -Double-click the RCSYSTEM key to edit it, and edit it so it looks EXACTLY LIKE THIS (If you're paranoid about doing something bad, COPY and PASTE this line pertaining to your installed OS. KEEP IN MIND THE INSTALLATION DRIVE LETTER, CHANGE FIRST LETTER IF NESCESSARY)
    -FOR WINDOWS XP x86 USERS: "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem -Startup
    -FOR WINDOWS XP x64 USERS: "C:\Program Files (x86)\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem -Startup
    -click OK button. Now it is changed.
    -------And we're DONE EDITING the Registry entry!
    -now go to FILE in the top-left menu, then select EXIT
    -RESTART your computer
    -------You should not receive the "DLLML.exe failed to load" (application error) again!!
    To check to see if it loaded into your system properly (as if not getting the error message anymore was proof enough it loaded properly), when you reboot back to the desktop, do the "three-fingered salute" (ctrl-alt-delete), then select the PROCESSES tab. Click on the IMAGE NAME heading to sort it alphabetically, and look for the name (WinXPx86) DLLML.exe or (WinXPx64) DLLML.exe *32.
    If you see it listed, it loaded!! CONGRATS, IT BE FIXED!!
    If this did not work for you, then your system is posessed, get a priest. I don't think a witchdoctor would give your comp good vibes O_o
    Hope this resolved it for you. Enjoy your EAX with Duke Nukem 3d again!
    EDIT: As a side note, I also noticed that since after this fix, my computer doesn't hang after sending the restart/shutdown killsignal, so I am wondering with people having similar hanging issues, if their issue could be resolved something similar to this.
    Just a thought for any admins/mods/users out there that know what they are doing that maybe wanna test that out.
    Sincerely,
    Jason Ostapyk
    3yr degree, MCP, CCNA, A+ certified, Specialised Electrician Class M Licensed

    G Kudos for a brilliant finding! After a Windows Hotfix on my XP SP3, when shutting down my PC I would wait for a program and then get an error that EAX was not responding before finally shutting down. On next reboot I lost sound on my PC. After running tests, the Direct Sound test failed pointing at EAX.
    This solution cured the problem. Again, kudos, job really well done!!!

  • Application error happening at least twice a day. Faulting applicaiton name: wmiprvse.exe

    We're experiencing an issue with one of our Windows Server 2008R2 Standard Edition SP1 servers where an Application error occurs at least twice, and sometimes up to 5 or 6 times per day.  The following error is what we see.  Any help would be greatly
    appreciated, and I'll be checking back frequently to check for updates and provide more info whenever needed.  Thanks!
    General:
    Faulting application name: wmiprvse.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d42
    Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c8f9
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c40f2
    Faulting process id: 0x1bbc
    Faulting application start time: 0x01cd5d65dbeb2e7c
    Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Details:
    System
    Provider
    [ Name]
    Application Error
    EventID
    1000
    [ Qualifiers]
    0
    Level
    2
    Task
    100
    Keywords
    0x80000000000000
    TimeCreated
    [ SystemTime]
    2012-07-09T08:34:39.000000000Z
    EventRecordID
    6812
    Channel
    Application
    Computer
    {FQDN}
    Security
    EventData
    wmiprvse.exe
    6.1.7601.17514
    4ce79d42
    ntdll.dll
    6.1.7601.17514
    4ce7c8f9
    c0000374
    00000000000c40f2
    1bbc
    01cd5d65dbeb2e7c
    C:\Windows\system32\wbem\wmiprvse.exe
    C:\Windows\SYSTEM32\ntdll.dll
    ebe1621c-c9a0-11e1-a1d4-5cf3fce8cef6
    ETA:  I also ran the wmidiag.exe tool from Microsoft.  I saw it as a suggestion on another forum and ran it.  I don't know if it has any bearing here, but this is the log in case it's helpful
    show
    06604 14:51:25 (0) ** WMIDiag v2.1 started on Tuesday, July 10, 2012 at 14:40.
    06605 14:51:25 (0) ** 
    06606 14:51:25 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    06607 14:51:25 (0) ** 
    06608 14:51:25 (0) ** This script is not supported under any Microsoft standard support program or service.
    06609 14:51:25 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    06610 14:51:25 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    06611 14:51:25 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    06612 14:51:25 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    06613 14:51:25 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    06614 14:51:25 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    06615 14:51:25 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    06616 14:51:25 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    06617 14:51:25 (0) ** of the possibility of such damages.
    06618 14:51:25 (0) ** 
    06619 14:51:25 (0) ** 
    06620 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06621 14:51:25 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    06622 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06623 14:51:25 (0) ** 
    06624 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06625 14:51:25 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User {Username} on computer {ComputerName}.
    06626 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06627 14:51:25 (0) ** Environment: ........................................................................................................ OK.
    06628 14:51:25 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
    06629 14:51:25 (0) ** Drive type: ......................................................................................................... SCSI (IBM ServeRAID M5015 SCSI Disk Device).
    06630 14:51:25 (0) ** There are no missing WMI system files: .............................................................................. OK.
    06631 14:51:25 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    06632 14:51:25 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
    06633 14:51:25 (0) ** AFTER running WMIDiag:
    06634 14:51:25 (0) ** The WMI repository has a size of: ................................................................................... 90 MB.
    06635 14:51:25 (0) ** - Disk free space on 'C:': .......................................................................................... 75295 MB.
    06636 14:51:25 (0) **   - INDEX.BTR,                     15818752 bytes,     7/10/2012 2:38:58 PM
    06637 14:51:25 (0) **   - MAPPING1.MAP,                  242388 bytes,       7/10/2012 2:33:33 PM
    06638 14:51:25 (0) **   - MAPPING2.MAP,                  242388 bytes,       7/10/2012 2:38:58 PM
    06639 14:51:25 (0) **   - OBJECTS.DATA,                  77570048 bytes,     7/10/2012 2:38:58 PM
    06640 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06641 14:51:25 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
    06642 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06643 14:51:25 (0) ** DCOM Status: ........................................................................................................ OK.
    06644 14:51:25 (0) ** WMI registry setup: ................................................................................................. OK.
    06645 14:51:25 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
    06646 14:51:25 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    06647 14:51:25 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    06648 14:51:25 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    06649 14:51:25 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    06650 14:51:25 (0) **          this can prevent the service/application to work as expected.
    06651 14:51:25 (0) ** 
    06652 14:51:25 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    06653 14:51:25 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    06654 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06655 14:51:25 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    06656 14:51:25 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    06657 14:51:25 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    06658 14:51:25 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    06659 14:51:25 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    06660 14:51:25 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    06661 14:51:25 (2) !! WARNING: Some WMI providers EXE/DLL file(s) are missing: ............................................................ 18 WARNING(S)!
    06662 14:51:25 (0) ** - ROOT/QLOGIC_CMPI, QLogic_NIC_Provider, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{28A5F598-F699-4A6B-B9F9-8C7EB9B7359F}:QLogic_NIC_Provider
    06663 14:51:25 (0) ** - ROOT/QLOGIC_CMPI, QLogic_FCHBA_Provider, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{0AE588DD-D2E9-41EB-BCD1-8BF474187EC5}:QLogic_FCHBA_Provider
    06664 14:51:25 (0) ** - ROOT/IBMSD, ADPT_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{B007445E-6AF0-4CBD-9009-809F071FCE69}:ADPT_Module
    06665 14:51:25 (0) ** - ROOT/IBMSD, IBM_PA_Providers, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{2244E0FA-D37A-4F6E-82FB-92F1DB78716D}:IBM_PA_Providers
    06666 14:51:25 (0) ** - ROOT/IBMSD, EndpointRegistrationProviderModule, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{BF833E81-33AA-40ED-B74A-329F006DB4F8}:EndpointRegistrationProviderModule
    06667 14:51:25 (0) ** - ROOT/CIMV2, SBLIM_Data_Gatherer, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{0D03AF80-A160-44EF-9E8B-318201F41693}:SBLIM_Data_Gatherer
    06668 14:51:25 (0) ** - ROOT/ADPT, ADPT_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{B007445E-6AF0-4CBD-9009-809F071FCE69}:ADPT_Module
    06669 14:51:25 (0) ** - ROOT/PG_INTEROP, SBLIM_Data_Gatherer, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{0D03AF80-A160-44EF-9E8B-318201F41693}:SBLIM_Data_Gatherer
    06670 14:51:25 (0) ** - ROOT/PG_INTEROP, LSIESG_SMIS13_HHR_ProviderModule, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{E21064DD-757A-4F2D-B798-81CDFF03B48C}:LSIESG_SMIS13_HHR_ProviderModule
    06671 14:51:25 (0) ** - ROOT/PG_INTEROP, emulex_fc_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{27734403-1E6C-4BC7-B97D-1FE9657B35EC}:emulex_fc_provider_Module
    06672 14:51:25 (0) ** - ROOT/PG_INTEROP, emulex_ucna_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{68D3C192-F517-41CC-B852-BA74A8D05A85}:emulex_ucna_provider_Module
    06673 14:51:25 (0) ** - ROOT/IBMSE, emulex_fc_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{27734403-1E6C-4BC7-B97D-1FE9657B35EC}:emulex_fc_provider_Module
    06674 14:51:25 (0) ** - ROOT/IBMSE, IBM_PA_Providers, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{2244E0FA-D37A-4F6E-82FB-92F1DB78716D}:IBM_PA_Providers
    06675 14:51:25 (0) ** - ROOT/IBMSE, emulex_ucna_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{68D3C192-F517-41CC-B852-BA74A8D05A85}:emulex_ucna_provider_Module
    06676 14:51:25 (0) ** - ROOT/LSI_MR_1_3_0, LSIESG_SMIS13_HHR_ProviderModule, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{E21064DD-757A-4F2D-B798-81CDFF03B48C}:LSIESG_SMIS13_HHR_ProviderModule
    06677 14:51:25 (0) ** - ROOT/EMULEX, emulex_fc_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{27734403-1E6C-4BC7-B97D-1FE9657B35EC}:emulex_fc_provider_Module
    06678 14:51:25 (0) ** - ROOT/EMULEX, emulex_ucna_provider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{68D3C192-F517-41CC-B852-BA74A8D05A85}:emulex_ucna_provider_Module
    06679 14:51:25 (0) ** - ROOT/BROCADE, brcdprovider_Module, C:\Program Files (x86)\Common Files\IBM\icc\cimom\bin\wmicpa.exe /G{48898EFD-0F9A-4657-B03D-FF400A7D2CDE}:brcdprovider_Module
    06680 14:51:25 (0) ** => This will make any operations related to the WMI class supported by the provider(s) to fail.
    06681 14:51:25 (0) **    This can be due to:
    06682 14:51:25 (0) **    - the de-installation of the software.
    06683 14:51:25 (0) **    - the deletion of some files.
    06684 14:51:25 (0) ** => If the software has been de-installed intentionally, then this information must be
    06685 14:51:25 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
    06686 14:51:25 (0) **    the provider registration data.
    06687 14:51:25 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\BROCADE path __Win32Provider Where Name='brcdprovider_Module' DELETE'
    06688 14:51:25 (0) ** => If not, you must restore a copy of the missing provider EXE/DLL file(s) as indicated by the path.
    06689 14:51:25 (0) **    You can retrieve the missing file from:
    06690 14:51:25 (0) **    - A backup.
    06691 14:51:25 (0) **    - The Windows CD.
    06692 14:51:25 (0) **    - Another Windows installation using the same version and service pack level of the examined system.
    06693 14:51:25 (0) **    - The original CD or software package installing this WMI provider.
    06694 14:51:25 (0) ** 
    06695 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06696 14:51:25 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
    06697 14:51:25 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    06698 14:51:25 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    06699 14:51:25 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    06700 14:51:25 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    06701 14:51:25 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    06702 14:51:25 (0) ** 
    06703 14:51:25 (0) ** Overall DCOM security status: ....................................................................................... OK.
    06704 14:51:25 (0) ** Overall WMI security status: ........................................................................................ OK.
    06705 14:51:25 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    06706 14:51:25 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
    06707 14:51:25 (0) ** - ROOT/SUBSCRIPTION, CommandLineEventConsumer.Name="BVTConsumer".
    06708 14:51:25 (0) **   'SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99'
    06709 14:51:25 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    06710 14:51:25 (0) **   'select * from MSFT_SCMEventLogEvent'
    06711 14:51:25 (0) ** 
    06712 14:51:25 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    06713 14:51:25 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
    06714 14:51:25 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    06715 14:51:25 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    06716 14:51:25 (0) ** - ROOT/SERVICEMODEL.
    06717 14:51:25 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    06718 14:51:25 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    06719 14:51:25 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    06720 14:51:25 (0) **    i.e. 'WMIC.EXE /NODE:"{ComputerName}" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    06721 14:51:25 (0) ** 
    06722 14:51:25 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    06723 14:51:25 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    06724 14:51:25 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 30 ERROR(S)!
    06725 14:51:25 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06726 14:51:25 (0) **   MOF Registration: ''
    06727 14:51:25 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06728 14:51:25 (0) **   MOF Registration: ''
    06729 14:51:25 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06730 14:51:25 (0) **   MOF Registration: ''
    06731 14:51:25 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06732 14:51:25 (0) **   MOF Registration: ''
    06733 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06734 14:51:25 (0) **   MOF Registration: ''
    06735 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06736 14:51:25 (0) **   MOF Registration: ''
    06737 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06738 14:51:25 (0) **   MOF Registration: ''
    06739 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06740 14:51:25 (0) **   MOF Registration: ''
    06741 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06742 14:51:25 (0) **   MOF Registration: ''
    06743 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06744 14:51:25 (0) **   MOF Registration: ''
    06745 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06746 14:51:25 (0) **   MOF Registration: ''
    06747 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06748 14:51:25 (0) **   MOF Registration: ''
    06749 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06750 14:51:25 (0) **   MOF Registration: ''
    06751 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06752 14:51:25 (0) **   MOF Registration: ''
    06753 14:51:25 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06754 14:51:25 (0) **   MOF Registration: ''
    06755 14:51:25 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06756 14:51:25 (0) **   MOF Registration: ''
    06757 14:51:25 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06758 14:51:25 (0) **   MOF Registration: ''
    06759 14:51:25 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06760 14:51:25 (0) **   MOF Registration: ''
    06761 14:51:25 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06762 14:51:25 (0) **   MOF Registration: ''
    06763 14:51:25 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06764 14:51:25 (0) **   MOF Registration: ''
    06765 14:51:25 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06766 14:51:25 (0) **   MOF Registration: ''
    06767 14:51:25 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06768 14:51:25 (0) **   MOF Registration: ''
    06769 14:51:25 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06770 14:51:25 (0) **   MOF Registration: ''
    06771 14:51:25 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06772 14:51:25 (0) **   MOF Registration: ''
    06773 14:51:25 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06774 14:51:25 (0) **   MOF Registration: ''
    06775 14:51:25 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06776 14:51:25 (0) **   MOF Registration: ''
    06777 14:51:25 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06778 14:51:25 (0) **   MOF Registration: ''
    06779 14:51:25 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06780 14:51:25 (0) **   MOF Registration: ''
    06781 14:51:25 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06782 14:51:25 (0) **   MOF Registration: ''
    06783 14:51:25 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
    06784 14:51:25 (0) **   MOF Registration: ''
    06785 14:51:25 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
    06786 14:51:25 (0) **    a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
    06787 14:51:25 (0) **    You can refresh the WMI class provider buffer with the following command:
    06788 14:51:25 (0) ** 
    06789 14:51:25 (0) **    i.e. 'WINMGMT.EXE /SYNCPERF'
    06790 14:51:25 (0) ** 
    06791 14:51:25 (0) ** WMI MOF representations: ............................................................................................ OK.
    06792 14:51:25 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    06793 14:51:25 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
    06794 14:51:25 (2) !! WARNING: WMI EXECQUERY operation errors reported: ................................................................... 2 WARNING(S)!
    06795 14:51:25 (0) ** - Root/CIMV2, 'Select * From Win32_PointingDevice WHERE Status = "OK"' did not return any instance while AT LEAST 1 instance is expected.
    06796 14:51:25 (0) ** - Root/CIMV2, 'Select * From Win32_Keyboard' did not return any instance while AT LEAST 1 instance is expected.
    06797 14:51:25 (0) ** 
    06798 14:51:25 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
    06799 14:51:25 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06800 14:51:25 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06801 14:51:25 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
    06802 14:51:25 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06803 14:51:25 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
    06804 14:51:25 (0) ** 
    06805 14:51:25 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    06806 14:51:25 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    06807 14:51:25 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    06808 14:51:25 (0) ** WMI static instances retrieved: ..................................................................................... 2072.
    06809 14:51:25 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    06810 14:51:25 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    06811 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06812 14:51:25 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    06813 14:51:25 (0) **   DCOM: ............................................................................................................. 0.
    06814 14:51:25 (0) **   WINMGMT: .......................................................................................................... 0.
    06815 14:51:25 (0) **   WMIADAPTER: ....................................................................................................... 0.
    06816 14:51:25 (0) ** 
    06817 14:51:25 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    06818 14:51:25 (0) **   DCOM: ............................................................................................................. 0.
    06819 14:51:25 (0) **   WINMGMT: .......................................................................................................... 0.
    06820 14:51:25 (0) **   WMIADAPTER: ....................................................................................................... 0.
    06821 14:51:25 (0) ** 
    06822 14:51:25 (0) ** 30 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
    06823 14:51:25 (0) ** => This error is typically a WMI error. This WMI error is due to:
    06824 14:51:25 (0) **    - a missing WMI class definition or object.
    06825 14:51:25 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
    06826 14:51:25 (0) **      You can correct the missing class definitions by:
    06827 14:51:25 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
    06828 14:51:25 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
    06829 14:51:25 (0) **            (This list can be built on a similar and working WMI Windows installation)
    06830 14:51:25 (0) **            The following command line must be used:
    06831 14:51:25 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
    06832 14:51:25 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
    06833 14:51:25 (0) **            with WMI by starting the ADAP process.
    06834 14:51:25 (0) **    - a WMI repository corruption.
    06835 14:51:25 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
    06836 14:51:25 (0) **      to validate the WMI repository operations.
    06837 14:51:25 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
    06838 14:51:25 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
    06839 14:51:25 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
    06840 14:51:25 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
    06841 14:51:25 (0) **      the WMI repository must be reconstructed.
    06842 14:51:25 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
    06843 14:51:25 (0) **          otherwise some applications may fail after the reconstruction.
    06844 14:51:25 (0) **          This can be achieved with the following command:
    06845 14:51:25 (0) **          i.e. 'WMIDiag ShowMOFErrors'
    06846 14:51:25 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
    06847 14:51:25 (0) **          ALL fixes previously mentioned.
    06848 14:51:25 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
    06849 14:51:25 (0) ** 
    06850 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06851 14:51:25 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
    06852 14:51:25 (0) ** INFO: Unexpected registry key value:
    06853 14:51:25 (0) **   - Current:  HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
    06854 14:51:25 (0) **   - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
    06855 14:51:25 (0) **     From the command line, the registry configuration can be corrected with the following command:
    06856 14:51:25 (0) **     i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
    06857 14:51:25 (0) ** 
    06858 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06859 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06860 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06861 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06862 14:51:25 (0) ** 
    06863 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06864 14:51:25 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    06865 14:51:25 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    06866 14:51:25 (0) ** 
    06867 14:51:25 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\{Username}\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_{ComputerName}_2012.07.10_14.40.25.LOG' for details.
    06868 14:51:25 (0) ** 
    06869 14:51:25 (0) ** WMIDiag v2.1 ended on Tuesday, July 10, 2012 at 14:51 (W:103 E:51 S:1).

    Following might help
    A Wmiprvse.exe process crashes in Windows Server 2008 R2 when you use the WMI interface to query the hardware status on a computer that supports the IPMI standard
    http://support.microsoft.com/kb/2280777
    I do not represent the organisation I work for, all the opinions expressed here are my own.
    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
    I saw this in my googling.  Listed as the cause on the hotfix page is the following: "This
    problem occurs because the Ipmiprv.dll module leads the Wmiprvse.exe process to crash. This behavior depends on certain hardware sensor types when the sensor is enumerated."  The
    faulting module for that hotfix is ipmiprv.dll, and our faulting module is ntdll.dll.  I'm thinking that this hotfix isn't applicable, but I'm open to hearing why I'm incorrect if I am.
    Seth Johnson

Maybe you are looking for