Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Nero Burning ROM Does Not Terminate Gracefully

Watch the following YouTube video to see Nero BurningROM exit (and try to restart?) in response to a termination request:



On occasion, it actually does restart. More randomness from Nero BurningROM.

Then, there's those event log entries:

APP CRASH

Log Name: Application
Source: Application Error
Date: 2/26/2017 3:24:24 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: My2ndToshiba
Description:
Faulting application name: nero.exe, version: 18.0.16.0, time stamp: 0x5836bcb8
Faulting module name: mfc140u.dll, version: 14.0.24215.1, time stamp: 0x57bfda81
Exception code: 0xc0000005
Fault offset: 0x000010b3
Faulting process id: 0x2e04
Faulting application start time: 0x01d2906e49715785
Faulting application path: D:\Program Files (x86)\Nero\Nero 2017\Nero Burning ROM\nero.exe
Faulting module path: C:\WINDOWS\SYSTEM32\mfc140u.dll
Report Id: f1653202-01ba-4d81-a2aa-dea2b957aff6
Faulting package full name:
Faulting package-relative application ID:
Event Xml:

1000
2
100
0x80000000000000

51737
Application
My2ndToshiba

nero.exe
18.0.16.0
5836bcb8
mfc140u.dll
14.0.24215.1
57bfda81
c0000005
000010b3
2e04
01d2906e49715785
D:\Program Files (x86)\Nero\Nero 2017\Nero Burning ROM\nero.exe
C:\WINDOWS\SYSTEM32\mfc140u.dll
f1653202-01ba-4d81-a2aa-dea2b957aff6




Log Name: Application
Source: Windows Error Reporting
Date: 2/26/2017 3:24:25 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: My2ndToshiba
Description:
Fault bucket 108695563582, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: nero.exe
P2: 18.0.16.0
P3: 5836bcb8
P4: mfc140u.dll
P5: 14.0.24215.1
P6: 57bfda81
P7: c0000005
P8: 000010b3
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AEA.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_nero.exe_6484b113a4eb687e4ac191bedafc1e37a54ed2_4a3626a6_0f723e64

Analysis symbol:
Rechecking for solution: 0
Report Id: f1653202-01ba-4d81-a2aa-dea2b957aff6
Report Status: 0
Hashed bucket: b5700e746395199b16bee0945eb0436b
Event Xml:

1001
4
0
0x80000000000000

51738
Application
My2ndToshiba

108695563582
1
APPCRASH
Not available
0
nero.exe
18.0.16.0
5836bcb8
mfc140u.dll
14.0.24215.1
57bfda81
c0000005
000010b3

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AEA.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_nero.exe_6484b113a4eb687e4ac191bedafc1e37a54ed2_4a3626a6_0f723e64

0
f1653202-01ba-4d81-a2aa-dea2b957aff6
0
b5700e746395199b16bee0945eb0436b



1 person has
this problem
+1
Reply
  • Jbass (Employee),

    Having noticed that you've been participating in the forum, I thought you'd like to acknowledge the existence of the bug described in this topic? The other employees have managed to ignore the issue for reasons unknown to me.

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned

  • Retraction

    I have now learned that killing nero.exe must be done in conjunction with killing startnbr.exe for Nero Burning ROM or startne.exe for Nero Express. In either case, an attempt to "request" termination results in an error message stating that the processes must be forcibly killed. For Nero Express:

    The following is ignored
    C:\WINDOWS\system32>taskkill -im nero.exe
    SUCCESS: Sent termination signal to the process "nero.exe" with PID 416.

    The following results in the error mentioned above
    C:\WINDOWS\system32>taskkill -im startne.exe
    ERROR: The process "StartNE.exe" with PID 11936 could not be terminated.
    Reason: This process can only be terminated forcefully (with /F option).

    The following results in the error mentioned above
    C:\WINDOWS\system32>taskkill -t -im startne.exe
    SUCCESS: Sent termination signal to process with PID 416, child of PID 11936.
    ERROR: The process with PID 11936 (child process of PID 9708) could not be terminated.
    Reason: This process can only be terminated forcefully (with /F option).

    The following works
    C:\WINDOWS\system32>taskkill -t -f -im startne.exe
    SUCCESS: The process with PID 416 (child process of PID 11936) has been terminated.
    SUCCESS: The process with PID 11936 (child process of PID 9708) has been terminated.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned