Use the NW.js action "show dev tools" and make it available through some hidden keyboard shortcut or something. This will bring up the browser error console (just like Chrome's) where it will log any errors if they happen in Javascript, and may help shed some light on it.
Also it could be a graphics driver issue, so updating drivers may help. Note Windows NW.js exports by default ignore the GPU blacklist (the --ignore-gpu-blacklist option in package.json), which means even if the drivers are known to be buggy it will still use GPU acceleration instead of falling back to a software renderer. Removing the option will allow the game to fall back to software rendering on known buggy drivers/hardware, which means it will be slow, but work, which is better than fast and doesn't work at all.