Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] RC QM Crashing PC #357

Closed
NickoliVolkolf opened this issue Apr 7, 2021 · 13 comments
Closed

[BUG] RC QM Crashing PC #357

NickoliVolkolf opened this issue Apr 7, 2021 · 13 comments
Labels
bug Something isn't working resolved Problem resolved or will be resolved in next version.

Comments

@NickoliVolkolf
Copy link

Describe the bug
Black screen freezing PC entirely within 5 minutes of starting quickminer.

To Reproduce
Turn on mining using 0.4.6.x

Expected behavior
For QM to not crash my PC. It just started with the RC from yesterday .6.0. Also tested using .6.5, same issue.

Version affected (please complete the following information):

  • RC .0.4.6.0
  • RC .0.4.6.5

Hardware
EVGA 3080 FTW3 Ultra, direct to PCI 3.0

Logs
Attached, I don't see anything really.
log.txt

Additional context
I downgraded to the latest Stable and it is running fine. You'll see that in the logs as well.

@NickoliVolkolf NickoliVolkolf added the bug Something isn't working label Apr 7, 2021
@nicehashdev
Copy link
Contributor

According to provided log, I would say you had issues with Excavator getting blocked by AV.

Also, can you provide all logs (including excavator logs).

@NickoliVolkolf
Copy link
Author

Attached are the logs. I haven't changed anything AV wise, the whole folder is excluded as it has been from day 1 using QM. I've been mining on the latest stable since I opened this without any changes to the AV.
excavator_log_2021-04-07_12-41-55.001.txt
excavator_log_2021-04-07_12-39-25.000.txt

@nicehashdev
Copy link
Contributor

That is the problem; making exclusion is not enough, you need to "allow on device". Then it stops getting targeted by Defender.

@nicehashdev
Copy link
Contributor

What is common for both logs you submitted is that speed goes to 0 before whatever happens. I am 99% sure it is Defender blocking Excavator. Make sure you allow it. Here is procedure how to do it: #204

@NickoliVolkolf
Copy link
Author

I have defender off, including the firewall. Was something changed in the latest RC that would be causing it. I haven't touched anything since I started using QM in v0.3.0.6_RC (besides updating when prompted)

@nicehashdev
Copy link
Contributor

I will repeat again; it does not help to have defender off or to have exclusion list. It would still block it unless you make "allow on device" exception for exactly that excavator.exe. It is a (intentional) bug by Microsoft to make mining very hard on PC.

@NickoliVolkolf
Copy link
Author

You're missing the point of the bug ticket. It was fine for 2 months, now in the RC it isn't working. A generic defender causing it doesn't explain it. Unless there is a new excavator.exe packaged with the latest RC. If you want to close it with that, its up to you. I'll just stick to the stable version as I have no issues with it. And If you have defender off, there isn't a way to make an exception to a software that isn't running in the first place.

@nicehashdev
Copy link
Contributor

Yes, there is new excavator.exe packed with it. In every new version, there is most likely new excavator.exe packed in because changes and updates are needed there too.

@NickoliVolkolf
Copy link
Author

I'll upgrade to the latest RC again tonight and post the logs (with reputation based turned off). There isn't a way to exclude in defender as it isn't on. I don't see how excavator crashing/being blocked causes a PC to hard lock and need rebooted. But either way Thank you for your time. I'll post logs later.

@nicehashdev
Copy link
Contributor

There is new RC version which is built using latest CUDA version (11.2 update2) which shall hopefully resolve all the unexplained errors. Try it please and report back.

@NickoliVolkolf
Copy link
Author

So far so good. Been mining for about 20 minutes with no issues. I'll close this in an hour or so if everything continues to be fine. Thanks!

@nicehashdev
Copy link
Contributor

Okay good. Glad your problem is fixed.

@nicehashdev nicehashdev added the resolved Problem resolved or will be resolved in next version. label Apr 8, 2021
@NickoliVolkolf
Copy link
Author

Yep still good. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working resolved Problem resolved or will be resolved in next version.
Projects
None yet
Development

No branches or pull requests

2 participants