Can't startup ReactOS after an app crash

[waraqa]

I was browsing the internet using Basilisk web browser from this link and suddenly I got this BSoD

[ external image ]

but after rebooting, It can't startup and I always get this

[ external image ]

It freezes at logon screen and this is the debug screen

[ external image ]

I wonder how an app crash can cause permanent damage to the system like that!

Are there any steps to fix it or do I have to reinstall the OS?

System version: reactos-bootcd-0.4.16-dev-304-gff46665-x86-gcc-lin-dbg
Environment: QEMU emulator version 7.2.13 (Debian 1:7.2+dfsg-7+deb12u7) on Chromebook

[dizt3mp3r]

ReactOS is alpha. It can crash for any reason.

You may have to regularly reinstall, that is part and parcel of an alpha project...

[waraqa]

I will reinstall anyway. But is it possible to know what really happened?

[EmuandCo]

Only if you were debugging while it did die: https://reactos.org/wiki/Debugging

[waraqa]

I didn't install or change anything in the system. But since it can't startup anymore, that means there must be a change in the OS files.
I can think of one possibility which is damage occurred in the file system due to force reset. Am I right?
I'm thinking of a way to compare the current system files with a new installation to find out what was changed when it crashed.
Any idea?

[cmonkey]

I didn't install or change anything in the system. But since it can't startup anymore, that means there must be a change in the OS files.
I can think of one possibility which is damage occurred in the file system due to force reset. Am I right?
I'm thinking of a way to compare the current system files with a new installation to find out what was changed when it crashed.
Any idea?

It could be something in the registry. If you had backup hive(s) you could compare the before and after. The only way to do that, now, is to retrace your install/setup path; and then compare your new hive(s) with the same saved from the crashed system.

But that isn't likely going to help development. That would just be for your curiosity.

For a test, maybe you could use the hive(s) from the LiveCD. Just replace them and boot with the /MININT switch (back-up your old ones, if you intend to keep trouble-shooting). If it boots, then the files are probably fine.

As for comparing files, you could HASH all of the system files. If you install (for your hash comparison) from the same disk (or just use the files from the install disk/usb) they should all have the same hash (I don't think the files on the install medium are compressed). I'm sure there is a hash file compare app out there. Otherwise, you could just overwrite all of the system files, with files from the install disk/usb.

My money is on the hive(s).

[dizt3mp3r]

ReactOS is a very unstable o/s in Alpha state. Your job is to find out how unstable, by experiencing the crashes and failures. Don't expect to be able to 'use' ReactOS as it is not ready. Have a look here : https://simple.wikipedia.org/wiki/Softw ... life_cycle

[waraqa]

It could be something in the registry. If you had backup hive(s) you could compare the before and after. The only way to do that, now, is to retrace your install/setup path; and then compare your new hive(s) with the same saved from the crashed system.

But that isn't likely going to help development. That would just be for your curiosity.

For a test, maybe you could use the hive(s) from the LiveCD. Just replace them and boot with the /MININT switch (back-up your old ones, if you intend to keep trouble-shooting). If it boots, then the files are probably fine.

As for comparing files, you could HASH all of the system files. If you install (for your hash comparison) from the same disk (or just use the files from the install disk/usb) they should all have the same hash (I don't think the files on the install medium are compressed). I'm sure there is a hash file compare app out there. Otherwise, you could just overwrite all of the system files, with files from the install disk/usb.

My money is on the hive(s).

Thanks for your suggestions.

I have successfully activated the serial to file. And I'm able to reproduce the bug even in a new installation.
here are the exported debug files
https://justpaste.it/fw2fu
https://justpaste.it/gz5w2

I hope this helps

[dizt3mp3r]

Mattermost is the location where the devs and other interested parties discuss and might be able to help to resolve or identify your issues, join the chat there with your debug logs.

[waraqa]

I had another crash today due to insufficient space and after restarting I got BSOD. I tried the boot option "Last known good configuration" and surprisingly it worked.
How to restore this good configuration and make it as a current configuration?