Hi there! I see that Geekbench 6 is shutting down and restarting your system specifically during the object detection test. Let me get a bit more information first—
1. Are you running Geekbench 6 on your Windows device only, or do you also experience this on other systems? 2. Has this issue started recently after an update, or has it been happening since you first installed Geekbench 6? 3. Do you notice if the system restarts immediately or after some delay when it reaches object detection? 4. Have you checked your system temperatures, like CPU or GPU, to see if overheating might be causing a sudden shutdown? 5. Also, did you install the latest Geekbench 6 version from the official site?
This info will help me pinpoint the issue better.
Meanwhile, here are some initial troubleshooting steps we can try:
1. Update your GPU Drivers: Object detection in Geekbench 6 uses machine learning workloads that may leverage GPU acceleration. Outdated or incompatible graphics drivers can cause crashes or restarts. Go to your graphics card manufacturer’s website (like NVIDIA, AMD, or Intel) and download the latest drivers compatible with Windows 10.
2. Close Background Apps: Sometimes other apps using intense CPU or GPU resources can interfere with Geekbench. Close unnecessary background programs before running the test.
3. Check System Temperatures: Use a tool like HWMonitor or Core Temp to check if your CPU or GPU is overheating when running Geekbench. High temperatures can lead to automatic shutdowns to protect hardware.
4. Run Geekbench as Administrator: Right-click the Geekbench executable and select “Run as administrator” to ensure it has all necessary permissions.
5. Verify System Updates: Make sure your Windows 10 is fully updated as some machine learning-related features may depend on OS updates.
If the issue persists after these steps, we can look deeper into the hardware health or power settings that might be causing restarts during AI workloads like object detection.
Let me know what you find with these, and we’ll get it sorted! Are you okay with trying these first?
Thanks for clarifying that the shutdown and restart happen during the CPU object detection test in Geekbench 6. That gives us better direction to troubleshoot.
This kind of behavior often points to CPU instability or issues when running heavy machine learning workloads like the object detection test in Geekbench 6. Here's what we can try next, step-by-step:
1. Check CPU Stability and Clock Speeds: - Are you overclocking your CPU or using any performance tweaks in BIOS? Overclocking can cause instability during heavy loads such as machine learning tests. - If yes, try resetting your BIOS to default settings or lowering your CPU clock speeds temporarily and run the test again.
2. Update Geekbench 6 to the Latest Version: - There have been fixes in versions after release addressing crashes in CPU tests, so confirm you have the latest Geekbench 6 version installed from the official source.
3. Update Windows and Drivers: - Make sure your Windows 10 is fully updated. - Update your chipset and CPU-related drivers from your motherboard manufacturer.
4. Run the Test While Monitoring Temps and Power: - Use HWMonitor or a similar tool to watch CPU temperatures and power consumption. Sudden spikes or overheating could cause shutdowns. - If temperatures shoot very high, your cooling solution might need checking.
5. Disable Power Saving Features Temporarily: - In Windows Power Options, set the plan to “High performance” and disable any CPU throttling settings like Intel SpeedStep or AMD Cool'n'Quiet.
6. Check Event Viewer for Errors: - After a reboot, open Event Viewer (Windows key + R, type eventvwr) and check under Windows Logs > System and Application for any error messages or critical events around the time of the crash. This might give clues if it’s a hardware or driver issue.
7. Run a CPU Stress Test: - Tools like Prime95 or IntelBurnTest can stress your CPU in ways similar to Geekbench’s object detection test, helping confirm if the CPU is stable under load.
If after these steps Geekbench 6 still causes shutdowns during the object detection CPU test, it may be due to hardware-related instability or a bug that needs reporting to our Geekbench developers. You can email [email protected] with your system details and crash description if you'd like me to assist in escalating.
Would you like me to help you walk through any of these steps in detail? Also, could you share your CPU model and whether you’ve tried overclocking? That will help me tailor the advice better.
Thanks for your question about known issues with Geekbench 6 on your device running Windows 10 with a WebKit browser.
From the information available, there isn't a widely reported or specific known issue with Geekbench 6 causing shutdowns and restarts during the CPU object detection test on Windows devices like yours. Most known fixes mentioned for Geekbench 6 relate to browser connection errors or GPU detection improvements, not system restarts during CPU tests4.
Some reports do mention bugs with device naming on Apple devices, but that doesn’t apply to your Windows system2.
Given that your issue involves a full system shutdown and restart during a CPU-intensive task, it's more likely related to hardware stability, drivers, or power/thermal management rather than a specific Geekbench 6 software bug.
I recommend proceeding with the troubleshooting steps I mentioned earlier to check CPU stability, temperatures, power settings, and driver updates, since these are more common causes.
If you want, I can guide you through these steps in detail. Also, if the problem persists after trying them, contacting Geekbench’s support at [email protected] with your system specs and crash logs would be the next best step.
Does that sound good to you? Would you like help with the next troubleshooting step?
Comments
Emily Roberts
Emily is passionate about explaining complex topics in plain English. She’s writ...
Followed by
Hi there! I see that Geekbench 6 is shutting down and restarting your system specifically during the object detection test. Let me get a bit more information first—
1. Are you running Geekbench 6 on your Windows device only, or do you also experience this on other systems?
2. Has this issue started recently after an update, or has it been happening since you first installed Geekbench 6?
3. Do you notice if the system restarts immediately or after some delay when it reaches object detection?
4. Have you checked your system temperatures, like CPU or GPU, to see if overheating might be causing a sudden shutdown?
5. Also, did you install the latest Geekbench 6 version from the official site?
This info will help me pinpoint the issue better.
Meanwhile, here are some initial troubleshooting steps we can try:
1. Update your GPU Drivers: Object detection in Geekbench 6 uses machine learning workloads that may leverage GPU acceleration. Outdated or incompatible graphics drivers can cause crashes or restarts. Go to your graphics card manufacturer’s website (like NVIDIA, AMD, or Intel) and download the latest drivers compatible with Windows 10.
2. Close Background Apps: Sometimes other apps using intense CPU or GPU resources can interfere with Geekbench. Close unnecessary background programs before running the test.
3. Check System Temperatures: Use a tool like HWMonitor or Core Temp to check if your CPU or GPU is overheating when running Geekbench. High temperatures can lead to automatic shutdowns to protect hardware.
4. Run Geekbench as Administrator: Right-click the Geekbench executable and select “Run as administrator” to ensure it has all necessary permissions.
5. Verify System Updates: Make sure your Windows 10 is fully updated as some machine learning-related features may depend on OS updates.
If the issue persists after these steps, we can look deeper into the hardware health or power settings that might be causing restarts during AI workloads like object detection.
Let me know what you find with these, and we’ll get it sorted! Are you okay with trying these first?
when running geekbench 6 it shuts down and restarts when it gets to object detection on the CPU test
Emily Roberts
Emily is passionate about explaining complex topics in plain English. She’s writ...
Followed by
Thanks for clarifying that the shutdown and restart happen during the CPU object detection test in Geekbench 6. That gives us better direction to troubleshoot.
This kind of behavior often points to CPU instability or issues when running heavy machine learning workloads like the object detection test in Geekbench 6. Here's what we can try next, step-by-step:
1. Check CPU Stability and Clock Speeds:
- Are you overclocking your CPU or using any performance tweaks in BIOS? Overclocking can cause instability during heavy loads such as machine learning tests.
- If yes, try resetting your BIOS to default settings or lowering your CPU clock speeds temporarily and run the test again.
2. Update Geekbench 6 to the Latest Version:
- There have been fixes in versions after release addressing crashes in CPU tests, so confirm you have the latest Geekbench 6 version installed from the official source.
3. Update Windows and Drivers:
- Make sure your Windows 10 is fully updated.
- Update your chipset and CPU-related drivers from your motherboard manufacturer.
4. Run the Test While Monitoring Temps and Power:
- Use HWMonitor or a similar tool to watch CPU temperatures and power consumption. Sudden spikes or overheating could cause shutdowns.
- If temperatures shoot very high, your cooling solution might need checking.
5. Disable Power Saving Features Temporarily:
- In Windows Power Options, set the plan to “High performance” and disable any CPU throttling settings like Intel SpeedStep or AMD Cool'n'Quiet.
6. Check Event Viewer for Errors:
- After a reboot, open Event Viewer (Windows key + R, type eventvwr) and check under Windows Logs > System and Application for any error messages or critical events around the time of the crash. This might give clues if it’s a hardware or driver issue.
7. Run a CPU Stress Test:
- Tools like Prime95 or IntelBurnTest can stress your CPU in ways similar to Geekbench’s object detection test, helping confirm if the CPU is stable under load.
If after these steps Geekbench 6 still causes shutdowns during the object detection CPU test, it may be due to hardware-related instability or a bug that needs reporting to our Geekbench developers. You can email [email protected] with your system details and crash description if you'd like me to assist in escalating.
Would you like me to help you walk through any of these steps in detail? Also, could you share your CPU model and whether you’ve tried overclocking? That will help me tailor the advice better.
Is there a known issue with Geekbench 6 on my device?
Emily Roberts
Emily is passionate about explaining complex topics in plain English. She’s writ...
Followed by
Thanks for your question about known issues with Geekbench 6 on your device running Windows 10 with a WebKit browser.
From the information available, there isn't a widely reported or specific known issue with Geekbench 6 causing shutdowns and restarts during the CPU object detection test on Windows devices like yours. Most known fixes mentioned for Geekbench 6 relate to browser connection errors or GPU detection improvements, not system restarts during CPU tests4.
Some reports do mention bugs with device naming on Apple devices, but that doesn’t apply to your Windows system2.
Given that your issue involves a full system shutdown and restart during a CPU-intensive task, it's more likely related to hardware stability, drivers, or power/thermal management rather than a specific Geekbench 6 software bug.
I recommend proceeding with the troubleshooting steps I mentioned earlier to check CPU stability, temperatures, power settings, and driver updates, since these are more common causes.
If you want, I can guide you through these steps in detail. Also, if the problem persists after trying them, contacting Geekbench’s support at [email protected] with your system specs and crash logs would be the next best step.
Does that sound good to you? Would you like help with the next troubleshooting step?