Undervolting and BSOD on G3-571

Sharfan
Sharfan Member Posts: 45 Troubleshooter
edited November 2023 in 2018 Archives
I decided to undervolt using throttlestop after noticing my cpu temps in the mid 80s. I think I used -125mV voltage offset on the core and cache. I tried out Just Cause 3 and I noticed much lower temps but the game then froze and I got a BSOD. I wasn't able to get a hold of the error message as my laptop rebooted automatically. I wanted to know if getting a BSOD from undervolting could damage my laptop in anyway?,

Best Answers

  • ven98
    ven98 ACE Posts: 4,073 Pathfinder
    edited January 2018 Answer ✓
    It can't and won't damage your device, but getting BSODs means that the voltage you have set is unstable and needs to be increased a bit. I suggest you to try with -120mV.
    Always post the following characterisitcs of the device:
    -Model number
    -Part number(not required, but helpful)
    -CPU
    -GPU
    -Operating system

    Helios 300 and Nitro 5 users DO NOT update the BIOS to version 1.22 if you don't want the keyboard's backlight to turn off after 30 seconds even when the device is plugged in.


    Hit 'Like' if you find the answer helpful!   
    Click on 'Yes' if the comment answers your question!

  • ven98
    ven98 ACE Posts: 4,073 Pathfinder
    Answer ✓
    If you get a BSOD again, then it most likely is the controller's driver fault. I think the reason why you got this error is because the system crash caused by the undervolting made the driver crash as well before it shuts down and windows reports this error only.

    You can go to control panel>system and security>system>advanced system settings>advanced(tab)>start up and recovery and disable automatic restart by removing the tick. This way you will have more time to check the error/s if you get BSOD. Go to the WINDOWS folder and find the folder 'Minidump'. Delete all files, except the 3 most recent ones. Download whocrashed. This tool will show what caused the error. You can post a picture of the log or copy and paste it back here.
    Always post the following characterisitcs of the device:
    -Model number
    -Part number(not required, but helpful)
    -CPU
    -GPU
    -Operating system

    Helios 300 and Nitro 5 users DO NOT update the BIOS to version 1.22 if you don't want the keyboard's backlight to turn off after 30 seconds even when the device is plugged in.


    Hit 'Like' if you find the answer helpful!   
    Click on 'Yes' if the comment answers your question!

