David Byers Posted March 8, 2019 Share Posted March 8, 2019 Plugging the plunder bug in to my Windows 10 laptop causes a BSoD with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED every time. Booting with the bug already connected worked, but unplugging it caused a BSoD. Similar on a colleague's laptop that has a lot less cruft on it than mine. Anyone see the same and have any ideas on what might be going on? Sad, because apart from crashing our Windows boxes, it really works great 🙂 Quote Link to comment Share on other sites More sharing options...
Darren Kitchen Posted March 8, 2019 Share Posted March 8, 2019 That is really strange. I've never seen this happen. It works perfectly on all of my Windows boxes. Do you happen to have a WiFi Pineapple NANO - because if that works with the Windows boxes I'm even more at a loss since they share the same ASIX chipset. Is anyone else experiencing this?  Quote Link to comment Share on other sites More sharing options...
David Byers Posted March 9, 2019 Author Share Posted March 9, 2019 I haven't tried any other devices with the same chipset. Reproducible on two devices (nobody else would let me try), consistently. Will try on a clean install from media week after next, then on a clean corporate install. Quote Link to comment Share on other sites More sharing options...
Darren Kitchen Posted March 13, 2019 Share Posted March 13, 2019 @David Byers I'm keen to get your particular unit in for testing. Please send an email to shop@hak5.org indicating such and linking to this post. Our customer service folks will send you a return label and ship a replacement. Quote Link to comment Share on other sites More sharing options...
David Byers Posted March 14, 2019 Author Share Posted March 14, 2019 I'll be in touch with them in due course. I have two units and want to test both in a clean corporate and a clean vanilla Windows 10 install, and on a non-HP laptop. Quote Link to comment Share on other sites More sharing options...
David Byers Posted March 25, 2019 Author Share Posted March 25, 2019 We have two corporate Windows 10 images -- old and new. The old one bluescreens reliably when we connect or disconnect the plunder bug. The new one doesn't and neither do clean-from-media installs of Windows 10. We're going to do some more testing to see if we can figure out what about the old image is causing an issue with the bug. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.