From f57d942c3ab18a9ac4433f0ef4ea2f56393aedb7 Mon Sep 17 00:00:00 2001 From: "Bruce A. Mah" Date: Tue, 17 Oct 2017 10:32:19 -0700 Subject: [PATCH] Add to FAQ an entry about BSODs under Windows 7. This question has come up a few times, so even though iperf3 doesn't officially support any Windows platform, I'm putting this in here. Thanks to @ijspzpt for the references. Addresses #590 and possibly #546. --- docs/faq.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/faq.rst b/docs/faq.rst index 5c7e17f..334a894 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -93,6 +93,17 @@ I'm using the --fq-rate flag, but it does not seem to be working. Why? I'm having trouble getting iperf3 to work on Windows, Android, etc. Where can I get help? iperf3 only supports Linux, FreeBSD, and OSX. For other platforms we recommend using iperf2. +I managed to get a Windows executable built, but why do I get a BSOD on Windows 7? + There seems to be a bug in Windows 7 where running iperf3 from a + network filesystem can cause a system crash (in other words Blue + Screen of Death, or BSOD). This is a Windows bug addressed in kb2839149: + + https://support.microsoft.com/en-us/help/2839149/stop-error-0x00000027-in-the-rdbss-sys-process-in-windows-7-or-windows + + A hotfix is available under kb2732673: + + https://support.microsoft.com/en-us/help/2732673/-delayed-write-failed-error-message-when--pst-files-are-stored-on-a-ne + Why can’t I run a UDP client with no server? This is potentially dangerous, and an attacker could use this for a denial of service attack. We don't want iperf3 to be an attack tool.