BSOD "Page fault in nonpaged area" #3730

Closed
opened 2026-02-21 16:55:56 -05:00 by deekerman · 18 comments
Owner

Originally created by @ghost on GitHub (Jan 16, 2016).

I get a BSOD when downloading large torrents with qbittorrent.

I am also sure it is the software. I have done HDD scans they are all fine, i have checked ram.
I also am using a different software now to download torrent and am not receiving the BSOD it is only with qbittorrent that it happens.

If you need any logs or more info i will be happy to provide it. (but tell me were to get it)

Originally created by @ghost on GitHub (Jan 16, 2016). I get a BSOD when downloading large torrents with qbittorrent. I am also sure it is the software. I have done HDD scans they are all fine, i have checked ram. I also am using a different software now to download torrent and am not receiving the BSOD it is only with qbittorrent that it happens. If you need any logs or more info i will be happy to provide it. (but tell me were to get it)
Author
Owner

@theTomaku commented on GitHub (Jan 16, 2016):

Related(?): #4536

I have exactly the same issue when I'm downloading big torrent file with qBittorrent, when I'm downloading small torrent file with qBittorrent I don't have any issues. This only happens with big torrent files.

I'm 100% sure of that this is only qBittorrent related issue, because I haven't had this issue with any other torrent application yet.

uTorrent - No BSOD
Bittorrent - No BSOD
Deluge - No BSOD
Transmission QT - No BSOD
Tixati - No BSOD
Vuze - No BSOD
FrostWire - No BSOD
qBittorrent - BSOD with both x86 and x64 build, and BSOD with 3.2.4, 3.2.5, 3.3.0 and 3.3.1.

Like I said, I get BSOD with qBittorrent only when I'm downloading a big torrent. I downloaded the same exact torrent with all of those torrent applications above and only qBittorrent gave me a BSOD. I don't have qBittorrent installed any longer, I got so frustrated so I did a clean install without qBittorrent. I have had this issue with 2 laptops and 1 pc, so it can not be a driver issue. It is qBittorrent's fault unfortunately.

@theTomaku commented on GitHub (Jan 16, 2016): Related(?): #4536 I have exactly the same issue when I'm downloading big torrent file with qBittorrent, when I'm downloading small torrent file with qBittorrent I don't have any issues. This only happens with big torrent files. I'm 100% sure of that this is only qBittorrent related issue, because I haven't had this issue with any other torrent application yet. uTorrent - No BSOD Bittorrent - No BSOD Deluge - No BSOD Transmission QT - No BSOD Tixati - No BSOD Vuze - No BSOD FrostWire - No BSOD qBittorrent - BSOD with both x86 and x64 build, and BSOD with 3.2.4, 3.2.5, 3.3.0 and 3.3.1. Like I said, I get BSOD with qBittorrent only when I'm downloading a big torrent. I downloaded the same exact torrent with all of those torrent applications above and only qBittorrent gave me a BSOD. I don't have qBittorrent installed any longer, I got so frustrated so I did a clean install without qBittorrent. I have had this issue with 2 laptops and 1 pc, so it can not be a driver issue. It is qBittorrent's fault unfortunately.
Author
Owner

@ghost commented on GitHub (Jan 16, 2016):

It could be a driver issue with qbittorrent. What is your network card and HDD or SSD.
This might help solve it.

Mine are
Samsung SSD 850 Evo
Asus Pce-AC68

@ghost commented on GitHub (Jan 16, 2016): It could be a driver issue with qbittorrent. What is your network card and HDD or SSD. This might help solve it. Mine are Samsung SSD 850 Evo Asus Pce-AC68
Author
Owner

@theTomaku commented on GitHub (Jan 16, 2016):

My SSD's are: 3x Samsung 850 EVO 250GB SSD RAID0 (OS)
My HDD is: Western Digital 2TB Caviar Green HDD (qBittorrent downloads)
My network card is: Intel Ethernet Connection (2) I218-V

