Bad_Pool_Header, Bsod error
Sounds like you need Alienware Verify and/or Nvidia’s. And check in their forums for known issues.
If this is a new computer then Alienware as OEM is responsible for the proper operation of both the hardware and Windows. So regardless of the cause it is theirs to resolve. And should be in full warranty.
If you want to troubleshoot the issue which I would not do on a brand new computer :
Troubleshoot blue screen errors
We can analyze the minidumps if you make them available from the OneDrive or other file sharing sites (such as MediaFire).
If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there.
Adding files to your OneDrive
Upload photos and files
One-Drive – Go Halve files and folders and change permissions
Zip or upload the contents of C:\Windows\minidump
Use OneDrive to upload collected files
Troubleshoot blue screen errors
BCCode: 19 0x00000019
That could be drivers although antivirus/antispyware/security programs and other
hardware are also probable causes. Updating the major drivers and BIOS would be
the best plan of attack. If needed also try uninstalling your antivirus/security as a
BCCode: 19 0x00000019 <– read this link
This advantage makes it easy to see which versions are loaded :
Run DriverView – set VIEW to Hide Microsoft drivers – update those without
Dump in their names (and update BIOS and chipset).
DriverView – Free – utility displays the list of all device drivers currently loaded
on your logic. For each driver in the list, additional useful information is
displayed: load address of the driver, description, edition, product name,
company that created the driver, and more.
For Drivers check Logic Maker as fallbacks and Device Maker’s which are the
most current. Control Panel – Device Manager – Display Adapter – send a letter to down
the make and complete model of your cartridge adapter – double click – Driver’s
tab – send a letter to down the version info. Now click keep informed Driver (this may not do
anything as MS is far behind certifying drivers) – then Right Click – Uninstall –
REBOOT this will refresh the driver stack.
Repeat that for Network – Network Card (NIC), Wifi, Thorough, Mouse and Keyboard
if 3rd party with their own software and drivers and any other major device drivers
Now go to Logic Maker’s position (Dell, HP, Toshiba as examples) (as rollback) and
then Device Maker’s position (Realtek, Intel, Nvidia, ATI as examples) and get their
latest versions. (Look for BIOS, Chipset, and software updates at Logic Maker’s
position while there.)
Download – SAVE – go to where you put them – Right Click – RUN AD ADMIN –
REBOOT after each installation.
Always check in Device Manager – Drivers tab to be sure the edition you are
installing actually shows up. This is because some drivers rollback before the
latest is installed (thorough drivers particularly do this) so install a driver – reboot
– check to be sure it is installed and repeat as needed.
Repeat at Device Makers – BTW at Device Makers DO NOT RUN THEIR SCANNER –
heck manually by model.
Manually look at manufacturer’s sites for drivers – and Device Maker’s sites.
Memory tests do not catch all errors such as mismatched memory (possible even
for sticks that appear to be identical) and when faster memory is placed in logic
behind slower memory. So it is best to also change over sticks in and out to check for
those even if all memory tests fail to show a problem.
To litmus test RAM check here – let it run 4+ hours or so. <– best method
MemTestX86 – Test RAM With
For the Windows Memory Diagnostic Tool.
Type in Cortana’s search box -> Windows Memory Diagnostics
at top of list – click it. in Windows 8/8.1/10 the name is “Windows Memory
After doing ALL the updates you can, and if the issue continues, then run
Driver Verifier can help find some BSOD issues :
Using Driver Verifier to identify issues with Windows drivers for advanced users
How To Troubleshoot Driver Problems in Windows Seascape or 7. (8/8.1 and 10
are essentially the same).
WINKEY + X – RUN – capture in -> verifier /reset hit enter to disable
Use BlueScreenView to see if there is a driver specified in the error message.
Also check with MyEventViewer at the phase of the BlueScreen.
If DriverVerifier creates a minidump upload it and post the link here so we can
Hope this helps.
Rob Brown –
Microsoft MVP <- profile – Windows Experience : Bicycle – Mark Twain said it right.