0

I was testing for Windows SVVP (server virtualization validation program) test and I observe unexpected behavior. When I put 80 Gigs of storage for a 60 cores system, I am able to get the "Complete" memory dump. However, with same configuration, the mini-dump stucks at 0%.

I search many documents including from MSDN, but could able to find a very good reason for this behavior. What is a possible reason for such behavior?

halfer
  • 19,824
  • 17
  • 99
  • 186
user3243499
  • 2,953
  • 6
  • 33
  • 75
  • Is this really a programming question? – Thomas Weller Dec 20 '16 at 19:55
  • 1
    If I had to guess, I'd say that a complete dump simply dumps all mapped memory regions. The minidump tries to find the "interesting" bits, so it's walking stacks and following key pointers. Perhaps there's corruption causing a cycle, so the dumper gets stuck trying to follow pointers forever. – Adrian McCarthy Dec 20 '16 at 22:29
  • @AdrianMcCarthy Could you please share any links where the complete events flow of these dump types - Minidump, kernel dump, and complete dump, are described. When I search on the web I found only the difference between these dump types and nothing about the flow. Thanks in advance. – user3243499 Dec 21 '16 at 05:42
  • @AdrianMcCarthy: AFAIK, interesting memory is only considered max. 2 pointers away, so this should not result in an endless loop. – Thomas Weller Dec 21 '16 at 11:48

0 Answers0