I just purchased a cheap i5 laptop to be used as my main laptop. It is a used laptop, but is working fine. I replaced its hard drive with the SSD from my previous laptop. Now, whenever I boot the computer I get a BAD POOL HEADER BSOD. This happens soon after starting to boot Windows. I am trying to work out how to find the cause of the BSOD. The SSD is able to boot to Windows with no issues on my old laptop. I presume it may be a driver issue causing it, however no dump file is saved when the computer crashes, so I have been unable to try and find the cause of the crash. Usually, when you take a hard drive/SSD with Windows 10 installed, and put it in a different computer, it will work in the new computer. The first time you boot, Windows will recognise the different hardware and install the needed devices, and after it will finish booting to Windows, and everything will be working just as it was on the old computer. For example, this is the fourth computer I've used this SSD in, with the same install of Windows and I had no trouble at all the last two times I put the SSD in a new computer. I even tried doing a system backup with Todo Backup, and then restoring the backup using the System Transfer function in Todo Backup which is designed to let you use a backup on a computer with dissimilar hardware. Todo asked me for for an inf file to install a driver when it had done the restore, as per step 6 in this link. I was not sure what dirver this was, so I skipped that. However, the result was same. I have done a memory test, which found no errors. The new laptop came with Windows 10 installed, so I know it is quite cable of running Windows 10. I am wondering if there is any way I can get my computer to save boot logs or save a dump file when the BSOD happens, so that I can hopefully track down the issue. I am not prepared to do a clean install of Windows, so if I can't resoved the BSOD issue, I will put the SSD back in my old laptop (where it is works fine). I really don't want to do this, as the new laptop has a bigger screen and is about 50% faster than the old one.
Roger, I don't know if this will be successful but I'd try it. I think you have TeraByte's OSDTool. Run it and select "Remove installed drivers". Then select "Keep storage drivers and remove all other installed drivers". Don't remove the storage drivers with Win10. Success? If it doesn't work you can restore your backup image to get back to square one. Edit... The script has been updated since I last used it. I just ran it and this works. ""Remove installed drivers". "Remove all installed drivers". Then exit. Win10 booted, you see "Getting devices ready", then the desktop.
@Brian K Thanks, I'll keep that in mind. I want to try and find a free solution first, as at the moment I have a very limited budget.
In the past you could buy TBOSDT Pro as a separate item for about $10. I can't see it listed anymore, except as included with other software. Best of luck.
1.2 Causes of this Error 1.2.1 Cause 1: Faulty RAM module 1.2.2 Cause 2: Corrupt or outdated device drivers 1.2.3 Cause 3: Anti-malware software is installed A RAM test doesn't always pick up errors. Try with one stick removed at a time.
I know that the RAM is working. I'm sure it is driver issue, but since I am unable to boot to Windows, or get it to save any log files, I am unable to find what driver is causing the problem. I'm a registered user of Easy Recovery Essentails, which is mentioned in the link, but it was not able to fix the issue.
Bad pool header is supposed to mean a driver or application incompatable with windows 10 is installed. You could try going through it on the old computer and uninstall any that looks suspicious. Shame about the crash dump, it would have said which one it is.
I can give it a go. But, I'm not sure if it would help, considering that it boots with no issues (other than when booting to Safe Mode) on the old computer.
Yeah but bsod in safe mode is not to be taken lightly even if it does boot in normal mode. It is starting to sound like virus activity.
I'm sure that m computer is virus free. I've been trying to do an In-Place Upgrade of Anniversary Update, and was going to put the SSD back in the new laptop after the first reboot. However, setup fails just before rebooting. It says it will restart in a few seconds, and then soon after that setup fails. I've tried doing a clean boot, and I also uninstalled Panda completely (I ran it's uninstaller, and then ran Panada's removal tool), however this has not made any difference. I just ran all the repairs with Tweaking.com's Windows Repair tool to see if that will help. After removing Panda and running Windows Repair, I still get the same BSOD when booting into Safe Mode. I'm trying an In-Place Upgrade again, to see if the it will work now, after running the repairs. I doubt it will, but it's worth a try. Despite the upgrade attemps failing, in the last few months I've had no trouble installing Windows Updates.
Have you tried the Windows built-in utility SysPrep already? It's not designed for use cases like this, but I've read succesful user experiences and also succesfully used it myself once.
I used SysPrep. At first it gave an error, but a quick Google search found a link with some PowerShell commands to fix it, which worked. I got the same BSOD the first time I booted with the SSD in the new laptop. However, now I am getting an INACESSIBLE BOOT DEVICE BSOD when I try to boot normally, or in Safe Mode. I am hopeful that this BSOD will be easier to fix.
I did a search on *oogle for INACESSIBLE BOOT DEVICE bluescreen + windows 10 There is a lot on it and I noticed this one https://www.ghacks.net/2017/06/12/fix-inaccessible-boot-device-windows-10/ and this part of the thread 'Marko June 14, 2017 at 1:23 pm # I have successfully repaired 7 WIN10 laptops with this exact same problem that they give error "Inaccessible boot device" after an Windows 10 update. _____________________________________________________________ Solution: 1. Boot into Advanced startup settings and open CMD(you can do this also through WIN10 USB-boot device) and type: • cd C:\Program Files (NOTE THAT THIS CAN VARY! Program Files can be under "D:" for example) • takeown /f WindowsApps /r /d Y • attrib WindowsApps -h • rename WindowsApps WindowsApps.old 2. Then run System restore 3. Reboot successfully into Windows'
I just tried that. I was unable to run System Restore at end, because it found no Restore Points. I did not work. But, I don't think it would have worked even if I had been able to do the restore, as Windows booted fine on the old laptop. It's only on the new laptop where there are issues.