Like I said, I have had this bug with 2 laptops and 1 pc.

@theTomaku commented on GitHub (Jan 16, 2016): My SSD's are: 3x Samsung 850 EVO 250GB SSD RAID0 (OS) My HDD is: Western Digital 2TB Caviar Green HDD (qBittorrent downloads) My network card is: Intel Ethernet Connection (2) I218-V Like I said, I have had this bug with 2 laptops and 1 pc.
Author
Owner

@ghost commented on GitHub (Jan 16, 2016):

And they all have a SSD? 850 Evo? xD
Btw i also download the qbittorrent to an HDD.

But qbittorrent is installed on the SSD.
I have the 1Tb though.

However if indeed you have that ssd on all your pc's and so do i maybe the problem lies in a conflict between that driver and qbittorrent?

It seems they need to look into that.
I like qbittorrent so i hope they will be able to find it.

@ghost commented on GitHub (Jan 16, 2016): And they all have a SSD? 850 Evo? xD Btw i also download the qbittorrent to an HDD. But qbittorrent is installed on the SSD. I have the 1Tb though. However if indeed you have that ssd on all your pc's and so do i maybe the problem lies in a conflict between that driver and qbittorrent? It seems they need to look into that. I like qbittorrent so i hope they will be able to find it.
Author
Owner

@theTomaku commented on GitHub (Jan 16, 2016):

No, different ssd's and hdd's. I had qBittorrent installed on the ssd and I put downloads on the hdd to save ssd's.

Edit:

@Bladeline

Can you please use Blue Screen View. Look at the latest .dmp-file listed in that program and look what is marked red. I don't have qBittorrent installed any longer and I did a clean install so I can not provide this nfo.

@theTomaku commented on GitHub (Jan 16, 2016): No, different ssd's and hdd's. I had qBittorrent installed on the ssd and I put downloads on the hdd to save ssd's. Edit: @Bladeline Can you please use [Blue Screen View](http://www.nirsoft.net/utils/blue_screen_view.html). Look at the latest .dmp-file listed in that program and look what is marked red. I don't have qBittorrent installed any longer and I did a clean install so I can not provide this nfo.
Author
Owner

@theTomaku commented on GitHub (Jan 19, 2016):

Any update?

@theTomaku commented on GitHub (Jan 19, 2016): Any update?
Author
Owner

@ghost commented on GitHub (Jan 20, 2016):

Sorry it has been a busy couple of days.
I tried but the window is empty is there something i need to do?
I just thought that opening it would be enough.

@ghost commented on GitHub (Jan 20, 2016): Sorry it has been a busy couple of days. I tried but the window is empty is there something i need to do? I just thought that opening it would be enough.
Author
Owner

@ghost commented on GitHub (Jan 31, 2016):

I recently got more BSOD and searched to the problem and i found out that for some reason my bios ram settings were not set to what they are supposed to be i fixed this and this should have solved my problem will let you know if i find anything else.

@ghost commented on GitHub (Jan 31, 2016): I recently got more BSOD and searched to the problem and i found out that for some reason my bios ram settings were not set to what they are supposed to be i fixed this and this should have solved my problem will let you know if i find anything else.
Author
Owner

@ghost commented on GitHub (Feb 1, 2016):

Seems that was not the sollution as it is not solved.

Now other torrent programs are also having this issue with me.
I think it is the Network driver it all started since i had this it is a PCE-AC68

I have done everything to try and fix this but it seems that i cannot as it is a problem in the driver itself. However Qbittorrent is the one that makes the BSOD happen the fastest for some reason.

Here are the 2 memory dumps i have from the BSOD:
Before reinstalling windows:
https://drive.google.com/file/d/0B_1hj6YFG6eSNlRTb2ZFTm1ETGs/view?usp=sharing
After reinstalling windows:
https://drive.google.com/file/d/0B_1hj6YFG6eSblRBdk83NThtT00/view?usp=sharing

