Jump to content
HWBOT Community Forums

lanbonden

Members
  • Posts

    276
  • Joined

  • Last visited

Posts posted by lanbonden

  1. I have to sadly report, that SuperPi v1.6 Techpowerup mod crash at 24h mark for 32M test too:

     

    Super_Pi_1_6_24h_crash.jpg

     

    That suxx. And sadly I did not took a photograph using camera from the amazingly fast run - 23 loop was at 23h 43min! IMHO good for 90MHz K5 PR75... ;)

     

    I wasnt home when it ended, but the 24h+ run on 1.6 sure has crashed for me aswell now after 24h plus. So confirmed that 1.5 and 1.6 cant run longer then 24 hours id say.

  2. So, that means you can confirm the crash at 24h or not? "Watched it close" seems to suggest that, but frankly... more direct confirmatio might be need.

     

    I run the v1.6 ... it goes faster, as before K5 PR75 @ 90MHz need 68min per loop, now 59min is enought... interesting. Maybe it run with the part of ram, that goes on 2 ranks dimm, instead of the 1 rank one? Dunno. But I'm, of course, nowhere near the end...

     

    Well, I guess so. I didnt get an error on WinXP but it just closed down instead. I took a risk at trying to end it with a nice time of 23h 59min XX seconds but it backfired and superpi just closed down instead so my guess for the crash is that the end time was 24h 00min XX sec which lead to a crash or that it just crashed the second it reached 24h.

     

    Im just over 19h into the run with 1.6 now so will know how it plays out in 5 hours.

  3. probably wont be home when it happens, but first referens round will finish in a bit over 4hours at an estimated runtime of 23h 53mins to see that my slowdown dont affect superpi in any wierd way. Next part after that is to start a new round with the goal to finish just after 24h to see if its possible with a "modern" system with winXP or if its actually superpi thats to blame instead of a bug with winNT and superpi or something.

  4. ObscureParadox -

     

    It just cannot be, I believe that I already proved it. 5 crashes at 24h mark is, IMHO, enough.

     

     

     

    Not that much, wPrime 1024M run suffer the same problem. When time flip at midnight to the next day, it write just "cheat detected" and stop the calculation. So this is another bench, besides SuperPi 32M, witch is limited to 24h.

    I recently encountered that with... you quessed what - AMD K5 PR75. So it is not all that strange for me, it is "normal behaviour" from my point of view. Of course that *SHOULD* get fixed. Who will bug the autor/autors or anyone who can help out?

     

     

    lanbonden - more verifications is need, agreed. But I'm quite sure already.

     

    The thing i do differnt is runing it on a "modern" rig with winXP, not that it should mater but still nice to see.

     

    wonder if we get this as a stage in the country cup, longest superpi32M run :D

  5. You can control the cache divider with CPUcool, so actually there is no need to do soldering work.

     

    Maybe you should also try to clean the pcb with alcohol as the soldering flux can be conducting.

     

    Thansks for the answeer.

    Well, I would still have had to solder the multiplier right? Or can that be changed with software also?

     

    Your cleaning advice seems to have fixed one of the 2 problems as R106 and R107 aint the same anymore, it didnt do anything for R103 / R104 side tho.

     

    This is a new image after the cleaning and some more solder removing, the combination of strong light and a bad camera really makes the dirt shine!

     

    82842071ef.jpg

     

    I also found this "bad" image of how it should look so I could see what was traces in the pcb. And according to this one should there be a short between R103/R104 at the lower side but not on the top side and I cant see anything that should be a short between R103/R104s top sides and nope, the board still doesnt boot with the CPU, just shows 4 red lights

     

    523b3666ba.png

  6. For group B ( just as a reference ) I vote 8800 GT 512MB, very common.

     

    There are many custom designs with simple voltmod.

     

    For group A ( just as a reference ) GTX 260 216SP or HD 5850.

     

    Voltmod allowed and AIO (CPU) / any aircooling method for GPU ?

     

    These are just options. 8800 GT is a very good card for beginners and has huge improvements from tweaking order / lod in older benchmarks.

     

    If anyone is offended by the suggestion posted above, please ignore my post. It's just my honest opinion.

     

    I vote for alowing watercooling aswell as there is probably more people then me that got waterblocks for pretty much anything but dont have any custom aircoolers for some specific old card and its kind of hard to get a custom cooler for say a 8800gt today..

  7. First time playing with Slot-A and no spare CPU so cant controll measure so checking if someone here is familar with this ancient stuff.

     

    This CPUs are heavily limited by the cashe speed so tried to do a hard mod to change the divider for the cashe from 1/2 to 1/3 according to http://www.ocinside.de/workshop_en/athlonresistors/

     

    Its a 500Mhz cpu with SEC 1/2 seting from start and that matched the setup from the guide and as its such a easy mod to just move 2 resistors did I get lazy and didnt controll measure any resistances before starting.. and ofc didnt it boot at all.

     

    76a1a137f6.jpg

     

    Ive removed the 2 resistors to try and see if there is a short but nothing I can see more then that the surface of the card looks horrible and I should have gone with lower temperature!

     

    the wierd thing:

    Point 1 - 2 ~5Ohm

    Point 1 - 5 0Ohm

    Point 1 - 6 ~5Ohm

    Point 2 - 6 0Ohm

     

    Point 3 - 4, 0Ohm

    Point 3 - 7, 133kOhm

    Point 3 - 8, 133kOhm

    Point 7 - 8, 0Ohm

     

    It just doesnt make sence, why move the resistor if R103/R104 seems to be in parallel anyways and same with R106/R107. Have I managed to burn the pcb so bad that Ive shorted something, anyone remember how the resistanse should be in this case and what points shouldnt be shorted?

     

    9d4b89d83e.jpg

  8. The stages are pretty much decided on but would want some input about timing of the competition.

     

    1) What do you think about the round lenght of 1 month? To long/short with only a few stages each round?

     

    2) When is a good time to start it? I was looking at starting it after the Country cup and the hollidays as I have a feeling no one wants to bench over Xmas/new year. Here in Sweden id say it would be fine to have first stage from 1-31 of january, is this ok for the rest of the world aswell? Wait another month to get a break after the hollydays and Country cup?

  9. Grats all... Definitely a fun run.

     

    Although it would be nice next year if TC is not the same as Old School! We have 10+ years of stuff to work with if we stop at 775. That's plenty ;)

     

    The good mix of all kinds of stages is what I like the most with the competition, that there is something for everyone and its a real team competition couse the chanse of one guy having all the stuff is very slim :)

     

    And a big grats to CP for great performance during the cup!

  10. Must say that I have no idea how its calculated yet.

     

    639769e6b8.png

     

    This is with the submissions reaching:

    CPU Challenge, best place 23 giving 7 points (points correct atleast)

    GPU Challenge, best place 1 giving 50 points.

    Misc Challenge, best place 7 giving 26 points.

    Mem Challenge, best place 12 giving 18 points

  11. No, just stoping of the CPU load... intesting for some, I believe. Some of the refreshbugs caused by not responding CPU-Z are visible...

     

    And of course, in the end score, there is the refreshbug again!

    http://img.hwbot.org/u8592/image_id_1496581.jpg

     

    And the score cannot be submited - just now. Just great!

     

    The GPUPi stage ended like 20 hours ago or something so if your trying to submit not you missed the deadline :(

  12. Just 1-2 hours later it crashed :( :(

     

    WHYYYY?!?!? Is there a bug in windows guts? It the aplication - CPU time limitation to 24 hrs or something? I do not understand this crap. Enough time waisting for this month. At least I did SPI1M and pifast benchmarks :)

     

    Interesting thought, is there any submissions at all thats longer then 24 hours posted from superpi?

     

    Got my thinking about some info from this post (that I shorted down to only include the relevant part)

     

    Depends on the hardware tested, but yes, running Spi32/W1024 on Pentium 1 will set you for 30 hours+. Do remember Wprime has an issue when a run takes over 24hrs, make sure you revert the OS time back every 23ish hours.

     

     

    Could it be that superpi got the same problem as Wprime with 24h+ runs?

  13. That sounds pretty interesting!

     

    Thats very much along the lines of what I was thinking. If its 5 stages it fits pretty good with the five 3dmarks thats runs on this old hardware. So limit the hardware to stuff released before that date, would also be fun to see if I can dig out some early worldrecord presented by some overclocker back at launch just for show and to try and beat :)

     

    3DMark99 MAX March 8, 1999 (October 26, 1998 for the none MAX version)

    3DMark2000 December 6, 1999

    3DMark2001 SE February 12, 2002 (March 13, 2001 for the regular 2001 version)

    3DMark03 February 11, 2003

    3DMark05 September 29, 2004

     

    Then for the second stage some 2dmark/frequency/memory test on a suitable platform from that era, this would also be a great time to revissit those sockets that seen no love in the past competitions like Socket A, socket 423 and Socket 754

×
×
  • Create New...