Answers

  • ven98
    ven98 ACE Posts: 4,073 Pathfinder
    edited January 2018 Answer ✓
    It can't and won't damage your device, but getting BSODs means that the voltage you have set is unstable and needs to be increased a bit. I suggest you to try with -120mV.
    Always post the following characterisitcs of the device:
    -Model number
    -Part number(not required, but helpful)
    -CPU
    -GPU
    -Operating system

    Helios 300 and Nitro 5 users DO NOT update the BIOS to version 1.22 if you don't want the keyboard's backlight to turn off after 30 seconds even when the device is plugged in.


    Hit 'Like' if you find the answer helpful!   
    Click on 'Yes' if the comment answers your question!

  • Sharfan
    Sharfan Member Posts: 45 Troubleshooter
    I settled with a -110mV undervolt and it seems to be fine so far. I also noticed that there was nothing written to my minidump folder even though my settings say that the dump file should be written to that folder. Under windows maintenance I noticed that the Bucket ID for the BSOD event mentioned something like "mijxfilt". it occurred to me that the drivers I use to connect my PS3 controller to my laptop had a driver file know as "mixfilt.sys". Is it possible that the drivers for the controller caused the BSOD or was it because of the undervolt? Please note that I have used those PS3 drivers on my previous laptop and i have never ran into a BSOD. Also before the undervolt I have never had a BSOD on my G3-571
  • ven98
    ven98 ACE Posts: 4,073 Pathfinder
    Answer ✓
    If you get a BSOD again, then it most likely is the controller's driver fault. I think the reason why you got this error is because the system crash caused by the undervolting made the driver crash as well before it shuts down and windows reports this error only.

    You can go to control panel>system and security>system>advanced system settings>advanced(tab)>start up and recovery and disable automatic restart by removing the tick. This way you will have more time to check the error/s if you get BSOD. Go to the WINDOWS folder and find the folder 'Minidump'. Delete all files, except the 3 most recent ones. Download whocrashed. This tool will show what caused the error. You can post a picture of the log or copy and paste it back here.
    Always post the following characterisitcs of the device:
    -Model number
    -Part number(not required, but helpful)
    -CPU
    -GPU
    -Operating system

    Helios 300 and Nitro 5 users DO NOT update the BIOS to version 1.22 if you don't want the keyboard's backlight to turn off after 30 seconds even when the device is plugged in.


    Hit 'Like' if you find the answer helpful!   
    Click on 'Yes' if the comment answers your question!

  • Sharfan
    Sharfan Member Posts: 45 Troubleshooter
    ven98 said:
    If you get a BSOD again, then it most likely is the controller's driver fault. I think the reason why you got this error is because the system crash caused by the undervolting made the driver crash as well before it shuts down and windows reports this error only.

    You can go to control panel>system and security>system>advanced system settings>advanced(tab)>start up and recovery and disable automatic restart by removing the tick. This way you will have more time to check the error/s if you get BSOD. Go to the WINDOWS folder and find the folder 'Minidump'. Delete all files, except the 3 most recent ones. Download whocrashed. This tool will show what caused the error. You can post a picture of the log or copy and paste it back here.
    i have checked inside the minidump folder and there are no files present. I ran whocrashed and it says that crash dumps are enabled but no valid crash dumps have been found.
  • Sharfan
    Sharfan Member Posts: 45 Troubleshooter
    ven98 said:
    If you get a BSOD again, then it most likely is the controller's driver fault. I think the reason why you got this error is because the system crash caused by the undervolting made the driver crash as well before it shuts down and windows reports this error only.

    You can go to control panel>system and security>system>advanced system settings>advanced(tab)>start up and recovery and disable automatic restart by removing the tick. This way you will have more time to check the error/s if you get BSOD. Go to the WINDOWS folder and find the folder 'Minidump'. Delete all files, except the 3 most recent ones. Download whocrashed. This tool will show what caused the error. You can post a picture of the log or copy and paste it back here.
    Also this is the only info i was provided by Windows Reliability Monitor: Source Windows Summary Shut down unexpectedly Date ‎26/‎01/‎2018 17:53 Status Report sent Problem signature Problem Event Name: BlueScreen Code: d1 Parameter 1: fffff80d9407b638 Parameter 2: 2 Parameter 3: 8 Parameter 4: fffff80d9407b638 OS version: 10_0_16299 Service Pack: 0_0 Product: 768_1 OS Version: 10.0.16299.2.0.0.768.101 Locale ID: 1033 Extra information about the problem Bucket ID: AV_CODE_AV_PAGED_IP_MijXfilt!unknown_function
  • ven98
    ven98 ACE Posts: 4,073 Pathfinder
    Sharfan said:
    ven98 said:
    If you get a BSOD again, then it most likely is the controller's driver fault. I think the reason why you got this error is because the system crash caused by the undervolting made the driver crash as well before it shuts down and windows reports this error only.

    You can go to control panel>system and security>system>advanced system settings>advanced(tab)>start up and recovery and disable automatic restart by removing the tick. This way you will have more time to check the error/s if you get BSOD. Go to the WINDOWS folder and find the folder 'Minidump'. Delete all files, except the 3 most recent ones. Download whocrashed. This tool will show what caused the error. You can post a picture of the log or copy and paste it back here.
    i have checked inside the minidump folder and there are no files present. I ran whocrashed and it says that crash dumps are enabled but no valid crash dumps have been found.
    Looks that if automatic restart is enabled when the system crashes, it doesn't create a minidump.
    Always post the following characterisitcs of the device:
    -Model number
    -Part number(not required, but helpful)
    -CPU
    -GPU
    -Operating system

    Helios 300 and Nitro 5 users DO NOT update the BIOS to version 1.22 if you don't want the keyboard's backlight to turn off after 30 seconds even when the device is plugged in.


    Hit 'Like' if you find the answer helpful!   
    Click on 'Yes' if the comment answers your question!