Windows 10: Constant BAD_POOL_HEADER BSOD after upgrade from Win7 to Windows 10

I have upgraded my Windows 7 Home Premium 64bit system to Windows 10. I have now completed this twice on this PC: first using Windows Update, and secondly (after rolling back to Win7) using the Media Creation Tool.
My problem is that within the first few minutes of start-up I always receive the BSOD BAD_POOL_HEADER.
This primarily occurs around a minute after login, sometimes up to 5 min, but on some occasions has also occurred before the login screen is displayed.
Based on what I've read in other threads I have tried disabling my DVD RW drive and card readers. I've removed all non-essential USB devices along with an el-cheapo USB 3 card I bought years ago and have had some trouble with in the past. I have four 4GB RAM chips installed, all DDR3 1333, but two different brands, so I have also tried removing two of them at a time (leaving remaining two in correctly colour-coded slots), all to no avail.
The problem does not occur when booting into safe mode.

I've included two debug files, one quickly taken under normal boot after only a couple of crashes, and the second taken in safe mode which includes a few more dump files.
This system has been running perfectly well on Windows 7 for six years. I hope someone can point me in the right direction to troubleshoot. Thanks in advance,
Ben
Attachment 75408
Attachment 75409

:)

 

Bad_Pool_Header started after a Windows 10 upgrade

Did the BSODs start immediately after you upgraded on 29 January 2016 or...?

 

Daily BSOD after upgrade to Win 10

hello,

I am using windows on my iMac. Early this month (July 2016), I upgraded from Win 7 to Win 10. Right after the upgrade, I get BSOD upon re-start. I remember one of the errors was BAD_POOL_HEADER. After the BSOD restart, it is working again. But ever since,
I am still getting BSOD when I turn on the computer almost every morning. And it works find throughout the day.

Anyone has any ideas?

 

Hi and welcome,

Both in normal and safemode your licence is not OK.
Please make sure that your Windows is Genuine:

Code: <DiagReport> <LicensingData> <ToolVersion>10.0.10586.0</ToolVersion> <LicensingStatus>SL_LICENSING_STATUS_UNLICENSED</LicensingStatus> <LicensingStatusReason>0xC004F014</LicensingStatusReason> <LocalGenuineState>SL_GEN_STATE_IS_GENUINE</LocalGenuineState> <LocalGenuineResultP>1</LocalGenuineResultP> <LastOnlineGenuineResult></LastOnlineGenuineResult> <GraceTimeMinutes>0</GraceTimeMinutes> <TotalGraceDays>0</TotalGraceDays>[/quote] Also:

Please remove all pirated programs and such from your system before we can start troubleshooting.
The Forum rules is meant for everything regarding piracy

• Discussing it,
• Asking for guidance,
• Asking for a crack,
• The use of it,
• Etc.

4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).



Code: # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost 127.0.0.1 activation.guitar-pro.com[/quote]

 

Thank you for your reply. I cannot understand why Windows is not showing as genuine - Windows 7 Home Premium OEM was bought and paid for and installed by the system builder. It always showed as genuine before I upgraded to 10. Unfortunately I do not know where to find the product key. When I try (in safe mode) to check Settings > Update & Security > Activation, the "Update & Security" window fails to open and the "Settings" window closes.
I have removed the offending Guitar Pro software and updated the hosts file accordingly. Would a fresh dump file be useful at this point?

 

Please open an admin command prompt and enter following command
Code: slmgr /dlv[/quote] Post a screenshot of the pop-up that shows, it may take a few moments for the pop-up to show.

 

Thanks:
Attachment 75423

 

