Throttlestop BSOD on Windows 10 Update Build 19041.329

[dziugas1959]

Does anyone else have this problem? I use ThrottleStop 8.70.6 not Beta and I updated my windows, but now when I launch Throttlestop it BSOD's after the 06 Commulative update for WIndows 10 2004

 

[unclewebb]

Are you using the FIVR - Disable and Lock Turbo Power Limits feature? Try disabling that. This feature uses the RwDrv.sys driver which seems to cause a BSOD.

 

[dziugas1959]

Are you using the FIVR - Disable and Lock Turbo Power Limits feature? Try disabling that. This feature uses the RwDrv.sys driver which seems to cause a BSOD.

problem is that when i double click it a.k.a open it IT just BSOD's instantly. Can you confirm that you have Windows 10 2004 19041.329 with ThrottleStop 8.70.6 because it worked before, but now just instant crash i will try Beta maybe will give me better results

OK it works on the Beta version ... Surprisingly and yes i do have Disable and Lock Turbo Power Limits On because of i want to Lower that Power limit throttling from 4.xxGhz or 3.xxGhz to 0.80Ghz that sucks really Dell really should get on that

 

[unclewebb]

Some users have found that adding a 2 or 3 minute time delay when auto starting ThrottleStop helps avoid the BSOD issues. I have not yet installed Windows 10 2004 so it will be a while before there are fixes for Microsoft's latest bugs.

 

[dziugas1959]

Some users have found that adding a 2 or 3 minute time delay when auto starting ThrottleStop helps avoid the BSOD issues. I have not yet installed Windows 10 2004 so it will be a while before there are fixes for Microsoft's latest bugs.

Yeah that's not the answer, but i can tell that you didn't understand my cause of issue it wasn't windows 10 2004 it was a commutative update for 2004 which is why I asked does anyone else have this problem after installing 06 month commutative update

 

[vient]

I've had exactly same problem just now — upgraded Windows 10 to 2004, BSOD. For me it was a bit worse because ThrottleStop was set up to load on startup so I needed to boot in Safe Mode and rename RwDrv.sys. After that, no more BSODs. I confirmed that the problem is in RwDrv by opening minidump file in WinDbg — BSOD occurs becuase of NULL pointer dereference in RwDrv. And yes, I had "Disable and Lock Turbo Power Limits" on too.

 

[unclewebb]

@vient - Good news. The RwDrv.sys driver is being retired. As you know, it is not compatible with Windows 10 2004.

I am working on an updated version of ThrottleStop so people will be able to use the Disable and Lock Turbo Power Limits feature without any BSOD issues. I also added a feature to try and prevent getting stuck in a BSOD loop if anything does go wrong such as overly aggressive undervolt settings.

Keep an eye on TechPowerUp for the announcement. It should be ready for testing later today or tomorrow.