hi,I am getting frequently BSOD here are details == Dump File : 060410-23359-01.dmp Crash Time : 6/4/2010 3:28:24 AM Bug Check String : BAD_POOL_HEADER Bug Check Code : 0x00000019 Parameter 1 : 00000000`00000003 Parameter 2 : fffff800`03014c40 Parameter 3 : 00000000`00000000 Parameter 4 : fffff800`03014c40 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+70600 File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 6.1.7600.16539 (win7_gdr.100226-1909) Processor : x64 Computer Name : Full Path : C:\Windows\Minidump\060410-23359-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 7600 ================================================== The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000003, 0xfffff80003014c40, 0x0000000000000000, 0xfffff80003014c40). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060410-23359-01 please advise thanks

If you're getting a BAD_POOL_HEADER bugcheck, you're experiencing a crash due to memory corruption. This could be due to faulty hardware such as RAM, or due to a buggy or incompatible driver. In this case, check the items below for running chkdsk, sfc, and driver verifier. Driver Verifier is the proper thing to turn to for memory corruption issues such as this, and chkdsk and sfc can turn up disk or file corruption. General guidance for dealing with memory corruption: Consider running chkdsk on all partitions. Let chkdsk complete on each partition and see if that helps. For memory corruption cases such as you seem to be experiencing, it can be helpful to use Driver Verifier. To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out of the dialog. Then, reboot and use the system as you normally would, and wait for a problem. In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes. Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive, and provide a link. Also consider running SFC /SCANNOW. If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot? Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test. Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules. Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're using the latest BIOS.

Check your hardware to make sure eveything is seated properly. The report smacks of a loose RAM stick. Vote if answered or helpful, I am running for Office (joke)! IT/Developer, Windows/Linux/Mainframe Need a some parts finish the new server, see the site for remaining items needed

the verifier slow down the windows alot, I had to delete every the settings is it possible that it may be a hard drive problem or a psu ?

A better PSU pays for itself in power savings. Right click on the disk in "Computer" vew and choose "properties". Now find the tools tab. At the top is check now, click on it. Make sure the option to fix errors is enabled and if you want, check and recover HD errors. Reboot and wait a few hours if you choose recover HD errors. Vote if answered or helpful, I am running for Office (joke)! IT/Developer, Windows/Linux/Mainframe Need a some parts finish the new server, see the site for remaining items needed

I have coolermaster 850w this should be one of the best psu but may be there is a problem from the factory, I checked too all my hdd drives !! how I know for sure if my psu is not faulty ? so I can RMA thanks

the 850 should be fine for most users. What is you system specs Vote if answered or helpful, I am running for Office (joke)! IT/Developer, Windows/Linux/Mainframe Need a some parts finish the new server, see the site for remaining items needed

my PC is i7 860 , biostar i55 , adata 4 gb ram , gtx 280 My hdd are 1 tera western digital black , I installed win 7 64 bit with AHCI enabled and that should make every thing fast but when I do multi tasking like download + copy + browsing I find my win 7 stop responding for 5~8 seconds !!! even when I move the highlight in the windows explorer from folder to folder it take 1 sec to see the highlight!! how with config like this I can not run 3 tasks at the same time I am really getting around myself here dont know what to do

I got a digital multimeter and I measured my psu and the volts are fine , but I found my hard drive has a problem, it sometimes did not detected from bios now but sometimes it is detected , so is this the cause of BSOD or also my RAM has a problem ?

If you disk is not being recognized, check the power connector and the SATA cable to be sure thay are all good. Vote if answered or helpful, I am running for Office (joke)! IT/Developer, Windows/Linux/Mainframe Need a some parts finish the new server, see the site for remaining items needed

not all my disks only one (the 500gb), the others detected normally , I also used the digital multimeter to make sure of the volts as I said above I installed now win 7 64bit on 1 tera wd black , this should be fast drive but sometimes the system hangup for few seconds !!! please advise

The bugcheck occurred because "The pool freelist is corrupt. (In a healthy list, the values of Parameters 2, 3, and 4 should be identical.)" So an incorrect or unexpected value was found to be in memory. Did you only enable standard settings for third-party drivers? If the perf impact is still too much, then enable it for 1/2 or 1/3 of the non-Microsoft drivers and note which one. If you get a bugcheck, upload the dump. If the dump shows verifier picked something up, then strategy can be adjusted from there. If not, then turn verifier off for the first set and enable it for the second set, etc. Can you upload the contents of c:\windows\minidump to your SkyDrive and provide a link?

I installed new windows on new hard drive, but here are the old dump files http://www.mediafire.com/?ozqzzmzeyy3 I used mediafire because it is faster thanks

All of the old dumps showed pool corruption (kernel memory corruption). If you reinstalled Windows, it is possible the drivers or versions of the drivers installed are different than when you had the installation that was bugchecking and produced the provided dumps. FWIW, the dumps did show the following stale drivers had been installed: BS_I2cIo.sys 6/16/2008 MTiCtwl.sys 11/4/2008 cpuz132_x64.sys 3/7/2009 hotcore3.sys 3/20/2009 While it is more likely for an older driver to cause the type of corruption you were experiencing, it could also have been caused by some newer third-party driver.

BS_I2cIo.sys----is for my motherboard utility MTiCtwl.sys-----is for cd/dvd writer but dont know which one so I dont use it in the fit cpuz132_x64.sys-----is for cpuz for information about my cpu, will not use again hotcore3.sys----is for Paragon partition utility, this software known to be the best !! how it can do BSOD !!!

Regardless of what the drivers are for, they are from before the RTM of Windows 7 and as such would be suspect in a situation like you are/were encountering. They could have compatibility or other issues and as such should be updated or removed from the scenario for testing.

Also consider running SFC /SCANNOW. If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot? Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test. Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules. Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're using the latest BIOS. Hi, The cause of BSOD varies. To narrow down the root cause and point us to the right direction, remove all unnecessary hardware devices from the computer, try entering Windows safe mode to test whether it is a third-party software/hardware compatibility issue. Follow the above troubleshooting and tell us the result in safe mode and device clean boot. This will tell us if the issue is caused by driver software or hardware. Meanwhile, when did this issue first occur? Can you associate this with any software or hardware changes? Generally, it is suggested to obtain the latest drivers including driver for chipset and bios. Regards,Magon Liu - MSFT