Windows 7 node.exe crashing error code 10 continuously

Let us help you. Please tell us about…

Windows 7 Pro 64 fully patched to July 2017 updates

Could you please describe the problem?

node.exe is continuously crashing with Event Error Code 10 causing high CPU usage.

And finally, please attach a screenshot if available (you can drag and drop images)

Below are extracts of one set of events from my Windows Logs

  • System

    • Provider

    [ Name] Execution Service

    • EventID 1

    [ Qualifiers] 0

    Level 3

    Task 0

    Keywords 0x80000000000000

    • TimeCreated

    [ SystemTime] 2017-08-05T09:58:28.000000000Z

    EventRecordID 1628580

    Channel Application

    Computer Study-Windows-7

    Security

  • EventData

    Watched process exited with code 10
    ======================

  • System

    • Provider

    [ Name] Execution Service

    • EventID 0

    [ Qualifiers] 0

    Level 4

    Task 0

    Keywords 0x80000000000000

    • TimeCreated

    [ SystemTime] 2017-08-05T09:58:28.000000000Z

    EventRecordID 1628581

    Channel Application

    Computer Study-Windows-7

    Security

  • EventData

    Process exited with code 10
    ============================

  • System

    • Provider

    [ Name] Execution Service

    • EventID 0

    [ Qualifiers] 0

    Level 4

    Task 0

    Keywords 0x80000000000000

    • TimeCreated

    [ SystemTime] 2017-08-05T09:58:28.000000000Z

    EventRecordID 1628582

    Channel Application

    Computer Study-Windows-7

    Security

  • EventData

    Launching process “C:\Windows\Prey\current\bin\node.exe” “lib\agent\cli.js”
    ===========================================

Any advice greatly appreciated,

John

Hi @jrp2706, can i see your C:\Windows\Prey\prey.log file?

Javo

Here you go, I have extracted data and converted it to plain text, hope I have not lost anything important…

████████████████ ████████████████ ████████████████ ██ ██
██ ██ ██ ██ ██ ██ ██
██ ██ ██ ████████████████ ██ ██
██ ██ ██ ██ ██ ██
████████████████ ██ ████████████████ ████████████████
██ ██
██ ████████████████

PREY 1.6.9 spreads its wings!
Current time: Sat Jul 22 2017 10:36:53 GMT+0100 (GMT Daylight Time)
Running with PID 34508 as STUDY_WINDOWS_7_ over Node.js v4.4.5 on a x64 windows system (undefined)

 warn Sat, 22 Jul 2017 09:36:54 GMT [control-panel] Not configured. Waiting for user input...
 info Sat, 22 Jul 2017 09:37:04 GMT [control-panel] Reloading config...
 info Sat, 22 Jul 2017 09:37:14 GMT [control-panel] Reloading config...
 info Sat, 22 Jul 2017 09:37:24 GMT [control-panel] Reloading config...
 info Sat, 22 Jul 2017 09:37:34 GMT [control-panel] Reloading config...
 info Sat, 22 Jul 2017 09:37:45 GMT [control-panel] Reloading config...
 info Sat, 22 Jul 2017 09:37:55 GMT [control-panel] Reloading config...
 info Sat, 22 Jul 2017 09:38:05 GMT [control-panel] Reloading config...
 info Sat, 22 Jul 2017 09:38:06 GMT Plugin loaded: control-panel
 info Sat, 22 Jul 2017 09:38:06 GMT 1 plugins loaded with 0 errors.
 info Sat, 22 Jul 2017 09:38:06 GMT Initialized.
 info Sat, 22 Jul 2017 09:38:06 GMT [triggers] Watching: connection, network, power
 info Sat, 22 Jul 2017 09:38:06 GMT [actions] Starting trigger: connection
 info Sat, 22 Jul 2017 09:38:06 GMT [actions] Running: connection
 info Sat, 22 Jul 2017 09:38:06 GMT [actions] Starting trigger: network
 info Sat, 22 Jul 2017 09:38:06 GMT [actions] Starting trigger: power
 info Sat, 22 Jul 2017 09:38:06 GMT [actions] Running: network
 info Sat, 22 Jul 2017 09:38:06 GMT [actions] Running: power

