BSOD 0x00000019 after shrinking system volume (SSD)

Hi All

My first post here so please be gentle .
I was looking at installing a trial version of Windows 8 and so wanted to create an empty partition.
I used Disk Management to shrink my current system volume and created the new empty partition successfully.
Also Windows Update had installed:

Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition
Windows Malicious Software Removal Tool x64 - July 2013 (KB890830)

Later, whilst browsing the web I encountered four successive BSODS:

0x00000019 (0x0000000000000020, 0xfffffa802297e080, 0xfffffa802297ee50, 0x0000000004dd0008)
0x00000019 (0x0000000000000003, 0xfffffa8019aa7de0, 0xfffffffffffffdff, 0xfffffa8019aa7de0)
0x00000019 (0x0000000000000020, 0xfffffa80196c8000, 0xfffffa80196c8dd0, 0x0000000004dd0000)
0x00000019 (0x0000000000000003, 0xfffffa8013293de0, 0xfffffffff7293def, 0xfffffa8013293de0)

I have now run start-up repair (no errors reported), restored the system to undo the Windows Updates and deleted the new partition and extended the system volume back to its full size.
The system is stable again, but I'm wondering if there is a proper explanation of and/or solution for the problem.
I have attached the output from SF_Diagnostic_Tool.exe.
Any help appreciated ...

Simon

Thanks for the response.
I have re-applied the windows updates and the system is still stable.
I'd certainly update the thread if I encounter another BSOD.
The thing is, I don't have the empty partition that I set out to create.
I could repeat the shrink / create procedure and see if this re-introduces the BSOD, but I was hoping that somebody might take a look at the dump and let me know if this issue has been seen before.

Thanks for looking at the dumps.
The BSODs were occurring within about 10 minutes of use, so I think it is obvious that the problem has been eradicated by deleting the partition that I had created given the system has been up for several hours now. So, if we leave things as they are I think we will wait forever for a recurrence.
I think I will need to re-create the empty partition and see if the problem recurs, don't you?
I had just hoped that somebody might say something like ... "oh, you get this problem when you have more than x partitions" or something like that.

Or perhaps I might have had somebody explain what a BAD_POOL_HEADER was and in what way mine was actually 'bad', how it might have happened and how to fix it. My disks are listed in my system specification and the files I uploaded include the MSINFO file where you can see the disk and drive data under the Components/Storage tree. This version of MSINFO was produced after I had removed the new partition that had been created. I had created a partition on my SSD by shrinking the partition that drive C: occupies and creating a new partition from the space released, but due to system instability I did not attempt to install the SF_Diagnostic_Tool and upload the relevant files whilst the empty partition was in existence - sorry!
Anyhow, thanks for your continued help.

Please post back a screenshot of Disk Management - Post a Screen Capture Image so we can look over your disk configuration for any problems. You may have been up against the limit on Primary Partitions which we can help you resolve.

Test your RAM - Test with Memtest86+ as Bad Pool Header often relates to RAM and it might have been stressed by the combination of Updates while shrinking C.

Likewise run a full Disk Check and test the drive you shrank with the maker's diagnostics to know for sure its condition.

Northern Soul : Well, I may be new here, but I'm not completely ignorant of how forums work. I did read the rules before I posted and I think I'm abiding by them. I have been polite and appreciative of Koolkat's contributions and I have already noted that she has lots of rep etc. I recognise that members contribute on the basis of generosity, but ultimately they choose to do so. So, I acknowledge all help and am happy to express great appreciation for replies that are helpful, informative, well considered and that demonstrate their mastery of their subject. My response was a factual one and intended to be helpful. I have seen others fall into the trap of trying to extricate themselves from an "attitude" situation and I'm not going to waste my time or that of forum members in turning this thread into a debate about "attitude".

Koolkat: Thanks again for being up for trying to help. No, I didn't perform a clean boot - what would be the point now that the system is stable? No, I haven't re-created the partition - I suggested this would be the likely next step so as to see that the problem is reproducible but at the time I created the thread I had not done that and I thought I had been clear about that. You haven't actually opined on that suggestion. No, it isn't that bad. It just means I may not be able to create another partition on my SSD and have a system that doesn't BSOD after every ten minutes or so. Yes, my SSD firmware is current. And yes, I am pretty experienced (CEng MBCS CITP CISM with 25+ years IT industry experience) but obviously I don't have the skills required to solve this particular problem, hence my appealing to the community for a bit of help.

Anyhow, apologies if I have come across as arrogant. If anyone is willing to help then I'm grateful, but as I said I don't intend to participate in a thread that focuses on "attitude" issues.