dflorea

No problem -- so if I cause a crash after hours tonight, will that dump file have the data I'm looking for -- I don't have to wait for the machine to error out and crash on its own? Appreciate the help. David

On one 2003 server, I frequently get a BSOD from a bad_pool_header 0x19 error. Here's the entire bugcheck message: 0x00000019 (0x00000020, 0x85ff0550, 0x85ff06e0, 0x0a320063) Problem is, no minidump file was saved, and my memory.dmp file is just over 1G. I was unable to open it with Wordpad. I downloaded Windbg, but when trying to open the crash dump file all I got was 'corruption' and 'out of context' errors -- apparently I have a learning curve to deal with on Windbg. These BSOD errors usually come after I do the Windows Updates from WSUS, often during the reboot. Yesterday this happened even when no reboot was required. I understand from looking at others' posts who've had this error that it's likely a device driver, but I need to know which one -- there are no substantive errors showing aside from this. I'm sure looking for good ideas... Thanks, David