Invalid access to memory location when loading bindings

[matortheeternal]

Description

When loading the module using require('fastcall') I'm getting this error:

Error: Invalid access to memory location.
\\?\E:\dev\git\zedit\node_modules\fastcall\build\Release\fastcall.node
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:173:20)
    at Object.Module._extensions..node (module.js:598:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:173:20)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at bindings (E:\dev\git\zedit\node_modules\bindings\bindings.js:81:44)
    at Object.<anonymous> (E:\dev\git\zedit\node_modules\fastcall\lib\native.js:19:37)
    at Object.<anonymous> (E:\dev\git\zedit\node_modules\fastcall\lib\native.js:20:3)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)

This occurs both when binding ref.node and when binding fastcall.node.

System information

• Windows 7 x64
• npm -v -> 5.4.2
• node -v -> v6.9.5
• node -p process.arch -> ia32
• node-gyp -v -> v3.6.1
• Using Electron

Steps to reproduce

• Download the latest version of fastcall via npm install fastcall.
• require('fastcall')

Details

• May be an issue with the node-gyp build file? Possibly platform/arch specific issue?