Solved Bad_Pool_Header BSOD after exiting sleep mode

[forbiddenspell]

I just built a new computer. Everything works fine, except when I wake my computer up from sleep mode, I get a BSOD with BAD_POOL_HEADER. I've attached the zip file as per the sticky.

I'm running Windows 7 Home Premium 64 bitMy research suggests this BSOD is caused by a driver issue. Any help towards resolving this would be greatly appreciated.

Let me know if you need further information about my setup.

Thanks in advance.

 

[VistaKing]

Hi forbiddenspell and welcome to SevenForums

Lets run a MGADiag

Please download MGADiag and save it to your desktop.

:ar: Double click

icon on your desktop.

:ar: Click on the

button

:ar: Click on the

button

:ar: Paste the log inside the box . Highlight all of the text then code wrap by pressing on the # icon on the top .

 

[koolkat77]

Welcome to Seven Forums.

The MGA diag report is not required, at least for now.

Daemon Tools/Alcohol %

[COLOR="DarkOrange"][B]Programs\DAEMON Tools Lite[/B][/COLOR]

Uninstall DAEMON Tools and/or Alcohol % software. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

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

Security App

[FONT="Consolas"]avgidsdrivera.sys           Fri Mar 29 07:40:56 2013 (5154F128)
avgidsdrivera.sys           Wed Feb 27 04:27:18 2013 (512D36C6)
avgidsha.sys                Fri Feb  8 09:14:48 2013 (51146DA8)
avgldx64.sys                Fri Feb  8 09:14:24 2013 (51146D90)
avgloga.sys                 Fri Feb  8 09:14:29 2013 (51146D95)
avgmfx64.sys                Fri Feb  8 09:14:48 2013 (51146DA8)
avgrkx64.sys                Fri Feb  8 09:14:05 2013 (51146D7D)
avgtdia.sys                 Thu Mar 21 07:50:47 2013 (514A6777)
avgtdia.sys                 Thu Feb 14 08:38:15 2013 (511C4E17)[/FONT]

Crashes indicate AVG being a possible cause. Remove AVG 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, both recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free

   Information

DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.

This is for information purposes only. The drivers in red should be updated. If updating does not help, remove them.

GVTDrv64.sys Tue Sep 5 13:10:02 2006 (44FD22CA)
Gigabyte Easy Tune 6 driver (known BSOD issues w/Win7)
http://www.carrona.org/drivers/driver.php?id=GVTDrv64.sys - Recommend complete removal with REVO.

se64a.sys Thu May 3 11:50:31 2007 (46397827)
EnTech softEngine x64 kernel-mode driver.[br]Most likely a component of EnTech's MonInfo - which is a part of the Monitor Asset Manager software.
http://www.carrona.org/drivers/driver.php?id=se64a.sys

gdrv.sys Fri Mar 13 09:22:29 2009 (49B9D175)
Gigabyte Easy Saver - mobo power utility driver
http://www.carrona.org/drivers/driver.php?id=gdrv.sys

AppleCharger.sys Thu Oct 25 06:51:02 2012 (50888CF6)
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))
http://www.carrona.org/drivers/driver.php?id=AppleCharger.sys - Recommend complete removal with REVO.

Revo Uninstaller

Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

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

Follow this:

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

BSOD BUGCHECK SUMMARY

[FONT="Lucida Console"]Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat May 11 10:42:23.873 2013 (UTC + 6:00)
System Uptime: 0 days 0:52:03.716
BugCheck 19, {20, fffffa80136b8c00, fffffa80136b8d20, 4120013}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1fb23 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat May 11 09:49:50.432 2013 (UTC + 6:00)
System Uptime: 0 days 3:48:00.275
BugCheck 19, {20, fffffa8013afc750, fffffa8013afc870, 4120020}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1fb23 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu May  9 10:49:22.217 2013 (UTC + 6:00)
System Uptime: 0 days 1:18:19.060
BugCheck 19, {20, fffffa80139d9e60, fffffa80139d9f80, 4120002}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1fb23 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu May  9 09:30:09.886 2013 (UTC + 6:00)
System Uptime: 0 days 1:24:01.729
BugCheck 19, {20, fffffa801364c3c0, fffffa801364c4e0, 412001e}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1fb23 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu May  9 08:05:02.304 2013 (UTC + 6:00)
System Uptime: 0 days 1:08:01.147
BugCheck 19, {20, fffffa8013ba4c40, fffffa8013ba4d60, 4120021}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1fb23 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[forbiddenspell]

