Signature: intel_aes_gcmINIT

This is for Sumo's Related Bugs 1263495 RESOLVED DUPLICATE crash in intel_aes_gcmINIT due to bad AVX instruction detection in freebl? 1225094 REOPENED --- Crash in [@ intel_aes_gcmINIT ]

This is being looked into. I've called for more help.

The CPU supports the instructions, then why is it illegal ?

Some support missing in Windows XP? How's that supposed to work? This CPU was issued in the XP era and has XP drivers

Can someone explain what's happening / is supposed to happen?

Thanks for looking into this

This problem was solved by doing a full XP repair; the partial repair I did first was not sufficient.

That was very good work. Well done. Please flag your last post as Solved Problem so others will know.

I spoke to soon, it is re-occurring, here's the latest: https://crash-stats.mozilla.com/report/index/a7e4d91d-b28e-4c54-a8cd-a77492161031

Sorry to hear that.  :-\

A post was flagged as Solved Problem. Please remove that flag. If you don’t, others that can help may not read this post.

Go to that message, and use the Undo link to its right.

Some more info: The PC is dual boot, Win 10 and Win XP. When the PC boots normally, the Win 10 boot loader gets control and you can select Win 10 or "earlier versions of Windows"

However, after the XP repair process the Windows 10 boot loader was over written and XP's NTLDR and the boot.ini menu (because I have two installs of XP) get control directly.

When the system was like this, I did not see any crash, neither in Firefox, avast nor Tmpgenc mpeg encoder. They all worked normally. (I looked at the summary of the earlier crash in the mpeg encoder, it also said illegal instruction)

A few hours later I restored the Win 10 loader using the recovery tools, now when XP is loaded like this (control passed from Win 10's loader) I start to see the crashes again.

Coincidence? I just don't know. Every time I thought I knew what was going on, I've been wrong..

For now, I've reinstalled XP's direct boot loader to see if it remains clean.

The other thing is, the problem(s) only occur n XP. Firefox in Windows 10 is just fine.

It would be a good idea to also post your question (about the duo system) here; http://answers.microsoft.com/en-US/windows/forum/windows_10

FredMcD said

It would be a good idea to also post your question (about the duo system) here; http://answers.microsoft.com/en-US/windows/forum/windows_10

Ok let me give it another day, to see if theory about the boot method holds up and I'll make the post tomorrow.

Here is my post to Microsoft Answers https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/doescould-the-windows-10-boot-loader-affect/255089aa-1449-4f41-85c0-b58dbd19e8ab?tm=1478108376571

I can confirm no further crashes have occurred in Firefox when booting XP directly from its own boot loader

That was very good work. Well done. Please flag your last post as Solved Problem so others will know.

FredMcD said

That was very good work. Well done. Please flag your last post as Solved Problem so others will know.

I see what you're saying. From Mozilla Firefox's perspective you could say they're absolved of blame, but I would like to find out what is actually going on. Is there nobody who can look at the dump and give me any more info? If I understood why it crashed, some more possibilities may come to light.

What is Windows 10 doing to the operating environment that affects XP down the line? Some option in the BCD ?

I called for more help; Duo boot Windows 10 & XP has problems / questions https://support.mozilla.org/en-US/forums/support-forum-contributors/712263

Thank you very much FredMcD - lets see what comes up

Here are my thoughts.

For this illegal instruction to be issued, either it was real instruction not supported, or some garbage because of memory corruption or similar. This kind of error may indicate a hardware problem, which I can look into further.

Isn't there anybody available to look at the dump and figure out what it was? This would be very helpful to me.

Thanks for any further info

This problem still occurs, new crash report https://crash-stats.mozilla.com/report/index/9ff5acc7-ba51-42fe-a361-409ab2170119#tab-details

Why am I unable to download the dump? It says I must be signed in first. Signed into what? I have logged onto Bugzilla and this forum and I still cant download the dump. I have updated this thread to see if I can get somebody to look at the crash dump https://bugzilla.mozilla.org/show_bug.cgi?id=1225094