BSOD - 64 bit version > 4.2.1 or so?

Windows specific questions, problems.
Post Reply
Microfiche62
Newbie
Newbie
Posts: 1
Joined: Sun Nov 15, 2020 1:10 pm

BSOD - 64 bit version > 4.2.1 or so?

Post by Microfiche62 »

Using PIA v 2.5.1 and Win 10 home v 2004
I did not get the bugcheck code when Windows crashed - it was late. I think it was a bad memory request.
Within a few moments of downloading using Qbittorrent 4.3.0.1, I would get BSOD
I rebooted, tried again, same result.
Then I recalled this had happened to me a while back after a qbittorrent upgrade and I had to downgrade to get it to work.
I didn't remember how far back I had to downgrade, so I uninstalled 4.3.0.1 and installed 4.2.3
Exact same result.
Uninstalled 4.2.3 and went back to 4.2.1 and it works smoothly again - ran for hours with no issues.
I just returned from a trip, so I was gone for a few weeks and had not been using qbittorrent, unfortunately I don't recall when this happened to me before, or what version I had to go back to previously.
Before I submitted to Github as a possible bug, thought I would check here to see if anyone had ideas?
I have been using qbittorent with the settings I currently have in place for years, and I didn't change any settings during the most recent installs and uninstalls. Nothing else change except for the normal hourly Windows updates...
User avatar
Peter
Administrator
Administrator
Posts: 1915
Joined: Wed Jul 07, 2010 6:14 pm

Re: BSOD - 64 bit version > 4.2.1 or so?

Post by Peter »

Whenever you get a BSOD, your memory is written out if you wait long enough.
MEMORY.DMP is in C:\Windows\System32\

Just copy it out and then use that to debug the BSOD.
1) Install WinDBG preview from store, no need for the winsdk
2) Set symbol path to ms servers ( https://www.instructables.com/How-to-An ... rash-Dump/ )
3) Open the dump, debug as instructed
4) See the real culprit

if you can't tell, you can post info here and we might take a guess too.
alexandrebr
Newbie
Newbie
Posts: 2
Joined: Fri Nov 27, 2020 7:48 am

Re: BSOD - 64 bit version > 4.2.1 or so?

Post by alexandrebr »

Microfiche62 wrote: Sun Nov 15, 2020 1:30 pm Using PIA v 2.5.1 and Win 10 home v 2004
I did not get the bugcheck code when Windows crashed - it was late. I think it was a bad memory request.
Within a few moments of downloading using Qbittorrent 4.3.0.1, I would get BSOD
I rebooted, tried again, same result.
Then I recalled this had happened to me a while back after a qbittorrent upgrade and I had to downgrade to get it to work.
I didn't remember how far back I had to downgrade, so I uninstalled 4.3.0.1 and installed 4.2.3
Exact same result.
Uninstalled 4.2.3 and went back to 4.2.1 and it works smoothly again - ran for hours with no issues.
I just returned from a trip, so I was gone for a few weeks and had not been using qbittorrent, unfortunately I don't recall when this happened to me before, or what version I had to go back to previously.
Before I submitted to Github as a possible bug, thought I would check here to see if anyone had ideas?
I have been using qbittorent with the settings I currently have in place for years, and I didn't change any settings during the most recent installs and uninstalls. Nothing else change except for the normal hourly Windows updates...
I've been facing the same issue. In my case, the problem happens if I have Kaspersky Total Security installed.
even2204133
Newbie
Newbie
Posts: 1
Joined: Mon Nov 23, 2020 9:33 am

Re: BSOD - 64 bit version > 4.2.1 or so?

Post by even2204133 »

Same issue here.
Also have Kaspersky Internet Security installed.
alexandrebr
Newbie
Newbie
Posts: 2
Joined: Fri Nov 27, 2020 7:48 am

Re: BSOD - 64 bit version > 4.2.1 or so?

Post by alexandrebr »

even2204133 wrote: Fri Nov 27, 2020 4:21 pm Same issue here.
Also have Kaspersky Internet Security installed.
Then we may say that Kaspersky is the real issue. If you uninstall KIS with Kavremvr and do a fresh install of KIS/KTS, maybe you'll notice the issue won't happen immediately. At least if you use the 2020 version. After some time, I think KIS/KTS gets updates and, suddenly, klids.sys (Kaspersky driver) starts freezing the system. WhoCrashed pointed that driver as the cause.

I've created a support ticket and, after sending some data, I'm waiting for a solution.
Post Reply