BSOD every 15-20 minutes - Bad Pool Header

[cjt20one]

I have a custom built PC running Windows 7 Pro x64. The all parts are 15 months old except for one 750 GB internal HDD I have some media on.

There doesn't seem to be any real pattern to the BSOD. The closest thing to a pattern I've noticed is when I've been working for a while and then open a new application it'll BSOD. So I'm doing xyz in Outlook, then I decide to open Chrome and it blue screens.

I swapped out the RAM (I have two 4 GB DIMMs) and it make the BSOD's far less frequent but they still happen. Prior to the RAM swap it was happening every 15 minutes or so. After the RAM swap it'll go 1-2 hours without a BSOD.

I haven't made any other hardware or software changes recently. I did the usual virus/malware removal techniques but nothing turned up. I can work in Safe Mode without issue.

At this point I think it might be two things:
1) The old 750 GB internal HDD. One time I opened Windows Explorer and began to browse that drive and it BSOD'd right away.

2) I have a PCIe card for wireless - TP-Link 450 Mbps N Dual Band. I have a suspicion that it might be causing the problem.

 

[x BlueRobot]

Welcome to the forums cjt20one,

[COLOR="Red"]BugCheck 19[/COLOR], {[COLOR="Blue"]20[/COLOR], fffffa800a33b680, fffffa800a33b720, 40a000d}

GetPointerFromAddress: unable to read from fffff80003513100
GetUlongFromAddress: unable to read from fffff800035131c0
Probably caused by : [COLOR="Red"]memory_corruption[/COLOR] ( nt!MiUnmapViewOfSection+295 )

Usual causes:  Device driver

This bugcheck indicates that a pool header has become corrupt, the Windows Memory Manager will allocate a block of memory which is more than needed, in order to add information about the allocation such as size and a tag, the extra memory used is called the header.

The common causes for this bugcheck are device drivers, RAM and the hard-drive.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.