notice Sat, 22 Jul 2017 09:38:06 GMT [control-panel] Updating value of auto_update to false
error Sat, 22 Jul 2017 10:18:55 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Sat, 22 Jul 2017 10:19:07 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Sat, 22 Jul 2017 10:21:21 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Sat, 22 Jul 2017 10:21:22 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Sat, 22 Jul 2017 10:21:24 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Tue, 25 Jul 2017 17:35:44 GMT Error: Invalid response received with status code 502
error Thu, 27 Jul 2017 23:10:36 GMT Error: Invalid response received with status code 502
error Fri, 28 Jul 2017 09:54:34 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:54:54 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:55:09 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:55:24 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:55:39 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:55:54 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:56:09 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:56:24 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:56:39 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:56:54 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:57:09 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:57:24 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:57:39 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:57:54 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:58:09 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:58:24 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:58:39 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:58:54 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:59:09 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:59:24 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:59:39 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 09:59:54 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 10:00:09 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 10:00:24 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 10:00:40 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 10:00:55 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 10:01:10 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 10:01:25 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 12:42:39 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 14:37:56 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 14:53:42 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 14:54:27 GMT [network] Connection error: Error: socket hang up
error Fri, 28 Jul 2017 17:30:56 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Fri, 28 Jul 2017 17:31:07 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Fri, 28 Jul 2017 17:34:43 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Fri, 28 Jul 2017 17:34:46 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Fri, 28 Jul 2017 17:34:52 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Fri, 28 Jul 2017 22:07:37 GMT Error: Invalid response received with status code 502
error Fri, 28 Jul 2017 22:07:37 GMT Error: Invalid response received with status code 502
error Fri, 28 Jul 2017 22:07:37 GMT Error: Invalid response received with status code 502
error Fri, 28 Jul 2017 22:07:38 GMT Error: Invalid response received with status code 502
error Fri, 28 Jul 2017 22:07:38 GMT Error: Invalid response received with status code 502
error Fri, 28 Jul 2017 22:07:38 GMT Error: Invalid response received with status code 502

████████████████ ████████████████ ████████████████ ██ ██
██ ██ ██ ██ ██ ██ ██
██ ██ ██ ████████████████ ██ ██
██ ██ ██ ██ ██ ██
████████████████ ██ ████████████████ ████████████████
██ ██
██ ████████████████

PREY 1.6.9 spreads its wings!
Current time: Sat Jul 29 2017 08:19:13 GMT+0100 (GMT Daylight Time)
Running with PID 1324 as STUDY_WINDOWS_7_ over Node.js v4.4.5 on a x64 windows system (undefined)

 info Sat, 29 Jul 2017 07:19:19 GMT Plugin loaded: control-panel
 info Sat, 29 Jul 2017 07:19:19 GMT 1 plugins loaded with 0 errors.
 info Sat, 29 Jul 2017 07:19:19 GMT Initialized.
 info Sat, 29 Jul 2017 07:19:19 GMT [triggers] Watching: connection, network, power
 info Sat, 29 Jul 2017 07:19:19 GMT [actions] Starting trigger: connection
 info Sat, 29 Jul 2017 07:19:21 GMT [actions] Running: connection
 info Sat, 29 Jul 2017 07:19:21 GMT [actions] Starting trigger: network
 info Sat, 29 Jul 2017 07:19:21 GMT [actions] Starting trigger: power
 info Sat, 29 Jul 2017 07:19:21 GMT [actions] Running: network
 info Sat, 29 Jul 2017 07:19:24 GMT [actions] Running: power

████████████████ ████████████████ ████████████████ ██ ██
██ ██ ██ ██ ██ ██ ██
██ ██ ██ ████████████████ ██ ██
██ ██ ██ ██ ██ ██
████████████████ ██ ████████████████ ████████████████
██ ██
██ ████████████████

