-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Crash in Windows 10 #12976
Comments
Does this also happen on an English Windows system? |
How should i know that? |
Setting ur system to English? |
Please provide version info. |
The version is shown in the log posted above among other info, it is 4.2.5.0, as for Windows the latest updated W10 Pro 64. |
We need at least a crash dump. For this, you need to tell Windows to create crash dumps in the first place: |
@treysis I'm sorry but i'm not going to do all that you ask. They are beyond my capabilities and also a bit on the risk side for my working pc. |
@dimalif Would you at least be willing to attach a debugger with pre-defined rules? This will hopefully provide a usable |
@xavier2k6 Sure, if you tell me how. |
Persistent crashes when downloading at high speed (25Mb/s). Crash dump: https://yadi.sk/d/_J8cEkIhkiBkrg |
Oh yes, I noticed something maybe related/similar. While I was testing something, I was running two bittorrent clients on my PC. So qBittorrent would download from the other. Being on the same machine, that resulted in high speeds. But qBittorrent would soon become irresponsive and needed to be forced closed. I could only see that speeds at the moment before freezing were around 32 MB/sec. |
I've looked at the crash dump, there's not much info to go on except that you received an exception |
Please download & install Debug Diagnostic Tool v2 Update 3 Download & extract these predefined rules Run DebugDiag 2 Collection from your start menu. This will hopefully help point us in the right direction to where there's a problem in the program. Your memory usage will probably increase more so than normal & the program itself may become unresponsive for a period of time due to having a debugger attached. As soon as a stacktrace is created, it will be ok to deactivate the rules & close/detach the debugger from qBittorrent |
@xavier2k6 I will do that and hope (and wait) until those happen again, because it is random. |
Most likely faulty drivers or hardware or some other issue. I routinely download at 50-100 MiB/s (500 Mbps - 1 Gbps) on multiple systems running both Linux and Windows, and running hardware as far back as 2008 without issues. |
@skidaddl3 you are experiencing a different crash to this issue, OP is getting If issue persists, please open a new issue with Crash Exception code: 0xc0000409 in the title. |
@xavier2k6 I am running the SFC test now. I have reduced the "Outstanding memory when checking torrents" from 1024MiB to 64MiB |
@FranciscoPombal this can probably be closed now as there's been no update in relation to stacktrace & OP is running 4.3.1 now, ref: #13992 @dimalif did you experience this again at any stage/manage to grab a stack trace?? |
@xavier2k6 Nope, the issue is gone. |
|
Please provide the following information
qBittorrent version and Operating System
Windows 10/64bit Pro GR
What is the problem
Sudden freeze of Windows for 1-2 minutes and then it continues. The freeze happened twice, 1st time when starting Qbit and an other time while running. The event log below is when freezed while STARTING qbit.
Extra info(if any)
The error from Windows 10 events
Όνομα ελαττωματικής εφαρμογής: qbittorrent.exe, έκδοση 4.2.5.0, χρονική σήμανση: 0x5ea37cc6
Όνομα ελαττωματικής λειτουργικής μονάδας: qbittorrent.exe, έκδοση: 4.2.5.0, χρονική σήμανση: 0x5ea37cc6
Κωδικός εξαίρεσης: 0xc0000005
Μετατόπιση σφάλματος: 0x00000000002bbee7
Αναγνωριστικό ελαττωματικής διεργασίας: 0x1f68
Χρόνος έναρξης ελαττωματικής εφαρμογής: 0x01d63ac91fb14c74
Διαδρομή ελαττωματικής εφαρμογής: C:\Program Files\qBittorrent\qbittorrent.exe
Διαδρομή ελαττωματικής λειτουργικής μονάδας:C:\Program Files\qBittorrent\qbittorrent.exe
The text was updated successfully, but these errors were encountered: