Windows 10: Ongoing BSOD Issues - BAD POOL HEADER

Hi.

I have been experiencing BSOD on a fairly regular basis. They seem to occur randomly, usually at least once a week.

I am running Windows 10 on a HP Spectre X360.

The DM log collector file is attached.

Any help on how to solve it would be much appreciated.

Thanks
Dominic

:)

 

Guys I really need your help. I'm getting BSOD (Bad Pool Header) so many times.

Click HERE for a really good thread on Bad Pool Header BSOD.

The thread is based around Windows 8, but the solution from Nannya Podder holds true for WIndows 10

I hope this Helps resolve your BSOD issue!

 

Win10 BSOD, Help.

One other thing when I did see the BSOD at random, it said BAD POOL HEADER.

 

Looks like you are over clicking your PC a bit:

Code: 3: kd> !sysinfo cpuspeed CPUID: "Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz" MaxSpeed: 2300 CurrentSpeed: 2400[/quote] Please set all clocks and voltages to normal, see if that makes any difference.

Also noticed you have some very old (2011) drivers from SuperAntiSpyware. Plese uninstall it, see if that helps.

 

Thanks for the response.

I havent done any overclocking myself, if it is high it has automatically done that. I had a quick look and couldn't find anywhere to change it in the bios.
I uninstalled superantispyware, but an hour or so later I got another BSOD (same bad pool header code). The latest dm log is attached.
Attachment 100510

 

Hi dominics.

My apologies for bumping in, but I'm posting to clarify the 'overclock' a bit.

Per the information provided by Intel it isn' an overclock, the CPU has a max frequency range of 2.8GHz.
This means that the CPU will perform with a frequency between 2.3GHz and 2.8GHz without any change in the BIOS or software, to add any overclock method is usually not possible with laptops.

 

Thanks for the info @axe0.

 

The latest dump indicates a problem with tdx.sys which is a Microsoft driver.
Code: BugCheck 19, {3, ffffc2870d6c9750, 0, ffffc2870d6c9750} *** WARNING: Unable to verify timestamp for tdx.sys *** ERROR: Module load completed but symbols could not be loaded for tdx.sys Probably caused by : tdx.sys ( tdx+6dbd )[/quote] Try updating the driver for your Intel® Dual Band Wireless-AC 7265 device. There is a 8/3/2016 update available. The one you have now is dated 2/26/16: Drivers & Software

 

I've installed the update and I'll let you know how it goes over the next couple of days.

Thanks

 

Had another BSOD just now, log file attached.
Attachment 101022

 

Something is going on but I don't know what the cause is. Got the following errors in windbg:

Code: ffffcc00`88a9b040 fffff802`d468e8a0Unable to load image \??\C:\WINDOWS\system32\drivers\mwac.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mwac.sys *** ERROR: Module load completed but symbols could not be loaded for mwac.sys[/quote] This belongs to MBAMWebAccessControl. Uninstall it and see if that helps.

Code: ffffcc00`88a9c908 fffff802`d4b09c4cUnable to load image \SystemRoot\System32\drivers\Netwtw04.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Netwtw04.sys *** ERROR: Module load completed but symbols could not be loaded for Netwtw04.sys Netwtw04+0x109c4c[/quote] This belongs to Intel(R) Wireless Adapter. Not sure what to do here as you have the latest driver available.

Code: ffffcc00`88a9dbf8 fffff802`ce2bf9a0Unable to load image \SystemRoot\system32\drivers\networx.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for networx.sys *** ERROR: Module load completed but symbols could not be loaded for networx.sys networx+0xf9a0[/quote] Description: Networx.sys is not essential for Windows and will often cause problems. Networx.sys is located in the C:\Windows\System32\drivers folder.
The driver can be started or stopped from Services in the Control Panel or by other programs. The program is not visible. The file is certified by a trustworthy company. The service has no detailed description. The networx.sys file is not a Windows core file. networx.sys appears to be a compressed file.

You can try stopping it in Services, see if that helps. I just checked and I don't have it on my computer.

 

Hi have uninstalled Networx, if I get another BSOD i'll uninstall malwarebytes.
I'll let you know how it goes.

 

I had another BSOD, but this one was a bit different. I occurred when I tried to put the computer to sleep (i didnt actually see the BSOD come up, but it did produce a minidump).
Attachment 101162

 

Still indicating a possible problem with your Intel Wireless:

Code: 2: kd> !irp ffffbb85c49866f0 Irp is active with 5 stacks 3 is current (= 0xffffbb85c4986850) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. cmd flg cl Device File Completion-Context [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 0 ffffbb85bc4f9050 00000000 00000000-00000000 Unable to load image \SystemRoot\System32\drivers\Netwtw04.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Netwtw04.sys *** ERROR: Module load completed but symbols could not be loaded for Netwtw04.sys \Driver\Netwtw04 Args: 00014400 00000000 00000004 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffbb85bbbab970 00000000 fffff80348647cac-ffffbb85beac5b80 Success Error Cancel pending \Driver\vwifibus nt!PopSystemIrpCompletion Args: 00014400 00000000 00000004 00000002 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffffbb85beac5b80 Args: 00000000 00000000 00000000 00000000[/quote] As you already have the latest driver for this, I'm not sure where to go.

One thing you can try is look through the Power Options and uncheck any settings that reduce power to the wireless.

Attachment 101291

 

Thanks for your continued support Ztruker.

I have set the 'On battery' wireless setting to maximum, the 'Plugged In' was already at maximum. I'll just be sure to put the computer to sleep via the start menu instead of just closing the lid, that seemed to be when it occurred.

It does seem to be going well since uninstalling Networx (at least regarding the original BSOD problem), fingers crossed that was it.
I'll keep you updated on how it goes the next few days.

Cheers