Yah, definitely no way; can't pull data from that which is nonexistent. In most cases I've seen from people generating nothing but corrupt crashdumps, they either have hardware failure (memory, mobo, psu or drive) or their drive controller drivers/BIOS is whacking out or they have an SSD drive with buggy firmware. Basically anything that has the potential to manipulate memory at the time of producing the crashdump, or cause failing/erroneous drive I/O. If you haven't already, you'll wanna look at my thread
here on an explanation as to how crashdumps are made. The book
Windows Internals also explains on their chapter on Crash Dump Analysis on how it takes place (if I recall correctly). It should help you get an idea what can impede on crashdump creation and steps necessary to ascertain cause.
