• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Cinebench crashed my PC. My Wi-Fi stopped working, and I keep getting a "Please wait" screen when I boot up my PC.

Joined
Oct 26, 2016
Messages
1,744 (0.63/day)
Location
BGD
System Name Minotaur
Processor Intel I9 7940X
Motherboard Asus Strix Rog Gaming E X299
Cooling Xigmatek LOKI SD963 double-Fan
Memory 64Gb DDR4 2800Mhz
Video Card(s) 1)RX 6900XT BIOSTAR 16Gb***2)MATROX M9120LP
Storage 2 x ssd-Kingston 240Gb A400 in RAID 0+ HDD 500Gb +Samsung 128gbSSD +SSD Kinston 480Gb
Display(s) BenQ 28"EL2870U(4K-HDR) / Acer 24"(1080P) / Eizo 2336W(1080p) / 2x Eizo 19"(1280x1024)
Case Lian Li
Audio Device(s) Realtek/Creative T20 Speakers
Power Supply F S P Hyper S 700W
Mouse Asus TUF-GAMING M3
Keyboard Func FUNC-KB-460/Mechanical Keyboard
VR HMD Oculus Rift DK2
Software Win 11
Benchmark Scores Fire Strike=23905,Cinebench R15=3167,Cinebench R20=7490.Passmark=30689,Geekbench4=32885
I wasn’t watching the temps at the exact time the crash happened, but my temperatures seemed fairly reasonable about 30 seconds before that during my test. They were all 80-90 degrees C. I’m honestly not sure how much voltage was applied since I just used the default PBO settings; it’s probably bad that I don’t know that lol. I do know it makes the frequency go from 3.8 to 5.1 GHz though. Thanks!
Well if you doing OC you MUST pay attention on this 2 things and they going hand in hand more Voltage higher the temps.....OC on default PBO is most likely to much of the Voltage....if you doing OC my advice is always go step by step and with the lowest possible Voltage / undervolted your CPU first in that case even when you have instability/BSOD it will be almost impossible to damage your hardware.......
 
Joined
Mar 5, 2023
Messages
140 (0.32/day)
Well if you doing OC you MUST pay attention on this 2 things and they going hand in hand more Voltage higher the temps.....OC on default PBO is most likely to much of the Voltage....if you doing OC my advice is always go step by step and with the lowest possible Voltage / undervolted your CPU first in that case even when you have instability/BSOD it will be almost impossible to damage your hardware.......
That makes sense. I’ll be more careful when I OC then and pay attention to the voltage and all. I'll modify it myself and lower the voltage more and I'll be more careful than before for sure. Thanks!
 
Joined
Sep 27, 2019
Messages
1,208 (0.72/day)
Location
Canada
System Name New compy
Processor AMD Ryzen 5800x3D
Motherboard MSI MPG x570S EDGE MAX WiFi
Cooling Noctua NH-D15S w. FHP141 + Xigmatek AOS XAF-F1451
Memory 32gb G.Skill Ripjaws V Samsung B-Die Dual Rank F4-4000C16D-32GVKA
Video Card(s) ASUS TUF GAMING RTX 4070ti
Storage 17tb (8+4tb WD Black HDD's, 2+2+0.5+0.5tb M.2 SSD Drives) + 16tb WD Red Pro backup drive
Display(s) Alienware AW2518H 24" 240hz, Sony X85K 43" 4k 120hz HDR TV
Case Thermaltake Core v71
Audio Device(s) iFi Nano Idsd Le, Creative T20 + T50, Sennheiser HD6Mix
Power Supply EVGA Supernova G2 1000w
Mouse Logitech G502 Hero custom w. G900 scroll wheel mod, Rival 3 + Rival 3 wireless, JLab Epic Mouse
Keyboard Corsair K68 RGB + K70 RGB + K57 RGB Wireless + Logitech G613
Software Win 10 Pro
Benchmark Scores https://valid.x86.fr/s2y7ny
Blaming software for a failed overclock is just silly.
Once upon a time in 2021 Amazons game killed a bunch of 3090's, blaming software for killing gpu's isn't far fetched or even laughable. Years ago it was Furmark destroying gpu's.

 
Last edited:
Joined
Jun 26, 2022
Messages
216 (0.32/day)
Processor 7950X, PBO CO -15
Motherboard Gigabyte X670 AORUS Elite AX (rev. 1.0)
Cooling EVGA CLC 360 w/Arctic P12 PWM PST A-RGB fans
Memory 64GB G.Skill Trident Z5 RGB F5-6000J3040G32GA2-TZ5RK
Video Card(s) ASUS TUF Gaming GeForce RTX 3070
Storage 970 EVO Plus 2TB x2, 970 EVO 1TB; SATA: 850 EVO 500GB (HDD cache), HDDs: 6TB Seagate, 1TB Samsung
Display(s) ASUS 32" 165Hz IPS (VG32AQL1A), ASUS 27" 144Hz TN (MG278Q)
Case Corsair 4000D Airflow
Audio Device(s) Razer BlackShark V2 Pro
Power Supply Corsair RM1000x
Mouse Logitech M720
Keyboard G.Skill KM780R MX
Software Win10 Pro, PrimoCache, VMware Workstation Pro 16
Once upon a time in 2021 Amazons game killed a bunch of 3090's, blaming software for killing gpu's isn't far fetched or even laughable. Years ago it was Furmark destroying gpu's.

Those are examples of the GPU trying to do more work than the components the mfg selected to build it from would allow combined with the clock/voltage settings they allowed.

Imagine an extremely simplified pipeline:
1) Software: Hey DirectX API, draw this.
2) DX12 API: Hey GPU draw this.
3) GPU: Thank sir, may I have another?
4) start over