@ghost commented on GitHub (Feb 1, 2016): Seems that was not the sollution as it is not solved. Now other torrent programs are also having this issue with me. I think it is the Network driver it all started since i had this it is a PCE-AC68 I have done everything to try and fix this but it seems that i cannot as it is a problem in the driver itself. However Qbittorrent is the one that makes the BSOD happen the fastest for some reason. Here are the 2 memory dumps i have from the BSOD: Before reinstalling windows: https://drive.google.com/file/d/0B_1hj6YFG6eSNlRTb2ZFTm1ETGs/view?usp=sharing After reinstalling windows: https://drive.google.com/file/d/0B_1hj6YFG6eSblRBdk83NThtT00/view?usp=sharing
Author
Owner

@jargon-au commented on GitHub (May 15, 2016):

Chiming in to say I have also encountered this issue on my Windows 10 PC, I'm also using a Samsung 850 SSD and have the PCE-AC56 wireless network card. Haven't had any issues until I tried to download a very large file (>20GB).

@jargon-au commented on GitHub (May 15, 2016): Chiming in to say I have also encountered this issue on my Windows 10 PC, I'm also using a Samsung 850 SSD and have the PCE-AC56 wireless network card. Haven't had any issues until I tried to download a very large file (>20GB).
Author
Owner

@ADTC commented on GitHub (May 20, 2016):

Upgraded from Windows 7 Professional to Windows 10 Pro. On Windows 7 I didn't have any problem with qB. But on Windows 10, the qB (which was migrated) caused a BSOD through the wireless card driver. IRQL_NOT_LESS_THAN_OR_EQUAL (NETwew01.sys). I traced this driver file and it's definitely used by the wireless card.

If I'm not wrong, qB does mess with the network settings and such, and I'm suspecting it does so at a low level, directly accessing and manipulating the network cards and their drivers. Is that so?

