Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autostart stopped working after BIOS update, writer.exe .NET exception in Event Viewer #223

Open
AniRayn opened this issue Jun 23, 2024 · 0 comments

Comments

@AniRayn
Copy link

AniRayn commented Jun 23, 2024

I had RawAccel's writer.exe set to launch at startup via Task Scheduler. After I updated my BIOS it stopped working with error code 0xe0434352 shown in Task Scheduler. In Event viewer I found this.

Event 1 (id 1026):
Application: writer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at System.Windows.Forms.MessageBox.ShowCore(System.Windows.Forms.IWin32Window, System.String, System.String, System.Windows.Forms.MessageBoxButtons, System.Windows.Forms.MessageBoxIcon, System.Windows.Forms.MessageBoxDefaultButton, System.Windows.Forms.MessageBoxOptions, Boolean)
at writer.Program.Exit(System.String)
at writer.Program.Main(System.String[])

Event 2 (id 1000):
Faulting application name: writer.exe, version: 1.6.1.0, time stamp: 0xbdc1284a
Faulting module name: KERNELBASE.dll, version: 10.0.19041.4522, time stamp: 0xf7a99bd4
Exception code: 0xe0434352
Fault offset: 0x000000000002ba99
Faulting process id: 0x10d4
Faulting application start time: 0x01dac5a6a71607a2
Faulting application path: C:\Program Files\RawAccel\writer.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: e1b40796-ee74-4269-ad2b-03c5f9cbebc7
Faulting package full name:
Faulting package-relative application ID:

Is this something that can be fixed on my side? OK, without rolling back my BIOS :)
I suspect it could have to do with changed initialization delay/duration of my USB devices, because running writer.exe a few seconds later works. Specifically, I changed the task trigger from "startup" to "log on of any user", which supposedly occurs later than "startup".
Let me know if you need additional logs or info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant