BSOD 0x00000019 after shrinking system volume (SSD)

[Simon1957]

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

​

 

[koolkat77]

For the time being keep a clean start up. Let us know if the BSOD's reoccur.

   Tip

Reduce items at start up:

Performing a Clean Startup in Windows 7

Add, or Remove Startup Programs in Windows 7
​

Your Antivirus software is basically whats just needed there.

 

[Simon1957]

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.

 

[koolkat77]

I did take a look at your dumps and currently there's nothing that can be said actually, as those BSOD's occured only when "I used Disk Management to shrink my current system volume and created the new empty partition successfully."
So what I would do is wait and see if you continue to get BSOD's.
Hope that's clear.

 

[Simon1957]

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.

 

[koolkat77]

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.

That's not the kind of replies or "answers" you'd get here.
You can recreate the partition as you wish.

How many hard drives do you have on your system really?
I seem to have lost count.

 

[Simon1957]

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.

 

[koolkat77]

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.

It isn't that bad, like I said earlier. In your OP you said that it happened only when you created another partition.

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.

Hmm, you sound like a very experienced person about this stuff, already.

Anyhow, thanks for your continued help.

I haven't done anything to help in this thread - not yet.

You didn't perform a clean boot, did you?
You haven't recreated the partition to see if it BSOD;s, or did you?
Is the firmware of the SSD(s) up-to-date?

 

[gregrocker]

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.

 

[Simon1957]

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.

 

[Simon1957]

Dear GregRocker

Many thanks for your reply.
Tomorrow I will re-create the partition, see if a BSOD recurs and if so I'll perform the tests you have suggested.
I'll report back once complete.
Thanks for the suggestions.

 

[gregrocker]

Nothing needs to start with Win7 except the OS and AV, perhaps your sync. Anything else is a freeloader which can wait until you run it, and is likely spying on you to sell your browsing habits to advertisers.

The best way to maintain a Clean Boot is to uncheck everything except AV in msconfig>Startup and >Services after Hiding All MS Services. Startup Programs - Change

 

[Simon1957]

OK, that is a justification for clean boot - chwarae teg (fair play, as we say in Wales). However, I am aware of the many things that I load at start-up and I consider the ones that I have left enabled (and there are quite a few) add value for me. I have a custom build and have performed a clean install so I don't have bloatware, but I do have a very sophisticated setup (albeit with a little less than 6 PCs) with a lot of software loaded. As for selling my browsing habits I am resigned to the fact that this something that is costlier (to me) to eliminate than it would be to lose the benefits of having stuff pre-loaded in case I need it. However, I don't think anyone has really suggested (having looked at the dump files) that this problem stems from a component other than Windows itself? Thanks for the advice, though.

 

[gregrocker]

Most users who think they need GPU or chipset software, etc. don't realize it's not needed unless overclocking, and wasting resources if not spying. Nothing is needed unless it's something that you must have running with Windows when you start up because you rely on it at all times, e.g. a Messenger.

 

[Simon1957]

Agreed! I choose to use the (generous) resources at my disposal to make my setup function in the most effective way possible based on my particular needs.
I'm struggling to find a way to respond to your visitor message (very considerate to not mess up the thread) and for which many thanks. I'm glad we are at peace!!!

 

[gregrocker]

I have not sent you a VM.

 

[Simon1957]

My mistake - very sorry - Simon

 

[gregrocker]

That's OK. I'll send you one if you'd like!

 

[koolkat77]

I probably have not yet gotten my message through to you.

We deal with BSOD's on a daily basis here. Most of them are caused due to software or hardware. Windows itself is a rare case.

In very incidental cases like yourselves, caused by windows. The reason why I kept repeating - about you saying that it happened only after you created a partition on your SSD and the system remained stable the rest of the time, and not otherwise till up to now I suppose?

Not all dumps that BSOD's have an accurate reasoning, we analysts disregard those.


This is a list of the third party drivers that were present during the crash. I wouldn't suggest updating or uninstalling anything. You probably don't have to until you get a BSOD again. To know what hardware/software the driver belongs, simply copy and paste it to Carrona's Driver Reference Table.

ASACPI.sys                  Mon Mar 28 08:30:36 2005 
GEARAspiWDM.sys             Fri May  4 01:56:17 2012 
LHidFilt.Sys                Thu Jan  3 14:13:04 2013
LMouFilt.Sys                Thu Jan  3 14:13:07 2013 
MarvinBus64.sys             Sat Sep 24 03:17:03 2005 
MpFilter.sys                Sat Jun  8 05:01:11 2013 
RTKVHD64.sys                Fri Jan 29 12:48:35 2010 
RimSerial_AMD64.sys         Tue Oct 23 02:51:51 2012 
WinRing0x64.sys             Sat Jul 26 19:29:37 2008 
amdxata.sys                 Fri Mar 19 22:18:18 2010 
ccSetx64.sys                Fri Mar 22 09:02:33 2013 
dtsoftbus01.sys             Fri Jan 13 19:45:46 2012 
e1y62x64.sys                Fri Oct 21 00:20:55 2011 
iaStor.sys                  Wed Apr 27 00:06:18 2011 
intelppm.sys                Tue Jul 14 05:19:25 2009 
lvrs64.sys                  Sat Sep 22 01:02:17 2012 
lvuvc64.sys                 Sat Sep 22 01:03:12 2012 
mv91cons.sys                Fri Aug 27 15:22:37 2010 
mv91xx.sys                  Fri Aug 27 15:49:22 2010 
mvxxmm.sys                  Fri Aug 27 15:49:03 2010 
nusb3hub.sys                Fri Apr 23 07:34:35 2010 
nusb3xhc.sys                Fri Apr 23 07:34:36 2010 
nvhda64v.sys                Mon Feb 25 11:27:35 2013 
nvlddmkm.sys                Fri Jun 21 15:06:16 2013 
tosporte.sys                Tue Jun 16 16:48:47 2009 
tosrfcom.sys                Tue Jul 28 16:18:20 2009 
tosrfusb.sys                Fri Sep 11 15:37:18 2009 
vpchbus.sys                 Sat Nov 20 17:35:38 2010 
vpcnfltr.sys                Sat Nov 20 17:35:20 2010 
vpcusb.sys                  Sat Nov 20 17:35:31 2010 
vpcvmm.sys                  Sat Nov 20 17:35:48 2010 
wdcsam64.sys                Wed Apr 16 14:39:08 2008

Here's hoping that your system is intact and either software or hardware do not need to be diagnosed further. Windows was messing up somewhere when you were creating the partition.

Thank you for reading,
KK.

 

[Simon1957]

That's OK. I'll send you one if you'd like!

Very thoughtful, but unless/until I figure out how to reply to it you might be wasting your time