SESSION5_INITIALIZATION_FAILED [FIXED]

Bug Reports
#1

Hello!
I update Comodo v3 to the latest version a couple of days ago. It crashed at first start but it was able to fix itself with diagnostics feature.
Today I went trough a checkdisk for maintenance as usual, but I got the following when Windows was starting after checkdisk:

A problem has been detected and windows has been shut down to prevent damage to your computer.

SESSION5_INITIALIZATION_FAILED

If this is the first time you’ve see the Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press f8 to select advanced Startup Options, and then select Safe Mode.

Technical information:

*** STOP: 0x00000071 (0x00000000, 0x00000000, 0x00000000, 0x00000000)


Now the useful info:
CPU: Pentium 4 HT x64
OS Windows XP Pro SP2 x32
Running security apps Only Avira Antivir, the other running stuff are only drivers
The bug only happens after a checkdisk, I tryed to boot on safe mode but it gave me only a black screen, the only way to make Windows work was booting trough last good option.
I didn’t try to solve it yet, I’m not with too much spare time. I did some research and I found that some ZoneAlarm users had that problem and, the only way to solve it was uninstalling it.
Both firewall and Defence are on training with safe mode, version is 3.0.16.295…

I didn’t related it to Comodo at first but, it was the only modification I did.

#2

Greetings!

Does Windows create a minidump file?
If yes, please post it here.

Cheers,
Ragwing

#3

Sorry, it doesn’t create any.
I related the issue with CPF because it was my only modification after my last checkdisk.

#4

Is “Block all the unknown requests if the application is closed” Defense+ setting unchecked?

#5

I can confirm that this is happening here too after a checkdisk. I can boot safe mode fine. Started after latest comodo update. rolling back.

#6

Checkdisk run fine please post more info.

#7

[ at ] gibran It was unchecked. I checked it a while ago. Checkdisk runs fine, the problem is when it finishes and Windows starts.

[ at ] Ashrak1978 I couldn’t boot in safe mode. I only was able to boot trough last good option.

#8

@ Munemasa Katagiri: So you get that BSOD regardless “Block all the unknown requests if the application is closed” setting?

#9

I didn’t try after checking the box, it was very late and I had to go to bed, now I’m at work. I’m affraid to try again and not have the last good option since safe mode do not work.
If I don’t use checkdisk, the system works normally.

#10

Ok. you don’t need to try that. during beta SESSION5_INITIALIZATION Failed occurred if “Block all the unknown requests if the application is closed” was checked.

#11

So, it’s a known bug?
It also happened with it unchecked on my computer.

#12

This is a a new one as it is triggered only by checkdisk.

I finally was able to reproduce this I got a minidump to post in the BSOD thread.
On My machine I got a BSOD after succesfully logging into windows though.

#13

Cool! News! Now they will be able to fix that bug. :BNC
I couldn’t start Windows, that’s why I didn’t get any dump files.
Did you get the same BSOD as me? With same message?

#14

I got a Stop F8 message If I recall correctly. Anyway the minidump should provide more infos than me.

#15

There was an update.
Was it fixed for you?

#16

I got rid of the BSOD but I need to reboot anyway because Many programs cannot load (failing dll/exe)

#17

I’ve just updated to the last version, but after a chkdsk I have the same BSOD, the only way to make windows load is to choose the last working configuration.
The defense+ level was on “disabled”, do you think that deactivating permanently Defense+ checking the relative option may solve the problem ?

Zipe.

#18

Please look at https://forums.comodo.com/bug_reports/bsods_please_add_your_minidump_files_here-t14909.0.html;msg104336#msg104336
to see if any minidump was generated. It could prove useful to fix this issue.

#19

I’m sorry, but I couldn’t find any minidump, probably because i couldn’t even make windows boot in safe mode. I had to choose the last working configuration.

:), Zipe.

#20

Ok if this happen again please look for a minidump, meanwhile refer to the bugreport board stickied topics to read about bureporting guidelines in order to add as much informations is possible to this topic.

Thanks for your understanding,
gibran