Why would the game/app be at fault instead of DirectX or OpenGL or whatever API is sitting between the app and the GPU?
Why would the API be at fault instead of the GPU drivers?
Why would the GPU drivers be at fault instead of the GPU components selected by the mfg, or the clock/voltage settings the mfg allowed?

If the software didn't bypass the GPU drivers or clock/voltage settings and was simply telling the GPU to draw things as fast as possible via typical methods, the software isn't responsible for killing the GPU.
 

ir_cow

Staff member
Joined
Sep 4, 2008
Messages
3,861 (0.67/day)
Location
USA
Once upon a time in 2021 Amazons game killed a bunch of 3090's, blaming software for killing gpu's isn't far fetched or even laughable. Years ago it was Furmark destroying gpu's.

No the game didn't kill the GPU, a faulty design that deviated from Nvidia Reference is the cause.

When it came to Furmark and the Femi, the card was simply not designed for a power virus app and instead actual workloads. Not sure if this is still present in the current GPU drivers, but Furmark exe was flagged and a power limit was put in place to prevent killing GPUs. Workaround was to change the exe name.

In both cases it was a fault in the design that is the problem, not the software.
 
Joined
Nov 4, 2005
Messages
11,725 (1.73/day)
System Name Compy 386
Processor 7800X3D
Motherboard Asus
Cooling Air for now.....
Memory 64 GB DDR5 6400Mhz
Video Card(s) 7900XTX 310 Merc
Storage Samsung 990 2TB, 2 SP 2TB SSDs, 24TB Enterprise drives
Display(s) 55" Samsung 4K HDR
Audio Device(s) ATI HDMI
Mouse Logitech MX518
Keyboard Razer
Software A lot.
Benchmark Scores Its fast. Enough.
Once upon a time in 2021 Amazons game killed a bunch of 3090's, blaming software for killing gpu's isn't far fetched or even laughable. Years ago it was Furmark destroying gpu's.

That sounds like hardware malfunctioning to me. I have only had software damage one card, and it was in pursuit of overclocking and voltage and it was completely my fault.


Stock devices should be capable of handling stability tests at stock values. Full stop.

If you choose to operate hardware outside its specified limits its your fault. Full stop.
 
Joined
Dec 29, 2010
Messages
3,493 (0.72/day)
Processor AMD 5900x
Motherboard Asus x570 Strix-E
Cooling Hardware Labs
Memory G.Skill 4000c17 2x16gb
Video Card(s) RTX 3090
Storage Sabrent
Display(s) Samsung G9
Case Phanteks 719
Audio Device(s) Fiio K5 Pro
Power Supply EVGA 1000 P2
Mouse Logitech G600
Keyboard Corsair K95
No the game didn't kill the GPU, a faulty design that deviated from Nvidia Reference is the cause.

When it came to Furmark and the Femi, the card was simply not designed for a power virus app and instead actual workloads. Not sure if this is still present in the current GPU drivers, but Furmark exe was flagged and a power limit was put in place to prevent killing GPUs. Workaround was to change the exe name.

In both cases it was a fault in the design that is the problem, not the software.
Also back in those days soooome ppl thought it was a good idea to loop Furmark for 24 hours and shit to prove stability, hence poof gone like Keyser Soze!
 
Top