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

Undervolting - Getting BSOD (unrecoverable error) HELP!

begg4r

New Member
Joined
May 17, 2023
Messages
7 (0.01/day)
EDIT: Just noticed my bios blocked undervolting again


So after getting some help in here from unclewebb my pc been performing beautifully until i tried to play Rust.
Everything was working well but my temps were almost hitting 100c and i tried undervolting a little more (-65 to -70 offset) and it didnt work, got the BSOD.
Now to mitigate the temps i tried lowering the OC to 41 on all cores but still got BSOD and after 6+ hours of gameplay randomly that my Alienware M15 R6 opened the bios recovery thing on startup claiming my bios was corrupted.
Any ideas on what could be happening?
At least the pc is turning on, so maybe i didnt fry any components lol

Heres the configs and log up untill the BSOD point


Screenshot 2023-05-27 023809.png


1685166179742.png
 

Attachments

  • 2023-05-27.txt
    606.4 KB · Views: 49
  • 2023-05-26.txt
    3.6 MB · Views: 43
D

Deleted member 57642

Guest
While testing/looking for an ideal Undervolt - TS should be set to OK - Do not save voltages - especially if it's set to start with Windows. Tho, i don't see any Undervolt in above screenshots (the Offset is +0 and all variables). Presumably, you didn't disable Virtualization Based Security? Then again, it's a Dell - and apparently Undervolting was locked with the latest BIOS...


You'll have o flash the BIOS using BIOS Recovery Image File

 

begg4r

New Member
Joined
May 17, 2023
Messages
7 (0.01/day)
While testing/looking for an ideal Undervolt - TS should be set to OK - Do not save voltages - especially if it's set to start with Windows. Tho, i don't see any Undervolt in above screenshots (the Offset is +0 and all variables). Presumably, you didn't disable Virtualization Based Security? Then again, it's a Dell - and apparently Undervolting was locked with the latest BIOS...


You'll have o flash the BIOS using BIOS Recovery Image File

Yes, it shows no offset because the bios just updated.
But before the last BSOD i did everything, disabled VBS, undervolted, downgraded bios. Was working well.

My concern was about the settings showed on TS, if they were the cause of the blue screens.
 
Joined
Mar 24, 2019
Messages
668 (0.30/day)
Location
Denmark - Aarhus
System Name Iglo
Processor 5800X3D
Motherboard TUF GAMING B550-PLUS WIFI II
Cooling Arctic Liquid Freezer II 360
Memory 32 gigs - 3600hz
Video Card(s) EVGA GeForce GTX 1080 SC2 GAMING
Storage NvmE x2 + SSD + spinning rust
Display(s) BenQ XL2420Z - lenovo both 27" and 1080p 144/60
Case Fractal Design Meshify C TG Black
Audio Device(s) Logitech Z-2300 2.1 200w Speaker /w 8 inch subwoofer
Power Supply Seasonic Prime Ultra Platinum 550w
Mouse Logitech G900
Keyboard Corsair k100 Air Wireless RGB Cherry MX
Software win 10
Benchmark Scores Super-PI 1M T: 7,993 s :CinebR20: 5755 point GeekB: 2097 S-11398-M 3D :TS 7674/12260
i would recommend getting a survivor kit like Medicat, if you get in big trouble.
a vid ex. here.
 
D

Deleted member 57642

Guest
Yes, it shows no offset because the bios just updated.
But before the last BSOD i did everything, disabled VBS, undervolted, downgraded bios. Was working well.

My concern was about the settings showed on TS, if they were the cause of the blue screens.
If you lower the voltage to much (each CPU is different - some need more voltage to function properly - while another CPU despite of being exactly the same model - works just fine with less or even higher - it's a CPU lottery) - yes, BSOD is a normal outcome. The thing is, you can lower the voltage - and the CPU may still give the impression of being stable - at least - till you start using a demanding task/app/game - which is when it might need slightly more voltage to run at a specific frequency - so the BSOD gets triggered (BSOD is basically a "fail-safe feature" - which gets triggered by all kinds of deviations from what's acknowledged as a safe functionality standard - deviations that could potentially damage the hardware or impact the OS/Windows's stability). Which is why be it while OC-ing or Undevolting - you're suppose to do all kind of stress tests shortly after. Tho, i don't se how your settings could corrupt the BIOS - since ThrottleStop works only in Windows (the BIOS setting get reverted on each restart and re-applied when ThrottleStop is started in Windows). Unless you made some changes in BIOS - manually (that's usually what can corupt a BIOS - besides a failed BIOS update).
 
Top