• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

3dmark 06 problem. Error messege.

Soldato
Joined
6 Feb 2004
Posts
3,450
Location
Wiltshire
system info error: Wbem not connected
MO_WMI::CWMIOBJECT::CONNECTTOWBEM()

Andy ideas?

System specs are as follows:

Nvidia 7900GT @ 565 / 800
805d @ 3.8 Ghz
2Gb DDR667
Rapter 74Gb
DS3 board.

Same happens when at stock so not a hardware fault.

edit - 01, 03, & 05 all work.
 
No I get the same.

There's an FAQ on the Futuremark site saying it's a known issue on some platforms, and is under investigation.
 
where abouts is the faq.

If thats true then i was going to say "well aint that great"

edit -

"3DMark06 exits or causes a bluescreen error whenever I try to launch it. How can this be corrected?
A: Try un-plugging any external USB/FireWire storage devices such as DVD-drives or external harddisks. Some network-attached storage devices may also cause this problem to appear, so unmounting all network drives might also help. You can also add "-nosysteminfo" at the end of the "Target:" field of 3DMark06's application shortcut to disable the SystemInfo from running when the benchmark is being launched. This should allow you to run all of the tests normally, but your results can't be submitted to the ORB if this option has been used to launch the benchmark."

Just change the target with nosystem info and its works. :)
 
Last edited:
http://service.futuremark.com/support/search.jsp?categoryid=14&search=1

The specific entry was:-

Q: I'm getting a "System Info error: WMI Enumeration not found" or a "System Info error: Wbem not connected" error message when starting the benchmark. How can this be corrected?
A: This problem occurs on some systems and we're currently investigating the cause. There are a couple of things which may help: 1) Ensure that you have the latest available motherboard BIOS installed. 2) If you have created a custom Windows XP installation CD or manually disabled standard services, please ensure that "Management Instrumentation (WMI)" service is installed and configured to run. You can also use the "-nosysteminfo" command line option to disable the SystemInfo from running. This will prevent you from submitting your results to the ORB, though.
 
Back
Top Bottom