NERO reboots CPU

[thegig]

Kinda strange behavior. I've been dealing with it for a while and just noticed a pattern for the resets, so I thought I would through the question out. Nero seems to "remember" the last session and on instantiation Nero will "look" for the drive (either read or write) and if there is no media (blank or not) it will reset the CPU. Do I have a setting wrong? Kinda annoying if I forget to have ALL the bays filled with media.

[skullfullomagots]

Resett the CPU? Umm, I think I dont fully understand you. But if you happen to have an XP, then you might wanna look at this.

Right click on My Computer and then click on Properties and then choose the tab Advanced. On this tab click on settings button for Statrup and Recovery and then on System Failure uncheck the "Automatically Restart" check box. And then watch out for Blue Screens

If you get a blue screen, then you should write the error code you get and seach on google to know what is exactly casuing the problem.

I have never head of Nero rememebering the previous sessions activity. I would like to know about it if there is something like that

Cheers mate

[thegig]

I guess I should not have used "CPU" but instead said computer .

Thanks for the tip, yes I have XP, I'll see what it says/does.

I have never head of Nero rememebering the previous sessions activity. I would like to know about it if there is something like that

Yea, I know it's the strangest thing, but is repeatable, and only Nero does it. None of my other "write" progs exhibit the behavior.

[Heywould3]

im wondering if your burner is sharing an IRQ with something like sound or video.. ? if so try to change that.. you should have your HDD and burner on seprate IDE cables.. both set as master. thats a good place to start

[Capmaster]

This is a software/CPU issue and not authoring ...moving to Computer forum ...

[thegig]

Well, thanks for the reminder how to get the BSOD. Turns out that the expansion IDE driver (cn2487.sys) and Nero like to fight each other. I get the STOP1 DRIVER_IRQL_NOT_LOWER_EQUAL. After several "suggestions" (memory allocation, re-load of driver, etc) I just turned off "Start with new compilation" in Nero and all is well... so far