Windows 10 never BSODed when qB was not running at all, and I have switched between several wireless networks, turned off and on the wireless setting, put the computer on sleep and resume several times, and have not shut down for nearly 3 days now. But it BSOD twice, both times I ran qB and left it running to download a torrrent. In a few hours, I come back to check and the screen is blue with a big :( face. I knew it has to be qB.

I updated to the latest qB but after reading the above, I'm afraid to run it. Should I just go look for an alternative?

@ADTC commented on GitHub (May 20, 2016): Upgraded from Windows 7 Professional to Windows 10 Pro. On Windows 7 I didn't have any problem with qB. But on Windows 10, the qB (which was migrated) caused a BSOD through the wireless card driver. `IRQL_NOT_LESS_THAN_OR_EQUAL (NETwew01.sys)`. I traced this driver file and it's definitely used by the wireless card. If I'm not wrong, qB does mess with the network settings and such, and I'm suspecting it does so at a low level, directly accessing and manipulating the network cards and their drivers. Is that so? Windows 10 never BSODed when qB was not running at all, and I have switched between several wireless networks, turned off and on the wireless setting, put the computer on sleep and resume several times, and have not shut down for nearly 3 days now. But it BSOD twice, both times I ran qB and left it running to download a torrrent. In a few hours, I come back to check and the screen is blue with a big `:(` face. I knew it has to be qB. I updated to the latest qB but after reading the above, I'm afraid to run it. Should I just go look for an alternative?
Author
Owner

@ghost commented on GitHub (May 20, 2016):

The problem is with the driver of the Pce-AC68 I have installed a older version and the issue was resolved.

@ghost commented on GitHub (May 20, 2016): The problem is with the driver of the Pce-AC68 I have installed a older version and the issue was resolved.
Author
Owner

@ADTC commented on GitHub (May 20, 2016):

You closed the issue because you managed to resolve it in a way that is unique to you? What about everyone else facing the same problem?

@ADTC commented on GitHub (May 20, 2016): You closed the issue because you managed to resolve it in a way that is unique to you? What about everyone else facing the same problem?
Author
Owner

@ghost commented on GitHub (May 20, 2016):

I closed it because i can't even tell if we have The same problem you have said that you traced it to your wireless card without mentioning what card you have. Also it could be a combination between The ssd 850 Evo and The pce-ac68 so if you fid not mention any hardware i could not compare our problems.

If you have a pce-ac68 just downgrade The driver and The problem will be resolved if it Does not you have another issue that i can't really help you with without More info

@ghost commented on GitHub (May 20, 2016): I closed it because i can't even tell if we have The same problem you have said that you traced it to your wireless card without mentioning what card you have. Also it could be a combination between The ssd 850 Evo and The pce-ac68 so if you fid not mention any hardware i could not compare our problems. If you have a pce-ac68 just downgrade The driver and The problem will be resolved if it Does not you have another issue that i can't really help you with without More info
Author
Owner

@ADTC commented on GitHub (May 21, 2016):

Sorry I have not. My card is Intel Centrino Wireless-N 2230 on driver from Intel version 15.18.0.1 2015-04-30. Even updating to the latest driver (from 15.16.x) didn't help - in fact, that's what I did after the first BSOD.

I had left the computer on overnight for 12 hours straight without qB running and it's totally fine, no BSOD whatsoever. In both times that BSOD occured in the past, qB was running for just a few hours.

Please reopen, it's not related to a particular network interface. This is a problem with qB itself, and could be a horrible bug in the communication among various network drivers, Windows 10 and qB.

@ADTC commented on GitHub (May 21, 2016): Sorry I have not. My card is **Intel Centrino Wireless-N 2230** on driver from Intel version 15.18.0.1 2015-04-30. Even updating to the latest driver (from 15.16.x) didn't help - in fact, that's what I did after the first BSOD. I had left the computer on overnight for 12 hours straight without qB running and it's totally fine, no BSOD whatsoever. In both times that BSOD occured in the past, qB was running for just a few hours. Please reopen, it's not related to a particular network interface. This is a problem with qB itself, and could be a horrible bug in the communication among various network drivers, Windows 10 and qB.
Author
Owner

@jargon-au commented on GitHub (Jun 3, 2016):

An update on my case, I uninstalled all of the drivers for my wireless card and restarted my PC. Windows 10 automatically added Broadcom drivers from 2013 and enabled the wireless card and my issue is gone. The drivers provided by Asus are not suitable for Windows 10 it seems.

@jargon-au commented on GitHub (Jun 3, 2016): An update on my case, I uninstalled all of the drivers for my wireless card and restarted my PC. Windows 10 automatically added Broadcom drivers from 2013 and enabled the wireless card and my issue is gone. The drivers provided by Asus are not suitable for Windows 10 it seems.
Author
Owner

@KevinSkull commented on GitHub (May 28, 2017):

Anyone using PCE-A68 the older drive version is he talking about is Version 2.0.8.8 here

https://www.asus.com/ie/Networking/PCEAC68/HelpDesk_Download/

Fixed my problems with that error with no restarts needed

@KevinSkull commented on GitHub (May 28, 2017): Anyone using PCE-A68 the older drive version is he talking about is Version 2.0.8.8 here https://www.asus.com/ie/Networking/PCEAC68/HelpDesk_Download/ Fixed my problems with that error with no restarts needed
Author
Owner

@Revan1985 commented on GitHub (Jun 29, 2017):

Last PCE-AC68 seems to have solved the problem for me...
Are 2 minutes that i have opened the qbittorrent and i got no more BSOD (before after seconds the pc crashes)...

@Revan1985 commented on GitHub (Jun 29, 2017): Last PCE-AC68 seems to have solved the problem for me... Are 2 minutes that i have opened the qbittorrent and i got no more BSOD (before after seconds the pc crashes)...
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#3730
No description provided.