📎 AI Summary:
The thread discusses a user experiencing recurring "Bad Pool Header" Blue Screen errors starting in March 2016, with troubleshooting efforts including memtest and chkdisk showing no issues. A responder analyzes dump files, identifying a problematic driver, IOMap64.sys, associated with ASUS software like GPU Tweak or Smart Doctor, and recommends uninstalling or updating relevant drivers and software such as Malwarebytes. The overall advice suggests updating all drivers, especially network and chipset, and refreshing security software, with the user advised to monitor for further errors and share new dump files if issues persist.
S

Szabolcs Varga

New Member
Member details
Joined
Mar 30, 2016
Messages
1
Thread Author #1
Hi, I need help. Since Sunday I got "Bad Pool Header" bsod randomly every day. Memtest and chckdisk were tried with no error. Using verifier exe, after restart I can get to the desktop and firewall, but when the Bitdefender 2016 Total Security would start BSOD happens again. Now, I trying to rule out the faulty drivers but I can't really understand the dump files.
Thanks for advance
UI Zip file attached
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {226, fffff80097647708, ffffcf8183c36ea0, 0}

Unable to load image \??\C:\Windows\system32\drivers\IOMap64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IOMap64.sys
*** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
Probably...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#2
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {226, fffff80097647708, ffffcf8183c36ea0, 0}

Unable to load image \??\C:\Windows\system32\drivers\IOMap64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IOMap64.sys
*** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys
Probably caused by : IOMap64.sys ( IOMap64+1708 )

Followup: MachineOwner
Hi,
the majority of dump files look like the one above and mean the verifier has caught a I/O driver misbehaving. The other dump files were as you know bugcheck 19 bad pool header. Interestingly Malwarebytes was involved in those dump files too.

IOMap64.sys Tue Jul 02 09:27:47 2013: ASUS Kernel Mode Driver ?Asus Smart Doctor/iTracker 2 Asus GPU Tweak? This driver could belong to either one of those apps listed. It's probably GPU Tweak and if you have it installed please uninstall it.

AsUpIO.sys Tue Aug 03 03:47:59 2010: ( related to the above?) ASUS hardware monitoring software please update. A later version is on support website:
Z97-P - Support

Please update all drivers, especially network and chipset although ideally update them all.
Z97-P - Support

As Malwarebytes seemed caught up in at least one set of dump files (it was mentioned in every bugcheck 19 dump file) the it's probably worth uninstalling and then downloading a new fresh copy and installing that.

See how you go with the above changes. Please post any new dump files.
 

Upvote 1 Downvote
Solution
You must log in or register to reply here.