How do I fix the Windows described below to save a minidump in %SystemRoot%\Minidump when a bugcheck occur?, as it should normally do. i need the minidump to know what driver failed and needs to be removed or changed
recoveros
The recoveros settings are correct
wmic recoveros list /format:list && wmic recoveros get debuginfotype,minidumpdirectory /format:list
AutoReboot=TRUE
WriteDebugInfo=TRUE
WriteToSystemLog=TRUE
DebugInfoType=3
MiniDumpDirectory=%SystemRoot%\Minidump
It doesn't matter if auto reboot is disabled
wmic recoveros set autoreboot=false
Bugcheck number
There's no indication that the bugcheck number matters (that a minidump is saved for some bugcheck numbers) because
no minidump has been saved for 307 (2012-12-03 - 2013-10-06) days
the number of bugchecks during this period is around 37 according to
Control Panel\System and Security\Action Center\Reliability Monitor
An example of a bugcheck name that isn't saved is
PROCESS_HAS_LOCKED_PAGES
no bugcheck name (the "BugCheck name" row in the topic "Bugcheck display" isn't written)
Bugcheck display
The bugcheck display the same message as when a minidump event (1001) is saved (don't indicate that it don't save a minidump)
A problem has been detected and Windows has been shutdown to prevent damage to your computer.
BugCheck name (this row is sometimes not displayed)
General information
Technical information:
*** STOP: BugCheck code (arguments)
*** driver where BugCheck was called
Collecting data for crash dump ...
Initializing disk for crash dump ...
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance.
wevtutil
When a bugcheck occur
Windows don't save a minidump event (1001)
wevtutil qe system /q:*[System[EventID=1001]] /rd:true /f:text /c:1
Windows save the other bugcheck events
wevtutil qe system /q:*[System[EventID=41]] /rd:true /f:text /c:1
Date: 2013-01-29T19:15:42.198
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
wevtutil qe system /q:*[System[EventID=6008]] /rd:true /f:text /c:1
Date: 2013-01-29T19:15:47.000
The previous system shutdown at 7:14:47 PM on 1/29/2013 was unexpected.
wevtutil qe system /q:*[System[EventID=1076]] /rd:true /f:text /c:1
Date: 2013-01-29T19:16:49.000
The reason supplied by user PC\User for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Problem ID:
Bugcheck String:
Comment:
werfault
Windows don't display this werfault dialog when starting after a BugCheck
Windows has recovered from an unexpected shutdown
Windows can check online for a solution to the problem.
Reliability Monitor
The Reliability Monitor history display this message when a bugcheck don't save a minidump
Critical events
Windodws was not properly shut down
The previous system shutdown at 2:11:08 AM on 8/21/2013 was unexpected.
instead of this message when a bugcheck save a minidump
Critical events
Windows stopped working
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff96000352e77, 0xfffff8802385fea0, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\100613-14570-01.dmp. Report Id: 100613-14570-01.
minidumpscount
minidumpscount is more than 0 (and, if it matters, higher than the number of minidumps)
reg query hklm\system\currentcontrolset\control\crashcontrol /v minidumpscount
minidumpscount REG_DWORD 0x3e7
dir %systemroot%\minidump | tail -2
35 File(s) 9▒917▒969 bytes
pagefileset
The adequate pagefileset size for saving a minidump isn't known. It could be this size
wmic pagefileset list /format:list
InitialSize=1000
MaximumSize=1000
These sizes have been tried without solving the problem
wmic pagefileset where name="c:\\pagefile.sys" set initialsize=2000,maximumsize=2000
wmic pagefileset where name="c:\\pagefile.sys" set initialsize=3000,maximumsize=3000
wmic pagefileset where name="c:\\pagefile.sys" set initialsize=4000,maximumsize=4000
wmic computersystem where name="%computername%" set automaticmanagedpagefile=true
attrib
The minidump folder isn't read-only (i.o.w. allow a BugCheck to save a minidump)
attrib %SystemRoot%\Minidump
I C:\Windows\Minidump
icacls
The minidump folder security is correct (i.o.w. allow a BugCheck to save a minidump)
icacls %SystemRoot%\Minidump
C:\Windows\Minidump BUILTIN\Administrators:(OI)(CI)(F)
NT AUTHORITY\SYSTEM:(OI)(CI)(F)
Successfully processed 1 files; Failed processing 0 files
rmdir
The minidump folder is deleted because
- that reduce the probability that the folder security is wrong because that normally cause the next BugCheck to create a folder with correct security
rmdir /s /q %SystemRoot%\Minidump
However, a BugCheck don't create a folder with the name %SystemRoot%\Minidump. But creating the minidump folder manually with the mkdir command below don't cause a BugCheck to save a minidump
mkdir %SystemRoot%\Minidump
Last minidump
The last 41 event for which there's a minidump is
wevtutil qe system /q:*[System[EventID=41]] /rd:true /f:text /c:6
Event[5]:
Date: 2012-12-03T06:21:37.590
dir %systemroot%\minidump /o:-d | head -8 | tail -1
2012-12-03 06:21 322▒616 120312-37830-01.dmp
System
my system is
Operating System
Windows 7 Ultimate 64-bit SP1
CPU
Intel Core i7 3770K @ 3.50GHz 49 °C
Ivy Bridge 22nm Technology
RAM
32,0GB Dual-Channel DDR3 @ 668MHz (9-9-9-24)
Motherboard
ASUSTeK COMPUTER INC. P8Z77-M PRO (LGA1155) 36 °C
Graphics
DELL U2312HM (1920x1080@60Hz)
BenQG2222HDL (1920x1080@60Hz)
Intel HD Graphics 4000 (ASUStek Computer Inc)
1024MB ATI AMD Radeon HD 6800 Series (XFX Pine Group) 79 °C
Hard Drives
112GB OCZ-VERTEX2 ATA Device (SSD) 30 °C
Optical Drives
QBCNK MRSHA3S5 SCSI CdRom Device
Audio
Corsair Vengeance 2000 Headset
The available c: disk space is
fsutil volume diskfree c:
Total # of free bytes : 19957088256
Total # of bytes : 119926681600
Total # of avail free bytes : 19957088256