Software Crashing After System Restart—Any Fixes?

  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

AvaDuncan

New member
Mar 26, 2025
1
0
Hi everyone,


After restarting my computer, I’ve noticed that my software crashes every time I try to open it. I’ve tried reinstalling it and checking for updates, but the issue persists. The error message doesn’t provide much info, just a general crash notification.


Has anyone experienced this? Any suggestions on what to check or how to troubleshoot the issue?


Thanks in advance!
https://www.concretecontractorsannarbormichigan.com/
 
Last edited:
@Tazz "... A run of the System File Checker might not
hurt either. From the command line: sfc /scannow
..."​

That's the throw-away knee-jerk reaction at Microsoft's
direct lack-of-support sites, the modern version of "... Is
the power on? Did you reboot? Did you update?
...", the
inability to say "... I've never seen this before, so I cannot
offer an answer on what I did to resolve that particular
problem, I'll await more information. Tell us more
...".

@AvaDuncan has not told us more, yet.

- - - - -


@AvaDuncan, contacting the vendor of the software is a
great place to start to let them know it's crashing, and
to see if they take responsibility, have a solution, or are
willing to work on a solution.


Aside, anecdotes: I say that from experience, getting​
free Google Picasa to have the benefits of the features​
it has today ( Google has since moved on from PC to​
Web and Droid development ), see​
plus older versions for XP and Mac. I also frequently​
gyrate with Sven Abel's Abelssoft over their free​
YouTube Song Downloader misbehaviors, and they​
are impressively responsive, see​
. . . Craig Jensen's Diskkeeper group wrote a​
pre-windows boot DOS defrag routine that moved​
directories to the outer ring because I challenged​
them to do what Peter Norton <-- also was very​
responsive to end-user feedback -- did in his original​
Speedisk, see​
. . . WordPerfect for DOS had an update diskette every​
month based on user feedback, see​
. . . And, hey, Steve Gibson has taken great advantage​
of end-user feedback in development of SpinRite

So, @AvaDuncan, contact the seller and let us know what
they say
.

- - - - -

Along with SFC and the prerequisite DISM, I also check and
repair reparse points using Shane Croft's free Tweaking
Windows Repair Windows
( yeah, redundant name ), along
with triggering a ChkDsk /f or ChkDsk /r on reboot,
rebooting through safe mode with networking, and
'refreshing' Windows settings in that Tweaking tool, see
https://www.majorgeeks.com/files/details/tweaking_com_windows_repair_portable.html
and https://www.pcwintech.com/about

There's a lot we can do to take as full responsibility as
possible for our computer.

- - - - -

That being said, here's my DISM and SFC batch file script
( geesh, @peterblaise, way to bury the lead ! ) :

Code:
rem  Dism /online /cleanup-image /checkhealth
rem  Dism /online /cleanup-image /scanhealth
rem  Dism /online /cleanup-image /restorehealth
pause AND sfc /scannow SHOWING RESULTS
Dism /online /cleanup-image /checkhealth
Pause
Dism /online /cleanup-image /scanhealth
Pause
Dism /online /cleanup-image /restorehealth
Pause
sfc /scannow
findstr /c:"[SR]" c:\windows\logs\cbs\cbs.log > \sfcdetail.txt
notepad \sfcdetail.txt

DISM and SFC and ChkDsk are just tools.

I also keep and reinstall older versions of any software in
case newer versions misbehave, enabling me to see if the
problem may be a newly distributed incompatibility, and
then I stay with the last working version, avoiding updates.

So, @AvaDuncan, please tell us more, and let us know
what you do
.
 
Have a look in the Event Log to see if there are any more diagnostics. Winkey +R "eventvwr". It should be in the Application logs.
 
@AlanD "... Have a look in the Event Log to see if there
are any more diagnostics. Winkey +R "eventvwr". It
should be in the Application logs ..."​

It strikes me that without prior experience, we don't even
know what to look for in any of the suggested
maintenance ( and troubleshooting ?) routines.

For example, in my Even Viewer, Application and Service
Logs, I see thousands of lines like these below, I'll start off
with Microsoft, Windows, API-Tracing, Operational:

The API Tracing engine discovered a mismatch for a​
required manifest file. Information about the​
mismatch is below.​
Executable path: C:\Windows\System32\regsvr32.exe​
Binary name: KERNEL32.dll​
System manifest ID: {00611880-0000-0000-6000-000000000000}​
Binary manifest ID: {0011e120-0000-0000-8018-610000000000}​
- System​
- Provider​
[ Name] Microsoft-Windows-API-Tracing​
[ Guid] {B98F0DB6-26E2-4A66-89FC-32A9A6A9AF61}​
EventID 1​
Version 0​
Level 4​
Task 0​
Opcode 0​
Keywords 0x8000000000000000​
- TimeCreated​
[ SystemTime] 2021-07-21T04:47:27.437120800Z​
EventRecordID 20​
Correlation​
- Execution​
[ ProcessID] 9020​
[ ThreadID] 11128​
Channel Microsoft-Windows-API-Tracing/Operational​
Computer D2400X2-W3503​
- Security​
[ UserID] S-1-5-21-1062448468-2640603965-20612060-1001​
- UserData​
- ManifestMismatchEvent​
ExecutablePath C:\Windows\System32\regsvr32.exe​
BinaryName KERNEL32.dll​
SystemManifestId {00611880-0000-0000-6000-000000000000}​
BinaryManifestId {0011E120-0000-0000-8018-610000000000}​
Binary data:​
In Words​
0000: 32ELRNKE ll.d​
In Bytes​
0000: KE RN EL 32 .d ll​
What would I do with that information?

And what would I be looking for in the first place?

In other words, is that information even relevant to my
own situation?

- - - - -

Interesting spread of random troubleshooting hints,
though.

- - - - -

Still awaiting any follow-up from @AvaDuncan.

But that's not slowing us down, eh?
 
When looking at the Event Logs, my normal "first stage" is to filter the logs to show only Errors. I would then look at the relevant entries around the time that the problem last occured. If it was a recurrent problem, I would then look for the previous similar errors and see if there is any common link.

A lot of the time, when a non-Microsoft application crashes, the diagnostic is "0xc0000005" which is an Access Violation - in other words, the program tried to access something that it was not allowed to access. This frequently turns out to be a DLL version mismatch between what the program expects, and what your Windows installation has installed. At least it gives you somewhere to start looking for answers.