Obviously, we expect there to be mini kernel memory dump files in the SysnativeFileCollectionApp.zip file attached by OPs.
Before assuming that there is something wrong with the OPs system rendering it incapable of producing dump files, it is worthwhile to check out some of the other files contained in the zip file first.
The WERCON portion of msinfo32.nfo ("Software Environment"; "Windows Error Reporting") is completely empty, which is rare, but not uncommon as Windows does provide an option to delete all WERCON entries via Action Center/ Problem Reporting & Solutions.
The oddity is compounded by the fact that the WERALL.txt file is not empty; however its contents reveal that the OP has some bad/broken Junctions; namely - - Documents and Settings - Appdata - Local Settings
Seeing WER files with those path names (specifically the 1st & 3rd) first led me to wrongly conclude momentarily that OP had an XP system. A quick check of systeminfo.txt shows build number 6.0.6002 = Vista SP2
You can see the Junction problems, especially given the many repetitive \Application Data paths listed:
1st line of file:
1680 1/16/2015 12:06:11 AM "C:\Documents and Settings\All Users\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Windows\WER\ReportArchive\Report024feca2\Report.wer"
The last time I tested, it was possible for the broken Junction to repeat itself up to 16 times. I guess it would depend on the length & the 255/6 character DOS shell limit. The Junction problem is also causing file listings to replicate for each WER file, i.e., you'll find the same filename, but with different numbers of replicated paths.
There is definitely something wrong with OPs system here because WERProgramData + WERLocalAppData files show at least 96 *.WER files, so I would expect to see msinfo32's WER section populated.
Anyway, back to our "no dump" issue --
Another file in the SysnativeFileCollectionApp.zip file that should be checked is the KernelDumpList.txt file, which I added to the app to create a DIR output listing of -
%windir%\minidump\*.dmp + also DIR for the full kernel dump, located - %windir%\memory.dmp
OPs KernelDumpList.txt file shows 15 minidumps, but no full kernel dump -
Read More:
Code:
Sat 05/23/2015 12:32:02.57
LISTING OF MINI KERNEL DUMP FILES
LISTING OF MINI KERNEL DUMP FILES
Volume in drive C is Partition_1
Volume Serial Number is 400F-9880
Directory of C:\Windows\minidump
05/20/2015 07:17 AM <DIR> JOHN-PC1\John .
05/20/2015 07:17 AM <DIR> JOHN-PC1\John ..
05/17/2015 09:20 AM 310,826 MINI05~1.DMP BUILTIN\Administrators Mini051715-01.dmp
05/18/2015 10:58 PM 293,405 MINI05~2.DMP BUILTIN\Administrators Mini051815-01.dmp
05/18/2015 11:00 PM 343,351 MINI05~3.DMP BUILTIN\Administrators Mini051815-02.dmp
05/18/2015 11:03 PM 293,405 MINI05~4.DMP BUILTIN\Administrators Mini051815-03.dmp
05/18/2015 11:05 PM 293,405 MI070B~1.DMP BUILTIN\Administrators Mini051815-04.dmp
05/19/2015 10:57 PM 342,823 MI0B7D~1.DMP BUILTIN\Administrators Mini051915-01.dmp
05/19/2015 11:06 PM 343,346 MI0F7D~1.DMP BUILTIN\Administrators Mini051915-02.dmp
05/19/2015 11:09 PM 293,405 MI038D~1.DMP BUILTIN\Administrators Mini051915-03.dmp
05/19/2015 11:13 PM 333,506 MI078D~1.DMP BUILTIN\Administrators Mini051915-04.dmp
05/19/2015 11:16 PM 342,583 MI0B8D~1.DMP BUILTIN\Administrators Mini051915-05.dmp
05/19/2015 11:19 PM 333,506 MI7BF6~1.DMP BUILTIN\Administrators Mini052015-01.dmp
05/20/2015 07:00 AM 342,219 MI7FF6~1.DMP BUILTIN\Administrators Mini052015-02.dmp
05/20/2015 07:05 AM 342,759 MI730F~1.DMP BUILTIN\Administrators Mini052015-03.dmp
05/20/2015 07:08 AM 342,768 MI770F~1.DMP BUILTIN\Administrators Mini052015-04.dmp
05/20/2015 07:11 AM 350,194 MI7B0F~1.DMP BUILTIN\Administrators Mini052015-05.dmp
15 File(s) 4,901,501 bytes
2 Dir(s) 238,163,210,240 bytes free
_______________________________________________________
Sat 05/23/2015 12:32:02.62
FULL KERNEL DUMP FILE
FULL KERNEL DUMP FILE
Volume in drive C is Partition_1
Volume Serial Number is 400F-9880
Directory of C:\Windows
_______________________________________________________
E O J
E O J
Sat 05/23/2015 12:32:02.64
I honestly have no idea why the mini dump files did not get copied, but the log entry does show a failing ERRLEVEL "1" for the "DONE" copy step -
In this case, my recommendation would be for OP to manually copy the \windows\minidump directory to \documents, then zip it up. You cannot zip up the \windows\minidump dir itself due to perm errors. Zipping in place will work if logged on to the SID -500 Hidden Admin user account.
Another place to check to see if an OP experienced BSODs are the Event Viewer logs. The SysnativeFileCollectionApp.zip file contains the System + Application Event Logs, courtesy of the wevtutil command. One search term is "Bugcheck" to help find the log entries.
This OPs system has quite a few strange things going on as outlined above. I guess things can be fixed, but given the inability of the Sysnative app to copy dumps; the empty WERCON in msinfo32; empty EVTX logs; Junction issues; etc... + the fact it is an old Vista installation (~7 years old):
OS Name: Microsoft® Windows Vista Home Premium
OS Version: 6.0.6002 Service Pack 2 Build 6002
If this were my system, I would seriously consider reinstalling Vista. That is the same recommendation that Carrona made to the OP.
One other strange item that I noticed -- the Sysnative app uses WMI to gather RAM info (RAMInfo.html file). It shows 5 sticks of RAM - (or 4 sticks + a 5th line...?) -
