• 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
Mar 5, 2023
Messages
155 (0.20/day)
This is my build: https://pcpartpicker.com/list/dBdqY9

I ran a multi-core CPU test in Cinebench to test my overclock. I enabled PBO in the BIOS. When the multi-core test ended, my entire PC crashed. Now, I cannot use my Wi-Fi for some reason. I'm getting the following errors in Device Manager with my Wi-Fi adapter: "This device cannot start. (Code 10) {Operation Failed} The requested operation was unsuccessful." and then "Currently, this hardware device is connected to the computer (COde 45). To fix this problem, reconnect the hardware device to the computer." once I restart my PC.
I also keep getting a black screen with a spinning loading circle and then a blue screen that says "Please wait" with another loading circle whenever I start up my PC. This did not happen before, and it makes startup take longer.
I tried to do a System Restore. My last restore point was yesterday, so I used that. However, that did not fix any of my issues. How can I fix this problem?

So far, I disabled PBO in the BIOS settings and then reset all my BIOS settings to the default settings. I'm unfortunately still getting these issues though. I'll try to clear the CMOS though too. I tried to uninstall the MediaTek wifi adapter multiple times, but I'm still getting this issue. Am I uninstalling it incorrectly or something?
 
Reinstall OS.
Thanks! I’ll try that to make sure there are no lingering issues. However, I was somehow able to fix these specific issues after all of the other stuff I tried like resetting the BIOS and all. I disabled the WiFi connector in the BIOS and re-enabled it, and it somehow fixed this issue. Is it still possible that the mobo got slightly damaged in some way though? It definitely seems weird that this even happened at all...
 
Thanks! I’ll try that to make sure there are no lingering issues. However, I was somehow able to fix these specific issues after all of the other stuff I tried like resetting the BIOS and all. I disabled the WiFi connector in the BIOS and re-enabled it, and it somehow fixed this issue. Is it still possible that the mobo got slightly damaged in some way though? It definitely seems weird that this even happened at all...
The OC Cinebench crash and WiFi disconnecting is probably unrelated. As for MB damage from OC, wouldn't worry at all about that.
 
You might want to remove the battery on the motherboard, turn off PSU, when it's completely shut down too. A complete reset of the BIOS this way, then do your clean install as mentioned above, after backing up your important stuff. Good luck!
 
Replace HDD/SSD that contains Operating System or do CHKDSK
I ran a chkdsk, and it appears that there weren't any major issues based on the Windows Event Viewer logs. I'm not entirely sure what they're saying, but it looks like there's nothing major. Thank you! I will replace it if I run into any further issues.
The OC Cinebench crash and WiFi disconnecting is probably unrelated. As for MB damage from OC, wouldn't worry at all about that.
Oh okay, that makes sense then and it's good it's just a coincidence and all. I'm glad there's no MB damage from the OC then too. Thank you!
You might want to remove the battery on the motherboard, turn off PSU, when it's completely shut down too. A complete reset of the BIOS this way, then do your clean install as mentioned above, after backing up your important stuff. Good luck!
I will be sure to follow those steps and back up everything tot make sure I don't lose anything important. Thank you!
 
I ran a chkdsk, and it appears that there weren't any major issues based on the Windows Event Viewer logs. I'm not entirely sure what they're saying, but it looks like there's nothing major. Thank you! I will replace it if I run into any further issues.

Oh okay, that makes sense then and it's good it's just a coincidence and all. I'm glad there's no MB damage from the OC then too. Thank you!

I will be sure to follow those steps and back up everything tot make sure I don't lose anything important. Thank you!

don't forget to put the battery back in after 20 seconds or so, also this resets any changes you made in BIOS, so just fyi.
 
don't forget to put the battery back in after 20 seconds or so, also this resets any changes you made in BIOS, so just fyi.
Thanks! I’ll make sure to take some pictures of my BIOS changes to set them again after I put the battery back in.
 
Just an fyi, I ran Cinebench 2024 with an unstable oc (edited the vf curve to ~+200mhz) and it borked my gpu, had to rma it due to issues in games afterwards. Fairly warned be thee says I.
 
Just an fyi, I ran Cinebench 2024 with an unstable oc (edited the vf curve to ~+200mhz) and it borked my gpu, had to rma it due to issues in games afterwards. Fairly warned be thee says I.
Did you apply an OC to the card?
 
Just an fyi, I ran Cinebench 2024 with an unstable oc (edited the vf curve to ~+200mhz) and it borked my gpu, had to rma it due to issues in games afterwards. Fairly warned be thee says I.
I see, I'll be more careful with Cinebench then since my GPU and my CPU are both overclocked. I realized that I set Cinebench R24 to Real-time Priority in Process Lasso a while back to get the best possible score, so is that why my PC crashed? I guess I got lucky a year ago when I ran it last, but I know running stuff in Real-time causes instability. I don't know why it caused my Wi-Fi isuses though.
Did you apply an OC to the card?
In my case, I applied an OC to my CPU. I realized that I set Cinebench R24 to Real-time Priority in Process Lasso a while back to get the best possible score, so is that why my PC crashed? I guess I got lucky a year ago when I ran it last, but I know running stuff in Real-time causes instability. I don't know why it caused my Wi-Fi isuses though.
 
Just an fyi, I ran Cinebench 2024 with an unstable oc (edited the vf curve to ~+200mhz) and it borked my gpu, had to rma it due to issues in games afterwards. Fairly warned be thee says I.
100% cannot see how a CPU OC killed your GPU. Another unrelated problem. Unless your saying it was a GPU OC, than still Cinebench isn't to blame, it would have happened anyways.
 
