BSOD after clean install of Win7 - BAD_POOL_HEADER - 0x00000019

I'm really a noobie when it comes to troubleshooting windows errors, but here's what happened - I was getting BSoDs quite frequently on Windows, so I thought that maybe a clean reinstallation would work using Darik's Boot And Nuke... but apparently it didn't solve the problem, because I'm still getting the crashes. I really don't know what the problem could be.

I've included a picture of the screen, but here's the error code in text if you want to do a copy-paste:

*** STOP: 0x00000019 (0x0000000000000020, 0xFFFFFA8008397F30, 0xFFFFFA8008398720, 0x00000000AD7F1327)

I'm burning memtest to a CD that I'm going to run overnight, and I set up the error dump settings so that I'll get a minidump in a directory that I set to a folder in my documents, so hopefully I can get some more information up here soon on those things, but is there anything else that I should be aware of/should be doing? Because I know that these things can be complicated...

Thanks!

Oh, and I'm not sure if this has anything to do with the problem, but I thought I would mention it - I'm not sure if the temperature gauge on my motherboard is shot or what, but I'm getting a very strange reading in Piriform Speccy on the temperature... obviously it can't be right, but could this be related to the BSoD problem, indicating that they might be resulting from some sort of hardware failure?

Also, I just ran the Windows Seven Forums Diagnostics Tool, and here's all the information from running the "grab all" command (attached)

Okay, so I was trying to reinstall the driver for the wireless adapter on the computer, because the network signal kept giving out over and over again (while my laptop always keeps a steady signal in the same location), and then I got another BSOD, but this one did not have the "BAD_POOL_HEADER" code, and had this as the technical information:

*** STOP: 0x0000001E (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

..which was different than the last one I got. ALSO, a file appeared in the minidump folder that I put in mydocs afterward, since this was the first BSOD since the last one, only I seem to be having a lot of trouble actually uploading it... when I try to upload it directly, the computer tells me that I do not have the permissions required to access the file, and that I need to contact the administrator (even though I am the only user on the machine, set as an admin), and when I try to upload it through a public Dropbox link, I also get an error. I don't know why this is happening, as other people don't seem to have that kind of trouble when they upload the dump files..

I'm really lost now. Any help would be greatly appreciated!

I just wanted to say that I ran memtest on my computer (version 5.1.0), and no errors came up in the safe mode (F1) of the program, which I ran a few times just to make sure - nothing. HOWEVER, when I enabled the forced multi-threading option (F2), the test encountered problems, and froze up at about 25% completion for both of the times that I ran it. Is there any way to get additional information as to what went wrong with the memtest, or is it pretty much a mystery once you enable forced multi-threading mode?

Okay, this was actually able to pass, and I managed also to install about 100 or so updates with the Windows Update tool, but I am still very concerned about instability - has anyone been able to make anything out of the files from the diagnostic utility?

Oh, and here's the output result file!

herebepenguins said:

Also, I just ran the Windows Seven Forums Diagnostics Tool, and here's all the information from running the "grab all" command (attached)

I'll just point out the drivers I see from your dumps, one was inconclusive the other is pointing to,

Avast firewall driver,

Code:

Unable to load image \SystemRoot\system32\DRIVERS\aswNdisFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswNdisFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswNdisFlt.sys

Driver Reference Table - aswNdisFlt.sys

And your NetLimiter software,

Code:

Unable to load image \??\C:\Program Files\NetLimiter 3\nltdi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys

Driver Reference Table - nltdi.sys

Code:

Unable to load image \SystemRoot\system32\DRIVERS\nlndis.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nlndis.sys
*** ERROR: Module load completed but symbols could not be loaded for nlndis.sys

Driver Reference Table - nlndis.sys

Try uninstalling Avast and use Microsoft Security Essentials and Windows firewall since it does not cause BSOD's.

Uninstall NetLimiter too and see if you keep getting the BSOD's.