3.45.1 - NETUI.exe Bluescreen after partial transfer

Come here to discuss FileZilla and FTP in general

Moderator: Project members

Post Reply
Message
Author
PatrickM
500 Command not understood
Posts: 3
Joined: 2019-10-13 14:18
First name: Patrick
Last name: McKnight

3.45.1 - NETUI.exe Bluescreen after partial transfer

#1 Post by PatrickM » 2019-10-13 14:27

I get a bluescreen several minutes after transfer is started. Multiple tries result the same. Since I cannot access last running version for download, I am dead in the water.

FileZilla Client
----------------

Version: 3.45.1

Build information:
Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-pc-linux-gnu
Build date: 2019-09-25
Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406
Compiler flags: -g -O2 -Wall

Linked against:
wxWidgets: 3.0.5
SQLite: 3.29.0
GnuTLS: 3.6.9

Operating system:
Name: Windows 7 (build 7601, Service Pack 1), 64-bit edition
Version: 6.1
Platform: 64-bit system
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 lm
Settings dir: C:\Users\patm\AppData\Roaming\FileZilla\

User avatar
botg
Site Admin
Posts: 35558
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse

Re: 3.45.1 - NETUI.exe Bluescreen after partial transfer

#2 Post by botg » 2019-10-14 07:08

Normal programs cannot cause bluescreens, the very design of modern operating system is there to prevent this.

This means that there's something wrong with your system. Could be corrupt system files or a bad driver. Last but not least, it could also be faulty hardware.

PatrickM
500 Command not understood
Posts: 3
Joined: 2019-10-13 14:18
First name: Patrick
Last name: McKnight

Re: 3.45.1 - NETUI.exe Bluescreen after partial transfer

#3 Post by PatrickM » 2019-10-16 20:48

FYI
Reinstalled latest bios and drivers, which didn't help, still got bluescreen when running FileZilla.
Rebooted again in "Safemode with Networking". FileZilla ran correctly.
Rebooted in normal mode.
Uninstalled latest 'System Mechanic Ultimate'
FileZilla ran correctly.
It turns out that the latest System Mechanic Ultimate 19.5 was causing the problem.

Hope this helps others...

Post Reply