it just sounds like some kind of midi feedback loop to me which can very easily crash your system. had the same issue with some bad code in my own midimasher app the other week - so put in some extra code to drop events if it sees too many coming per second.
you 100% sure you have midi in/out devices set correctly? and no silly things like the all-ports option that traktor has etc?
quick tests… do crashes happen when you don’t have any midi-out port set to the launchpad, i.e: to stop leds lighting up and then have u tried something like bomes midi keyboard that would let you route midi input from say a nanokey to the input of the lp. if u can do that does pressing keys on the nanokey make the leds light up on the lp without any issues…
I tried running midikatapult. Same crash.
It is indeed a LED problem.
If I cut the output from traktor, then I can use it. But hard to navigate on a 8 page layout on 64 button grid (512 buttons in total) without any LED Feedback.
and u have the in and out ports set explicitly to the lp, no other tsi’s sitting around using all-ports and no other devices/apps that could be affecting it somehow? shouldnt be able to connect any extra apps anyway to the lp ports if they’re explicitely connected to the real lp ports.
the lp itself shouldnt be sending any data back just when it gets input over midi - but still sounds like a feedback loop
it happens with or without automap and with or without katapult.
All my traktor mapping is completely from scratch and I didn’t screw it up (works perfectly on OSX) I wonder if it has something to do with the USB controller?
I haven’t tried to do it with no traktor output mappings (for LEDs) but I might for giggles… I’ll make a new map from scratch on the laptop and see what happens - and if it works, I’ll see if it crashes when I program an output to an LED… I’m not optimistic though 
so u DO have the lp in and out ports selected explicitly and no other mappings loaded that are set to all ports?
afaik, because when I mapped it manually I set them all to channel 1.
The control is set to accept and send not to/from all, but specified as Launchpad (not specified as channel 1, but when I did midi learn from the LP they all came up channel 1)
My mappings are set with MIDI in out device specific. Still crashes.
I had the same issue with a Thinkpad T60 (Traktor Audio 6, Kontrol X1 and Launchpad, loopBe) and was about to return the Launchpad. But now I solved the problem 
: IIRC I first uninstalled the Novation software (Windows>System Settings>Programs, look for Novation) and then, today I unplugged all Midi devices and installed a new version of the Novation USB drivers (v2.33) and selected “Midi only device” in the installation dialog. After that I reconnected the Launchpad and let Windows finish its driver installation process. Then I reconnected all other Midi devices and started Traktor Pro. After that I had no Windows freeze any more when selecting Launchpad as Midi in and Midi out in Traktor Controller Manager. Hope this helps. Now I just need to find a good mapping or maybe use Midimasher or Katapult. I wonder if Midimasher is essentially a hands off Midi driver after the initial setup, or if I have to lauch/configure it each time before I start Traktor, any experience with this?
when i was using windows 7 i had a lot of hangs when using the launchpad until i upgraded to some beta drivers. was a while ago so i guess those fixes are now in the latest non-beta version.
midikatapult is very good. i used that before writing midimasher. midimasher is the same as midikatapult in as far as it needs to be started each time u run traktor. tho it should be simple enough to make it auto run on login and run some default config or something. on windows it needs to be run after the virtual midi port app tho - so probably safer to just run it by hand. it doesn’t matter whether you run it before or after traktor, so long as the virtual midiports are running first - tho if u run it before traktor midimasher will get the current ‘out’ states from traktor automatically. on mac and linux it is able to setup it’s own virtual midi ports.
if i pull my finger out and release the next version of midimasher… it’ll have a much simpler config format, more like vdjscript, tho u can still use LUA for more advanced stuff. the next version basically works - but i want to make some changes to the new script syntax that would be incompatible with how it is atm, so not releasing just yet.