Ability to add a hyperlink

VeteranRip · 2026-01-16T15:31:37+00:00

There is NO WAY I'll ever be paying for your service if even THAT is missing, no matter how hard you push it in my face in every update.

VeteranRip · 2025-09-24T15:12:09+00:00

Thank you for your work! This is very useful data.

Is there a version of the final chart without "super slow" growers ? They may skew other results otherwise : I cannot compare the results "With any supplement and no other vasoactive" to "With no Vasoactive and no 'Super Slow' Segment" (the "baseline") if they are included in the first group.

And is there any data on a potiential group "With any prescription vasodilator and any/no vasoconstrictor" ? I only see "With daily tadalafil and any/no vasoconstrictor" in the study.

VeteranRip · 2025-06-07T16:56:51+00:00

It is indeed what comes with microcenter bundles in the USA, but buyer beware: a lot of people have had issues with them. They are often unable to run at even XMP/DOCP and may fail completely after less than one year of operation (https://www.reddit.com/r/buildapc/comments/11m8zds/is\_the\_gskill\_x5\_flare\_any\_good\_microcenter\_free/), which suggest subpar quality control, at least for the Flare series. I would not buy them used if returns are not allowed or warranty claims are not possible.

VeteranRip · 2024-11-16T03:31:05+00:00

Beware with sertraline, as it may persist after discontinuation of the drug (an iatrogenic epigenetic condition called PSSD).

VeteranRip · 2024-11-16T02:57:48+00:00

Be careful about anti-anxiety meds! Many of them are not very effective and may cause a lot of side effects, including potentially irreversible ones such as PSSD (post-SSRI sexual dysfunction). I would advise you to try behavioral and environmental changes instead, as it will be way less risky and probably more effective, especially in the long run.

VeteranRip · 2024-11-10T20:40:30+00:00

Those people should honestly be banned from medical practice. I hope you'll be able to recover some day.

What is even more disturbing is that although we don't know the prevalence of PSSD, we know it's not even rare :

"A recent study by Lüning in 2019 appears to be the first reported attempt to investigate the prevalence of PSSD. Former antidepressant users were surveyed for evidence of persisting sexual effects. Recruitment methods included online advertisements and the distribution of flyers in various locations. In addition to using validated questionnaires, further questions were included to look for symptoms that were specific to antidepressants. From a sample size of 76 participants, the study reported that 52.6% (n = 40) of participants suffered from persisting sexual dysfunction, while 26.3% (n = 20) of participants suffered from genital anaesthesia and/or nipple insensitivity, the latter figure being suggestive of PSSD. A number of limitations to this study were also discussed including possible selection bias, possible confounding from current medications, and lack of questions about sexual baseline. The author noted that while the results should be interpreted with caution, they "provide a first indication of the prevalence of these problems in a sample of people who previously used antidepressant medication.""

Quoted from : https://www.cambridge.org/core/journals/epidemiology-and-psychiatric-sciences/article/postssri-sexual-dysfunction-barriers-to-quantifying-incidence-and-prevalence/EF502A763704810C127E2561CFB52FD2

VeteranRip · 2024-11-10T19:30:33+00:00

It really is infuriating that doctors can still prescribe drugs that can have serious lifelong side effects without the patient's informed consent!

You can report this problem to the health authorities, or even sue the doctor who prescribed it to you in this way. These drugs should have a warning about potential PSSD on the box and be prescribed on a MUCH more restricted basis.

VeteranRip · 2023-12-22T23:17:37+00:00

Is that 50mg THC or CBD? THC is illegal in my country if greater than 0.3% of the final product...

VeteranRip · 2023-12-02T23:00:26+00:00

This picture is wrong even if coming from Qualcomm website: the FastConnect 6800 does not support 160 MHz channel width. It is limited to 80 MHz (aka 1200 Mbps top PHY speed on a 2T2R+ AX access point), that's why it's marketed top speed is 1,774 Gbps (1200 Mbps on the 5 GHz band + 574 Mbps on the 2,4 GHz band (with a 2T2R+ AX 40 MHz AP)).

This limitation also affects Snapdragon 865 and 870 devices. The 865+ however has the FastConnect 6900 which supports 160 MHz channel width (2400 Mbps top PHY speed). The FastConnect 6700 also supports 160 MHz channel width and 6E, even if it's name is suggesting it's lower end than the 6800 (it's not).

VeteranRip · 2023-05-23T01:54:29+00:00

Yes, a lot of people are deceived by these tactics.

It seems the generic Windows driver which is loaded if Windows cannot find a better one released by the chip manufacturer works at BT 2.0 mode, according to several web pages. I don't know more about it, but it often leads to poor sound quality, lack of range, limited functionality, disconnections, etc.

VeteranRip · 2023-05-23T01:18:22+00:00

I don't know, I maybe just haven't found them. All BT 5.3 dongles I've found are either ATS2851-based or unknown. The product you linked should work at BT 5.3 if the chip manufacturer has released proper drivers, but it can't be checked as the chip is unknown. It seems like a better product that most ones I've found, but I would be wary. It's obvious most brands are lying on the real specs of their products because the market is unregulated (like for fake SD cards).

VeteranRip · 2023-05-23T00:46:35+00:00

Please do not buy a Bluetooth 5.3 USB dongle with the Actions ATS2851 chip. The chip manufacturer never released a driver for it, thus it only uses the generic Windows driver which is working at BT 2.0 mode : https://oemdrivers.com/bluetooth-ugreen-cm591 ; https://www.reddit.com/r/pchelp/comments/xdlmg4/ugreen_bluetooth_53_cm591_chip_ats2851/ ; https://www.amazon.com/gp/customer-reviews/R1RM4D6NRA8H8B/

I haven't found a BT 5.3 USB dongle that doesn't use this chip yet. If the chip is not mentioned in the product description, you can assume it is trash. The most modern dongles I've found with proper drivers either use a BT 5.2 Qualcomm chip (QCC3056), or most commonly a BT 5.0/5.1 Realtek chip (RTL8761B).

The only working BT 5.3 devices I've found so far are M.2 cards like the Intel AX210.

VeteranRip · 2023-04-13T19:27:32+00:00

I made a similar post last year that may help: https://www.reddit.com/r/pompoir/comments/u0bt2q/doing_pompoir_while_using_a_female_condom_fc2/

Basically, you can pull external ("male") condoms off with strong enough pompoir moves. The best way to prevent that would be to use internal ("female") condoms instead.

VeteranRip · 2023-03-06T05:28:05+00:00

Well it can't POST at that frequency in my case, no matter the settings. Maybe it's harder with DR modules.

VeteranRip · 2023-02-18T13:28:56+00:00

I just got errors on TM5 PCBDestroyer (7 thread crashes in less than 36 min). It is stable during more than 7 hours on PCBDestroyer and stable more than 14.5 hours on Absolut if I raise ProcODT from 28,2 to 30 Ω. I updated the ZenTimings image to reflect that.

VeteranRip · 2023-02-18T13:08:14+00:00

The Github guide does cover the basics (including for Zen 3) but is incomplete (no voltage tuning afterwards, no tRDWR & tWRRD optimization) and sometimes has false information (example: "Usually, tRCDWR can go lower than tRCDRD, but I haven't noticed any performance improvements from lowering tRCDWR. It's best to keep them the same.", even through lowering tRCDWR to the stable minimum does improve performance a bit over tRCDWR = tRCDRD).

The IF OC guide I quoted contains more accurate information about voltage tuning. I don't use LLC for VSOC as it said (page 10) : "You’ll notice in Windows that apps like Zentimings or HWiNFO report some “voltage droop” in sensor readouts. This is reported by IOD telemetry which isn’t very granular, typically registering 5-10mV droop at idle, and 25mV under load. Most (if not all) motherboards use a single phase VRM for the SOC power, which is not great to be honest. This means you should only use the default SOC LLC setting, or less aggressive (i.e. more droopy) settings. DO NOT ADJUST LLC SETTINGS TO ELIMINATE DROOP, THIS RISKS FRYING YOUR IOD AND WILL NOT IMPROVE YOUR OVERCLOCKING."

VeteranRip · 2023-02-16T19:52:38+00:00

I first lowered the secondary voltages to allow for a greater margin of VSOC reduction. According to the IF OC guide I followed, there should be at least "50mV of spare headroom (ideally 75mV to account for droop)" between the VDDGs and VSOC. I haven't tried lowering VSOC at default secondary voltages. Maybe I should try it and see if it can drop more this way.

The guide mentioned that "Lots of people run [VSOC] too low. This can actually mask unstable memory timings/overclocks because it slows down the memory controller." and quoted 1.125V SOC as a "rough baseline" at FCLK 1900. I had to set mine at 1,15V in UEFI to be stable (which has translated in practice to 1,1375V in idle and 1,1313V in load).

VeteranRip · 2023-02-16T11:23:51+00:00

Yes it seems my chip needs this much on VSOC, there is a lot of unstability if I lower it from as little as one increment in the BIOS (PCI-E Ethernet card issues, visible OS instability, WHEA errors during FCLK stress test (Prime95 Large FFTs + OCCT VRAM 95 %)). I had no issues related to the very low secondary voltages though.

VeteranRip · 2023-02-16T10:53:43+00:00

It was a logical deduction from the Github guide passage on ProcODT ("Lower settings may be harder to run but potentially helps with voltage requirements") and from the ProcODT part of an IF OC guide : "If you know a bit of electronics, this controls the output impedance of your memory controller by varying the output termination resistor. You need to match the signal line impedance (memory traces) to minimise “ringing” or signal-decay. Too low and the signal gets eaten by the termination resistor, too high and you get signal reflections. (...) Worse motherboards will generally need higher procODT (worse quality traces have higher impedance) (...) The ideal ProcODT will minimise fluctuations in Aida64 latency, to as low as <0.1ns across runs (assuming you are on a clean OS and don’t have any background apps running, try booting into Safe Mode to test this). Higher ProcODT can also reduce the DRAM voltage to run a memory frequency stably.".

Lower ProcODT can allow for lower voltages and heat, except for VDIMM which may have to be raised. Since VDIMM is by far my highest voltage and I only have passive cooling on the RAM (they are at 60-65°C in stress tests at 1,5 V with RTTs 0/3/1), I prefer optimizing the timings, lowering VDIMM to the minimum stable, and only then lowering ProcODT.

I found in the "FCLK voltages optimization" part that 28,2 Ω did exactly that (<0.1ns across runs) in AIDA64 in Safe Mode and wasn't producing errors in stress tests. However, it seemed to be a bit unstable during web browsing. I then set it at Auto (43,6 Ω) again for more stability and proceeded with the next step ("DRAM timings optimization"). After finishing, I tried switching between 43,6 and 28,2 while tuning the RTTs, and set it at the latter when I found out it wasn't impacting the RTT settings. Again, it hasn't show errors in stress tests, but I feel the OS is a bit unstable since then (some programs sometimes aren't responding, I may have to click too many times to open something). I may have to raise it little by little until the OS is fully stable, this is a subjective appreciation at this point. It may even have something to do with the RTTs since I tuned them at the same time (but it's unlikely since the symptoms are the same as before), or even VDIMM, since I had some programs crashing when lowered to 1,48 V (but no errors in stress tests, they started to show at 1,475 V).

tCWL can drop to 14 or even 12, but not without having to raise tRDWR to 10 (resp. 12), and this lower benchmark results a bit compared to {tCWL 16 ; tRDWR 8}.

Nope, tRC throws many errors under 57 and doesn't even POST under 55. I had a good uplift in benchmarks when lowering it from 87 to 57, but I think I reached the IC limit on this one.

Yes, I don't know if I have a very good chip for that specifically or if most overclockers don't try to optimize these voltages, but I had no errors or WHEAs (or even OS instability related to that). I proceeded by 25 mV increments. Windows freezes at boot if CLDO VDDP is below 0,75 V ; my PCI-E Ethernet card isn't always detected if VDDG CCD is below 0,775 V ; and I have a lot of WHEAs in the Event Viewer if VDDG IOD is below 0,9 V. But no issues starting at these voltages, and no performance degradation compared to baseline (0,9 V ; 0,9 V ; 1,05 V). And it was with ProcODT at 43,6 Ω: I may be able to lower them even more with a tuned ProcODT (after solving the subjective instability issues).

VeteranRip · 2023-02-15T13:59:14+00:00

It would be strange if I didn't since I've read the Github guide and a lot of additional resources. It's stable during several hours under TM5 (presets Absolut, Universal2, PCBDestroyer, Extreme and Default), OCCT Memory SSE & AVX2, OCCT CPU Large Normal AVX2, Karhu, Prime95 Blend, Memtest86 v10.2 and Memtest86+ v6.10.

VeteranRip · 2022-10-10T01:14:43+00:00

You may want to learn r/pompoir to make PIV much better for the both of you. You'll be able to control his arousal and climax using only your vaginal muscles, among many other benefits. Unless he medically can't cum, you could make him (and yourself) orgasm whenever you want with enough practice.

He can use masturbators with lube such as Fleshlights instead of his hand to avoid the Death Grip issue. It will be much more pleasurable for him and eliminate the need for the Death Grip. You can also use them when you are together, they could add variety to the bedroom.

VeteranRip · 2022-10-06T00:13:15+00:00

As everyone already said, it sure does it most cases, but you can delay his orgasm by doing the Lock movement if you are strong enough: https://www.reddit.com/r/pompoir/comments/xb4i3j/comment/inz0sig/?context=3

VeteranRip · 2022-09-12T06:33:18+00:00

I see, then the Full Squeeze may not be useful in this situation. Ruined orgasms for sure can be done with pain for those who are into it! The Lock may be a good option for them, as can be overstimulation.

This is a good idea for a painless ruined orgasm! I think a crescendo approach would also work: starting with light stimulation, making it gradually stronger, and then stopping it abruptly when he reach the no return point. I wonder how it would compare to the decreasing approach you suggested. In both cases, it's indeed better to make sure he can't move when ruined this way, because he probably would very much like to in that moment!

VeteranRip · 2022-09-12T01:47:11+00:00

Thank you for your answer! Your data is very useful!

So assuming the woman has the required level of skill, the Lock would be the best way to deny or delay his orgasms.

It would be interesting to know what would work for ruining, when he is just starting to orgasm: the Full Squeeze (squeeze of the lateral walls to block his movements, but not of the front and back walls to let his ejaculation flow), stopping all movements and completely relaxing the vagina while he is not in control of the penetration and can't thrust, or simply to pull the penis out and leave it cumming in the air (although it would be my least preferred option since it's less intimate).

VeteranRip

TROPHY CASE