PREY 1.6.9 spreads its wings!
Current time: Sat Jul 29 2017 13:30:17 GMT+0100 (GMT Daylight Time)
Running with PID 1904 as STUDY_WINDOWS_7_ over Node.js v4.4.5 on a x64 windows system (undefined)

 info Sat, 29 Jul 2017 12:30:25 GMT Plugin loaded: control-panel
 info Sat, 29 Jul 2017 12:30:25 GMT 1 plugins loaded with 0 errors.
 info Sat, 29 Jul 2017 12:30:26 GMT Initialized.
 info Sat, 29 Jul 2017 12:30:26 GMT [triggers] Watching: connection, network, power
 info Sat, 29 Jul 2017 12:30:26 GMT [actions] Starting trigger: connection
 info Sat, 29 Jul 2017 12:30:35 GMT [actions] Running: connection
 info Sat, 29 Jul 2017 12:30:35 GMT [actions] Starting trigger: network
 info Sat, 29 Jul 2017 12:30:37 GMT [actions] Starting trigger: power
 info Sat, 29 Jul 2017 12:30:46 GMT [actions] Running: network
 info Sat, 29 Jul 2017 12:30:46 GMT [actions] Running: power
error Sat, 29 Jul 2017 12:30:46 GMT [network] Connection error: Error: socket hang up
error Sat, 29 Jul 2017 20:21:55 GMT [network] Connection error: Error: socket hang up
error Sat, 29 Jul 2017 20:23:25 GMT [network] Connection error: Error: socket hang up
error Mon, 31 Jul 2017 17:36:48 GMT Error: Invalid response received with status code 502
error Mon, 31 Jul 2017 17:36:57 GMT Error: Invalid response received with status code 502
error Mon, 31 Jul 2017 17:37:08 GMT Error: Invalid response received with status code 502
error Mon, 31 Jul 2017 17:37:08 GMT Error: Invalid response received with status code 502
error Mon, 31 Jul 2017 17:37:08 GMT Error: Invalid response received with status code 502
error Mon, 31 Jul 2017 17:37:09 GMT Error: Invalid response received with status code 502
error Mon, 31 Jul 2017 17:37:09 GMT Error: Invalid response received with status code 502
error Mon, 31 Jul 2017 17:37:09 GMT Error: Invalid response received with status code 502
error Mon, 31 Jul 2017 17:37:09 GMT Error: Invalid response received with status code 502
error Mon, 31 Jul 2017 17:37:57 GMT Error: Invalid response received with status code 502
error Tue, 01 Aug 2017 11:57:02 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 08:09:53 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Wed, 02 Aug 2017 17:45:52 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 17:46:01 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:30:42 GMT [network] Connection error: Error: socket hang up
error Wed, 02 Aug 2017 21:36:24 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:36:27 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:36:42 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:36:57 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:37:12 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:37:27 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:37:42 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:37:57 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:38:12 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:38:27 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Wed, 02 Aug 2017 21:38:49 GMT [network] Connection error: Error: socket hang up
error Wed, 02 Aug 2017 21:39:07 GMT [network] Connection error: Error: socket hang up
error Wed, 02 Aug 2017 21:39:20 GMT [network] Connection error: Error: connect ECONNREFUSED 192.168.0.1:443
error Wed, 02 Aug 2017 21:39:35 GMT [network] Connection error: Error: connect ECONNREFUSED 192.168.0.1:443
error Wed, 02 Aug 2017 21:39:50 GMT [network] Connection error: Error: connect ECONNREFUSED 192.168.0.1:443
error Wed, 02 Aug 2017 21:40:05 GMT [network] Connection error: Error: connect ECONNREFUSED 192.168.0.1:443
error Wed, 02 Aug 2017 21:40:16 GMT [network] Connection error: Error: connect ECONNREFUSED 192.168.0.1:443
error Thu, 03 Aug 2017 06:24:40 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Thu, 03 Aug 2017 06:24:49 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Thu, 03 Aug 2017 10:02:16 GMT Error: Invalid response received with status code 502
error Fri, 04 Aug 2017 19:01:21 GMT [network] Connection error: Error: socket hang up
error Sat, 05 Aug 2017 02:20:43 GMT Error: Invalid response received with status code 502

