Greetings. I am writting to ask about information about a blue screen error in my system. At the end of this message are the errors details copied from de dmp file opened with WinDbg, I performed an !analyze -v sentence to catch more information. I posted the code of the last one. I think that the problem is related to a video problem, but I am not sure about that and also if it is a hardware or software problem. My computer is a new one (20 days of use), an HP Pavilion dv6, AMD Phenom II Quad Core N930, 2.0 GHz and 2 MB cache. 6 MB RAM DDR3. The video Driver is ATI Radeon with two GPUs: one of less performance HD 4200 for power save, and the other is an HD 5400 for high performance. The change between both GPUs happens when you change from AC power to Battery power, but also you can change the GPUs manually when you want. After buy the computer, I donwloaded a new version of de video drive, so I think that maybe that is the problem. However I returned today to old version of driver (downloaded from de HP webpage for this model of computer) and I am waiting to see what happens now. In all that time I had aprox. 15 errors of this kind. If anybody can helpe with this, please tell me so I can find a solution. Thank you in Advance! 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) 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: fffffa8005271b20, The pool entry we were looking for within the page. Arg3: fffffa8005271f80, The next pool entry. Arg4: 000000000446000a, (reserved) Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_POOL_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_POOL_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_POOL_TRACKER_BIG_PAGES *** *** *** ************************************************************************* Cannot get _POOL_TRACKER_BIG_PAGES type size ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: nt FAULTING_MODULE: fffff80002c58000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 BUGCHECK_STR: 0x19_20 POOL_ADDRESS: fffffa8005271b20 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002dfb6d3 to fffff80002cc8740 STACK_TEXT: fffff880`031d2b88 fffff800`02dfb6d3 : 00000000`00000019 00000000`00000020 fffffa80`05271b20 fffffa80`05271f80 : nt+0x70740 fffff880`031d2b90 00000000`00000019 : 00000000`00000020 fffffa80`05271b20 fffffa80`05271f80 00000000`0446000a : nt+0x1a36d3 fffff880`031d2b98 00000000`00000020 : fffffa80`05271b20 fffffa80`05271f80 00000000`0446000a 00000000`00000000 : 0x19 fffff880`031d2ba0 fffffa80`05271b20 : fffffa80`05271f80 00000000`0446000a 00000000`00000000 00000000`00000000 : 0x20 fffff880`031d2ba8 fffffa80`05271f80 : 00000000`0446000a 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`05271b20 fffff880`031d2bb0 00000000`0446000a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`05271f80 fffff880`031d2bb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02fb1600 : 0x446000a STACK_COMMAND: kb FOLLOWUP_IP: nt+70740 fffff800`02cc8740 48894c2408 mov qword ptr [rsp+8],rcx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt+70740 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------

Bug Check 0x19: BAD_POOL_HEADER The BAD_POOL_HEADER bug check has a value of 0x00000019. This indicates that a pool header is corrupt. http://msdn.microsoft.com/en-us/library/ff557389%28VS.85%29.aspx Hi, please enable Driver verifier to get the causing driver: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html http://support.microsoft.com/?kbid=244617 when you get a new BSOD, boot to safe mode, disable driver verifier, reboot to normal mode and upload the newest dmp file from the folder C:\Windows\Minidump to your public SkyDrive [1] folder and post the link here. André [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/