I ended up just trying uninstalling AVG and Daemon tools. Not sure which one did it, but I'm not seeing any more BSOD issues.

I'll wait just a little longer before I mark it as solved.

Thanks for the quick support!

 

[koolkat77]

Good to hear. Give it a week or more before marking as solved

I'll be here for a follow up.

 

[koolkat77]

Hi -

   Tip

• :tip: If your problem is solved please use the
  
  Mark this thread as solved link at the top of your thread or down on the left corner.
  
  
  

 

[forbiddenspell]

Having problems again. Attached a new zip file.

Everything was working great for a while and now I'm back to getting BSODs again.

Only recent change is new video card drivers.

Thanks in advance!

 

[koolkat77]

Roll back to the previous video drivers you were using: Device Manager - Roll Back Driver

Update this driver to its latest or remove the software:

se64a.sys                   Thu May  3 11:50:31 2007

EnTech softEngine x64 kernel-mode driver.[br]Most likely a component of EnTech's MonInfo - which is a part of the Monitor Asset Manager software.
Driver Reference Table - se64a.sys

   Note

Revo Uninstaller
Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

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

Perform a clean install of your Intel(R) 82579V Gigabit Network Connection driver e1c62x64.sys

• Driver Reference Table - e1c62x64.sys
  Image name: e1c62x64.sys
  Timestamp: Fri Mar 16 09:57:28 2012 (4F62BA28)

   Tip

How to clean left over drivers
Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to Clean Left Over Driver Files with Driver Sweeper

• Click on the Start rb:
• Control Panel
• Programs
• Uninstall a program
• Uninstall everything related to the software

Delete remnants of its drivers/older drivers using Driver Sweeper
​

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.
Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7

   Information

If you have an SSD, make sure the following are up to date:

1. SSD firmware
2. BIOS Version
3. Chipset Drivers
4. Hard disk controller drivers/SATA drivers
5. If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Thanks to Writhziden for the steps above.

SFC /scannow to check windows for corruption:

How to Repair Windows 7 System Files with System File Checker
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

sfc /scannow

and hit enter.

Disk Check
For errors on your Hard drive(s): How to Run Disk Check in Windows 7

BSOD BUGCHECK SUMMARY

[FONT="Consolas"]Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jul  5 04:23:59.960 2013 (UTC + 6:00)
System Uptime: 0 days 1:19:01.803
BugCheck 19, {20, fffffa801395a770, fffffa801395a890, 4120013}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1fb23 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jul  5 01:34:50.273 2013 (UTC + 6:00)
System Uptime: 0 days 3:23:36.116
BugCheck 19, {20, fffffa8013709890, fffffa80137099b0, 4120003}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1fb23 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat Jun 29 11:36:57.268 2013 (UTC + 6:00)
System Uptime: 0 days 2:00:17.001
BugCheck C2, {99, fffffa80136bad60, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!CcWorkerThread+29e )
BUGCHECK_STR:  0xc2_99
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jun 28 11:40:13.287 2013 (UTC + 6:00)
System Uptime: 0 days 1:34:06.130
BugCheck 19, {20, fffffa8012641420, fffffa8012641540, 412001c}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1fb23 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jun 28 10:05:39.679 2013 (UTC + 6:00)
System Uptime: 0 days 3:22:18.522
BugCheck 19, {20, fffffa80136f0420, fffffa80136f0540, 4120006}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1fb23 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]