It is normal that in safe mode the genuine state changes (don't ask why).
If the activation gives problems it can be quite some reasons as to why, if that would happen you better create a thread at Windows Updates and Activation - Windows 10 Forums for assistance

Your activation looks fine *Smile

 

Ok i had a look at the two DMP files.

First off, did you overclock your system? Reason for asking :
Code: 0: kd> !sysinfo cpuspeed CPUID: "Intel(R) Core(TM) i5 CPU 661 @ 3.33GHz" MaxSpeed: 3330 CurrentSpeed: 3345[/quote] If so, please revert you OC to stock speeds. OC's are a possible reason for unstable systems.

Your two DMP files point to : dnelwf64.sys

Driver Reference Table

This driver seems to be Citrix related.
@ the support page ( DNE Support - Deterministic Networks - Citrix)

there is a mentioning of possible BSOD's on W7.
I would remove the software/drivers completly, and after a reboot do a clean install of this software.
Hopefully that will clear out the bugs. I must note that i didn't see any reference to Windows 10 at this page.
Might not be compatible?

 

Thanks so much for your help zztemp and axe0.
I have not overclocked my system, although I did notice a baked-in feature in the BIOS called Intel Turbomode which allows the system to automatically increase the clock speed in some situations. This was set to [Enabed], and I have set it to [Disabled]. I notice, however that the current speed is still showing 3345 Mhz in the msinfo32.nfo. Odd - I'm not sure how to address this - I've tried restoring BIOS to default/recommended settings, but there appears to be no change.
I have uninstalled Cisco VPN client, and tried uninstalling DNE Update, but receive the message: "Unable to manage networking component. Operating system corruption may be preventing installation."
I've followed all the instructions on the DNE Support page including running the winfix tool, but cannot seem to get DNE Update completely uninstalled. I've emailed Citrix Support regarding this to see what they can advise and also attached the log created by winfix here in case it sheds any light.

When the BSODs continued I also removed some old stuff I'm no longer using from startup, and on next boot to normal mode things seemed to be going OK for perhaps 20 minutes, then another BSOD but this time with a different error: KMODE_EXCEPTION_NOT_HANDLED
That seemed like progress, but subsequent boots have seen the return of BAD_POOL_HEADER very soon after login, so I've again had to create the most recent debug file from safe mode. I noticed the previous one taken in normal mode showed <LicensingStatus>SL_LICENSING_STATUS_LICENSED</LicensingStatus> so I've included that too.

Attachment 75649
Attachment 75650
Attachment 75651

 

Please verify that all VPN software is removed while troubleshooting and follow below instructions.





Diagnostics Test

Clean boot
Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
If the problem still persist, try booting in safe mode and see if the problem still persist

 

Thank you axe0.
I have confirmed no VPN software remains installed.
I can confirm the problem still exists under clean boot with all startup applications and non-MS services disabled.
I can confirm the problem does not exist in safe mode with networking.

I have received a response from Citrix Support as follows:

Ben


It may be impossible to uninstall DNEUpdate in your situation. First it is a very old DNE (​7/26/2010) that is not for Windows 10. The many crashes may very well have cause more corruption. But you can try these steps:



1) From safe mode, delete the file c:\windows\system32\drivers\dnelwf64.sys

2) Reboot and see if it is possible to uninstall DNEUpdate from the Programs Control Panel. This is probably unlikely since winfix has ran prior.

3) Try winfix again



----------------------



You can do Windows Recovery to put the OS back to the beginning state. Be careful though. I think Recovery will remove the possibility of going back to Windows 7.



http://windows.microsoft.com/en-us/w...covery-options



You can go back to Windows 7 and start over.


I tried the above before sending the following response:Thank you for the suggestions Bill.


I followed the instructions you provided, and you were right: even after deleting dnelw64.sys it was not possible to uninstall DNE Update. I ran winfix again, and this also reported DNEUpdate could not be uninstalled. On reboot, however, the BSODs were gone. Unfortunately, however, so was the ability of my NIC to make any connection, even to the connected router. Windows troubleshooting suggested a problem with the LAN Connection Adapter driver. I downloaded the updated driver from the manufacturers website using another device and transferred it to the affected system and uninstalled, then reinstalled the adapter driver. This had no effect. After trying several troubleshooting steps including sharing the internet connection from my phone which was also unsuccessful, I restored dnelw64.sys from the recycle bin. This restored my network connectivity, but also the BSODs.


Given this information do you have any advice on how I can restore my connectivity in the absence of dnelw64.sys? Or are my only options to perform a system recovery or revert to Windows 7? Neither are particularly attractive to me as I feel like I'm really close to having a functional Windows 10 system, but I don't want to lose the ability to go back to 7 if the recovery fails to fix the problem. Is a registry cleaner or similar likely to help whilst dnelw64.sys is removed?


Thanks and regards,
Ben


So it seems the problem is likely related to dnelw64.sys, however I suspect it could equally be related to some other application or service that does not run in Safe mode, but only causes a problem when it has network connectivity.

Any other suggestions would be much appreciated before I resign to restoring back to Windows 7.

Many thanks,
Ben

 

So I heard back from Bill at Citrix support:

"You can uncheck DNE from the network adapter properties. But this does not fix the corruption that may prevent installation (and uninstall) of other network filter drivers.



It is better if you go to a clean state first. And don't install this version of DNE onto the clean system."

So as a test I have tried that: deleted dnelw64.sys and booted to normal mode, confirmed no BSOD, but no network connectivity.
Disabled DNE Lightweight Filter in the network adapter settings and connectivity restored, and 3 hours now with no BSOD.
Having confirmed the root cause, when I get the chance I will restore to the clean Win7 state, correctly uninstall the old version of DNE, and then attempt the upgrade again.

Thank you very much to the very knowledgeable folks here (and Bill from Citrix) for the excellent assistance. I know you do this in your spare time - let me know if/how I can buy you a beer.

I hope this information will be useful to someone else in this situation.

 

Thank you for sharing your solution, I'm sure it'll help lots others *Thumbs