New
#31
The latest dump looks similar to the others.
Just ran Torrex on an Ethernet connection for over 3 hours while I took a young lady for dinner and no BSODs. The problem is obviously specific to the wireless connection. I cannot continue on Ethernet because I cannot use my printers and cannot move the laptop.
Tell me when you give up so I can move this issue to HP.
Wouldn't it make more sense to contact the Torrex developer? Lots of times software is the cause and only manifests a Stop at the hardware level.
Or... you can contact Broadcom, HP, and Torrex - they'll all point fingers, but one might actually help with a setting or an eventual patch.
A full dump might tell you more, but I'm no longer a dump reader (too old ... )
The problem is I contacted Torrex and they sent me a beta which is now an update but it made no difference. Also to be fair to them Torrex works on my Lenovo wifi and works on the HP Ethernet. Obviously the problem lies with Broadcom or HP.
I was hoping you came across this problem before and know of a setting or patch that I can apply.
I will revert to HP because the Broadcom site is not designed for consumers.
Good morning, Its an upgrade from 8.1 but it was bought directly from HP online store and the win 10 update came out 1 month later. As you can tell from the specs the laptop was not off-the-shelf so I did order the fastest, biggest, best etc... when I defined the specs.
I only began using Torrex after updating to win 10 because bittorrent began crashing about midway through this year (some dubious windows update).
For info Torrex has been running on the HP all night on Ethernet without a single BSOD. Probably is certainly to do with Wifi
Good troubleshooting.
Here's what I would do:
Compare the configurations on both machines (Torrex and IP).
This is difficult to troubleshoot in a forum, but since you have one machine that doesn't BSOD, you might find something on the Lenovo that is not set or set differently on the HP. It's a pain, but ...
On both machines:
Command promptCompare the settings.
ipconfig /all
On the HP - try: Network Adapters - Cleanup and Reset in Windows 10 - Windows 10 Forums
A catchall thread on network issues: Solved Resolve network issues - Windows 10 Forums
Test another torrent pgm to see if there is a generic issue with the WiFi adapter or the settings
-> qBittorrent official website
As a last ditch effort, I'd backup my machine and clean install Win10:
Sorry I can't be more specific on the issue, but there are many things that could affect the issue.
I've run out of suggestions, best of luck.
Bill
.
Hello,
Just for those who have a similar problem and are watching this thread, I have tested Bittorrent and utorrent both with the same result.
The most obvious difference between the Lenovo and HP is that the Lenovo does not use the Broadcom driver.
I already did a clean re-install when we started this thread based on your instructions, (check the beginning of this thread).
I will try the cleanup of the network etc... if it is resolved I will post on this thread. Meanwhile I have been running Torrex on the HP since this morning with ethernet and there are no BSODs.
Thanks for the update and sorry about the clean install suggestion (sometimes I post while I'm thinking about the issue and don't re-read the thread )
A few other things come to mind and then I really am out of ideas.
Try disabling the Bluetooth adapter - there were issues a while back with anything BT.
You might wnat to buy a good but inexpensive USB wireless adapter. I picked up an ASUS USB-N53 for $30 because the BCM half card in my HP was terrible.
Ok, I'll see how your thread turns out.
Again, best of luck.
Bill
.
I believe I have a solution though I think it is temporary. I went to the adaptor driver and found 3 previous HP provided drivers, all still resulted in BSOD. There was a driver without a reference number which I believe is the bundled windows generic driver. I installed that and it seems my problem is solved without any deterioration in download speed and 2 hours later no BSOD.
I said I is temporary because sooner or later HP will come up with a driver that actually works!
FYI