BSOD Caused by ntoskrnl.exe - Occurs when Displaying on VGA Monitor

[SFeldman217]

Hi there,

I am the Administrator at my company and I'm out of ideas on how to fix this problem. Mostly all users who use the TV in the Conference Room to do Presentations are getting Blue Screens. The BSOD says the issue is a BAD_POOL_HEADER, and Blue Screen Viewer shows me the issue is caused by ntoskrnl.exe failing. I have (to my knowledge) the most updated Graphics Drivers and this seems to only affect our HP Computers (6555b or 6560b models).

I've uploaded the SF Diagnostic Tool output file, in the format that was described in this: http://www.sevenforums.com/tutorials/92394-sf-diagnostic-tool-using-troubleshooting.html thread.

I'm not sure what other information, if any, you need. But I can provide more information if you need it.

I look forward to hearing back soon.

 

[YoYo155]

Hello .
I would just like to point out that if you found this post (<link) useful please mark the thread as solved
and thank Arc for his time, one of the greatest supporters on the boards.

A single dump is not enough in most cases a few more would have been nice.
This case is somewhat similar.

BugCheck 19, {22, fffffa800818f000, 0, 0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+74654 )

lmvm igdkmd64
start             end                 module name
fffff880`04a90000 fffff880`04fac380   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        [COLOR=Red]Wed Jan 16 22:30:35 2013[/COLOR]

• Driver Reference Table - igdkmd64.sys

Please update the driver using this online utility and see if the machine still bug checks,
if it does enable Driver Verifier and post back with a three or four new dump files.

• Intel® Driver Update Utility

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.