Solved BSOD -- Bad Pool Header.

[Casuaisxtynine]

Please advise.
Thanks,
Casualsixtynine

 

[Casuaisxtynine]

Bump.. Please help, anyone? It's rather important as I use this system for business. Thanks.

 

[Casuaisxtynine]

Bumps...

 

[Casuaisxtynine]

Bumps. still no solution.

 

[Thedoctor44]

Please don't keep posting on your own thread as I go through threads based on their replies and if you keep bumping it looks like somebody is helping you.

Now, can you please update your Intel 4000 graphics driver as you have a display crash. However your graphics driver is pretty up to date.

https://downloadcenter.intel.com/Se...Core™+Processors+with+Intel®+HD+Graphics+4000

If it still BSODs when you've update this driver can you please run Driver Verifier by following these instructions.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8005234e80, fffffa8005234f20, 40a0008}

[COLOR="red"]Probably caused by : dxgmms1.sys[/COLOR] ( dxgmms1!VidMmCloseAllocation+44 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="Red"]BAD_POOL_HEADER (19)[/COLOR]
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8005234e80, The pool entry we were looking for within the page.
Arg3: fffffa8005234f20, The next pool entry.
Arg4: 00000000040a0008, (reserved)

fffff880`09c32000 fffff880`0a056000   igdkmd64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: [COLOR="Red"]igdkmd64.sys[/COLOR]
    Timestamp:        [COLOR="Blue"]Wed Jan 22 22:42:16 2014[/COLOR] (52E04948)
    CheckSum:         004167F1
    ImageSize:        00424000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Casuaisxtynine]

I'm so sorry.

I will go ahead and do that and update you once it's finished. Thanks so much!

 

[Casuaisxtynine]

Issue fixed by doing OSRI. Thanks Thedoctor44