What is a "bad pool header". When it comes up it demands to reboot. Things will be just fine and then occasionally it will come up again and demands a reboot. Is there any "fix". What is going on, any way to fix it, to stop the process. What and why is it occurring?
I started getting some BSOD errors after updating to Windows 10 from 8.1. Windows 10 updated a couple months ago, and since that update I get bad pool header crashes multiple times a day. I used the DM log collector and attached the file.
Since upgrading to Windows 10 from Windows 7, my computer would crash once a day with a bad pool header notification. I have tried everything I can think of to resolve this issue, and am coming here as a last resort. Below is my DM Log Collector zip.
I tried updating to Windows 10 from Windows 7 Pro Sp1.
Update went through fine but as soon as I get to the login screen and hit enter I get a BSOD with Bad Pool Header. I couldn't boot into safe mode, do the "reset my PC" option or system restore. The system restore says image corrupt.
Only thing I could do is go back to previous build, which worked.
So now I was going to try to manually install, but getting the Windows 10 iso through the media creation tool. I load it up and it just loads and says "something Happened" 0x8007002- 0x20016. I also wanted to get my product key to have on hand for when I do get it to work. So I load up Produkey, and it says my Product Key not found.
There is a script that is on the MS scripting site that will query and convert the key from hex to decimal. I run that and it reports back just "B". All B's.
So im assuming my key got screwed up during the install. Not sure what else i can do if I don't have a key to install Windows 10 when I get an ISO from another computer.
Every since I upgraded to windows 10 and boot my desktop machine I get a BSOD with Bad Pool header. It keeps looping and rebooting with the same error. The only way around it is to go into the bios and save changes and then it allows me to log in. I have disabled fast reboot and still no joy. Attached is a log file with all the relevant info
Upgraded a stable Win7 laptop to windows 10 and started getting Bad Pool Header BSODs. Some I cleared ( It used to happen immediately when connecting the network cable).
It happens a short time after I connect with the regular windows VPN to our office.
After I upgraded to Windows 10 I have been getting BSODs at when either watching videos in VLC or playing mainly World of Warcraft. The primary BSOD I have been getting is the bad_pool_header which first occurred a week after upgrading and was seemingly a random occurrence. Subsequent BSODs would occur at least every other day, if not longer apart, and I didn't think much of it. However, I experienced two bad_pool_header errors today within 4 hours of each other, both while watching videos in VLC with some web browsing so I am believing that it is a more serious error than random crashes.
I just got Windows 10 today and when I did my own stuff, I get Bad Pool Header error messages. It has happened every time when plugging in game controller or accessing internet.
Is my computer not compatible with Windows 10? Or is it something else?
creating the zip file but the dmp files weren't in there when I followed the instructions so i have managed to make copies instead hopefully this still works.
Problem started a few weeks back out of nowhere , had a few watchdog failures but they have stopped now, I have uninstalled most programs which may of being causing it but still having no luck.
Running updated Windows Ten, etc its the Lenovo Flex 2 pro laptop.
I recently bought a new laptop with Windows 10 (just a few days ago), and last night, after a short gaming session on the laptop, it blue-screened with the error being indicated as being: Bad_Pool_Caller. I was just wondering how I should proceed from this point on to make sure the laptop remains functional and everything works smoothly.
I've just built my new computer however am getting heaps of BSOD saying bad pool caller. I've downloaded blue screen view and here is what comes up.
[URL] ......
My computer is i7 5820k Noctua nh d15 Asus x99 pro kingston hyper x fury 4 x 4gb 2133 samsung 850 evo ssd 250gb x 2 wd caviar blue 1tb x 2 Gigabyte geforce gtx 960 4gb corsair rm850i
I followed the instructions and uninstalled Kapersky Antivirus. Still getting the Bad Pool Called Blue Screen now and again. Also finding I can not turn on my windows defender it just keeps turning it self back off again instantly. I have uploaded the dmp files.
'm having a major crash issue with 'bad pool caller'. i found a similar thread and tried to follow.BSOD bad_pool_caller, possibly related to wi-fi adapter - Windows 10 Forums.
I'm having for a while a BSOD Bad pool caller. All the drivers and software in my OS are up to date. I don't think it's a memory problem, the Windows Memory Diagnostic gave me no errors, I also tried the SFC /SCANNOW to try fixing the file systems, and also chkdsk /r to check and the disk integrity, but everything seems cool. I did all types of virus/malware scans with mcafee and malwarebytes, my system still seems clean.
I'm using a ACER Aspire E5 - 511 - P29D: Intel Pentium quad core processor N3540.
It doesn't happen at a particular moment, I can be browsing on the Internet or watching a movie. And it's not frequent, it happens every 3 or 4 days. It started 6, 7 weeks ago, after I did a upgrade to Windows 10. I haven't made any change to my computer yet.
I've had some issues with a BSOD for over a year now, first when I was running Windows 8 and now still with Windows 10. It first appeared after I got a USB wi-fi adapter which I replaced with an adapter that connected to the motherboard, but the BSODs have not stopped.
I inquired about it a few months ago on several other forums. It was apparently related to some driver that the USB adapter installed (the name of which I can no longer remember), but I was unable to uninstall it or delete it without my wi-fi becoming unusable. I'm also unable to use a wired connection in my apartment, though I'm not sure that would even be possible if I deleted the driver. The error code I get is "bad_pool_caller", but I believe I used to get "irql_not_less_or_equal" as well.
For some background, the BSOD usually appears when I'm doing something intensive over the internet like watching video on YouTube or Twitch, streaming audio, etc.
Here's my debug folder: COLIN-PC-Wed_09_02_2015_214036_86.zip
My problem is very similar to one described by tomzino earlier this month in this forum. Since upgrading from windows 7 home premium to windows 10, my computer gets a BSOD and reboots daily; so far in November it has crashed 20 times. The only days it didn't, the system was powered down. The error message is the 'bad pool header' . Oddly, 85% of the BSODs have occurred between 12:12pm and 12:43pm EST. I ran the DM Log collector to gather the information from the last two crashes for diagnosis.
I had 3x 3TB drives in a parity pool. It started to fill up so i added a fourth 3TB drive and months later one of the original 3 began to fail on me. Performance was slow, then slower, then it showed disconnected.
I retired the drive and added a replacement, literally the same model 3TB drive. I cannot however, get it to remove the failed physical disk and repair the pool. I even tried adding another 2TB drive i had available in case it needed the extra space (didn't make sense but i was reaching).
I get the "drive could not be removed because not all data could be reallocated. add an additional drive to this pool and reattempt this operation."
I have searched a lot and don't really seem to be getting anywhere. The only way i was able to retire the drive was through powershell. I'm assuming it's a GUI issue and perhaps i'm not approaching it correctly via powershell. Attempting to repair virtual disk didn't work.
I really don't want to lose this data. I wasn't able to backup much before the drive failed completely.
If I run SFC it tells me I have corrupt files that it can not fix. When I tried to use DISM checking health says the files can be repaired yet if I run DISM with /online feature with out a source it says the same thing if I run it with a source which is it can not find the files needed. I have attached the CBS log and DISM log below in
After I installed TH2 on Thursday I decided to run a SFC check to see if I had errors and it came up with some that it said it couldn't correct. The assembly look at the attached file and tell me what I need to do.
I downloaded and installed windows 10 home premium version on my desktop. The blue screen have been annoying me time by time when I'm using OS properly. There are several errors shows up every often, such as bad pool xxxx, page management, no area paged found. I tried reinstalled OS but the problems still exist. How to solve those errors. Someone said its caused by the drive software which I don't know how to pick it up from so many drive tools in my system. By the way, is there anyway to solve problems directly except downloading new OS version again?Currently running home premium 10240
I purchased a new NUC6i3SYK last week. I have installed a 250gb Samsung evo 850 M.2 HD and 1 8gb stick of Corsair PC4-17000 DDR4 Ram.
Windows 10 is a fresh purchase and install downloaded direct from MS.
The Nuc worked fine with both the HD and Ram being recognised and W10 installed fine. I loaded the drivers from the Nuc support page and then updated Windows. Everything still fine. Then I proceeded to install other programs and went to bed.
Next morning the PC had crashed and failed to restart. After searching the net for possible cause I decided to reinstall Windows 10. This time i didn't load any drivers and the PC was NOT able to connect to the Internet because I thought one of the updates may have cased the crash.
PC was still unstable and crashed often to the point it was in a BSOD loop. I then reinstalled Windows 10 again and this time I installed the LAN driver only and Windows 10 updated itself. It stayed on for 12 hours and has now gone into a BSOD loop again.
The BSOD error message changes but the main ones seem to be
Run Memtest86 for approx 20hrs with no errors Performed a disk check Installed samsung magician to confirm HD firmware is the current version Updated the BIOS to current version
For the past few weeks I've been seeing errors in the Event Viewer relating to the LockScreen. These only happen when waking the PC up from Sleep mode. The errors are:-
5973 Activation of application Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error: The app didn't start in the required time. See the Microsoft-Windows-TWinUI/Operational log for additional information.
and
1002 The program LockApp.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.