Latest posts of: psc

Show Posts
Pages: [1]

on: January 20, 2014, 09:03:46 PM

Quote from: ozie on January 20, 2014, 08:52:24 PM You are the best! I will report how vertcoin performs. Getting about 81 kh/s on a 770M (910MHZ) vs 214 kh/s on a R9 270X (which was getting 450 kh/s on "normal" scrypt and 2.9 kh/s on YAC) - Impressive

on: January 20, 2014, 08:28:43 PM

Quote from: ozie on January 20, 2014, 08:19:11 PM Any news on the vertcoin issue? latest github version still gives me the following error: Unhandled exception at 0x000007F679AD8A64 in cudaminer.exe: Stack cookie instrumentation code detected a stack-based buffer overrun. Seems something related to cpu memory management. Crashes with Win and Linux. I know there are maybe more important things to do but vertcoin is already looking very promising. Not sure which issue you are referring to ? The post linked to in the post above (yours) has a working version for windows - there was a slight change for vertcoin apparently.

on: January 20, 2014, 08:16:59 PM

I see that someone has "released cudaminer" for vertcoin https://bitcointalk.org/index.php?topic=404364.msg4620453#msg4620453 at least with a better ratio than the buggy AMD implementation vs scrypt - would have been gentlemanly if they had tipped their hat to Christian for all his effort.

on: January 15, 2014, 10:22:22 PM

Quote from: lolobubu on January 15, 2014, 10:11:45 PM Oh i see, im not yet a pro at .NET and C++ anyone else here can help me out with a compiled working binary ? will donate some YAC as soon as i can make some Windows one was indicated here https://bitcointalk.org/index.php?topic=167229.msg4427833#msg4427833

on: January 15, 2014, 08:42:37 PM

Quote from: cbuchner1 on January 15, 2014, 08:14:59 PM It may still make sense to increase the default batch size -b 1024 to something like -b 4096 or -b 8192 when running interactive mode with scrypt-jane. This costs a bit of display smoothness, but adds more hash/s. Thanks for the tip ! - increased my 770M hashrate from 1.1 to 1.33 on windoze (-b 4096)

on: December 31, 2013, 09:31:47 AM

Quote from: Scribbles646 on December 31, 2013, 02:23:35 AM Sort of solved my own problem, adding the device flag (-d 0)(-d 1) and running each card from a separate window solved the problem, confirmed increase from 49kh/s to 73kh/s, however I quickly went back to the previous build, as the build from the 18th raised my gpu temps to a high of 91C. I would probably use the new build if this wasn't a thousand dollar laptop. On a notebook you can use NVIDIA Inspector to set a temperature target for your GPU's

on: December 28, 2013, 08:10:21 PM

Quote from: skyhawk on December 28, 2013, 05:22:40 PM December 26th? That's two days after the Hashcows theft. Why the hell would he start mining to the same address two days after stealing 40BTC from another coin-switching pool? This bloke's incredibly arrogant, or incredibly stupid, or both. Or is he trying to somehow dilute or launder his ill-gotten goods? https://blockchain.info/address/13R87ropkDKzDEuVeQoX64kkcLvPWVdTKH He's starting to spend the funds. Probably trying to find a soft spot on the other pools ?

on: December 28, 2013, 04:23:49 PM

They were active on middlecoin http://middlecoin2.s3-website-us-west-2.amazonaws.com/reports/13R87ropkDKzDEuVeQoX64kkcLvPWVdTKH.html

on: December 28, 2013, 08:57:14 AM

The 4GB card will use slightly more power and will probably have less headroom for memory over-clocking. You will only get 470 kh/s with a dose of over-clocking. I run a 270X @ 450 kh/s : E : 1060 M : 1425 (5700)

Pages: [1]