Bsod at random times.. bugcheck code 19, bad pool header

[jeff321]

Hey all and thanks for your help. My friend just bought this laptop and im trying to help him out. The bsod has happened twice in the last few days and from what i can tell it is a driver maybe trying to be loaded twice..? Or maybe a iscsi initiator problem possibly?

Here is my dm log collector file and thanks again!

 

[jeff321]

Dont know if this helps but the BSOD did happen while downloading a windows update the second time.. He just bought this pc used on 6-11 (it does have its serial key sticker) I have run sfc/ scannow and windows memory diagnostics on it with no errors. I dont see any sign of malwarebytes ever being on this pc.

And here is a WhoCrashed 5.51 scan.

 

[axe0]

Hi jeff321,

Could you upload the memory.dmp in %systemroot% to a 3rd party uploader like dropbox, onedrive, google drive, or another one and post a share link in your next reply. It is only for this time

While trying to check something I am blocked because of limited data the minidump holds.

GetPointerFromAddress: unable to read from fffff80002f08100
Unable to get MmSystemRangeStart
GetPointerFromAddress: unable to read from fffff80002f08100
Unable to get MmSystemRangeStart
GetPointerFromAddress: unable to read from fffff80002f08100
Unable to get MmSystemRangeStart

 

[jeff321]

Hey axe0 and thanks very much for your help! Here is the link
https://drive.google.com/file/d/0ByErjwuRRi_2Z2FIRVMyTUUtemM/view?usp=sharing

 

[axe0]

As I suspected, the pool was corrupted, this may be due to the Intel network drivers. If updating the Intel network drivers from Dell doesn't help then enable driver verifier per below instructions to catch the driver that corrupted the pool before Intel referenced it.

0: kd> !pool fffff8a00dc3d650
Pool page fffff8a00dc3d650 region is Paged pool
 fffff8a00dc3d000 size:  580 previous size:    0  (Allocated)  NtfF
 fffff8a00dc3d580 size:   10 previous size:  580  (Free)       ....
 fffff8a00dc3d590 size:   c0 previous size:   10  (Free )  FIcs
*fffff8a00dc3d650 size:  130 previous size:   c0  (Free ) *Ntf0
		Pooltag Ntf0 : General pool allocation, Binary : ntfs.sys

fffff8a00dc3d780 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...

fffff8a00dc3d780 is not a valid large pool allocation, checking large session pool...
Unable to read large session pool table (Session data is not present in mini and kernel-only dumps)
fffff8a00dc3d780 is not valid pool. Checking for freed (or corrupt) pool
Bad previous allocation size @fffff8a00dc3d780, last size was 13

***
*** An error (or corruption) in the pool was detected;
*** Attempting to diagnose the problem.
***
*** Use !poolval fffff8a00dc3d000 for more details.


Pool page [ fffff8a00dc3d000 ] is __inVALID.

Analyzing linked list...
[ fffff8a00dc3d650 ]: invalid block size [ 0x13 ] should be [ 0x3 ]


Scanning for single bit errors...

None found

0: kd> !poolval fffff8a00dc3d650
Pool page fffff8a00dc3d650 region is Paged pool

Validating Pool headers for pool page: fffff8a00dc3d650

Pool page [ fffff8a00dc3d000 ] is __inVALID.

Analyzing linked list...
[ fffff8a00dc3d650 ]: invalid block size [ 0x13 ] should be [ 0x3 ]


Scanning for single bit errors...

None found


0: kd> lmvm NETwsw00
Browse full module list
start             end                 module name
fffff880`06853000 fffff880`073a3000   NETwsw00   (no symbols)           
    Loaded symbol image file: NETwsw00.sys
    Image path: \SystemRoot\system32\DRIVERS\NETwsw00.sys
    Image name: NETwsw00.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR="Red"]Tue Jul 01 16:50:11 2014[/COLOR] (53B2CAA3)
    CheckSum:         00B0AD37
    ImageSize:        00B50000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[jeff321]

Hey axe0.. I installed the new drivers for the wired and wireless I believe. Think I also installed intel proSet/wifi software by accident. The computer only crashes every now and then it seems, so do you want me to just give it some time to see if it crashes again or should I go ahead and use verifier to make sure that was it?

Let me know what you want me to do and thanks again!

 

[axe0]

If updating the Intel network drivers from Dell doesn't help then enable driver verifier per below instructions to catch the driver that corrupted the pool before Intel referenced it.

 

[jeff321]

Ill give it a week and if all is fine I will come back and mark as solved.

Thanks again man!