salut,
 
ayant installé 3Dmark06 pour tester l'o/c de mon C2D, des que je le lance, il scanne ma config et me marque l'erreur suivante :
 
System info error : no wbem connected
MO_WMI::CWMIObject::connectToWbem()
 
Savez vous d'où cela peut il venir ?
 
Merci de votre aide  

Bon j'ai trouvé ca comme erreur mais je ne sais pas comment réparer tout ca...
 
.1184 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1185 23:31:57 (0) ** -------------------------------------- WMI REPORT: BEGIN -------------------------------------------
.1186 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1187 23:31:57 (0) **  
.1188 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1189 23:31:57 (0) ** Windows XP - Service pack 2 - 32-bit - User 'PC-xxxx\LSD3USER' on computer 'PC-xxxx'.
.1190 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1191 23:31:57 (0) ** There are no missing WMI system files: ..................................................... OK.
.1192 23:31:57 (0) ** There are no missing WMI repository files: ................................................. OK.
.1193 23:31:57 (0) ** BEFORE running WMIDiag:
.1194 23:31:57 (0) ** The WMI repository has a size of: .......................................................... 10 MB.
.1195 23:31:57 (0) ** - Disk free space on 'C:': ................................................................. 8277 MB.
.1196 23:31:57 (0) **   - INDEX.BTR,                     1433600 bytes,      05/11/2006 07:01:34
.1197 23:31:57 (0) **   - INDEX.MAP,                     724 bytes,          02/01/2002 23:00:55
.1198 23:31:57 (0) **   - MAPPING.VER,                   4 bytes,            02/01/2002 23:00:55
.1199 23:31:57 (0) **   - MAPPING1.MAP,                  4992 bytes,         02/01/2002 21:34:13
.1200 23:31:57 (0) **   - MAPPING2.MAP,                  4992 bytes,         02/01/2002 23:00:55
.1201 23:31:57 (0) **   - OBJECTS.DATA,                  8601600 bytes,      05/11/2006 07:01:34
.1202 23:31:57 (0) **   - OBJECTS.MAP,                   4268 bytes,         02/01/2002 23:00:55
.1203 23:31:57 (0) ** AFTER running WMIDiag:
.1204 23:31:57 (0) ** The WMI repository has a size of: .......................................................... 10 MB.
.1205 23:31:57 (0) ** - Disk free space on 'C:': ................................................................. 8277 MB.
.1206 23:31:57 (0) **   - INDEX.BTR,                     1433600 bytes,      05/11/2006 07:01:34
.1207 23:31:57 (0) **   - INDEX.MAP,                     724 bytes,          02/01/2002 23:00:55
.1208 23:31:57 (0) **   - MAPPING.VER,                   4 bytes,            02/01/2002 23:00:55
.1209 23:31:57 (0) **   - MAPPING1.MAP,                  4992 bytes,         02/01/2002 21:34:13
.1210 23:31:57 (0) **   - MAPPING2.MAP,                  4992 bytes,         02/01/2002 23:00:55
.1211 23:31:57 (0) **   - OBJECTS.DATA,                  8601600 bytes,      05/11/2006 07:01:34
.1212 23:31:57 (0) **   - OBJECTS.MAP,                   4268 bytes,         02/01/2002 23:00:55
.1213 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1214 23:31:57 (0) ** INFO: Windows Firewall status: ............................................................. ACTIVE.
.1215 23:31:57 (0) ** => Windows Firewall 'RemoteAdmin' status is INACTIVE.
.1216 23:31:57 (0) **    - This will prevent any WMI remote connectivity to this machine.
.1217 23:31:57 (0) **    - You can adjust the configuration by executing the following command:
.1218 23:31:57 (0) **    - e.g. 'NETSH.EXE FIREWALL SET SERVICE REMOTEADMIN ENABLE SUBNET'
.1219 23:31:57 (0) ** => Windows Firewall application exception for 'UNSECAPP.EXE' is missing.
.1220 23:31:57 (0) **    - This will prevent any script and MMC application asynchronous callbacks to this machine.
.1221 23:31:57 (0) **    - You can adjust the configuration by executing the following command:
.1222 23:31:57 (0) **    - e.g. 'NETSH.EXE FIREWALL SET ALLOWEDPROGRAM %SYSTEMROOT%\SYSTEM32\WBEM\UNSECAPP.EXE WMICALLBACKS ENABLE'
.1223 23:31:57 (0) **  
.1224 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1225 23:31:57 (0) ** WMI registry setup: ........................................................................ OK.
.1226 23:31:57 (0) ** INFO: WMI service has dependents: .......................................................... 2 SERVICE(S)!
.1227 23:31:57 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1228 23:31:57 (0) ** - Windows Firewall/Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Automatic')
.1229 23:31:57 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1230 23:31:57 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
.1231 23:31:57 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
.1232 23:31:57 (0) **          this can prevent the service/application to work as expected.
.1233 23:31:57 (0) **  
.1234 23:31:57 (0) ** RPCSS service: ............................................................................. OK (Already started).
.1235 23:31:57 (0) ** WINMGMT service: ........................................................................... OK (Already started).
.1236 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1237 23:31:57 (0) ** WMI service DCOM setup: .................................................................... OK.
.1238 23:31:57 (0) ** WMI components DCOM registrations: ......................................................... OK.
.1239 23:31:57 (0) ** WMI ProgID registrations: .................................................................. OK.
.1240 23:31:57 (0) ** WMI provider DCOM registrations: ........................................................... OK.
.1241 23:31:57 (0) ** WMI provider CIM registrations: ............................................................ OK.
.1242 23:31:57 (0) ** WMI provider CLSIDs: ....................................................................... OK.
.1243 23:31:57 (0) ** WMI providers EXE/DLL availability: ........................................................ OK.
.1244 23:31:57 (0) ** - Started at 'Root' --------------------------------------------------------------------------------
.1245 23:31:57 (1) !! ERROR: WMI ADAP status: .................................................................... NOT AVAILABLE
.1246 23:31:57 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1247 23:31:57 (0) **    the performance counters with the WMI performance classes with the following commands:
.1248 23:31:57 (0) **    e.g. 'WINMGMT.EXE /CLEARADAP'
.1249 23:31:57 (0) **    e.g. 'WINMGMT.EXE /RESYNCPERF'
.1250 23:31:57 (0) **    The ADAP process logs informative events in the Windows NT event log.
.1251 23:31:57 (0) **    More information can be found on MSDN at:
.1252 23:31:57 (0) **    http://msdn.microsoft.com/library/ [...] events.asp
.1253 23:31:57 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: ......................... 5 ERROR(S)!
.1254 23:31:57 (0) ** - Root, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1255 23:31:57 (0) ** - Root, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1256 23:31:57 (0) ** - Root/Default, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1257 23:31:57 (0) ** - Root/CIMv2, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1258 23:31:57 (0) ** - Root/WMI, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.1259 23:31:57 (0) **  
.1260 23:31:57 (0) ** WMI GET static operations: ................................................................. OK.
.1261 23:31:57 (0) ** WMI MOF representations: ................................................................... OK.
.1262 23:31:57 (0) ** WMI QUALIFIER access operations: ........................................................... OK.
.1263 23:31:57 (0) ** WMI ENUMERATION operations: ................................................................ OK.
.1264 23:31:57 (0) ** WMI EXECQUERY operations: .................................................................. OK.
.1265 23:31:57 (0) ** WMI PUT operations: ........................................................................ OK.
.1266 23:31:57 (0) ** WMI DELETE operations: ..................................................................... OK.
.1267 23:31:57 (0) ** WMI GET VALUE operations: .................................................................. OK.
.1268 23:31:57 (0) ** WMI static instances retrieved: ............................................................ 0.
.1269 23:31:57 (0) ** WMI dynamic instances retrieved: ........................................................... 0.
.1270 23:31:57 (0) ** WMI instances request cancellations (to limit performance impact): ......................... 0.
.1271 23:31:57 (0) **  
.1272 23:31:57 (0) ** 5 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
.1273 23:31:57 (0) ** => This error is typically a WMI error. This WMI error is due to:
.1274 23:31:57 (0) **    - a missing WMI class definition or object.
.1275 23:31:57 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
.1276 23:31:57 (0) **      You can correct the missing class definitions by:
.1277 23:31:57 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
.1278 23:31:57 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
.1279 23:31:57 (0) **            (This list can be built on a similar and working WMI Windows installation)
.1280 23:31:57 (0) **            The following command line must be used:
.1281 23:31:57 (0) **            e.g. 'WMIDiag CorrelateClassAndProvider'
.1282 23:31:57 (0) **    - a WMI repository corruption.
.1283 23:31:57 (0) **      Under Windows XP SP2, you can validate the repository consistency
.1284 23:31:57 (0) **      by executing the following command:
.1285 23:31:57 (0) **      e.g. 'WMIDiag CheckConsistency'
.1286 23:31:57 (0) **    Note: Under Windows XP SP2, when the repository is checked and detected INCONSISTENT,
.1287 23:31:57 (0) **          a new repository is automatically re-created based on Auto-Recovery mechanism.
.1288 23:31:57 (0) **          Note that some information can be lost during this process (e.g. static data, CIM registration).
.1289 23:31:57 (0) **          However, the original repository is located at 'C:\WINDOWS\SYSTEM32\WBEM\Repository.001'.
.1290 23:31:57 (0) **          The machine must be rebooted for the system to work with the re-created repository.
.1291 23:31:57 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1292 23:31:57 (0) **          otherwise some applications may fail after the reconstruction.
.1293 23:31:57 (0) **          This can be achieved with the following command:
.1294 23:31:57 (0) **          e.g. 'WMIDiag ShowMOFErrors'
.1295 23:31:57 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1296 23:31:57 (0) **          ALL fixes previously mentioned.
.1297 23:31:57 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (e.g. SMS Inventory)
.1298 23:31:57 (0) **  
.1299 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1300 23:31:57 (0) ** WMI Registry key setup: .................................................................... OK.
.1301 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1302 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1303 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1304 23:31:57 (0) ** --------------------------------------- WMI REPORT: END --------------------------------------------
.1305 23:31:57 (0) ** ----------------------------------------------------------------------------------------------------
.1306 23:31:57 (0) **  
.1307 23:31:57 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\LSD3USER\LOCAL SETTINGS\TEMP\WMIDIAG-V1.10_XP__.CLI.SP2.32_PC-xxxx_2002.01.02_23.31.55.LOG' for details.
.1308 23:31:57 (0) **  
.1309 23:31:57 (0) ** WMIDiag executed in 2 second(s).