Your pc is unstable it seems
I realized that I set Cinebench R24 to Real-time Priority in Process Lasso a while back to get the best possible score, so is that why my PC crashed? I guess I got lucky a year ago when I ran it last, but I know running stuff in Real-time causes instability. I don't know why it caused my Wi-Fi connector to get messed up though, so does it still seemthat my PC is unstable?
 
I realized that I set Cinebench R24 to Real-time Priority in Process Lasso a while back to get the best possible score, so is that why my PC crashed? I guess I got lucky a year ago when I ran it last, but I know running stuff in Real-time causes instability. I don't know why it caused my Wi-Fi connector to get messed up though, so does it still seemthat my PC is unstable?
To be honest process lasso is a good software but you dont need it on your build.It can cause conflicts/crashes. It's only good to mess/play around with and mostly for lower spec systems.
 
Ctrl+R, type CMD

A black window will appear.

At the prompt type "sfc /scannow" without the quotes.

Does Cinebench run with the adapter disabled?
 
To be honest process lasso is a good software but you dont need it on your build.It can cause conflicts/crashes. It's only good to mess/play around with and mostly for lower spec systems.
Seems like it would be more ideal to use on systems that have scheduling issues such as 7900X3D and 7950X3D, or limiting use of ecores in certain applications.
 
100% cannot see how a CPU OC killed your GPU. Another unrelated problem. Unless your saying it was a GPU OC, than still Cinebench isn't to blame, it would have happened anyways.
No, Cinebench was definitely to blame, and it was a gpu oc of ~+200mhz on the core, the maximum I thought stable since it didn't crash any other benchmark test (including Superposition and 3D Mark), but halfway (maybe less) through the gpu test in Cinebench 2024 my system froze/crashed and restarted.

After that I had graphical issues in every game I played, so it definitely was Cinebench that borked my gpu (RMA confirmed gpu had issues when I sent it in which didn't exist prior to the Cb24 gpu test w oc). Also Cb24 ran fine @ stock clocks.

This is roughly the curve I used, I set the boost to over 3ghz @ less than 1.1v and Cinebench 24 borked it. Try it yourself if you don't believe me, it would be entertaining to watch others suffer the same fate despite my warning.

curve.jpg
 
Last edited:
Ctrl+R, type CMD

A black window will appear.

At the prompt type "sfc /scannow" without the quotes.

Does Cinebench run with the adapter disabled?
sfc /scannow didn't encounter any issues. Additionally, Cinebench runs with the adapter disabled. Thanks!

Seems like it would be more ideal to use on systems that have scheduling issues such as 7900X3D and 7950X3D, or limiting use of ecores in certain applications.
I am considering getting one of the X3D CPUs, so I'll make sure to use it if I ever get one. With that said, I heard the 7800X3D is better and doesn't have major scheduling issues if I am understanding everything I read correctly. Thanks!

No, Cinebench was definitely to blame, and it was a gpu oc of ~+200mhz on the core, the maximum I thought stable since it didn't crash any other benchmark test (including Superposition and 3D Mark), but halfway (maybe less) through the gpu test in Cinebench 2024 my system froze/crashed and restarted.

After that I had graphical issues in every game I played, so it definitely was Cinebench that borked my gpu (RMA confirmed gpu had issues when I sent it in which didn't exist prior to the Cb24 gpu test w oc). Also Cb24 ran fine @ stock clocks.

This is roughly the curve I used, I set the boost to over 3ghz @ less than 1.1v and Cinebench 24 borked it. Try it yourself if you don't believe me, it would be entertaining to watch others suffer the same fate despite my warning.

View attachment 344724
Since I have both a CPU and a GPU OC, I'll be careful when I run Cinebench more. I guess I'll reset my GPU OC to its default settings while I run Cinebench. Thanks!
 
No, Cinebench was definitely to blame, and it was a gpu oc of ~+200mhz on the core, the maximum I thought stable since it didn't crash any other benchmark test (including Superposition and 3D Mark), but halfway (maybe less) through the gpu test in Cinebench 2024 my system froze/crashed and restarted.
Blaming software for a failed overclock is just silly.
 
Running something like cinebench in Real Time CPU mode and a network driver that probably relies on the CPU responding in XX number of milliseconds to help.l it assemble and discard packets efficiently isn't the best choice.
 
What was yours temperatures on CPU and VRM?How much Voltage you applied on your OC over the stock settings?
 
sfc /scannow didn't encounter any issues. Additionally, Cinebench runs with the adapter disabled. Thanks!


I am considering getting one of the X3D CPUs, so I'll make sure to use it if I ever get one. With that said, I heard the 7800X3D is better and doesn't have major scheduling issues if I am understanding everything I read correctly. Thanks!


Since I have both a CPU and a GPU OC, I'll be careful when I run Cinebench more. I guess I'll reset my GPU OC to its default settings while I run Cinebench. Thanks!
Get the 7800X3D if you're primarily gaming and there won't be any reason to use process lasso.
 
Running something like cinebench in Real Time CPU mode and a network driver that probably relies on the CPU responding in XX number of milliseconds to help.l it assemble and discard packets efficiently isn't the best choice.
Oh okay that makes sense then in terms of why my network driver got messed up when I was using my CPU to that extent. Thank you!

What was yours temperatures on CPU and VRM?How much Voltage you applied on your OC over the stock settings?
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!

Get the 7800X3D if you're primarily gaming and there won't be any reason to use process lasso.
Oh okay that makes sense. When I decide to upgrade my PC, I’ll definitely go with a 7800X3D then. Thanks!
 
Back
Top