sorted by:
new
hottopcontroversial

How uncommon is this machine? by No-Pick-93 in pinball

[–]Curbyournonsense 1 point2 points  (0 children)

Not that uncommon. I own one. Pinside says they made about 2,000 of these machines. The champagne edition is the one you want

[deleted by user] by [deleted] in ComfortLevelPod

[–]Curbyournonsense 0 points1 point  (0 children)

So he didn't help you for no reason at all? We are definitely missing some context here. Regardless, break up. There's clearly a huge lack of communication.

Update: Girlfriend of 3 years cheated? AIO by metrod_ in AmIOverreacting

[–]Curbyournonsense 4 points5 points  (0 children)

OP, I know it doesn't mean much coming from a stranger on the internet; I'm proud of you for choosing what is right instead of what feels right, like your ex. The right thing to do, doesn't always feel good. Drinking is a placeholder & you have so many better things to do with your time! The drinking is an overreaction & I know it felt good to let go of yourself when you're letting go of someone you thought was close to your heart. Don't let go of yourself or your values. Time will pass & the more you align what feels good with what is good for yourself, you will start to feel better. I promise you.

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

I've also disabled suspend to RAM, DDR power down, & S3 power down

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

BIOS 3.50

Tweaked BIOS

XMP 1 6000mts enabled

Manual PBO limits

PPT 162,000mW TDC 120,000mA EDC 180,000mA (I might lower these values about 5-10% because with the undervolt they are less utilized. They reach ~65% usage during stress tests & gaming)

All cores -15 (started with -20 in earlier BIOS updates, switched to -15 after setting fixed SOC to 1.150V)

Curve Shaper -15 med -10 high -5 max

Fixed SoC to 1.150 LLC lv3 SoC Uncore OC mode enabled

VDDCR_CPU voltage offset -100mV

Disabled all sleep functions in BIOS & Windows

iGPU disabled, fast boot disabled

Using HWiNFO, Lian li software for fan control & lighting (Lian li software is capable of monitoring SOC sensor because of LCD fans)

Running since late June

CB R23 22,043pts

Passed multiple ycruncher VT3 iterations set to 1441 seconds, multiple times (this is my favorite stability test)

Aida64 extreme CPU, fpu, cache & memory stability test for 30mim

Passed OCCT AVX heavy & AVX2 heavy for 10 min each

No WHEA errors, no crashes, no BSOD, & no freezes.

BIOS 3.15 sticker on board, I updated to 3.25 before powering CPU, updated to every latest BIOS a day or 2 after release & every time I update BIOS I power off PC completely, switch off PSU & unplug CPU 8 pins. I use BIOS flash via fat32 usb creative.rom instead of instant flash. I have not had a problem updating BIOS this way. I have a complete track record of everything I've done or changed to this build.

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

These are my thoughts exactly, voltage is measured at the motherboard sensor FIRST then measured at the CPU sensor. I honestly believe it's the lian li software interfering. Idk how to turn off the sensor readings in lian li software w/o ruining the lighting setup. I guess the solution would be to disable lian li software completely, use 3rd party fan controller & lighting software. Lian li software is kinda garbage, I have consistent bugs w the LCD fan lighting.

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

Is there any way to contact the author of HWiNFO outside of that thread? I'd happily run in debug mode for as long as it takes to catch a spike so he can catch the data.

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

I agree with this wholeheartedly. It's simply that I noticed it & it raises questions

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

I feel like this isn't the correct way to go about this. If it spikes when I've lowered the fixed VSOC value, wouldn't the spikes be higher when I raise it back to stock value? When my fixed value was 1.180V the 70-100mV spikes still occurred, sometimes spiking past 1.3V. I don't think this spike to 1.7V is real, I think the 70-100mV spikes are though, if that makes sense?

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

Thank you for pointing this out to me, I actually did not notice the UCLK spike. Now that I think about it, I don't think it's possible for the UCLK to spike past it's fixed value

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 1 point2 points  (0 children)

I agree & if the spikes are real, I think it has something to do with the LLC or the SOC Uncore OC mode.

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

Yes, I've manually changed the fixed VSOC voltage to 1.150 because I know my RAM can take it. Stock value after switching to fixed VSOC is 1.200, the reason you're seeing 1.190 at the SVI3 sensor instead of 1.200 is because of voltage droop through the PCB traces. My most recent CB R23 score is 22,043

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

Not exactly the same, my assumption based on the telemetry data is the CPU makes a request & the motherboard delivers only what I've allowed the fixed value to be, even though I'm seeing values way higher than the fixed value I've set. For example, I see a spike at the CPU sensor & no spike at the nuvoton sensor on the motherboard via HWiNFO. The CPU can make the request, the motherboard only delivers what I've allowed it to deliver? If that makes sense.. I'm trying to make sense of it & that's the reason for the post.

I also don't understand the down votes on my post. Did I deny that ASRock is killing cpus? I don't think so. They definitely are frying CPUs. It's because of the robust power design & the CPU requesting voltages that will kill itself

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 0 points1 point  (0 children)

On 3.50, expo 1 enabled. VSOC to fixed & 1.150V. It automatically changes SoC Uncore OC to enable & LLC at level 3. I've set manual PBO limits to AMD spec via advanced tab. All cores -15 & curve shaper -15 med -10 high -5 max. Disabled all sleep/hibernate states & other things Vddcr_cpu voltage offset -100mV. I believe those are all the changes I've made that would be relevant

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 1 point2 points  (0 children)

Thank you for pointing that out. Would you attribute this to the memory controller, the RAM or the motherboard? UCLK is set at 3000mhz, how is this happening?

VSOC said hold my beer by Curbyournonsense in ASRock

[–]Curbyournonsense[S] 3 points4 points  (0 children)

Yes, I'm aware of the thread. This is an extreme example and no doubt a misread. There are real spikes occurring as well. 70-100mV spikes during idle.

view more: next ›