📎 AI Summary:
The thread discusses a BSOD related to a "bad pool header" caused by potential memory corruption, possibly linked to outdated drivers, specifically the BIOSTAR I2C I/O driver. The original poster attempts troubleshooting through driver updates, driver verifier, and memtest86, with no recent crashes but ongoing screen issues upon restart. Overall, the community recommends further memory testing and updating or removing suspect drivers to resolve the problem.
K

killit

New Member
Member details
Joined
Jul 18, 2017
Messages
12
Thread Author #1
Hi, I have been having a bad pool header bsod lately. I have been trying the process of elimination to find out why but no luck yet. So here is the crash dump file hoping some with more knowledge than me to help analyze it. Thank you
 

Attachments

Solution
K
kemical said:
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89cf9eb03, b3b7465eef76ba29, fffff8000359b900, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!SeQuerySecurityDescriptorInfo+0 )...
Click to expand...
Sort by date Sort by votes
K

killit

New Member
Member details
Joined
Jul 18, 2017
Messages
12
Thread Author #21
kemical said:
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89cf9eb03, b3b7465eef76ba29, fffff8000359b900, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!SeQuerySecurityDescriptorInfo+0 )

Followup:     MachineOwner


Hi,
please remove these drivers:
BS_I2cIo.sys Mon Dec 11 07:48:39 2006: BIOSTAR I2C I/O driver Found in BIOSTAR BIOS Flash Utility.

I see your running Bullguard:

BdSpy.sys Wed Sep 23 09:06:34 2015: BullGuard File Monitor, part of the Bullguard security suite. We ask users to remove any third party AV suites and just use Windows Defender or Link Removed until the source of the bsod is found. You can always install it again but it just cuts down on the variables.

Did you use the DDU when updating your graphics card?

You mentioned that the machine possibly overheated when using memtest86?

It doesn't usually create a huge amount of heat so are you overclocking? If so please return to default values.

If you try running memtest86 again and the same thing happens try running one the one stick and test them individually.
Click to expand...

Hi I'm having trouble finding that void driver to get rid of it will a clean of everything help
 

Upvote 1 Downvote
Solution
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#23
killit said:
will a clean of everything help
Click to expand...
You mean like a re-install?

Try running scannow first as this might clear up any data corruption. Find cmd prompt, right click, properties and run as admin. Type:
sfc /scannow

Press enter and await results.
 
Upvote 0 Downvote
K

killit

New Member
Member details
Joined
Jul 18, 2017
Messages
12
Thread Author #24
kemical said:
You mean like a re-install?

Try running scannow first as this might clear up any data corruption. Find cmd prompt, right click, properties and run as admin. Type:
sfc /scannow

Press enter and await results.
Click to expand...

Hi for the sfc /scannow I got Resoirce protection did not find any integrity violations. I did test with memtest86 and all passed still cant find that bios file
 
Upvote 0 Downvote
K

killit

New Member
Member details
Joined
Jul 18, 2017
Messages
12
Thread Author #26
Hi happen again but got bad pool caller this time I thought I fix it but looks like not
 

Attachments

Upvote 0 Downvote
kemical

kemical

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

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, 105, fffff8a012aa8260}

GetPointerFromAddress: unable to read from fffff800034ba100
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800034ba2e8
GetUlongPtrFromAddress: unable to read from fffff800034ba498
GetPointerFromAddress: unable to read from fffff800034ba0b8

fffff8a012aa8250 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...

GetUlongFromAddress: unable to read from fffff80003427a58
GetPointerFromAddress: unable to read from fffff800034ba100
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800034ba2e8
GetUlongPtrFromAddress: unable to read from fffff800034ba498

fffff8a012aa8250 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...

GetUlongFromAddress: unable to read from fffff80003427a58
Probably caused by : memory_corruption ( nt!MiSegmentDelete+19e )

Followup:     MachineOwner
Hi,
this means a driver is corrupting the memory pool.

To find which driver is causing the problems you need to run the driver verifier with Pool options enabled. Basically you just need to check the boxes which apply:
Link Removed

I notice you still have Bullguard installed:
BdAgent.sys Tue May 17 10:30:50 2016: Bullguard Security Agent Driver

Please remove this security suite as they often at the cause of the issue and it's worth removing simply to test. If the error continues after removal then you can always re-install the application.
 
Upvote 0 Downvote
K

killit

New Member
Member details
Joined
Jul 18, 2017
Messages
12
Thread Author #28
Hi I'm not getting the BSOD with the verifier this what I'm getting this is the 4 time to day and no it doesn't go away I left it there before dinner and over an hour later it's here just to see what would happenLink Removed
 
Upvote 0 Downvote
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#29
You may have either an issue with your graphics driver or the card itself.

If your overclocking the card, please stop.

Download the DDU or Display Driver Uninstaller

Download the latest driver for your card or a fresh copy.

Boot into safe mode and use the DDU to remove the driver. This will also remove any corruption left behind by previous driver installs.

Once back in Windows install or re-install gpu driver.

So your saying the blue screens have stopped?
 
Upvote 0 Downvote
You must log in or register to reply here.