BSOD after clean install of Win7 - BAD_POOL_HEADER - 0x00000019

[herebepenguins]

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!

 

[herebepenguins]

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?

 

[herebepenguins]

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

 

[herebepenguins]

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!

 

[herebepenguins]

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?

 

[herebepenguins]

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?

 

[herebepenguins]

Oh, and here's the output result file!

 

[essenbe]

Run Memtest86+ V 4.20, the next one down. You can download the USB key installer and run it from a USB key, if you want. Let it run for 8 complete passes or overnight. Each pass includes 9 tests and easch pass tests something different, so it takes 8 passes at least to do a full check. If you get errors, you can stop the test by pressing escape key.

The minidump file always gives that warning as it is a system dump file, click continue and paste it to your desktop. Then right click it, select send to then select compressed zip folder. Upload the Zip folder with your next post.

 

[Britton30]

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

This file has 2 dmp files from Mar 2 in it.

If you use the memtest86+ 5.01 again, let it start on its own without pressing anything. The 4.20 will be best for your system though as essenbe said.

 

[derekimo]

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,

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,

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

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.

 

[herebepenguins]

Computer no longer crashing, but is now freezing randomly

I was having a lot of trouble with BSODs in the past, but I recently just went through a long period of time where there were actually relatively few problems with my computer... and then the freezing started to occur. It happens on a completely random basis - the computer appears at first as though it is struggling as if I gave it a taxing command, but then it becomes completely unresponsive - nothing works. I can only move the cursor (the "loading" one) around a screen that responds to nothing. I'm not sure what to do. How would I go about figuring out what is wrong with my computer?