Posts by Karsten Vinding

1) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1924214)
Posted 6 days ago by Profile Karsten Vinding
I have to ask, mostly because I have had similar problems recently myself...:

Did you upgrade your BIOS about the time where you moved the PC?

I have had problems since I upgraded my BIOS from ver 3401 (AGESA 1071) to 3803 (AGESA 1000a). My board is the ASUS TUF B350M-PLUS GAMING.

The system became unstable and would crash. There was no regularity to the crashes. They happened at stock, overclocked, sometimes after few minutes sometimes the system would run for days.

But it allways crashed with a blue screen, never just froze.

As a last resort i set my ram to 2400MHz. My ram is Ryzen certified DDR 3200 (G.Skill FlareX), which I have been running at 3200 since day one without problems. But setting it to 2400 MHz removed the crashes.

I have been reading up on the problem, and its a known problem with the latest AGESA that it breaks some RAM (others get better). And if the ram is unstable peoble have seen corruption of their OS'es.

I am a little irritated that my, rather expensive, ram is now running below spech, but at least my system is now stable.

I'll wait for a fix, mostly because a downgrade is not really very straight forward on my board.
2) Message boards : Number crunching : Gridcoin...? (Message 1915473)
Posted 27 Jan 2018 by Profile Karsten Vinding
An update on my Gridcoin experience up until now.

I have been Gridcoining for about 45 days now, and earned my first stake of coins today. All in all I have made Gridcoins that have a value of about 40$....

It has been a steep learning curve, and I'm still not sure I understand all the inner workings of the system. I probably do not.

The original plan was to donate all my earnings to Seti. That is still the plan, but I have had to modify it.

First of all I dropped riding Solo for a start, and joined a pool, which has steadily been paying since then. Slowly rising to about 15 coins a day.
I still run 20% Seti beside the pool in solo mode, to keep up a little RAC, so I could probably make some more coins, but I like it the way I have it set up.
I have also tried getting free coins from the so called "faucets", but they pay very little, and are often offline, so I'll probably stop doing that soon. Its not worth the effort.

My plan now is to keep the current setup until I start staking coins regularly, like once every 14 days or so.

Then I'll start increasing my solo crunching and reduce the pool crunching, while still building up coins. When I get enough coins that I stake once to twice a week (on average), I'll go full solo.
From then on I'll pay my earnings to Seti, but keep a high enough coin balance to keep up the staking frequency.
As dificulty keeps going up, I'll have to add coins to my wallet to keep staking often. So not all coins will go to Seti, only the surplus not needed to keep up my staking interval. Theres a balance there that will need to be found.

But in some time, most probably 3-6 months, I should be able to pay Seti a small amount of coins every month. How many coins, and what their value would be, I have no idea right now.
That will be up to factors such as how fast the dificulty rises, how much a Gridcoin is worth and probably other factors.

My computer setup, could at some time prove to small / slow to keep up with difficulty, and then my staking interval would get longer (and longer, and longer).
I'm not going to update like crazy to keep up with this, I'll upgrade when I feel it necessary, and that is still mostly driven by the computer games that I play on the system.

But with a little patience and some effort, I'll be able to support Seti a little bit in this way :)

And even though there has been some work and a lot of learning, I have found it fun and sometimes very interesting to get this thing going.
3) Message boards : Number crunching : PC Build for my Dad (Message 1913154)
Posted 15 Jan 2018 by Profile Karsten Vinding
I dont have any qualms either.

I dont have exactly the same settings as you, but am running at the next highest setting for the core, and standard for the SOC.

And my core voltage is now at 1,25V, so there's room for more there. Going beyond 3.8Ghz, starts to demand much more voltage...

Perhaps I'll try to up the SOC a little (its at 1.1V). Although I'm running the mem in spec, it is a overclocked setting when you look at the system data.

My system is in a room where I do lots of other stuff, and is also my main computer for doing "real" work, so I want it to be quiet.
4) Message boards : Number crunching : PC Build for my Dad (Message 1913143)
Posted 15 Jan 2018 by Profile Karsten Vinding
Your comment about black-screen crashes are very much in line with what I've read elsewhere.
Just wanted to mention the C-state thing, in case that could help. Cant hurt for him to try, just don't get the hopes up too much.

My system was, speaking of it, crashed with the black screen this morning....

So stabilizing the GFX gard seems to have brought back the other bug. Or rather it was probably allways there, the GFX card just crashed first :)

I have upped the core voltage for the 1700 with 0.05 Volts, time will tell if thats enough. I'm not worried about temperatures, theres plenty of headroom in the cooling setup.
I would like to keep the computer somewhat queit, which is off course made harder by me wanting to overclock everything :)
5) Message boards : Number crunching : PC Build for my Dad (Message 1913055)
Posted 14 Jan 2018 by Profile Karsten Vinding
I don't know if I can be of any help, but I have had some stability problems on my own Ryzen system, that I now seem to have resolved (fingers crossed).

