They usually wanted me to check if there were any issues or if the dump actually was created, this was in the middle of troubleshooting and they took some initiative to help in identifying why no dumps were created, but I don't think it's meant as a joke or something.
I guess that maybe you guys have not been exposed like I have to the posting of fake BSODs.
I would estimate that I have encountered somewhere between 50-100 threads involving absolutely fake BSODs since 2007 - over the last 12+ years.
Beware of Fake BSOD Posts
Where are dump files (.dmp) saved after crash ?
A lot of them came after I inadvertently posted BSOD help at a notorious site known for hacking and working with cracked Windows. I did not know what kind of a site it was at the time I posted, but I posted that the Windows OS was cracked and everyone seemed to laugh and I did not get the joke. I did a very detailed analysis of the full kernel dump provided and showed them exactly how I came to my conclusions. They were very thankful! :0
This unfortunate exchange led to quite a few fake BSOD threads in the following weeks and months. I was obviously being targeted and the OPs were laughing all the way. But I was able to catch each fake BSOD usually by noticing an old hex date on the picture of the BSOD attached to the post (i.e., OP would say it was W7 or W8, but the hex timestamp was for a 2002 XP-era driver) or by some other method before investing a lot of time trying to solve the thread.
Others were outright cracked Windows.
Some had drivers from 2 or 3 different versions of Windows in one dump, which I easily figured out with the pver/cver FOR command that IDs module/driver versions and this was very easy for me to spot.
So, being a target of pranksters, I always think that something like
0xdeaddead is a joke of some kind first, until other evidence shows me otherwise.
John
