BSOD while playing Battlefield 3, error 0x0000019 (Bad_Header_Pool)

Security App
Crashes indicate AVG and Kaspersky being a possible cause. Remove them and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software

Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials for Windows
MalwareBytes Free

   Information

• Do not start the free trial of MalwareBytes, unselect that option when prompted.
  
  
• Update and make full scans with both separately.

Daemon Tools/Alcohol %
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

As an alternative many people recommend the use of Total Mounter or Magic ISO

Start up
Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

Performing a Clean Startup
Startup Programs - Change

Code:

AppleCharger.sys            Mon Jan 10 15:57:29 2011 (4D2AD809)

GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge [br] May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
Driver Reference Table - AppleCharger.sys

gdrv.sys Fri Mar 13 09:22:29 2009 (49B9D175)
Gigabyte Easy Saver - mobo power utility driver
Driver Reference Table - gdrv.sys

Please remove the software above with Revo Uninstaller free.

   Note

Revo Uninstaller
Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware

Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

SFC /scannow

1. Click Start
2. In the search box, type Command Prompt
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type

Code:

sfc /scannow

5. Hit enter
System File Checker

This tutorial USB Selective Suspend - Turn On or Off may help:
To Disable Selective Suspend:
1. open the control panel
2. go to power options (you may have to set view to small icons)
3. click change plan settings
4. in the window that opens:
5. click change plan settings
6. click change advanced power settings, expand usb and ensure usb selective suspend is disabled.

Memtest86+
Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
How to test and diagnose RAM issues with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

   Tip

Do this test overnight.

BSOD BUGCHECK SUMMARY

Code:

Debug session time: Tue Jul  9 07:26:28.158 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:41:54.001
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72e6 )
BugCheck 19, {22, 80000000000000, 0, 0}
BugCheck Info: BAD_POOL_HEADER (19)
Bugcheck code 00000019
Arguments: 
Arg1: 0000000000000022, 
Arg2: 0080000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_22_nt!_??_::FNODOBFM::_string_+72e6
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Jul  9 06:30:26.077 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 4:03:26.920
Probably caused by : usbhub.sys
BugCheck 9F, {3, fffffa8009a6c440, fffff80000b9c3d8, fffffa800d085820}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Bugcheck code 0000009F
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8009a6c440, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800d085820, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_athurx_IMAGE_usbhub.sys
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Jul  9 01:11:19.431 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 8:32:14.664
Probably caused by : usbhub.sys
BugCheck 9F, {3, fffffa800a697440, fffff80000b9c3d8, fffffa800b548c10}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Bugcheck code 0000009F
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800a697440, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800b548c10, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_athurx_IMAGE_usbhub.sys
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Jul  7 09:11:14.749 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 14:02:25.982
Probably caused by : usbhub.sys
BugCheck 9F, {3, fffffa800a1aa440, fffff80000b9c3d8, fffffa8006cb85a0}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Bugcheck code 0000009F
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800a1aa440, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8006cb85a0, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_athurx_IMAGE_usbhub.sys
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Jul  5 22:30:42.005 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 5:09:37.848
Probably caused by : usbhub.sys
BugCheck 9F, {3, fffffa800a1a5440, fffff80000b9c3d8, fffffa800e90cc10}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Bugcheck code 0000009F
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800a1a5440, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800e90cc10, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_athurx_IMAGE_usbhub.sys
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Jul  5 09:05:33.811 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 6:36:41.044
Probably caused by : usbhub.sys
BugCheck 9F, {3, fffffa8009ce0440, fffff80000b9c3d8, fffffa800824ec10}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Bugcheck code 0000009F
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8009ce0440, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800824ec10, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_athurx_IMAGE_usbhub.sys
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Jul  4 22:18:11.830 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 4:56:49.673
Probably caused by : usbhub.sys
BugCheck 9F, {3, fffffa800a73a060, fffff80000b9c3d8, fffffa800daabc10}
BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
Bugcheck code 0000009F
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800a73a060, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800daabc10, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_athurx_IMAGE_usbhub.sys
MaxSpeed:     3300
CurrentSpeed: 3309
BiosVersion = F10
BiosReleaseDate = 10/12/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = Z68X-UD3H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``