Soldato
- Joined
- 19 Oct 2010
- Posts
- 2,905
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Just in case you're not getting it, the 3000 series had pretty bad transient spikes. The 4000 series did not. So it could still be your PSU.I had a look and its doesnt specify other than saying a crash and hard power off report
the card was crashing every time I fired up stalker 2, but Ive had 3 cards after the 3090 and they worked perfectly, zero black screens, the 4090 I used every day for around 10 days and it didnt crash or lock up my PC
ive got a Asus ROG Thor 1200Watt Platinum PSU, its new and Ive connected to the 4090 and 5080, zero crashes zero black screens, it cant be my PSU otherwise I would have had black screens with the 4090 and 5080 right?It's the year 3074 and the OP still hasn't answered what PSU they are using![]()
Gigabyte are saying they ran Timespy Extreme for hours with zero issues, 2560x1440 yet I discovered you can use the internet, browsing and Utube example with zero issues but as soon as you start a game Stalker 2 @ 4k full settings it black screens on me, did the same thing on a work PC, Lenovo P620 which had a 1000watt PSU and an already installed RTXA6000Can the OP run Timespy extreme for hours. If not, PSU.
No.If it was the PSU then surley the 4090 and 5080 would have black screened right?
ive got a Asus ROG Thor 1200Watt Platinum PSU, its new and Ive connected to the 4090 and 5080, zero crashes zero black screens, it cant be my PSU otherwise I would have had black screens with the 4090 and 5080 right?
really?No.
The 3090 has sudden, brief, massive power spikes that can trigger the over current protection of a PSU.
This is the PSU working as intended. It would look like what you are describing.
It's a quirk that is specific to the 3090.
Is it just crashing in the one specific game?really?
if this over current trigger is not considered abnormal? as in if it keeps on crashing a PC and a physical restart is needed to get it back up how will people use this GPU? I had a 3090ti for about 16 months and it didnt display this issue, also the gigabyte 3090 didnt display this issue after like 2 years of owning the card but this appeared suddenly in the past few weeks?
werll this psu was bought back in the day of when the 30 series was released, its a few years old but a solid psu, im really not sureArghhhh! How many times!
We’re trying to help but you still haven’t answered the main question: is it an ATX 3.0 or 3.1 PSU?
Not all ROG Thor 1200w are 3.0.
For example, the ROG Thor 1200P is an older spec (ATX12V).
no crashes on all i tried stalker and warhammerIs it just crashing in the one specific game?
werll this psu was bought back in the day of when the 30 series was released, its a few years old but a solid psu, im really not sure
ASUS | ROG THOR 1200W [non-II] [1][8][11]
[1] Units experiencing tripping issues with high transient power draw GPUs like AMD Vega, 6900 XT and Nvidia RTX3080/3090. Generally fixed in newer batches.
[8] Seasonic PRIME based units experience shutdowns with RTX3080/3090 (and possibly RX6900 XT) GPUs. The cause is not the OCP tripping but a PSU design flaw as evident by the PSU not latching off on shutdown and 1000W+ models being affected too. Doesn’t manifest in 100% cases as it’s also dependent on motherboard model and GPU OC. Seasonic provides a replacement 24-pin ATX cable to fix this via support. Appears to be fixed post 2021 although there’s no official confirmation from Seasonic.
[11] Ball bearing fan, possibly not silent even at very low RPMs.
ASUS | ROG Strix AURA [14] – ROG THOR II Platinum / Titanium
[14] Potential ATX 3.0 units either not tested for compatibility (no Aris review), not received the certification (no entry in Intel’s DB), having problems with passing ATX 3.0 tests (failed Aris review), or without proper reviews in the first place to put them in the normal priority subtier.
You really need to find the answer to this question as the most obvious answer to what is happening for you is (I) that you don’t have an ATX 3.0 PSU and (II) something has now changed in your system that is causing your non-3.0 PSU to have problems.
There should be some indication on the label of a model number. Or you can check your email receipts.
Just to be super clear: I bought a PSU at the time of the 30 series. It was a ROG Thor (850w). Plenty of wattage. I kept getting black screens. So did everyone else. Nobody understood what was happening. It was super annoying.
Then eventually a new power supply standard was released to deal with the problem of ‘high power spikes’: ATX 3.0. These can handle double the wattage for a short period.
I got a new ATX 3.0 PSU. No more black screens. Done.
If it’s the case that only recently you’re getting the black screens, it could be the case that something has changed (more demanding games, drivers, windows 24h2, whatever) that is changing the overall power usage and you have crept up over the 1,200w limit of your PSU for just microseconds.
Or, another possibility is that your 3090 is struggling with new drivers - as a lot of people are having issues with the latest ones issues by Nvidia. You could try a fresh install of an older Nvidia driver and if everything is fine you have at least ruled out it being a GPU hardware defect (but the issue would remain as whether it’s (I) the new driver itself that’s the problem or (II) the new driver is causing higher wattage which is causing a problem with your non-ATX3.0 PSU).
That's hard to say, because it depends on the benchmark (some are more demanding than others), but I wouldn't consider Timespy sufficient to identify a fault, no.Also when a GPU is RMA'd do you think it should be tested via playing games or running timespy and ingame benchmarks? below is the 3090 tested by Gigabyte, they said the benches and timespy failed to identify a fault, isn't playing games different to running a benchmark?