I run a Ryzen 1700 on a ASUS tuf b350m-plus gaming with 16Gb DDR3200 ram (G.Skill F4-3200C14-8GFX). The mem is guaranteed for 3200 with Ryzen, and has been completely unproblematic. My graphics card is a RX480 (and a HD7770).

Today I run the Ryzen at 3800Mhz, on a watercooled loop where it sits at 60 - 66 degrees C. I could probably push it more, but it really starts to want a lot of core voltage, and I dont want to push the motherboard too hard.
But the problems below all happened running at stock too, with much lower temps.

I sort of had 3 different things happen.

At first I had a black screen freeze, where the system turned of the monitor, and the system was unresponsive to my input. I could see some HDD activity though. This would happen completely random. Sometimes the system ran a few hours, other times more than a day.
Following some thread in a forum, I found a guy that said turning of all C-states for the CPU in BIOS, had solved the crashes for him. It seemed to help for me too, but I cant be 100% certain, since I installed a new BIOS a few days later, that could be the fix too. But I havent seen these crashes since turning of C-states for my CPU.

After this I had some system resets. Working at the system, the system would suddenly reboot. No warning of any kind.
I went ahaed and turned up the load line calibration for the core voltage, and the system has not reset itself since then.

The last crash I had, was harder to fix. Working at the system, or sometimes being away from it, the screen would freeze, with a constant picture. I couldn't move the mouse, the system was completely unresponsive. Reset / power toggle was the only way to restart.
This one really bugged me. But while working with my graphics card I noticed, that the core voltage to the GPU was lower than what the driver requested (I used HWiNFO64 to see these things). Consistently about 0.03V lower actually.
That doesnt seem like much.
But I could see 1.144V being requested (with voltage control in the driver at automatic), and the measured voltage was 1.110V. I changed the setting to manual voltage. That specified a 1.163 GPU core voltage instead, and now the core voltage is measured at 1.138. This has completely removed the crashes.

I cant claim 100% stability yet, since I made the last changes friday evening, but the system hasn't crashed since then.
6) Message boards : Number crunching : My main system is down! (Message 1912232)
Posted 10 Jan 2018 by Profile Karsten Vinding
Anything is relative as they say, but my case does have a few years on it.

Its the original Antec P180, which is still a nice case. A case that was originally build with low noise in mind.

And in that regard its still a good case.

But its correct that the 5 1/4" bays are going away, together with the CD / DVD / Blueray (And before that the 5 1/4" floppy and HDD) drives. Just evolution doing its job.

I have considered replacing it, since many new features are lacking (USB3.x for instance), but I think I'll keep it around for a few years to come :)
7) Message boards : Number crunching : My main system is down! (Message 1912159)
Posted 10 Jan 2018 by Profile Karsten Vinding
Allthough this is originally RueiKe's thread, I will post a followup.

All the parts have arrived a few days ago, and I have been installing and testing a lot.

I had some dificulties along the way. I destroyed my old radiator, so I had to get a new one (I got a alphacool ST30 360, mainly because I could have it here in 1 day).

While I was at it, I decided to replace my old tubes, as they had a lot of miscolouring, and had lost some of their flexibility.

Its up and running now, and I can say that the Eisfach is doing the job nicely.

Even though the new radiator is less efficient than the old one (because its half as thick (the old one was 60mm)), the clearly increased flow from the new pump, has made my temps stay more or less the same.

For now I can recommend it to anyone needing a reservoir that fits into dual 5 1/4" bays.

I have found it easy to work with, and there is a lot of flexibilty with all the extra ports, so you can set it up in many different ways.
8) Message boards : Number crunching : My main system is down! (Message 1910193)
Posted 2 Jan 2018 by Profile Karsten Vinding
Since the retailer couldn't promise me a delivery date for the EK reservoir / pump I have cancelled the order, and have gone and ordered an Alphacool Eisfach with a single Laing DDC pump.

Basically the same pump as in the EK reservoir, but with the cooling ribs included, and in a bigger reservoir. They could ship immediatly, and this setup is 25% cheaper.

So I'm looking forward to getting this and installing it.
9) Message boards : Number crunching : My main system is down! (Message 1910044)
Posted 1 Jan 2018 by Profile Karsten Vinding
I was actually looking at the Alphacool Eisfach, that uses that exact pump.

It does seem solid enough.

Maybe for the next build :)
10) Message boards : Number crunching : My main system is down! (Message 1910027)
Posted 1 Jan 2018 by Profile Karsten Vinding
I have actually added a cooling kit for the pump to my order, in order to try to increase its longlivety.
11) Message boards : Number crunching : My main system is down! (Message 1910015)
Posted 1 Jan 2018 by Profile Karsten Vinding
I actually ordered the new reservoir/pump at a local retailer, and havent received any info on the expected delivery date yet.

