No warning, no messages - just rebooted the system like I'd selected "restart."
Since this is the 1st app - portable or otherwise - that's completely crashed Vista (or any I remember on XP), it's very unusual.
Anyone else seen this problem w/ the new v3.0.0?
2nd) Is there a "real" manual for qBittorrent? Not one w/ portable pkg. Before it crashed, when I clicked on Help > ? user manual (not sure what it said), just linked to official qBT help page, which is pretty thin. Haven't found a manual on their site either.
Thanks.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
An app can't crash a modern Windows OS on its own unless something is wrong with it. Typically, the fault lies in drivers, generally graphics drivers. The app most responsible for finding errors in graphics drivers is a web browser, so a torrent client triggering it is a bit unusual. Try updating your graphics drivers. And be sure Windows is fully up to date.
Sometimes, the impossible can become possible, if you're awesome!
LOL
- that's a good one... "apps can't crash an OS." I won't go into why that's not true.
But, for others' - my GPU drivers are up to date & so is Vista. And Fx works fine - never crashes.
When your OS has NEVER crashed, after installing/ uninstalling hundreds of apps, then suddenly crashes w/ a new one... pretty suspicious.
Modern Windows OS is designed so that apps can not crash it. They're in their own spaces so when they crash, they can't affect anything else. The only thing that can normally crash an OS is something running at the lower system level like a driver. The most common 'apps' to crash modern Windows are browsers and games, nearly always due to buggy display drivers. Especially on laptops (which have notoriously bad display drivers). Firefox has specifically added code to their browser to prevent badly written Nvidia display drivers from crashing, for instance. Did you check the event log to see why Windows crashed?
When an app used by hundreds of thousands of people without issue crashes only your PC, there's reason to be suspicious.
Sometimes, the impossible can become possible, if you're awesome!
No, there's nothing in Event Viewer to indicate anything specific that caused a crash, AFAICT. Nothing that said, so & so happened & windows is / must shut down. Only an entry that "the previous system shutdown was unexpected." I have a UPS, so the power didn't go off.
Whether or not the part about "apps are in their own space," is true, the statement to the effect, "you're the 1st one that's ever called (our tech support center) w/ this problem," means nothing to me. I've had hundreds of people tell me similar, about ALL SORTS of things - only to find out I wasn't "the only one."
I'll give it another go & see what happens.
Other question - what about a user manual?
EDIT: TRIED 'ER AGAIN. 1st time since crashed last nite. Started it & it gave (I read common) msg: qBT didn't shut down properly. It will now clean up. Then restart it manually."
Did its thing & closed (or I closed when it finished). Then started it again. IT CRASHED VISTA IMMEDIATELY, AS IN 1 SEC - AGAIN. If I had ANY crashes w/ ANY other apps, or just Vista, I might agree w/ you - but I don't. It ain't no co-inky-dink that it's crashed 2x - starting qBT, but NOT w/ any other apps starting / running.
This time the error for qBT in event viewer was:
The entry \APPDATA\LOCAL\QBITTORRENT\CACHE> in the hash map cannot be updated.
Context: Application, SystemIndex Catalog
Details:
A device attached to the system is not functioning. (0x8007001f)
I looked in that cache & there's 1 torrent file from last night- that's it. BTW, before d/l'g w/ qBT, I changed the file & torrent d/l paths in options, but it obviously didn't pay attention.
Don't know what "device" not functioning is. It's not the HDD where the cache is, cause other apps are writing to it.
If qBT is the only app I've tried that has a problem w/ Nvidia drivers (cause nothin' else crashes), too bad. Seems unlikely since no other app - commercial or free - crashes.
As far as, "qBT being in its own space," how do I know how qBT (or the portable) is written? I'll agree MOST times, apps don't crash Windows. But "never" is a long time.
Any properly written modern OS is setup so that apps running in userspace can't crash it. True there are resource issues it can exploit, but a full-on crash should not happen. If it does, it's either purposely exploiting a known Windows bug (and there used to be some you could trigger with Notepad) or a bug in a driver or something else attached that is triggering it. As no one else has this issue and we've supported qBittorrent for over a year and a half. Not to mention the fact that qBittorrent the base app has been around since 2006 (1.7m downloads). Couple all that with the fact that you see a "device" error in your log, and something is definitely up with your system. Figuring out what is more complex.
It doesn't matter how qB is written, it can't access anything nasty in your system without you allowing it to via admin rights, anyway.
In Firefox vs graphics drivers, it was due to it using hardware acceleration. The fix was to either disable hardware acceleration or fix your graphics driver. Perhaps since qBittorrent is a Qt app it's using some hardware APIs that other apps don't, say to determine what drives are on your system or similar. Something the app doesn't need but the framework accesses. I'm not sure what it is, but the root cause is something in your system or drivers. qBittorrent just happens to be triggering the problem.
Sometimes, the impossible can become possible, if you're awesome!
Thanks John. Apps vs OS vs semantics. Yes, there's a difference. End result same. qBT is only app to crash system. Not impossible, but hard to imagine it's written to use something that NO other app, even BT clients, have ever used (& crashed) - in yrs.
Be great if qBT had log file / err reporting capability.
Windows err codes have been notoriously cryptic (& often plain wrong) about the "real" problem. So are many apps' error reporting. The msg, "device attached to the system is not functioning," is common as dirt. In dozens of posts on MS, none had solutions listed.
Ran sfc /scannow. Aside from tons of winsxs lines, on thing said was repairing (or was corrupt):
Will reboot now & see if qBT still crashes. Unless some dev is willing to pursue this w/ me, after these last steps, & considering nothing else has a problem, not worth spending hours / days.
EVEN IF I were only one to have this problem - EXTREMELY unlikely (many users don't bother troubleshooting; if app doesn't work, just uninstall / del it.), you assume it's problem w/ Vista & not a qBT problem. If for Ex., qBT (any app) is looking for a rarely used Windows file & doesn't find it / not vers. expected, but doesn't give an intelligible error, that's as much an app problem as Windows. Error logs!
Even if qBittorrent had logs, it wouldn't log the crash since it isn't qBittorrent crashing, it's Windows. qBittorrent isn't crashing. If qBittorrent crashed, it would either go unresponsive, shutdown, or close outright with an error being reported. That's what an app crash looks like. But that's not happening here.
qBittorrent is causing Windows to crash. And the only way it can do that is if something is wrong somewhere in Windows (corrupted files, bad driver, corrupted registry, Windows bug, etc) that qBittorrent is hitting directly or triggering via something else (like antivirus, software firewall since it attempts to establish a listener, etc). It's not a 'Vista problem' as qBittorrent Portable works perfectly fine on Vista (see here). It's a problem with your specific setup, either hardware or software.
It's not something that's in our realm of responsibility (it's not a portable problem), I'm just trying to help you determine your issue.
Sometimes, the impossible can become possible, if you're awesome!
Either it's too soon to tell; that del stranded torrent file from cache; sfc replacing one corrupted file or all the above - has stopped the crashing for now. NOT yet tried d/l'g a torrent file.
Need more info. Will start another post on options.
Thanks.