miahallen Posted December 29, 2010 Share Posted December 29, 2010 Anyone ever seen this before? I cannot submit my result with this problem Quote Link to comment Share on other sites More sharing options...
Maxi Posted December 29, 2010 Share Posted December 29, 2010 01 isn't supported by FM anymore, ORB is gone for this bench. Quote Link to comment Share on other sites More sharing options...
Crew Turrican Posted December 29, 2010 Crew Share Posted December 29, 2010 as soon as you click on "show details" a "details.txt" file is created under c:\documents and settings\your-username\temp\ which shows just what you see in "show details". delete it and try again. Quote Link to comment Share on other sites More sharing options...
SoF Posted December 29, 2010 Share Posted December 29, 2010 01 isn't supported by FM anymore, ORB is gone for this bench. and how does this help in any way? why not trying to help instead beeing like FM.... Is it an old windows which you ran 01 a zillion times? try what turrican said I think it'll help. Another possibility (but I don't think that will happen with a bench windows) you have installed it with User a and now you are logged-in as User b and don't have write access to that specific folder. check the user rights then. Quote Link to comment Share on other sites More sharing options...
miahallen Posted December 29, 2010 Author Share Posted December 29, 2010 01 isn't supported by FM anymore, ORB is gone for this bench. Thats why I posted my question here, and not at FM as soon as you click on "show details" a "details.txt" file is created under c:\documents and settings\your-username\temp\ which shows just what you see in "show details". delete it and try again. Tried that already...build is brand new. When I delete the file then click the button to open the details again...the file re-creates itself. This is the BZ XP build.....I think I'm gonna try another build, I think it's the first time I've ever tried to run 01 on his OS. Quote Link to comment Share on other sites More sharing options...
Maxi Posted December 29, 2010 Share Posted December 29, 2010 and how does this help in any way? why not trying to help instead beeing like FM.... hey don't cut my head off, i didn't look at screen properly Quote Link to comment Share on other sites More sharing options...
SoF Posted December 30, 2010 Share Posted December 30, 2010 hey don't cut my head off, i didn't look at screen properly I'm a small guy - when I cut off something of somebody it mainly will be his feet Quote Link to comment Share on other sites More sharing options...
Massman Posted December 30, 2010 Share Posted December 30, 2010 I'm a small guy Quoted for eternity Quote Link to comment Share on other sites More sharing options...
SoF Posted January 2, 2011 Share Posted January 2, 2011 I just had the same - are you running "a new" platform? had this with 2600K and 465 GTX... Quote Link to comment Share on other sites More sharing options...
FM_Jarnis Posted January 3, 2011 Share Posted January 3, 2011 My guess: "too new" hardware totally confusing the ancient hardware detection routines of 3DMark 2001... Quote Link to comment Share on other sites More sharing options...
Massman Posted January 3, 2011 Share Posted January 3, 2011 Shouldn't be a problem. I got perfectly valid runs with 2600K and GTX480. Quote Link to comment Share on other sites More sharing options...
Maxi Posted January 3, 2011 Share Posted January 3, 2011 My guess: "too new" hardware totally confusing the ancient hardware detection routines of 3DMark 2001... Is there a switch to disable this like we had in other FM 3DMarks? Quote Link to comment Share on other sites More sharing options...
FM_Jarnis Posted January 5, 2011 Share Posted January 5, 2011 (edited) Is there a switch to disable this like we had in other FM 3DMarks? Not that I know of. I think it wasn't seen as needed because no matter what the 3DMark 2001SE detection code gets, the benchmark runs ignoring all that completely. It would only affect submits (no longer supported) and viewing of detailed results. Patch probability = 0%. Sorry. Edited January 5, 2011 by FM_Jarnis Quote Link to comment Share on other sites More sharing options...
miahallen Posted January 6, 2011 Author Share Posted January 6, 2011 I just got done building a new stripped 01 build with SP3 slipstreamed in. I loaded up with 182.50 drivers and a GTX 285 Still running the 2600K EXACT SAME ISSUE I just had the same - are you running "a new" platform? had this with 2600K and 465 GTX... Yes, this was with 2600K & 580... My guess: "too new" hardware totally confusing the ancient hardware detection routines of 3DMark 2001... Even though support has been dropped, we do appreciate your comments on the matter, thanks Shouldn't be a problem. I got perfectly valid runs with 2600K and GTX480. YGPM Quote Link to comment Share on other sites More sharing options...
SoF Posted January 9, 2011 Share Posted January 9, 2011 My guess: "too new" hardware totally confusing the ancient hardware detection routines of 3DMark 2001... seems to depend on the mobo not gpu - the more "unknown devices" shown in xp device manager the higher the probability of recieving the error... Quote Link to comment Share on other sites More sharing options...
Massman Posted January 9, 2011 Share Posted January 9, 2011 seems to depend on the mobo not gpu - the more "unknown devices" shown in xp device manager the higher the probability of recieving the error... Confirmed. Had no issues with the P67A-UD4 and same error on M4E. UD4 doesn't have EFI? Quote Link to comment Share on other sites More sharing options...
miahallen Posted January 10, 2011 Author Share Posted January 10, 2011 Great....I'll test on my GBT boards ASAP.....I'm a bit tied up writing reviews ATM Quote Link to comment Share on other sites More sharing options...
SV1SH Posted January 13, 2011 Share Posted January 13, 2011 (edited) I have the same problem only with 4850 and 4870.01 do not show details Edited January 13, 2011 by SV1SH Quote Link to comment Share on other sites More sharing options...
Maxi Posted January 13, 2011 Share Posted January 13, 2011 seems to depend on the mobo not gpu - the more "unknown devices" shown in xp device manager the higher the probability of recieving the error... Does it still appear if all drivers are loaded so there are no unknown devices? What about if you disable the unknown devices? Quote Link to comment Share on other sites More sharing options...
Massman Posted January 14, 2011 Share Posted January 14, 2011 Confirmed. Had no issues with the P67A-UD4 and same error on M4E. UD4 doesn't have EFI? Just tested the MSI P67A-GD65, no problem. So this is ASUS specific? Quote Link to comment Share on other sites More sharing options...
SoF Posted January 15, 2011 Share Posted January 15, 2011 Does it still appear if all drivers are loaded so there are no unknown devices? What about if you disable the unknown devices? i never install drivers on my bench-systems but disabling the devices was something I wanted to test for quite a while now. I will report back after testing maybe tomorrow afternoon. Quote Link to comment Share on other sites More sharing options...
Maxi Posted January 18, 2011 Share Posted January 18, 2011 Hey guys, Q56_Monster found the answer recently. Try it! Click orb submission, then click the detail button. Quote Link to comment Share on other sites More sharing options...
slamms Posted January 19, 2011 Share Posted January 19, 2011 it is not working on MIVE Quote Link to comment Share on other sites More sharing options...
Q56_Monster Posted January 19, 2011 Share Posted January 19, 2011 Are you clicking the "online results browser" button? There is a "details" button on the ORB pop up that works...works for me on an Asus P8P67 Deluxe mobo. Quote Link to comment Share on other sites More sharing options...
dejo1 Posted January 19, 2011 Share Posted January 19, 2011 nice find Q. many have been having this issue Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.