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 1935221)
Posted 11 May 2018 by Profile Karsten Vinding
Post:
Well, then it seems that I, almost by chance, have found a good tool for the job.

It does work well, its nice to have a tool that this reliably finds errors relatively fast.

It does make experimenting and troubleshooting much easier.
2) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1935064)
Posted 11 May 2018 by Profile Karsten Vinding
Post:
I have been experimenting a little with Ryzen DRAM Calculator, and its so called "safe" settings.

I made settings for 3533, 3400, and 3200, all with the safe calculations.

3533 didn't boot. And I honestly didn't expect it to.

3400 did boot, but windows crashed loading the desktop.

Tried 3333 with the 3400 settings, and it booted and started correctly. Running RAM tester gave me an error within 1 minute.

3200 with safe settings, booted fine, but RAM tester threw an error after about 30 seconds.

3200 with bios defaults, but with 48 ohm ProcODT, runs fine. Default settings are a lot more relaxed, as far as I can see.

So, I guess I'll stick to 3200 at (almost) default for now, which was really also what I was hoping for.

My only problem with this is that the system should be able to run at the safe settings (at least at 3200), as they make sure that the specs of the actual ram is maintained. So the bios / agesa is not doing what it should.
3) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1935026)
Posted 11 May 2018 by Profile Karsten Vinding
Post:
I was reading some articles about finding a good memtester that would run in Windows.

Finding that memtest64, wouldnt find errors, even with settings that eventually crashed, I tried to read up on it.

I found a guy promoting "RAM test" (by Karhu software). A program that it seems is basically made for testing RAM on Ryzen CPU's (will work on others too)
The downside was, it costs 10$ (9.99). After some time thinking about it, I decided to try it, and bought a license. Its not that much money anyway.

And it has proven to be a good decision. I can run the program at 3200 for an hour (and more) without errors, but at 3266 I get an error from the program within 20 seconds (at a setting where the system could run 12+ hours yesterday).
You can set the program to stop on errors or keep running. And you can set it to beep on eroors.

It has helped me very much in finding reliable settings. I found that setting back GDM to auto did nothing, the system is still stable (perhaps its on pr. default at 3200), but the ProcODT has to be set at 48 ohm on my system, higher than that I get memory errors.

I like the simplicity of it, and I like how fast it detects errors, at least on my system, when I push things too much.
4) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1934818)
Posted 10 May 2018 by Profile Karsten Vinding
Post:
Thanks for your comments.

I will see if Gear Down Mode (GDM) could perhaps make my RAM stable at higher speed, but I'll have to measure real world performance to see whats fastest (3200 vs. eg 3400 w. GDM).

48 Ohms have helped me in the past, so that'll have to be tried out as well, allthough that would purely be for reliability.

The system crashed at 3266 after many hours, so now I'm trying 3200, still with standard settings for now.
5) Message boards : Number crunching : Welcome to the 19 Year Club! (Message 1934700)
Posted 9 May 2018 by Profile Karsten Vinding
Post:
I will be joining the club in 9 days :)

In fact it would have been before that. I created a Seti account in April 99, but somehow registered with a nonexistant mail adress.

And back then I couldn't find a way to change it (I don't hink it was possible). So I created a new account, which I'm using to this date.

Next year will be an aniversary. I wonder if the peoble behind the project will do something to celebrate it?
6) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1934690)
Posted 9 May 2018 by Profile Karsten Vinding
Post:
Yes, there are many many variables, and I just don't understand the technology well enough to do educated adjustments.

I'll take the standard timings, and push the frequency as high as it will go, and leave it at that (for now).

3333 crashed after about 45 minutes.

But 3266 does seem more stable. Its at about 1h45 mins now, so improved, but not definitively reliable yet.

Time will tell. But 4011 is definately an improvement on my system. With 4009 I never reached 10 minutes without crashes at 3200.
7) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1934670)
Posted 9 May 2018 by Profile Karsten Vinding
Post:
The system was not stable at 3400.

Had a blue screen after some time. Was also almost too good to be true :)

Now I'm at 3333, lets see how that works.

The fact that its able to boot at these settings is something new to my setup :)
8) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1934622)
Posted 9 May 2018 by Profile Karsten Vinding
Post:
Just an update.

Yesterday I updated to the newly released 4011 bios for my board.

There have been varying reports of succes, but on my system, with my G-Skill FlareX, that are rated to 3200Mhz, I seem to have gained complete stability at 3200Mhz. At least it ran for nearly 24h without crashing.

Now I have even been able to boot and run at 3400Mhz, which I decided to try due to reports from another user with the same RAM. I have never been able to even boot at that speed before.

Even at 3400, the system seems stable.

I'll have to run it for some days before I can say for sure if its reliable, but it does seem the 4011 bios is an improvement over 4009.
9) Message boards : Number crunching : Back into the party! (Message 1933651)
Posted 4 May 2018 by Profile Karsten Vinding
Post:
I used to run it passively cooled with a heatsink on the CPU.

Today I have a 120mm fan at low rpm pushing air across the heatsink.