I wont call myself an EK fan as such, but the stuff I use from them is very well made, and has run fine. I have had no complaints.
Their TR waterblock is sadly a little lacking compared to others (, but off course only when you really push the system.

I just checked my mails, and the XSPC pump/reservoir that broke down, was ordered just under 4 years ago (46 months). I don't think I can actually complain about that as it was not an expensive kit, but breakdowns are irritating nonetheless.

With the new EK pumps MTBF, I expect a longer lifespan. Its also a much more expensive kit.
12) Message boards : Number crunching : SIGSEGV: segmentation violation (Message 1909940)
Posted 1 Jan 2018 by Profile Karsten Vinding
I have been trying to run seti on my NAS computer that runs based on Centos/Fedora.

I am able to run e.g. World Community grid and Rosetta, but with Seti, after some time, the crunching starts to fail.

In the results for the WU's I get this:

terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
SIGABRT: abort called
Stack trace (12 frames)

Is this the same problem as described in this thread?
13) Message boards : Number crunching : Happy New Year! (Message 1909936)
Posted 1 Jan 2018 by Profile Karsten Vinding
Happy new year :)
14) Message boards : Number crunching : My main system is down! (Message 1909817)
Posted 31 Dec 2017 by Profile Karsten Vinding
Nice to hear that your system is back in working order.

I guess your kind of setup really separates the lambs from the goats :)

I am strugling with my setup too.
Off course things break during the holidays, so I'll have to wait even longer for replacements.

Good thing I had a few alternative parts lying around, so that it is at least working, even though not at fast as a few days ago :)
15) Message boards : Number crunching : PC Build for my Dad (Message 1909642)
Posted 30 Dec 2017 by Profile Karsten Vinding
Astropulse V7, choose AVX.

Multibeam V8, choose AVX (it's the best for Ryzen / Threadripper).

ATI, skip it (click on Next), you have NVidia GPU's.

Astropluse v7 (NVidia), enable.

Multibeam V8 (NV Cuda), enable and choose the option with SoG_r3557 in the end (the last one).

The last page with Intel iGPU's skip it (click on Next), they are not relevant for your AMD CPU.

Next window click on Install.

That should do it.
16) Message boards : Number crunching : Anything relating to AstroPulse tasks (Message 1909639)
Posted 30 Dec 2017 by Profile Karsten Vinding
Since there doesn't seem to be any fixes on the way for the invalid crunching of AP on AMD RXxx0 (RX400 and 500 series (possibly also Vega?)) GPU's, I have added the following to the <options> section of my cc_config.xml:


This will exclude my RX480 (device 1) from running AstroPulse WU's, but still let them run on my HD7770 (which is device 0).

I would recommend anyone with RXxx0 cards that they do the same until this problem is resolved. Just be certain that you exclude the correct GPU.

Otherwise we risk that invalid WU's get validated, if they happen to be paired with another RXxx0 card.
17) Message boards : Number crunching : Gridcoin...? (Message 1907538)
Posted 16 Dec 2017 by Profile Karsten Vinding
Well, then you're welcome :)

I sent them 1 GRC yesterday, just to see how it works. Its all very new to me :)

Now I'm just twidling my thumbs, waiting for coins to start rolling in from the pool (it takes time to build up your magnitude).
18) Message boards : Number crunching : Gridcoin...? (Message 1907518)
Posted 16 Dec 2017 by Profile Karsten Vinding
Its of course irritating that you cant get it to work, and I hope you find a fix.
Its my impression that AMD support on the Linux platform has been much improved (extremely much), much of it because the drivers are now open source (AFAIK), so I think theres a good chance for it to get solved.

I find it frustrating that the works gets done, time is spent, and then the results are invalid. I really hope this gets fixed one day.
19) Message boards : Number crunching : Gridcoin...? (Message 1907509)
Posted 16 Dec 2017 by Profile Karsten Vinding
Sorry, I was not clear.

They dont error out, they just dont validate. Some of them does, but most of them don't.

It is especially bad when two GPU's of the RXxx0 type validate against each other. The WU's validate, but the data is actually invalid.
20) Message boards : Number crunching : Gridcoin...? (Message 1907464)
Posted 16 Dec 2017 by Profile Karsten Vinding
But as you have two RX 480's, and assuming you aren't just running seti, you should be fine.

What appears as two RX480's is actually 1 RX480 and 1 HD7770. Boinc simply displays the best GPU, instead of showing them individually.

I'm running a mix of different projects, and will be fine tuning to get the best payout as I go along, so to get to the point where I can go solo as fast as possible.
I would like to run Seti at about 50% of the time, but we'll see how that pays off.

Regarding MB's on GPU, it has been available from a time long before AP. So you should be able to find it.
And AP's errors out on RXxx0's under windows too (they run fine on the HD7770). There is a bug in the code somewhere (either the driver or the app). For a short time I had Raistmer looking into it, but he seems to be busy with other things.

Next 20

©2018 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.