U usasma Retired Admin Joined Feb 20, 2012 Posts 2,126 Feb 8, 2013 #1 From this post: Windows 8 keeps BSOD when using P2P and surfing net - Page 3 Reading the link there ( [GUIDE] Nvidia Inspector GTX670/680 - disable boost / fixed clock speed / undervolting ) this brings up similarities to the problems that we saw with "Turbo" applications in the BIOS back a year or two ago. There's been an increasing discussion on the forums about rolling back drivers - and success' with this. So I'm wondering if we should start looking at underclocking (auto or otherwise) as a possible source of BSOD issues. I usually recommend disabling any "auto" overclocking utilities - maybe this should also apply to any clock altering behavior on any device? At least for troubleshooting purposes?
From this post: Windows 8 keeps BSOD when using P2P and surfing net - Page 3 Reading the link there ( [GUIDE] Nvidia Inspector GTX670/680 - disable boost / fixed clock speed / undervolting ) this brings up similarities to the problems that we saw with "Turbo" applications in the BIOS back a year or two ago. There's been an increasing discussion on the forums about rolling back drivers - and success' with this. So I'm wondering if we should start looking at underclocking (auto or otherwise) as a possible source of BSOD issues. I usually recommend disabling any "auto" overclocking utilities - maybe this should also apply to any clock altering behavior on any device? At least for troubleshooting purposes?
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,542 Location New Jersey Shore Feb 8, 2013 #2 usasma said: There's been an increasing discussion on the forums about rolling back drivers - and success' with this. Click to expand... How far back can Windows 8 drivers be rolled? i.e., back into beta stage? (W8 Consumer, Developer Previews)? Any trying to roll back to Windows 7 drivers (IDK if that's even possible or not). usasma said: So I'm wondering if we should start looking at underclocking (auto or otherwise) as a possible source of BSOD issues. I usually recommend disabling any "auto" overclocking utilities - maybe this should also apply to any clock altering behavior on any device? At least for troubleshooting purposes? Click to expand... Sounds like a plan if the software winds up o/c on a percentage basis v. an actual clock-speed number. IDK - never o/c anything myself.
usasma said: There's been an increasing discussion on the forums about rolling back drivers - and success' with this. Click to expand... How far back can Windows 8 drivers be rolled? i.e., back into beta stage? (W8 Consumer, Developer Previews)? Any trying to roll back to Windows 7 drivers (IDK if that's even possible or not). usasma said: So I'm wondering if we should start looking at underclocking (auto or otherwise) as a possible source of BSOD issues. I usually recommend disabling any "auto" overclocking utilities - maybe this should also apply to any clock altering behavior on any device? At least for troubleshooting purposes? Click to expand... Sounds like a plan if the software winds up o/c on a percentage basis v. an actual clock-speed number. IDK - never o/c anything myself.