One of my Pi's (3B+) is in a closed case used as a media player for my TV. That one is passively cooled with a heatsink, and only runs two Wu's at one time.
10) Message boards : Number crunching : Back into the party! (Message 1933495)
Posted 4 May 2018 by Profile Karsten Vinding
Post:
My Pi 3B does the seti WU's in 10-16 hours or so.

At least the ones that I can see right now have been in that time frame.

Not a speed demon, but its a cheap low power device.

I only run 3 WU's a time to keep temperatures down, it does get pretty hot.

Make sure you've got sufficient cooling.
11) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1930981)
Posted 20 Apr 2018 by Profile Karsten Vinding
Post:
Yess the Zen+ is doing nice up until 4Ghz (plus a litlle more), but clearly still hits a frequency wall at higher frequencies.

Voltage requirements for higher clocks then seem to go upwards quickly.

Still this CPU will probably do up towards 4GHz with all cores loaded, if the cooling is sufficient, when set to automatic.

I would also think about a good X370 board, they are probably going to be cheap now.
12) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1930939)
Posted 19 Apr 2018 by Profile Karsten Vinding
Post:
Well it seems our experiences match.

I am actually considering the 2700X, perhaps even a new build with it.

I agree that its a small evolution of the original Ryzens, but the Precision boost 2 technology does seem to work much better than Pb1.

Perhaps to a point where I would leave the CPU at stock, and leave clocks up to its internal management.

I don't have the money for the change right now, so It'll have to wait, and that wont be a problem. With some luck the prices will go down before I purchase, if I decide to do so.
13) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1930925)
Posted 19 Apr 2018 by Profile Karsten Vinding
Post:
Well, that test didn't last long.

I installed the BIOS, went into BIOS, and set the same settings as before, with the exception of letting the RAM run at its specified 3200MHz.

Booted windows and started using it. The computer crashed with a blue screen within 10 minutes....

I have rebooted now, with 3133MHz RAM, where it was stable on the 3805 Bios.

I hope it still is.....
14) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1930919)
Posted 19 Apr 2018 by Profile Karsten Vinding
Post:
Have you tried the latest 4009 BIOS'es, or read anything about them?

I'm downloading at the moment, will report if I see improvements.
15) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1927505)
Posted 31 Mar 2018 by Profile Karsten Vinding
Post:
My system has now been running 34hrs without a crash.

This with memory timings at DOCP3200 settings, but with mem clock reduced to 3133 Mhz.

This is very promising, and I can live with the small speed reduction on the RAM, if this proves to be reliable.
16) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1927251)
Posted 30 Mar 2018 by Profile Karsten Vinding
Post:
Well raising VCore didn't help, this time it black screened....

Its allways easy for me to spot, as fans go to max speed, and the computer gets rather noisy. And most of the time I cant simply reset it, I have to toggle the power switch on the PSU.

Something is obviously still not OK...
On 3803 I never saw a black screen on DDR 2400 speeds. I suspect I could end up there on 3805 too.

I must experiment with mem speed to see what I can reliably reach, but will also turn down my CPU OC, to rule out instability due to that.

This is frustrating, the system was very solid on 3401, so having to deal with these things now is SO irritating.
17) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1927144)
Posted 29 Mar 2018 by Profile Karsten Vinding
Post:
Damn, the system just bluescreened without any warning while I was typing on the keyboard.

The error was something about a system exception, so seemingly not a memory error.

I have turned the vcore to the CPU up a notch, perhaps that can bring the last bit of stability.
18) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1927104)
Posted 29 Mar 2018 by Profile Karsten Vinding
Post:
I cant say for sure yet, but the system has been running for ~ 12 hrs since I changed the resistance to 48 Ohms, I rebooted the system ~ 8 hrs ago to change the Vsoc, but otherwise it has been stable.

The change to VSOC reduced my core temps with ~ 3 degrees C. More than I expected...

I'm very hopefull that these changes could bring stability, but in reality my dream is for AMD to bring out a working AGESA that fixes these problems.

I suspect their focus right now is the upcoming 2x00 series, and of course fixing the security "holes" reported by the stock market speculating CTS-labs.
19) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1927035)
Posted 29 Mar 2018 by Profile Karsten Vinding
Post:
Thanks for that info :)

I have reduced Vsoc to 1.05. Anything that helps with stability, and probably reduces power usage, is good.

I just downloaded the latest DRAM calculator. It has been much improved since last time I tried using it. Allthough it still recommends 53,3 Ohm for my ram.
20) Message boards : Number crunching : (0xC0000005) STATUS_ACCESS_VIOLATION any idea what caused it?? Or what it exactly is describing?? Internet searches find nothing. (Message 1927014)
Posted 29 Mar 2018 by Profile Karsten Vinding
Post:
I understand your frustration.

Not being able to find the cause of instability is irritating.

My PC chose to reboot while I slept, I was awakened by the Windows logo/theme music...
So its not stable here with 3805 either. Though I did get a relatively long uptime.

I have tried setting 48 Ohm ProcODT now, will se if that helps.


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.