squidy/qBittorrent
1
0
Fork 0
mirror of https://github.com/qbittorrent/qBittorrent.git synced 2025-12-23 16:58:06 -06:00
Code Issues Packages Projects Releases Wiki Activity

Updated How to diagnostic IO error, BSOD, crash [Windows] (markdown)

Duke
2017-01-20 11:27:07 +01:00
parent 35b3aa9488
commit 8c58aabdae
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
How-to-diagnostic-IO-error,-BSOD,-crash-[Windows].md

@@ -1,8 +1,7 @@
# This wiki page is still work in progress! Please, check back later.
Version 0.2.2
## qBittorrent gave you a lockup or BSOD (Blue Screen of Death). Now what? ## qBittorrent gave you a lockup or BSOD (Blue Screen of Death). Now what?
First of all, if you get a BSOD, and it's not `irql_not_less_or_equal`, there is a good chance you will be able to debug the BSOD. It is a very powerful and useful tool to find why your Windows system just crashed.
Well, the thing is, it was not qBittorrent. Well, the thing is, it was not qBittorrent.
There are four major things that can cause a freeze or BSOD. There are four major things that can cause a freeze or BSOD.
The numbers mean how hard is it to check on a scale of 5. The numbers mean how hard is it to check on a scale of 5.
@@ -29,6 +28,8 @@ The `c:\symbols` will be your local symbol cache. I would suggest using somethin
4. File -> Open Crash Dump. 4. File -> Open Crash Dump.
5. Navigate to `C:\Windows\` 5. Navigate to `C:\Windows\`
6. Open `memory.dmp` 6. Open `memory.dmp`
7. Wait. Once you see "Ready", use the `!analyze -v` command.
8. It will tell you the most likely culprit, but the other loaded things are also suspects. For me, the "most likely" thing was a Windows DLL, but my Avast file scanner service was also there. Removed Avast - boom - no BSOD ever since.
*** ***
@@ -104,4 +105,4 @@ Your PSU might also be able to deliver stable power during stress (not likely),
## Something else ## Something else
Check if the cables to your HDD/things are connected firmly, and they are not loose. This can also cause trouble. Check if the cables to your HDD/things are connected firmly, and they are not loose. This can also cause trouble.
If nothing helped, your motherboard can also be faulty. If nothing helped, your motherboard can also be faulty. An anti-virus can also cause BSOD, but it will show up with "windbg".