List of kernel memory dump hotfixes for Windows Vista/Server2008 and Windows 7/Server2008R2
Applies to:
Windows Server 2008 R2 Service Pack 1
Windows Server 2008 R2 SP1
W2K8 R2 Service Pack 1
W2K8 R2 SP1
Windows 7 Service Pack 1
Windows 7 SP1
Win7 Service Pack 1
Win7 SP1
Windows Server 2008 Service Pack 2
Windows Server 2008 SP2
W2K8 Service Pack 2
W2K8 SP2
Windows Vista Service Pack 2
Windows Vista SP2
Note: You should check https://support.microsoft.com for the latest version of the different files.
Note 2: These are not available in Windows Update.
Note 3: You can download them without entering your e-mail address and captcha if you are a Microsoft Premier customer and have a https://Premier.Microsoft.com account.
Note 4: Carefully review the list and decide which might be applicable to your unique environment.
Note 5: Test in your test and your quality assurance environment.
List of kernel memory dump hotfixes for Windows Vista/Server2008 and Windows 7/Server2008R2 as of Nov. 2013.
For those that need to generate a manual memory dump using the steps listed on this article that I compiled many years ago:
969028 How to generate a kernel or a complete memory dump file in Windows Server 2008 and Windows Server 2008 R2
https://support.microsoft.com/?id=969028
You might not be able to generate a bug check (a.k.a. blue screen). It could be because you are running into one of the hotfixes mentioned below.
List of kernel memory dump hotfixes for Windows 7 SP1 and/or Windows Server 2008 R2 SP1:
2826910 Secondary dump data is limited to 256 MB in Windows 7 and Windows Server 2008 R2
https://support.microsoft.com/?id=2826910
Update(s):
Crashdmp.sys 6.1.7601.18110
Crashdmp.sys 6.1.7601.22277
2716542 A hotfix is available that enables a Windows 7-based or Windows Server 2008 R2-based computer to create a memory dump file without a page file
https://support.microsoft.com/?id=2716542
Update(s):
Crashdmp.sys 6.1.7601.17857 (Superseded by 2826910)
Crashdmp.sys 6.1.7601.22012 (Superseded by 2826910)
Ntoskrnl.exe 6.1.7601.17857
Ntoskrnl.exe 6.1.7601.220122587660 Memory dump file is generated very slowly on a Hyper-V virtual machine that uses Dynamic Memory when the Maximum RAM setting is over 4 GB in Windows Server 2008 R2
https://support.microsoft.com/?id=2587660
Update(s):
Vmwp.exe 6.1.7601.17761
Vmwp.exe 6.1.7601.21897
Vid.dll 6.1.7601.17761
Vid.sys 6.1.7601.17761
Vid.dll 6.1.7601.21897
Vid.sys 6.1.7601.218972541014 Hibernation does not work or memory dump file is not created after you install Windows 7 or Windows Server 2008 R2 Service Pack 1
https://support.microsoft.com/?id=2541014
Update(s):
Diskdump.sys 6.1.7601.17601
Diskdump.sys 6.1.7601.21710Supersede(s):
2495523 Sleep and hibernation do not work or a crash memory dump file is not created after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2
https://support.microsoft.com/?id=2495523
Update(s):
Diskdump.sys 6.1.7601.17601
Diskdump.sys 6.1.7601.217102528507 Incorrect memory dump files in an x64-based version of Windows 7 SP1 or of Windows Server 2008 R2 SP1
https://support.microsoft.com/?id=2528507
Update(s):
Ntoskrnl.exe 6.1.7601.17591
Ntoskrnl.exe 6.1.7601.21700
Ntkrnlpa.exe 6.1.7601.17591
Ntoskrnl.exe 6.1.7601.17591
Ntkrnlpa.exe 6.1.7601.21700Ntoskrnl.exe 6.1.7601.21700
List of kernel memory dump hotfixes for Windows Vista SP2 and/or Windows Server 2008 SP2:
2570946 Memory dump file is not generated in Windows Vista or in Windows Server 2008 if the system drive is not larger than 4 times the amount of RAM
https://support.microsoft.com/?id=2570946
Update(s):
Smss.exe 6.0.6002.22674971877 The Windows Server 2008 system stops responding (hangs) when an application or a driver triggers an NMI to generate a memory dump file forcibly
https://support.microsoft.com/?id=971877
Update(s):
Pshed.dll 6.0.6002.22242
Comments
- Anonymous
April 05, 2015
It's been years since I wrote the following two articles to force a blue screen (for you *nix admin