Re: Unexpected System Crash : limitation of Filesize (because of memory) ?

Edward Kim wrote:
> Before test, I turned automatic rebooting off to watch out that BLUE SCREEN..
> Of course, I disabled all the other programs & minor services (including Virus-Checking).
> At the 1st test, my system crashed with full physical memory dump (2GB).
>
> Blue screen only gave me;
> BAD_POOL_HEADER
> BCCode:19, BCP1:0x00000020, BCP2:0x89acc120, BCP3:0x89acc238, BCP4:0x0a230001
> with some usual descriptions.. (ask your admin...blah blah blah...)
>
> There are 5 critical system error event logs and 2GB physical memory dump data.
> All of them are related with this crash issue. (category number is 102.)
> However, I cannot find which driver cause this from these data..

You need to install windbg and use it to analyze the memory dump:

        http://www.microsoft.com/whdc/devtools/debugging/default.mspx
        http://www.networkworld.com/news/2005/041105-windows-crash.html

Just set up the symbol server as shown in the networkworld.com article,
open your crashdump and run a "!analyze -v". That should tell you which
driver triggered the crash, but not neccessarily which caused it - as
BAD_POOL_HEADER errors usually occur when there's already some memory
corruption...

-- 
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
.......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1106537
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].