████████████████ ████████████████ ████████████████ ██ ██
██ ██ ██ ██ ██ ██ ██
██ ██ ██ ████████████████ ██ ██
██ ██ ██ ██ ██ ██
████████████████ ██ ████████████████ ████████████████
██ ██
██ ████████████████

PREY 1.6.9 spreads its wings!
Current time: Sat Aug 05 2017 09:27:04 GMT+0100 (GMT Daylight Time)
Running with PID 1916 as STUDY_WINDOWS_7_ over Node.js v4.4.5 on a x64 windows system (undefined)

 info Sat, 05 Aug 2017 08:27:06 GMT Plugin loaded: control-panel
 info Sat, 05 Aug 2017 08:27:06 GMT 1 plugins loaded with 0 errors.
 info Sat, 05 Aug 2017 08:27:06 GMT Initialized.
 info Sat, 05 Aug 2017 08:27:06 GMT [triggers] Watching: connection, network, power
 info Sat, 05 Aug 2017 08:27:06 GMT [actions] Starting trigger: connection
 info Sat, 05 Aug 2017 08:27:08 GMT [actions] Running: connection
 info Sat, 05 Aug 2017 08:27:08 GMT [actions] Starting trigger: network
 info Sat, 05 Aug 2017 08:27:08 GMT [actions] Starting trigger: power
 info Sat, 05 Aug 2017 08:27:08 GMT [actions] Running: network
 info Sat, 05 Aug 2017 08:27:10 GMT [actions] Running: power

████████████████ ████████████████ ████████████████ ██ ██
██ ██ ██ ██ ██ ██ ██
██ ██ ██ ████████████████ ██ ██
██ ██ ██ ██ ██ ██
████████████████ ██ ████████████████ ████████████████
██ ██
██ ████████████████

PREY 1.6.9 spreads its wings!
Current time: Sat Aug 05 2017 12:53:38 GMT+0100 (GMT Daylight Time)
Running with PID 1348 as STUDY_WINDOWS_7_ over Node.js v4.4.5 on a x64 windows system (undefined)

 info Sat, 05 Aug 2017 11:53:42 GMT Plugin loaded: control-panel
 info Sat, 05 Aug 2017 11:53:42 GMT 1 plugins loaded with 0 errors.
 info Sat, 05 Aug 2017 11:53:42 GMT Initialized.
 info Sat, 05 Aug 2017 11:53:42 GMT [triggers] Watching: connection, network, power
 info Sat, 05 Aug 2017 11:53:42 GMT [actions] Starting trigger: connection
 info Sat, 05 Aug 2017 11:53:45 GMT [actions] Running: connection
 info Sat, 05 Aug 2017 11:53:45 GMT [actions] Starting trigger: network
 info Sat, 05 Aug 2017 11:53:46 GMT [actions] Starting trigger: power
 info Sat, 05 Aug 2017 11:53:46 GMT [actions] Running: network
 info Sat, 05 Aug 2017 11:53:51 GMT [actions] Running: power
 info Sat, 05 Aug 2017 11:53:51 GMT [long-polling] Got 1 commands.
 info Sat, 05 Aug 2017 11:53:58 GMT [reports] Gathering status report.
error Sat, 05 Aug 2017 11:53:59 GMT [reports] Unable to get active_access_point: No active access point(s) found.
error Sat, 05 Aug 2017 11:54:00 GMT [reports] Unable to get battery_status: No Instance(s) Available.

 info Sat, 05 Aug 2017 11:54:00 GMT [reports] Report gathered: status
 info Sat, 05 Aug 2017 11:54:00 GMT [control-panel] Posting data
 info Sat, 05 Aug 2017 11:54:00 GMT [control-panel] Got 200 response: OK
 info Sat, 05 Aug 2017 11:58:56 GMT [long-polling] Got 1 commands.
 info Sat, 05 Aug 2017 11:58:57 GMT [reports] Gathering status report.
error Sat, 05 Aug 2017 11:58:58 GMT [reports] Unable to get active_access_point: No active access point(s) found.
error Sat, 05 Aug 2017 11:58:59 GMT [reports] Unable to get battery_status: No Instance(s) Available.

 info Sat, 05 Aug 2017 11:58:59 GMT [reports] Report gathered: status
 info Sat, 05 Aug 2017 11:58:59 GMT [control-panel] Posting data
 info Sat, 05 Aug 2017 11:58:59 GMT [control-panel] Got 200 response: OK
