Unexpected shutdown -- alert, after AV upgrades

I have NOT had a BSOD



This is a copy of the "View Details" report

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    3081

Additional information about the problem:
  BCCode:    1000004a
  BCP1:    8368C951
  BCP2:    00000002
  BCP3:    00000000
  BCP4:    00000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\070916-25864-01.dmp
  C:\Users\Owner\AppData\Local\Temp\WER-60107-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\windows\system32\en-US\erofflps.txt

When I saw the "Blue Screen", not sure which sub-forum to post on.

I had just installed Bitdefender Internet Security 2016 (aka. BIS-2016)
- to replace BIS-2015 -- BIS-2016 required all other BD products to be removed/uninstalled
- which I did with the official BD uninstaller_2016

Every year AV renewals always cause problems ...

On another machine (64bit Win7 PRO) new BD has sabotaged "OpenWith" assignments and locked opening TXT files to Notepad.
Brink's REG file solutions Restore_Open_With.reg and Default_TXT.reg did not resolve the issue
The only way I could change the file-association for .TXT was with File Type Manager by Nirsoft
-----
This 32bit Win-7 Home Premium laptop was screwed up by Kaspersky install in March last year and I have not had email on this machine ever since, despite clean re-installs (of mail client) and trialing other mail clients.
-----
So my faith in AVs is very strained to say the least.

End of rant

Since the alert on this machine everything is operating fine, and the temptation to-fix is strong... but now it ain't broken.

From the above "results" can anybody interpret what the problem might have been ? :)

------------
ADDEND:
Last year I screwed up the TXT and VBS file associations and Brink's .REG files rectified my screw-up.
Thanks Shaun :)

You may have not had a blue screen of death, but technically you did have a crash, it just wasn't bad enough to lock up your machine.

The sub-forum would have been: BSOD Help and Support In any event you would be asked to run the utility: Blue Screen of Death (BSOD) Posting Instructions, and post the results.

As to your code revealing anything; The line BCCode: 1000004a indicates a memory management problem, I'm not sure what the other four arguments refer to.

• STOP 0x0000001A: MEMORY_MANAGEMENT

• Bug Check 0x1A: MEMORY_MANAGEMENT

If you wanted to move this thread to the BSOD forum for better visibility go to the in the upper right corner and kindly ask one of the Mods if they would move it over to there.