error Sat, 05 Aug 2017 12:10:31 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Sat, 05 Aug 2017 12:10:31 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443

████████████████ ████████████████ ████████████████ ██ ██
██ ██ ██ ██ ██ ██ ██
██ ██ ██ ████████████████ ██ ██
██ ██ ██ ██ ██ ██
████████████████ ██ ████████████████ ████████████████
██ ██
██ ████████████████

PREY 1.6.9 spreads its wings!
Current time: Sat Aug 05 2017 20:04:43 GMT+0100 (GMT Daylight Time)
Running with PID 2004 as STUDY_WINDOWS_7_ over Node.js v4.4.5 on a x64 windows system (undefined)

 info Sat, 05 Aug 2017 19:04:47 GMT Plugin loaded: control-panel
 info Sat, 05 Aug 2017 19:04:47 GMT 1 plugins loaded with 0 errors.
 info Sat, 05 Aug 2017 19:04:47 GMT Initialized.
 info Sat, 05 Aug 2017 19:04:47 GMT [triggers] Watching: connection, network, power
 info Sat, 05 Aug 2017 19:04:47 GMT [actions] Starting trigger: connection
 info Sat, 05 Aug 2017 19:04:49 GMT [actions] Running: connection
 info Sat, 05 Aug 2017 19:04:49 GMT [actions] Starting trigger: network
 info Sat, 05 Aug 2017 19:04:49 GMT [actions] Starting trigger: power
 info Sat, 05 Aug 2017 19:04:49 GMT [actions] Running: network
 info Sat, 05 Aug 2017 19:04:52 GMT [actions] Running: power
error Sat, 05 Aug 2017 19:21:22 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Sat, 05 Aug 2017 19:21:34 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Sun, 06 Aug 2017 08:37:16 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Sun, 06 Aug 2017 08:37:41 GMT [network] Connection error: Error: socket hang up
error Sun, 06 Aug 2017 08:37:52 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443
error Sun, 06 Aug 2017 11:31:01 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Sun, 06 Aug 2017 11:31:09 GMT [network] Connection error: Error: getaddrinfo ENOENT solid.preyproject.com:443
error Sun, 06 Aug 2017 12:26:20 GMT [network] Connection error: Error: getaddrinfo ENOTFOUND solid.preyproject.com solid.preyproject.com:443

Thank you for your assistance.

Since I reloaded my PC it seems to be behaving now, very strange!

Cheers,

John

Old thread but this was the first result I got from Googleing. I just had the same thing, laptop fan whirring because nodejs is constantly restarting. Checked the event viewer and can see prey crashing with error code 10 repeatedly.

I did a bit of digging out of curiosity and ran the cli.js from the command line which showed:

The Prey agent is running. Good job!
It has been live for 1588. minutes, under process ID 1764.
To trigger actions or retrieve information, log in to your Prey account at https://preyproject.com
For additional configuration options, please run prey config.

I checked the PID, and it was actually associated with another service ‘SurSvc.exe’ - an Intel service for updating drivers. I killed that and the restarts stopped - node is now running fine and my laptop is silent once more.

Weird bug?

Yes, that was my thought and as you can see the Support Team didn’t seem to be interested once I told them the problem went away with a PC reload.

I have had the same problem again at various times over the intervening year and a half and it still does it occasionally, so I just reboot and it goes away for a while.

Best of luck going forward, perhaps someone will look at this thread now that it is active again.

Cheers,

John

Hi @jrp2706,

Write to me at [email protected] so we can review this issue deeply.

Regards,
Javo

Javo - see above image from a crashing scenario - it shows prey reporting the incorrect pid (again it belonged to SurSvc.exe).

Killing that process resulted in node no longer crashing with error code 10, shown in below image taken an hour later:

Hi @vivo,

That Sursvc.exe process does not belongs to prey, I’m gonna check it out.
Thank you for notifying that to us, let me know if the problem persists.

Kind Regards,
Javo