0xc000021aエラーコード(16進数8桁)：関連のページ

このページでは、0xc000021aエラーコード(16進数8桁)：に関連するサポートページの一覧を紹介します。

http://support.microsoft.com/en-us/kb/2829996/en-us
MS13-036: Vulnerabilities in kernel-mode driver could allow elevation of privilege: April 9, 2013対象製品：Windows RT, Windows 8, Windows 8 Enterprise, Windows 8 Pro, Windows Server 2012 Datacenter, Windows Server 2012 Essentials, Windows Server 2012 Foundation, Windows Server 2012 Standard, Windows 7 Service Pack 1, when used with:, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows 7 Home Premium, Windows 7 Home Basic, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows 7 Home Premium, Windows 7 Home Basic, Windows Server 2008 R2 Service Pack 1, when used with:, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 Service Pack 2, when used with:, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 Standard, Windows Web Server 2008, Windows Vista Service Pack 2, when used with:, Windows Vista Business, Windows Vista Enterprise, Windows Vista Home Basic, Windows Vista Home Premium, Windows Vista Starter, Windows Vista Ultimate, Windows Vista Enterprise 64-bit Edition, Windows Vista Home Basic 64-bit Edition, Windows Vista Home Premium 64-bit Edition, Windows Vista Ultimate 64-bit Edition, Windows Vista Business 64-bit Edition, Microsoft Windows Server 2003 Service Pack 2, when used with:, Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Datacenter x64 Edition, Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, Standard x64 Edition, Microsoft Windows XP Professional x64 Edition, Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems, Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows XP Service Pack 3, when used with:, Microsoft Windows XP Home Edition, Microsoft Windows XP Professional

http://support.microsoft.com/en-us/kb/2839011/en-us
You receive an Event ID 55 or a 0xC000021A

Stop error in Windows 7 after you install security update 2823324対象製品：Windows 7 Service Pack 1, when used with:, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows 7 Home Premium, Windows 7 Home Basic, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows 7 Home Premium, Windows 7 Home Basic, Windows Server 2008 R2 Service Pack 1, when used with:, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 Service Pack 2, when used with:, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 Standard, Windows Web Server 2008

http://support.microsoft.com/ja-jp/kb/2829996/ja
[MS13-036] カーネルモードドライバーの脆弱性により、特権が昇格される (2013 年 4 月 9 日)対象製品：Windows RT, Windows 8, Windows 8 Enterprise, Windows 8 Pro, Windows Server 2012 Datacenter, Windows Server 2012 Essentials, Windows Server 2012 Foundation, Windows Server 2012 Standard, Windows 7 Service Pack 1を以下の環境でお使いの場合, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows 7 Home Premium, Windows 7 Home Basic, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows 7 Home Premium, Windows 7 Home Basic, Windows Server 2008 R2 Service Pack 1を以下の環境でお使いの場合, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 Service Pack 2を以下の環境でお使いの場合, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 Standard, Windows Web Server 2008, Windows Vista Service Pack 2を以下の環境でお使いの場合, Windows Vista Business, Windows Vista Enterprise, Windows Vista Home Basic, Windows Vista Home Premium, Windows Vista Starter, Windows Vista Ultimate, Windows Vista Enterprise 64-bit edition, Windows Vista Home Basic 64-bit edition, Windows Vista Home Premium 64-bit edition, Windows Vista Ultimate 64-bit edition, Windows Vista Business 64-bit edition, Microsoft Windows Server 2003 Service Pack 2を以下の環境でお使いの場合, Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Datacenter x64 Edition, Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, Standard x64 Edition, Microsoft Windows XP Professional x64 Edition, Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems, Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows XP Service Pack 3を以下の環境でお使いの場合, Microsoft Windows XP Home Edition, Microsoft Windows XP Professional

http://support.microsoft.com/ja-jp/kb/2839011/ja
セキュリティ更新プログラム 2823324 のインストール後に Windows 7 でイベント ID 55 または 0xC000021A

Stop エラーが表示される対象製品：Windows 7 Service Pack 1を以下の環境でお使いの場合, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows 7 Home Premium, Windows 7 Home Basic, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows 7 Home Premium, Windows 7 Home Basic, Windows Server 2008 R2 Service Pack 1を以下の環境でお使いの場合, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 Service Pack 2を以下の環境でお使いの場合, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 Standard, Windows Web Server 2008

http://support.microsoft.com/ja-jp/kb/922410/ja
Windows XP Professional を実行しているコンピューターを再起動すると、エラーメッセージ:"stop 0xC000021A

http://blogs.technet.com/b/jpsecurity/archive/2013/04/12/3566398.aspx
Blogs - 日本のセキュリティチーム - Site Home - TechNet Blogs

http://blogs.technet.com/b/ben_parker/archive/2009/06/05/debugging-a-fatal-system-error-0xc000021a-status-system-process-terminated-with-verification-of-a-known-dll-failed-x64-0xc000021a-c000012f.aspx
Debugging a fatal system error 0xC000021A

(STATUS_SYSTEM_PROCESS_TERMINATED) with Verification of a known DLL failed X64_0xc000021a_c000012f - Ben Parker's Blog - Site Home - TechNet Blogs

http://answers.microsoft.com/en-us/insider/wiki/insider_wintp-insider_install/how-to-troubleshoot-common-setup-and-stop-errors/324d5a5f-d658-456c-bb82-b1201f735683
How to: Troubleshoot common Setup and Stop Errors during Windows - Microsoft Community対象製品：Windows Insider Program, Windows Insider Preview, Install, upgrade, and activate

http://blogs.technet.com/b/platformtr/archive/2013/04/12/kb2839011-yay-nland.aspx
KB2839011 yaynland! - Team: Windows Platform Turkiye - Site Home - TechNet Blogs

http://answers.microsoft.com/en-us/feed/u/7e9a1df1-850e-4b00-add2-f7f6817bec54/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
Microsoft Community - Threads activity by BackupJoe

http://answers.microsoft.com/en-us/feed/u/c7adeaad-9e98-4df4-8e9e-dce8d0a1d75b/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
Microsoft Community - Threads activity by Erik788

http://answers.microsoft.com/en-us/feed/u/a16dad82-cdc2-4a1f-ae37-ccb052e8034c/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
Microsoft Community - Threads activity by HeikoHHB

http://answers.microsoft.com/en-us/feed/u/9cdc7e5b-25f9-4c3b-8e60-bbaed21fe0ae/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
Microsoft Community - Threads activity by Panzer Castle´s

http://answers.microsoft.com/en-us/feed/u/54b89688-7b09-468b-8589-dc3419e0e413/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
Microsoft Community - Threads activity by RDrewD2

http://www.itmedia.co.jp/enterprise/articles/1304/13/news009.html
MicrosoftXVvOsAACXg[ - ITmedia G^[vCY

http://www.itmedia.co.jp/news/articles/1304/13/news009.html
MicrosoftXVvOsAACXg[ - ITmedia j[X

http://blogs.technet.com/b/securekorea/archive/2013/04/25/ms13-036.aspx
MS13-036 - Secure Korea - Site Home - TechNet Blogs

http://blogs.technet.microsoft.com/jpsecurity/2013/04/12/ms13-036-2823324/index.html
MS13-036 2823324 適用後の問題について – 日本のセキュリティチーム

http://blogs.technet.com/b/latam/archive/2013/04/12/problemas-de-inicializa-231-227-o-no-windows-7-ap-243-s-instalar-a-atualiza-231-227-o-de-seguran-231-a-2823324.aspx
Problemas de inicializacao no Windows 7 apos instalar atualizacao de seguranca 2823324 - LATAM Team blog - Site Home - TechNet Blogs

http://blogs.technet.microsoft.com/latam/2013/04/12/problemas-de-inicializao-no-windows-7-aps-instalar-atualizao-de-segurana-2823324/index.html
Problemas de inicialização no Windows 7 após instalar atualização de segurança 2823324 – LATAM Team blog

http://blogs.technet.microsoft.com/systemcenterjp/2016/10/07/stop-unexpectedupdates/index.html
System Center Configuration Manager で管理者が予期しない更新プログラムが配信されてしまったときの対応方法 – Japan System Center Support Team Blog

http://blogs.technet.com/b/?pi142383=5376
TechNet Blogs

http://blogs.technet.com/b/yongrhee/?pi50463=8
The troubleshooters and problem solvers... - Site Home - TechNet Blogs

http://blogs.technet.com/b/yongrhee/archive/2010/01/06/troubleshooting-stop-0xc000021a-winlogon-exe.aspx
Troubleshooting Stop 0xC000021A

Winlogon.exe - The troubleshooters and problem solvers... - Site Home - TechNet Blogs

http://answers.microsoft.com/ja-jp/feed/u/7e9a1df1-850e-4b00-add2-f7f6817bec54/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
マイクロソフトコミュニティ - スレッド活動者 BackupJoe

http://answers.microsoft.com/ja-jp/feed/u/c7adeaad-9e98-4df4-8e9e-dce8d0a1d75b/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
マイクロソフトコミュニティ - スレッド活動者 Erik788

http://answers.microsoft.com/ja-jp/feed/u/a16dad82-cdc2-4a1f-ae37-ccb052e8034c/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
マイクロソフトコミュニティ - スレッド活動者 HeikoHHB

http://answers.microsoft.com/ja-jp/feed/u/9cdc7e5b-25f9-4c3b-8e60-bbaed21fe0ae/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
マイクロソフトコミュニティ - スレッド活動者 Panzer Castle´s

http://answers.microsoft.com/ja-jp/feed/u/54b89688-7b09-468b-8589-dc3419e0e413/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
マイクロソフトコミュニティ - スレッド活動者 RDrewD2

http://support.microsoft.com/ja-jp/kb/156758/ja
BUG SQL のプロシージャキャッシュを監視するときにパフォーマンスモニターを終了します。

http://support.microsoft.com/en-us/kb/156758/en-us
BUG: Perfmon Terminates While Monitoring SQL Procedure Cache対象製品：Microsoft SQL Server 1.1 Standard Edition

http://support.microsoft.com/en-us/kb/184744/en-us
DHCP Server Leaks Registry Quota on Alpha Version of Windows NT対象製品：Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/112455/en-us
Err Msg: STOP Message 0xC000021A

Starting Windows Application対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1

http://support.microsoft.com/en-us/kb/295087/en-us
Error message cites "Stop error code 0xC000021A

(STATUS_SYSTEM_PROCESS_TERMINATED)" event

http://support.microsoft.com/en-us/kb/304742/en-us
Event ID: 6008 After Remote Shutdown with an Active Screensaver対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT 4.0 Service Pack 6a, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT 4.0 Service Pack 6a

http://support.microsoft.com/en-us/kb/155766/en-us
FIX: Perfmon Terminates While Monitoring SQL Procedure Cache対象製品：Microsoft SQL Server 6.5 Standard Edition

http://support.microsoft.com/en-us/kb/192463/en-us
Gathering Blue Screen Information After Memory Dump in Windows 2000 or Windows NT対象製品：Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Datacenter Server, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/en-us/kb/235496/en-us
How to Enable a Memory.dmp File Capture Using the Graphical User Interface or the Registry対象製品：Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/en-us/kb/318666/en-us
Internet Explorer Maintenance Policies May Cause an Access Violation in Winlogon対象製品：Microsoft Windows XP Professional

http://support.microsoft.com/ja-jp/kb/298193/ja
List of bugs fixed in Windows 2000 Service Pack 2 (4 of 4)対象製品：Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP2, Microsoft Windows 2000 Professional SP2

http://support.microsoft.com/ja-jp/kb/128531/ja
Microsoft Windows NT 3.51 Service Pack 5 README.TXT の内容対象製品：Microsoft Windows NT Workstation 3.51 SP5, Microsoft Windows NT 3.51 Service Pack 5

http://support.microsoft.com/en-us/kb/893376/en-us
Stack corruption occurs if you remove and insert a smart card during a user log on process in Windows XP Service Pack 1 or Windows XP Service Pack 2

http://support.microsoft.com/en-us/kb/219319/en-us
STOP 0xc000021 in Winlogon.exe When Printing and Running Screen Saver対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/en-us/kb/319425/en-us
Stop 0xC000021A

Error Message on a Blue Screen on Your Windows NT 4.0 Server-Based Computer対象製品：Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/145578/en-us
STOP Msg: 0xC000021A

After Changing Drive Letter Assignment対象製品：Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/145578/ja
STOP メッセージ: 0xC000021A

ドライブ文字の割り当てを変更しました後対象製品：Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

http://support.microsoft.com/en-us/kb/113976/en-us
Using Emergency Repair Disk With Fault Tolerant Partitions対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/ja-jp/kb/137396/ja
Windows NT 3. 51 のアップグレード中にファイルをコピーできませんでした。対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/319425/ja
Windows NT 4. 0 Server ベースコンピューターでブルースクリーンに STOP 0xC000021A

エラーメッセージ対象製品：Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/244925/en-us
Windows NT 4.0 Csrss.exe Stops Responding with a Stop 0xC000021A

Error Message対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT 4.0 Service Pack 4, Microsoft Windows NT 4.0 Service Pack 5, Microsoft Windows NT 4.0 Service Pack 6, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT 4.0 Service Pack 4, Microsoft Windows NT 4.0 Service Pack 5, Microsoft Windows NT 4.0 Service Pack 6, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/ja-jp/kb/225037/ja
Windows NT 4.0 Service Pack 5 で修正されたバグの一覧

http://support.microsoft.com/ja-jp/kb/219319/ja
Windows NT 4.0 で印刷中にスクリーンセーバーが起動すると Winlogon.exe が停止する対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/ja-jp/kb/244925/ja
Windows NT 4.0 の Csrss.exe が STOP 0xC000021A

エラーメッセージで応答を停止する対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT 4.0 Service Pack 4, Microsoft Windows NT 4.0 Service Pack 5, Microsoft Windows NT 4.0 Service Pack 6, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT 4.0 Service Pack 4, Microsoft Windows NT 4.0 Service Pack 5, Microsoft Windows NT 4.0 Service Pack 6, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/ja-jp/kb/891534/ja
Windows NT Server 4.0 Service Pack 6a (SP6a) を実行しているコンピュータに Windows NT Server 4.0 Terminal Server Edition 用のセキュリティ更新プログラム MS04-037 をインストールした後、STOP エラーメッセージ "C000021A" が表示される対象製品：Microsoft Windows NT 4.0 Service Pack 6a

http://support.microsoft.com/en-us/kb/891534/en-us
You receive a "C000021A" Stop error message after you install the MS04-037 security update for Windows NT Server 4.0, Terminal Server Edition on a computer that is running Windows NT Server 4.0 with Service Pack 6a (SP6a)

http://support.microsoft.com/en-us/kb/158376/en-us
"Stop 0xC000021A

" During Setup対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/ja-jp/kb/155766/ja
[FIX] SQL Server 6.5 SQL Procedure Cache モニタリング時の Perfmon の終了対象製品：Microsoft SQL Server 6.5 Standard Edition

http://support.microsoft.com/ja-jp/kb/158376/ja
[NT] セットアップ中の "Stop 0xC000021A

"対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/ja-jp/kb/184744/ja
[NT]Alpha 版の DHCP サーバーはレジストリクォータを消費する対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Terminal Server

http://support.microsoft.com/ja-jp/kb/235496/ja
グラフィカルユーザーインターフェイスまたはレジストリを使用して、Memory.dmp ファイルキャプチャを有効にする方法

http://support.microsoft.com/ja-jp/kb/304742/ja
スクリーンセーバーの実行中にリモートからシャットダウンするとイベント ID 6008 が発生する対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT 4.0 Service Pack 6a, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT 4.0 Service Pack 6a

http://support.microsoft.com/ja-jp/kb/109076/ja
スタートアップようにすることがある NTFS パーティションにアクセス許可を削除します。対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1

http://support.microsoft.com/ja-jp/kb/893376/ja
スタック破損が Windows XP Service Pack 1 または Windows XP Service Pack 2 でプロセスのユーザーログオン中に、スマートカードを削除し、そして挿入する場合、発生します。対象製品：Microsoft Windows XP Service Pack 2を以下の環境でお使いの場合, Microsoft Windows XP Professional, Microsoft Windows XP Service Pack 1を以下の環境でお使いの場合, Microsoft Windows XP Professional 64-Bit Edition (Itanium), Microsoft Windows XP Professional

http://support.microsoft.com/ja-jp/kb/113976/ja
フォールトトレラントパーティションでシステム修復ディスクを使う対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/ja-jp/kb/112455/ja
メッセージ 0xC000021A

開始 Windows アプリケーションの停止エラーメッセージ。対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1

http://support.microsoft.com/ja-jp/kb/192463/ja
メモリダンプ後にブルースクリーン情報を収集する対象製品：Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/ja-jp/kb/116405/ja
無効な PATH のためのログオン時に STOP メッセージ: 0xC000021A

対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1

http://support.microsoft.com/en-us/kb/192298/en-us
Third Party GINAs May Fail with Service Pack 4 Causing STOP 0x21A in WINLOGON対象製品：Microsoft Windows 2000 Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows 2000 Advanced Server

http://support.microsoft.com/en-us/kb/244925/en-us
Windows NT 4.0 Csrss.exe Stops Responding with a Stop 0xC000021A

http://support.microsoft.com/ja-jp/kb/244925/ja
Windows NT 4.0 の Csrss.exe が STOP 0xC000021A

http://support.microsoft.com/en-us/kb/2564071/en-us
Stop 0xC000021A

in Windows Session manager while starting windows対象製品：Windows 7 Enterprise, Windows 7 Enterprise E, Windows 7 Enterprise N, Windows 7 Home Basic, Windows 7 Home Premium, Windows 7 Home Premium E, Windows 7 Home Premium N, Windows 7 Professional, Windows 7 Professional E, Windows 7 Professional N, Windows 7 Service Pack 1, Windows 7 Starter, Windows 7 Starter E, Windows 7 Starter N, Windows 7 Ultimate, Windows 7 Ultimate E, Windows 7 Ultimate N

http://blogs.technet.com/b/joscon/archive/2011/05/10/supported-workaround-for-torn-state-installations-on-windows-7-sp1.aspx?pi47623=4
Supported workaround for torn state installations on Windows 7 SP1 - The Windows Servicing Guy - Site Home - TechNet Blogs

http://blogs.technet.com/b/yongrhee/archive/2010/01/06/troubleshooting-stop-0xc000021a-winlogon-exe.aspx
Troubleshooting Stop 0xC000021A

Winlogon.exe - The troubleshooters and problem solvers... - Site Home - TechNet Blogs

http://support.microsoft.com/en-us/kb/216477/en-us
Environment Path Too Long Can Cause Access Violation in Winlogon

http://support.microsoft.com/en-us/kb/225037/en-us
List of bugs fixed in Windows NT 4.0 Service Pack 5対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/en-us/kb/128531/en-us
README.TXT: Windows NT Version 3.51 U.S. Service Pack対象製品：Microsoft Windows NT Workstation 3.51 SP5, Microsoft Windows NT 3.51 Service Pack 5

http://support.microsoft.com/ja-jp/kb/161782/ja
SMS リモートエージェントのインストールされている SMS: STOP 0xC000021A

エラー対象製品：Microsoft Systems Management Server 1.2 Standard Edition

http://support.microsoft.com/en-us/kb/161782/en-us
SMS: Stop 0xC000021A

Error with SMS Remote Agent Installed対象製品：Microsoft Systems Management Server 1.2 Standard Edition

http://support.microsoft.com/en-us/kb/155026/en-us
Stop 0xC000021A

in Windows Subsystem with Status c00000005対象製品：Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

http://support.microsoft.com/en-us/kb/238495/en-us
STOP 0xC000021A

in Winlogon.exe on a Terminal Server

http://support.microsoft.com/en-us/kb/200848/en-us
Stop 0xC000021A

on Windows NT Server 4.0 with Service Pack 4対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition

http://support.microsoft.com/en-us/kb/166160/en-us
Stop C000021a after Applying Windows NT 4.0 Service Pack対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/150140/en-us
STOP Msg: 0xC000021A

as Application Terminates対象製品：Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/150140/ja
STOP メッセージ: アプリケーションとして 0xC000021A

の終了対象製品：Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/238495/ja
Windows NT 4.0 で Winlogon.exe を実行すると STOP 0xC000021A

のエラーが発生する対象製品：Microsoft Windows NT Server 4.0 Terminal Server, Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4

http://support.microsoft.com/ja-jp/kb/216477/ja
Windows NT 4.0 で環境変数パスが長すぎると Winlogon でアクセス違反が発生する対象製品：Microsoft Windows NT Server 4.0 Terminal Server

http://support.microsoft.com/en-us/kb/889088/en-us
Your computer does not start and you receive a "Stop 0xC000021A

" error message in Windows Server 2003対象製品：Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

http://support.microsoft.com/en-us/kb/308575/en-us
"Access Denied" Error Message When You Copy or Rename Files in the Recovery Console

http://support.microsoft.com/ja-jp/kb/166160/ja
[NT] サービスパックの適用後 Stop C000021a が発生対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/ja-jp/kb/200848/ja
[NT]SP4 を適用した NT 4.0 で Stop 0xC000021A

エラー対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft BackOffice Small Business Server 4.0a

http://support.microsoft.com/ja-jp/kb/413592/ja
[NT]Windows NT 4.0 Service Pack 5修正一覧対象製品：Microsoft Windows NT Server 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/ja-jp/kb/308575/ja
コピーまたは回復コンソールでのファイルの名前を変更するとエラーメッセージ「アクセスが拒否されました」

http://support.microsoft.com/ja-jp/kb/889088/ja
コンピューターが起動しないし Windows Server 2003 で、0xC000021A

の停止] エラーメッセージ表示されたら対象製品：Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

http://support.microsoft.com/ja-jp/kb/155026/ja
状態 c00000005 を持つ Windows サブシステムで 0xC000021A

を停止します。対象製品：Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/2848819/ja
サービスが失敗した場合の回復操作として [コンピューターを再起動する] を設定すると STOP エラーが発生します対象製品：Windows Server 2012 Datacenter, Windows Server 2012 Standard, Windows 8

http://support.microsoft.com/en-us/kb/950928/en-us
Error message when you restart a computer that is running Windows Server 2003 or an x64-based version of Windows XP Professional: "Stop 0xC000021A

"対象製品：Microsoft Windows Server 2003 Service Pack 1, when used with:, Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems, Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows Server 2003 Service Pack 2, when used with:, Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems, Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows Server 2003, Datacenter x64 Edition, Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, Standard x64 Edition, Microsoft Windows Server 2003, Datacenter x64 Edition, Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, Standard x64 Edition, Microsoft Windows XP Professional x64 Edition, Microsoft Windows XP Service Pack 2, when used with:, Microsoft Windows XP Professional x64 Edition

http://support.microsoft.com/en-us/kb/922410/en-us
Error message when you restart a computer that is running Windows XP Professional: "Stop 0xC000021A

"対象製品：Microsoft Windows XP Professional

http://support.microsoft.com/ja-jp/kb/950928/ja
Windows Server 2003 または x64 ベースバージョンの Windows XP Professional を実行しているコンピューターを再起動すると、エラーメッセージ:"Stop 0xC000021A

"対象製品：Microsoft Windows Server 2003 Service Pack 1を以下の環境でお使いの場合, Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems, Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows Server 2003 Service Pack 2を以下の環境でお使いの場合, Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems, Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows Server 2003, Datacenter x64 Edition, Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, Standard x64 Edition, Microsoft Windows Server 2003, Datacenter x64 Edition, Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, Standard x64 Edition, Microsoft Windows XP Professional x64 Edition, Microsoft Windows XP Service Pack 2を以下の環境でお使いの場合, Microsoft Windows XP Professional x64 Edition

http://blogs.technet.com/b/ben_parker/default.aspx
Ben Parker's Blog - Site Home - TechNet Blogs

http://blogs.technet.microsoft.com/plitpro/tag/bezpieczenstwo/feed/index.html
Bezpieczestwo – Polski TechNet Blog

http://blogs.technet.com/b/richard_macdonald/archive/2007/03/26/706879.aspx
Blogs - Richard's Weblog - Site Home - TechNet Blogs

http://blogs.technet.com/b/robert_hensing/archive/2005/01/17/354471.aspx?pi47623=1
Blogs - Robert Hensing's Blog - Site Home - TechNet Blogs

http://msdn.microsoft.com/en-us/library/windows/hardware/ff538869.aspx
Blue Screen Data (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557196(v=vs.85).aspx
Bug Check 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557196.aspx
Bug Check 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557201(v=vs.85).aspx
Bug Check 0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557201.aspx
Bug Check 0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557203(v=vs.85).aspx
Bug Check 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557203.aspx
Bug Check 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557206(v=vs.85).aspx
Bug Check 0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557206.aspx
Bug Check 0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557208(v=vs.85).aspx
Bug Check 0x100: LOADER_BLOCK_MISMATCH - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557208.aspx
Bug Check 0x100: LOADER_BLOCK_MISMATCH (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557211(v=vs.85).aspx
Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557211.aspx
Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791853(v=vs.85).aspx
Bug Check 0x102: DPC_WATCHDOG_TIMEOUT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557215(v=vs.85).aspx
Bug Check 0x103: MUP_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557215.aspx
Bug Check 0x103: MUP_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557218(v=vs.85).aspx
Bug Check 0x104: AGP_INVALID_ACCESS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557218.aspx
Bug Check 0x104: AGP_INVALID_ACCESS (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557220(v=vs.85).aspx
Bug Check 0x105: AGP_GART_CORRUPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557220.aspx
Bug Check 0x105: AGP_GART_CORRUPTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557223(v=vs.85).aspx
Bug Check 0x106: AGP_ILLEGALLY_REPROGRAMMED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557223.aspx
Bug Check 0x106: AGP_ILLEGALLY_REPROGRAMMED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557225(v=vs.85).aspx
Bug Check 0x108: THIRD_PARTY_FILE_SYSTEM_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557225.aspx
Bug Check 0x108: THIRD_PARTY_FILE_SYSTEM_FAILURE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557228(v=vs.85).aspx
Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557228.aspx
Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557230(v=vs.85).aspx
Bug Check 0x10A: APP_TAGGING_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557230.aspx
Bug Check 0x10A: APP_TAGGING_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557232(v=vs.85).aspx
Bug Check 0x10C: FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557232.aspx
Bug Check 0x10C: FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557235(v=vs.85).aspx
Bug Check 0x10D: WDF_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557235.aspx
Bug Check 0x10D: WDF_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557238(v=vs.85).aspx
Bug Check 0x10E: VIDEO_MEMORY_MANAGEMENT_INTERNAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557238.aspx
Bug Check 0x10E: VIDEO_MEMORY_MANAGEMENT_INTERNAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557241(v=vs.85).aspx
Bug Check 0x10F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557241.aspx
Bug Check 0x10F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557243(v=vs.85).aspx
Bug Check 0x10: SPIN_LOCK_NOT_OWNED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557243.aspx
Bug Check 0x10: SPIN_LOCK_NOT_OWNED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557246(v=vs.85).aspx
Bug Check 0x111: RECURSIVE_NMI - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557246.aspx
Bug Check 0x111: RECURSIVE_NMI (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557248(v=vs.85).aspx
Bug Check 0x112: MSRPC_STATE_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557248.aspx
Bug Check 0x112: MSRPC_STATE_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557253(v=vs.85).aspx
Bug Check 0x113: VIDEO_DXGKRNL_FATAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557253.aspx
Bug Check 0x113: VIDEO_DXGKRNL_FATAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557257(v=vs.85).aspx
Bug Check 0x114: VIDEO_SHADOW_DRIVER_FATAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557257.aspx
Bug Check 0x114: VIDEO_SHADOW_DRIVER_FATAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557259(v=vs.85).aspx
Bug Check 0x115: AGP_INTERNAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557259.aspx
Bug Check 0x115: AGP_INTERNAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557263(v=vs.85).aspx
Bug Check 0x116: VIDEO_TDR_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263.aspx
Bug Check 0x116: VIDEO_TDR_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557271(v=vs.85).aspx
Bug Check 0x117: VIDEO_TDR_TIMEOUT_DETECTED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557271.aspx
Bug Check 0x117: VIDEO_TDR_TIMEOUT_DETECTED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557275(v=vs.85).aspx
Bug Check 0x119: VIDEO_SCHEDULER_INTERNAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557275.aspx
Bug Check 0x119: VIDEO_SCHEDULER_INTERNAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557279(v=vs.85).aspx
Bug Check 0x11A: EM_INITIALIZATION_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557279.aspx
Bug Check 0x11A: EM_INITIALIZATION_FAILURE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557284(v=vs.85).aspx
Bug Check 0x11B: DRIVER_RETURNED_HOLDING_CANCEL_LOCK - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557284.aspx
Bug Check 0x11B: DRIVER_RETURNED_HOLDING_CANCEL_LOCK (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557292(v=vs.85).aspx
Bug Check 0x11C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557292.aspx
Bug Check 0x11C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557296(v=vs.85).aspx
Bug Check 0x11D: EVENT_TRACING_FATAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557296.aspx
Bug Check 0x11D: EVENT_TRACING_FATAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791891(v=vs.85).aspx
Bug Check 0x11E: TOO_MANY_RECURSIVE_FAULTS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791892(v=vs.85).aspx
Bug Check 0x11F: INVALID_DRIVER_HANDLE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557303(v=vs.85).aspx
Bug Check 0x11: THREAD_NOT_MUTEX_OWNER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557303.aspx
Bug Check 0x11: THREAD_NOT_MUTEX_OWNER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791893(v=vs.85).aspx
Bug Check 0x120: BITLOCKER_FATAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557307(v=vs.85).aspx
Bug Check 0x121: DRIVER_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557307.aspx
Bug Check 0x121: DRIVER_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557313(v=vs.85).aspx
Bug Check 0x122: WHEA_INTERNAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557313.aspx
Bug Check 0x122: WHEA_INTERNAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791894(v=vs.85).aspx
Bug Check 0x123: CRYPTO_SELF_TEST_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557321(v=vs.85).aspx
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557321.aspx
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557326(v=vs.85).aspx
Bug Check 0x127: PAGE_NOT_ZERO - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557326.aspx
Bug Check 0x127: PAGE_NOT_ZERO (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791854(v=vs.85).aspx
Bug Check 0x128: WORKER_THREAD_RETURNED_WITH_BAD_IO_PRIORITY - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791855(v=vs.85).aspx
Bug Check 0x129: WORKER_THREAD_RETURNED_WITH_BAD_PAGING_IO_PRIORITY - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791856(v=vs.85).aspx
Bug Check 0x12A: MUI_NO_VALID_SYSTEM_LANGUAGE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557329(v=vs.85).aspx
Bug Check 0x12B: FAULTY_HARDWARE_CORRUPTED_PAGE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557329.aspx
Bug Check 0x12B: FAULTY_HARDWARE_CORRUPTED_PAGE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557339(v=vs.85).aspx
Bug Check 0x12C: EXFAT_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557339.aspx
Bug Check 0x12C: EXFAT_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791857(v=vs.85).aspx
Bug Check 0x12D: VOLSNAP_OVERLAPPED_TABLE_ACCESS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557348(v=vs.85).aspx
Bug Check 0x12: TRAP_CAUSE_UNKNOWN - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557348.aspx
Bug Check 0x12: TRAP_CAUSE_UNKNOWN (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/jj154556(v=vs.85).aspx
Bug Check 0x133 DPC_WATCHDOG_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/jj154556.aspx
Bug Check 0x133 DPC_WATCHDOG_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791858(v=vs.85).aspx
Bug Check 0x136: VHD_BOOT_HOST_VOLUME_NOT_ENOUGH_SPACE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/jj191737.aspx
Bug Check 0x138 GPIO_CONTROLLER_DRIVER_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/jj191737(v=vs.85).aspx
Bug Check 0x138: GPIO_CONTROLLER_DRIVER_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/jj569891.aspx
Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/jj569891(v=vs.85).aspx
Bug Check 0x139: KERNEL_SECURITY_CHECK_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791859(v=vs.85).aspx
Bug Check 0x13B: PASSIVE_INTERRUPT_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791860(v=vs.85).aspx
Bug Check 0x13C: INVALID_IO_BOOST_STATE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557361(v=vs.85).aspx
Bug Check 0x13: EMPTY_THREAD_REAPER_LIST - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557361.aspx
Bug Check 0x13: EMPTY_THREAD_REAPER_LIST (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/hh450914(v=vs.85).aspx
Bug Check 0x144: BUGCODE_USB3_DRIVER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/hh450914.aspx
Bug Check 0x144: BUGCODE_USB3_DRIVER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791861(v=vs.85).aspx
Bug Check 0x145: SECURE_BOOT_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791862(v=vs.85).aspx
Bug Check 0x147: ABNORMAL_RESET_DETECTED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/hh995020.aspx
Bug Check 0x14B SOC_SUBSYSTEM_FAILURE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/hh995020(v=vs.85).aspx
Bug Check 0x14B: SOC_SUBSYSTEM_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791863(v=vs.85).aspx
Bug Check 0x14C: FATAL_ABNORMAL_RESET_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557367(v=vs.85).aspx
Bug Check 0x14: CREATE_DELETE_LOCK_NOT_LOCKED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557367.aspx
Bug Check 0x14: CREATE_DELETE_LOCK_NOT_LOCKED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791864(v=vs.85).aspx
Bug Check 0x151: UNSUPPORTED_INSTRUCTION_MODE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791865(v=vs.85).aspx
Bug Check 0x152: INVALID_PUSH_LOCK_FLAGS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791866(v=vs.85).aspx
Bug Check 0x154: UNEXPECTED_STORE_EXCEPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791867(v=vs.85).aspx
Bug Check 0x156: WINSOCK_DETECTED_HUNG_CLOSESOCKET_LIVEDUMP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791868(v=vs.85).aspx
Bug Check 0x157: KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791869(v=vs.85).aspx
Bug Check 0x158: ILLEGAL_IOMMU_PAGE_FAULT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791870(v=vs.85).aspx
Bug Check 0x15A: SDBUS_INTERNAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/dn376329.aspx
Bug Check 0x15D SOC_SUBSYSTEM_FAILURE_LIVEDUMP (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/dn376329(v=vs.85).aspx
Bug Check 0x15D: SOC_SUBSYSTEM_FAILURE_LIVEDUMP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/dn308254(v=vs.85).aspx
Bug Check 0x15E: BUGCODE_NDIS_DRIVER_LIVE_DUMP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557375(v=vs.85).aspx
Bug Check 0x15: LAST_CHANCE_CALLED_FROM_KMODE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557375.aspx
Bug Check 0x15: LAST_CHANCE_CALLED_FROM_KMODE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791871(v=vs.85).aspx
Bug Check 0x160: WIN32K_ATOMIC_CHECK_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791872(v=vs.85).aspx
Bug Check 0x162: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791873(v=vs.85).aspx
Bug Check 0x163: WORKER_THREAD_TEST_CONDITION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791874(v=vs.85).aspx
Bug Check 0x16D: INVALID_SLOT_ALLOCATOR_FLAGS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791875(v=vs.85).aspx
Bug Check 0x16E: ERESOURCE_INVALID_RELEASE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557378(v=vs.85).aspx
Bug Check 0x16: CID_HANDLE_CREATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557378.aspx
Bug Check 0x16: CID_HANDLE_CREATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557381(v=vs.85).aspx
Bug Check 0x17: CID_HANDLE_DELETION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557381.aspx
Bug Check 0x17: CID_HANDLE_DELETION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791876(v=vs.85).aspx
Bug Check 0x18B: SECURE_KERNEL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557386(v=vs.85).aspx
Bug Check 0x18: REFERENCE_BY_POINTER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557386.aspx
Bug Check 0x18: REFERENCE_BY_POINTER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791877(v=vs.85).aspx
Bug Check 0x190: WIN32K_CRITICAL_FAILURE_LIVEDUMP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791878(v=vs.85).aspx
Bug Check 0x192: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791879(v=vs.85).aspx
Bug Check 0x195: SMB_SERVER_LIVEDUMP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791880(v=vs.85).aspx
Bug Check 0x196: LOADER_ROLLBACK_DETECTED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791881(v=vs.85).aspx
Bug Check 0x199: KERNEL_STORAGE_SLOT_IN_USE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791882(v=vs.85).aspx
Bug Check 0x19A: WORKER_THREAD_RETURNED_WHILE_ATTACHED_TO_SILO - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791883(v=vs.85).aspx
Bug Check 0x19B: TTM_FATAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791884(v=vs.85).aspx
Bug Check 0x19C: WIN32K_POWER_WATCHDOG_TIMEOUT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791885(v=vs.85).aspx
Bug Check 0x19D: CLUSTER_SVHDX_LIVEDUMP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557389.aspx
Bug Check 0x19: BAD_POOL_HEADER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557391(v=vs.85).aspx
Bug Check 0x1A: MEMORY_MANAGEMENT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557391.aspx
Bug Check 0x1A: MEMORY_MANAGEMENT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557399(v=vs.85).aspx
Bug Check 0x1B: PFN_SHARE_COUNT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557399.aspx
Bug Check 0x1B: PFN_SHARE_COUNT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791886(v=vs.85).aspx
Bug Check 0x1C4: DRIVER_VERIFIER_DETECTED_VIOLATION_LIVEDUMP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/mt791887(v=vs.85).aspx
Bug Check 0x1C5: IO_THREADPOOL_DEADLOCK_LIVEDUMP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff557401(v=vs.85).aspx
Bug Check 0x1C: PFN_REFERENCE_COUNT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557401.aspx
Bug Check 0x1C: PFN_REFERENCE_COUNT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557404(v=vs.85).aspx
Bug Check 0x1D: NO_SPIN_LOCK_AVAILABLE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557404.aspx
Bug Check 0x1D: NO_SPIN_LOCK_AVAILABLE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557408(v=vs.85).aspx
Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557408.aspx
Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557414(v=vs.85).aspx
Bug Check 0x1F: SHARED_RESOURCE_CONV_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557414.aspx
Bug Check 0x1F: SHARED_RESOURCE_CONV_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557419(v=vs.85).aspx
Bug Check 0x1: APC_INDEX_MISMATCH - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557419.aspx
Bug Check 0x1: APC_INDEX_MISMATCH (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557421(v=vs.85).aspx
Bug Check 0x20: KERNEL_APC_PENDING_DURING_EXIT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557421.aspx
Bug Check 0x20: KERNEL_APC_PENDING_DURING_EXIT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557424(v=vs.85).aspx
Bug Check 0x21: QUOTA_UNDERFLOW - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557424.aspx
Bug Check 0x21: QUOTA_UNDERFLOW (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557425(v=vs.85).aspx
Bug Check 0x22: FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557425.aspx
Bug Check 0x22: FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557429(v=vs.85).aspx
Bug Check 0x23: FAT_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557429.aspx
Bug Check 0x23: FAT_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557433(v=vs.85).aspx
Bug Check 0x24: NTFS_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557433.aspx
Bug Check 0x24: NTFS_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557436(v=vs.85).aspx
Bug Check 0x25: NPFS_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557436.aspx
Bug Check 0x25: NPFS_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557441(v=vs.85).aspx
Bug Check 0x26: CDFS_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557441.aspx
Bug Check 0x26: CDFS_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557446(v=vs.85).aspx
Bug Check 0x27: RDR_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557446.aspx
Bug Check 0x27: RDR_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557448(v=vs.85).aspx
Bug Check 0x28: CORRUPT_ACCESS_TOKEN - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557448.aspx
Bug Check 0x28: CORRUPT_ACCESS_TOKEN (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557452(v=vs.85).aspx
Bug Check 0x29: SECURITY_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557452.aspx
Bug Check 0x29: SECURITY_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557457(v=vs.85).aspx
Bug Check 0x2A: INCONSISTENT_IRP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557457.aspx
Bug Check 0x2A: INCONSISTENT_IRP (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557460(v=vs.85).aspx
Bug Check 0x2B: PANIC_STACK_SWITCH - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557460.aspx
Bug Check 0x2B: PANIC_STACK_SWITCH (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557461(v=vs.85).aspx
Bug Check 0x2C: PORT_DRIVER_INTERNAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557461.aspx
Bug Check 0x2C: PORT_DRIVER_INTERNAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557463(v=vs.85).aspx
Bug Check 0x2D: SCSI_DISK_DRIVER_INTERNAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557463.aspx
Bug Check 0x2D: SCSI_DISK_DRIVER_INTERNAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557468(v=vs.85).aspx
Bug Check 0x2E: DATA_BUS_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557468.aspx
Bug Check 0x2E: DATA_BUS_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557471(v=vs.85).aspx
Bug Check 0x2F: INSTRUCTION_BUS_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557471.aspx
Bug Check 0x2F: INSTRUCTION_BUS_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557475(v=vs.85).aspx
Bug Check 0x2: DEVICE_QUEUE_NOT_BUSY - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557475.aspx
Bug Check 0x2: DEVICE_QUEUE_NOT_BUSY (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557478(v=vs.85).aspx
Bug Check 0x30: SET_OF_INVALID_CONTEXT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557478.aspx
Bug Check 0x30: SET_OF_INVALID_CONTEXT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557479(v=vs.85).aspx
Bug Check 0x31: PHASE0_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557479.aspx
Bug Check 0x31: PHASE0_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557483(v=vs.85).aspx
Bug Check 0x32: PHASE1_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557483.aspx
Bug Check 0x32: PHASE1_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557488(v=vs.85).aspx
Bug Check 0x33: UNEXPECTED_INITIALIZATION_CALL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557488.aspx
Bug Check 0x33: UNEXPECTED_INITIALIZATION_CALL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557491(v=vs.85).aspx
Bug Check 0x34: CACHE_MANAGER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557491.aspx
Bug Check 0x34: CACHE_MANAGER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557494(v=vs.85).aspx
Bug Check 0x35: NO_MORE_IRP_STACK_LOCATIONS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557494.aspx
Bug Check 0x35: NO_MORE_IRP_STACK_LOCATIONS (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557496(v=vs.85).aspx
Bug Check 0x36: DEVICE_REFERENCE_COUNT_NOT_ZERO - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557496.aspx
Bug Check 0x36: DEVICE_REFERENCE_COUNT_NOT_ZERO (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff557498(v=vs.85).aspx
Bug Check 0x37: FLOPPY_INTERNAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557498.aspx
Bug Check 0x37: FLOPPY_INTERNAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558936(v=vs.85).aspx
Bug Check 0x38: SERIAL_DRIVER_INTERNAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558936.aspx
Bug Check 0x38: SERIAL_DRIVER_INTERNAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558941(v=vs.85).aspx
Bug Check 0x39: SYSTEM_EXIT_OWNED_MUTEX - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558941.aspx
Bug Check 0x39: SYSTEM_EXIT_OWNED_MUTEX (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558945(v=vs.85).aspx
Bug Check 0x3A: SYSTEM_UNWIND_PREVIOUS_USER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558945.aspx
Bug Check 0x3A: SYSTEM_UNWIND_PREVIOUS_USER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558949(v=vs.85).aspx
Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949.aspx
Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558955(v=vs.85).aspx
Bug Check 0x3C: INTERRUPT_UNWIND_ATTEMPTED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558955.aspx
Bug Check 0x3C: INTERRUPT_UNWIND_ATTEMPTED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558963(v=vs.85).aspx
Bug Check 0x3D: INTERRUPT_EXCEPTION_NOT_HANDLED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558963.aspx
Bug Check 0x3D: INTERRUPT_EXCEPTION_NOT_HANDLED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558965(v=vs.85).aspx
Bug Check 0x3E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558965.aspx
Bug Check 0x3E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558968(v=vs.85).aspx
Bug Check 0x3F: NO_MORE_SYSTEM_PTES - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558968.aspx
Bug Check 0x3F: NO_MORE_SYSTEM_PTES (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558969(v=vs.85).aspx
Bug Check 0x3: INVALID_AFFINITY_SET - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558969.aspx
Bug Check 0x3: INVALID_AFFINITY_SET (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791889(v=vs.85).aspx
Bug Check 0x4000008A: THREAD_TERMINATE_HELD_MUTEX - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff558972(v=vs.85).aspx
Bug Check 0x40: TARGET_MDL_TOO_SMALL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558972.aspx
Bug Check 0x40: TARGET_MDL_TOO_SMALL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558974(v=vs.85).aspx
Bug Check 0x41: MUST_SUCCEED_POOL_EMPTY - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558974.aspx
Bug Check 0x41: MUST_SUCCEED_POOL_EMPTY (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558976(v=vs.85).aspx
Bug Check 0x42: ATDISK_DRIVER_INTERNAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558976.aspx
Bug Check 0x42: ATDISK_DRIVER_INTERNAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558978(v=vs.85).aspx
Bug Check 0x43: NO_SUCH_PARTITION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558978.aspx
Bug Check 0x43: NO_SUCH_PARTITION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558982(v=vs.85).aspx
Bug Check 0x44: MULTIPLE_IRP_COMPLETE_REQUESTS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558982.aspx
Bug Check 0x44: MULTIPLE_IRP_COMPLETE_REQUESTS (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558984(v=vs.85).aspx
Bug Check 0x45: INSUFFICIENT_SYSTEM_MAP_REGS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558984.aspx
Bug Check 0x45: INSUFFICIENT_SYSTEM_MAP_REGS (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558987(v=vs.85).aspx
Bug Check 0x46: DEREF_UNKNOWN_LOGON_SESSION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558987.aspx
Bug Check 0x46: DEREF_UNKNOWN_LOGON_SESSION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558991(v=vs.85).aspx
Bug Check 0x47: REF_UNKNOWN_LOGON_SESSION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558991.aspx
Bug Check 0x47: REF_UNKNOWN_LOGON_SESSION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558993(v=vs.85).aspx
Bug Check 0x48: CANCEL_STATE_IN_COMPLETED_IRP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558993.aspx
Bug Check 0x48: CANCEL_STATE_IN_COMPLETED_IRP (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff558996(v=vs.85).aspx
Bug Check 0x49: PAGE_FAULT_WITH_INTERRUPTS_OFF - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558996.aspx
Bug Check 0x49: PAGE_FAULT_WITH_INTERRUPTS_OFF (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559001(v=vs.85).aspx
Bug Check 0x4A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559001.aspx
Bug Check 0x4A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559007(v=vs.85).aspx
Bug Check 0x4B: STREAMS_INTERNAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559007.aspx
Bug Check 0x4B: STREAMS_INTERNAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559010(v=vs.85).aspx
Bug Check 0x4C: FATAL_UNHANDLED_HARD_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559010.aspx
Bug Check 0x4C: FATAL_UNHANDLED_HARD_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559012(v=vs.85).aspx
Bug Check 0x4D: NO_PAGES_AVAILABLE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559012.aspx
Bug Check 0x4D: NO_PAGES_AVAILABLE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559014(v=vs.85).aspx
Bug Check 0x4E: PFN_LIST_CORRUPT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559014.aspx
Bug Check 0x4E: PFN_LIST_CORRUPT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559017(v=vs.85).aspx
Bug Check 0x4F: NDIS_INTERNAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559017.aspx
Bug Check 0x4F: NDIS_INTERNAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559022(v=vs.85).aspx
Bug Check 0x4: INVALID_DATA_ACCESS_TRAP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559022.aspx
Bug Check 0x4: INVALID_DATA_ACCESS_TRAP (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559023(v=vs.85).aspx
Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023.aspx
Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559026(v=vs.85).aspx
Bug Check 0x51: REGISTRY_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559026.aspx
Bug Check 0x51: REGISTRY_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559031(v=vs.85).aspx
Bug Check 0x52: MAILSLOT_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559031.aspx
Bug Check 0x52: MAILSLOT_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559035(v=vs.85).aspx
Bug Check 0x53: NO_BOOT_DEVICE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559035.aspx
Bug Check 0x53: NO_BOOT_DEVICE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559040(v=vs.85).aspx
Bug Check 0x54: LM_SERVER_INTERNAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559040.aspx
Bug Check 0x54: LM_SERVER_INTERNAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559044(v=vs.85).aspx
Bug Check 0x55: DATA_COHERENCY_EXCEPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559044.aspx
Bug Check 0x55: DATA_COHERENCY_EXCEPTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559049(v=vs.85).aspx
Bug Check 0x56: INSTRUCTION_COHERENCY_EXCEPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559049.aspx
Bug Check 0x56: INSTRUCTION_COHERENCY_EXCEPTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559054(v=vs.85).aspx
Bug Check 0x57: XNS_INTERNAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559054.aspx
Bug Check 0x57: XNS_INTERNAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559058(v=vs.85).aspx
Bug Check 0x58: FTDISK_INTERNAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559058.aspx
Bug Check 0x58: FTDISK_INTERNAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559061(v=vs.85).aspx
Bug Check 0x59: PINBALL_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559061.aspx
Bug Check 0x59: PINBALL_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559064(v=vs.85).aspx
Bug Check 0x5A: CRITICAL_SERVICE_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559064.aspx
Bug Check 0x5A: CRITICAL_SERVICE_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559066(v=vs.85).aspx
Bug Check 0x5B: SET_ENV_VAR_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559066.aspx
Bug Check 0x5B: SET_ENV_VAR_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559069(v=vs.85).aspx
Bug Check 0x5C: HAL_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559069.aspx
Bug Check 0x5C: HAL_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559072(v=vs.85).aspx
Bug Check 0x5D: UNSUPPORTED_PROCESSOR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559072.aspx
Bug Check 0x5D: UNSUPPORTED_PROCESSOR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559078(v=vs.85).aspx
Bug Check 0x5E: OBJECT_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559078.aspx
Bug Check 0x5E: OBJECT_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559085(v=vs.85).aspx
Bug Check 0x5F: SECURITY_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559085.aspx
Bug Check 0x5F: SECURITY_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559087(v=vs.85).aspx
Bug Check 0x5: INVALID_PROCESS_ATTACH_ATTEMPT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559087.aspx
Bug Check 0x5: INVALID_PROCESS_ATTACH_ATTEMPT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559094(v=vs.85).aspx
Bug Check 0x60: PROCESS_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559094.aspx
Bug Check 0x60: PROCESS_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559097(v=vs.85).aspx
Bug Check 0x61: HAL1_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559097.aspx
Bug Check 0x61: HAL1_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559104(v=vs.85).aspx
Bug Check 0x62: OBJECT1_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559104.aspx
Bug Check 0x62: OBJECT1_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559108(v=vs.85).aspx
Bug Check 0x63: SECURITY1_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559108.aspx
Bug Check 0x63: SECURITY1_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559117(v=vs.85).aspx
Bug Check 0x64: SYMBOLIC_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559117.aspx
Bug Check 0x64: SYMBOLIC_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559120(v=vs.85).aspx
Bug Check 0x65: MEMORY1_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559120.aspx
Bug Check 0x65: MEMORY1_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559123(v=vs.85).aspx
Bug Check 0x66: CACHE_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559123.aspx
Bug Check 0x66: CACHE_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559126(v=vs.85).aspx
Bug Check 0x67: CONFIG_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559126.aspx
Bug Check 0x67: CONFIG_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559132(v=vs.85).aspx
Bug Check 0x68: FILE_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559132.aspx
Bug Check 0x68: FILE_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559133(v=vs.85).aspx
Bug Check 0x69: IO1_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559133.aspx
Bug Check 0x69: IO1_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559137(v=vs.85).aspx
Bug Check 0x6A: LPC_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559137.aspx
Bug Check 0x6A: LPC_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559142(v=vs.85).aspx
Bug Check 0x6B: PROCESS1_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559142.aspx
Bug Check 0x6B: PROCESS1_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559147(v=vs.85).aspx
Bug Check 0x6C: REFMON_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559147.aspx
Bug Check 0x6C: REFMON_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559152(v=vs.85).aspx
Bug Check 0x6D: SESSION1_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559152.aspx
Bug Check 0x6D: SESSION1_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559154(v=vs.85).aspx
Bug Check 0x6E: SESSION2_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559154.aspx
Bug Check 0x6E: SESSION2_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559156(v=vs.85).aspx
Bug Check 0x6F: SESSION3_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559156.aspx
Bug Check 0x6F: SESSION3_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559160(v=vs.85).aspx
Bug Check 0x6: INVALID_PROCESS_DETACH_ATTEMPT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559160.aspx
Bug Check 0x6: INVALID_PROCESS_DETACH_ATTEMPT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559167(v=vs.85).aspx
Bug Check 0x70: SESSION4_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559167.aspx
Bug Check 0x70: SESSION4_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559171(v=vs.85).aspx
Bug Check 0x71: SESSION5_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559171.aspx
Bug Check 0x71: SESSION5_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559178(v=vs.85).aspx
Bug Check 0x72: ASSIGN_DRIVE_LETTERS_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559178.aspx
Bug Check 0x72: ASSIGN_DRIVE_LETTERS_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559183(v=vs.85).aspx
Bug Check 0x73: CONFIG_LIST_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559183.aspx
Bug Check 0x73: CONFIG_LIST_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559188(v=vs.85).aspx
Bug Check 0x74: BAD_SYSTEM_CONFIG_INFO - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559188.aspx
Bug Check 0x74: BAD_SYSTEM_CONFIG_INFO (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559192(v=vs.85).aspx
Bug Check 0x75: CANNOT_WRITE_CONFIGURATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559192.aspx
Bug Check 0x75: CANNOT_WRITE_CONFIGURATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559194(v=vs.85).aspx
Bug Check 0x76: PROCESS_HAS_LOCKED_PAGES - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559194.aspx
Bug Check 0x76: PROCESS_HAS_LOCKED_PAGES (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559197(v=vs.85).aspx
Bug Check 0x77: KERNEL_STACK_INPAGE_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559197.aspx
Bug Check 0x77: KERNEL_STACK_INPAGE_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559206(v=vs.85).aspx
Bug Check 0x78: PHASE0_EXCEPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559206.aspx
Bug Check 0x78: PHASE0_EXCEPTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559209(v=vs.85).aspx
Bug Check 0x79: MISMATCHED_HAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559209.aspx
Bug Check 0x79: MISMATCHED_HAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559211(v=vs.85).aspx
Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559211.aspx
Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559218(v=vs.85).aspx
Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559218.aspx
Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559221(v=vs.85).aspx
Bug Check 0x7C: BUGCODE_NDIS_DRIVER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559221.aspx
Bug Check 0x7C: BUGCODE_NDIS_DRIVER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559232(v=vs.85).aspx
Bug Check 0x7D: INSTALL_MORE_MEMORY - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559232.aspx
Bug Check 0x7D: INSTALL_MORE_MEMORY (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559239.aspx
Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559244(v=vs.85).aspx
Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559244.aspx
Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559247(v=vs.85).aspx
Bug Check 0x7: INVALID_SOFTWARE_INTERRUPT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559247.aspx
Bug Check 0x7: INVALID_SOFTWARE_INTERRUPT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559250(v=vs.85).aspx
Bug Check 0x80: NMI_HARDWARE_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559250.aspx
Bug Check 0x80: NMI_HARDWARE_FAILURE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559255(v=vs.85).aspx
Bug Check 0x81: SPIN_LOCK_INIT_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559255.aspx
Bug Check 0x81: SPIN_LOCK_INIT_FAILURE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559261(v=vs.85).aspx
Bug Check 0x82: DFS_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559261.aspx
Bug Check 0x82: DFS_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559264(v=vs.85).aspx
Bug Check 0x85: SETUP_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559264.aspx
Bug Check 0x85: SETUP_FAILURE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559268(v=vs.85).aspx
Bug Check 0x8B: MBR_CHECKSUM_MISMATCH - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559268.aspx
Bug Check 0x8B: MBR_CHECKSUM_MISMATCH (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559271(v=vs.85).aspx
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559271.aspx
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559274(v=vs.85).aspx
Bug Check 0x8F: PP0_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559274.aspx
Bug Check 0x8F: PP0_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559278(v=vs.85).aspx
Bug Check 0x8: IRQL_NOT_DISPATCH_LEVEL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559278.aspx
Bug Check 0x8: IRQL_NOT_DISPATCH_LEVEL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559280(v=vs.85).aspx
Bug Check 0x90: PP1_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559280.aspx
Bug Check 0x90: PP1_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559285(v=vs.85).aspx
Bug Check 0x92: UP_DRIVER_ON_MP_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559285.aspx
Bug Check 0x92: UP_DRIVER_ON_MP_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559292(v=vs.85).aspx
Bug Check 0x93: INVALID_KERNEL_HANDLE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559292.aspx
Bug Check 0x93: INVALID_KERNEL_HANDLE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559296(v=vs.85).aspx
Bug Check 0x94: KERNEL_STACK_LOCKED_AT_EXIT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559296.aspx
Bug Check 0x94: KERNEL_STACK_LOCKED_AT_EXIT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559300(v=vs.85).aspx
Bug Check 0x96: INVALID_WORK_QUEUE_ITEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559300.aspx
Bug Check 0x96: INVALID_WORK_QUEUE_ITEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559303(v=vs.85).aspx
Bug Check 0x97: BOUND_IMAGE_UNSUPPORTED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559303.aspx
Bug Check 0x97: BOUND_IMAGE_UNSUPPORTED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559306(v=vs.85).aspx
Bug Check 0x98: END_OF_NT_EVALUATION_PERIOD - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559306.aspx
Bug Check 0x98: END_OF_NT_EVALUATION_PERIOD (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559312(v=vs.85).aspx
Bug Check 0x99: INVALID_REGION_OR_SEGMENT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559312.aspx
Bug Check 0x99: INVALID_REGION_OR_SEGMENT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559317(v=vs.85).aspx
Bug Check 0x9A: SYSTEM_LICENSE_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559317.aspx
Bug Check 0x9A: SYSTEM_LICENSE_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559318(v=vs.85).aspx
Bug Check 0x9B: UDFS_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559318.aspx
Bug Check 0x9B: UDFS_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559323(v=vs.85).aspx
Bug Check 0x9C: MACHINE_CHECK_EXCEPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559323.aspx
Bug Check 0x9C: MACHINE_CHECK_EXCEPTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559326(v=vs.85).aspx
Bug Check 0x9E: USER_MODE_HEALTH_MONITOR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559326.aspx
Bug Check 0x9E: USER_MODE_HEALTH_MONITOR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329.aspx
Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559337(v=vs.85).aspx
Bug Check 0x9: IRQL_NOT_GREATER_OR_EQUAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559337.aspx
Bug Check 0x9: IRQL_NOT_GREATER_OR_EQUAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff559341(v=vs.85).aspx
Bug Check 0xA0: INTERNAL_POWER_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff559341.aspx
Bug Check 0xA0: INTERNAL_POWER_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560101(v=vs.85).aspx
Bug Check 0xA1: PCI_BUS_DRIVER_INTERNAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560101.aspx
Bug Check 0xA1: PCI_BUS_DRIVER_INTERNAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560105(v=vs.85).aspx
Bug Check 0xA2: MEMORY_IMAGE_CORRUPT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560105.aspx
Bug Check 0xA2: MEMORY_IMAGE_CORRUPT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560106(v=vs.85).aspx
Bug Check 0xA3: ACPI_DRIVER_INTERNAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560106.aspx
Bug Check 0xA3: ACPI_DRIVER_INTERNAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560110(v=vs.85).aspx
Bug Check 0xA4: CNSS_FILE_SYSTEM_FILTER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560110.aspx
Bug Check 0xA4: CNSS_FILE_SYSTEM_FILTER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560114(v=vs.85).aspx
Bug Check 0xA5: ACPI_BIOS_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560114.aspx
Bug Check 0xA5: ACPI_BIOS_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560117(v=vs.85).aspx
Bug Check 0xA7: BAD_EXHANDLE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560117.aspx
Bug Check 0xA7: BAD_EXHANDLE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560119(v=vs.85).aspx
Bug Check 0xAB: SESSION_HAS_VALID_POOL_ON_EXIT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560119.aspx
Bug Check 0xAB: SESSION_HAS_VALID_POOL_ON_EXIT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560121(v=vs.85).aspx
Bug Check 0xAC: HAL_MEMORY_ALLOCATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560121.aspx
Bug Check 0xAC: HAL_MEMORY_ALLOCATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560125(v=vs.85).aspx
Bug Check 0xAD: VIDEO_DRIVER_DEBUG_REPORT_REQUEST - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560125.aspx
Bug Check 0xAD: VIDEO_DRIVER_DEBUG_REPORT_REQUEST (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560129(v=vs.85).aspx
Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560129.aspx
Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560133(v=vs.85).aspx
Bug Check 0xB4: VIDEO_DRIVER_INIT_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560133.aspx
Bug Check 0xB4: VIDEO_DRIVER_INIT_FAILURE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560140(v=vs.85).aspx
Bug Check 0xB8: ATTEMPTED_SWITCH_FROM_DPC - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560140.aspx
Bug Check 0xB8: ATTEMPTED_SWITCH_FROM_DPC (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560144(v=vs.85).aspx
Bug Check 0xB9: CHIPSET_DETECTED_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560144.aspx
Bug Check 0xB9: CHIPSET_DETECTED_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560151(v=vs.85).aspx
Bug Check 0xBA: SESSION_HAS_VALID_VIEWS_ON_EXIT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560151.aspx
Bug Check 0xBA: SESSION_HAS_VALID_VIEWS_ON_EXIT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560155(v=vs.85).aspx
Bug Check 0xBB: NETWORK_BOOT_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560155.aspx
Bug Check 0xBB: NETWORK_BOOT_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560159(v=vs.85).aspx
Bug Check 0xBC: NETWORK_BOOT_DUPLICATE_ADDRESS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560159.aspx
Bug Check 0xBC: NETWORK_BOOT_DUPLICATE_ADDRESS (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560161(v=vs.85).aspx
Bug Check 0xBE: ATTEMPTED_WRITE_TO_READONLY_MEMORY - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560161.aspx
Bug Check 0xBE: ATTEMPTED_WRITE_TO_READONLY_MEMORY (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/mt791890(v=vs.85).aspx
Bug Check 0xBFF: BC_BTHMINI_VERIFIER_FAULT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff560167(v=vs.85).aspx
Bug Check 0xBF: MUTEX_ALREADY_OWNED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560167.aspx
Bug Check 0xBF: MUTEX_ALREADY_OWNED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560171(v=vs.85).aspx
Bug Check 0xB: NO_EXCEPTION_HANDLING_SUPPORT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560171.aspx
Bug Check 0xB: NO_EXCEPTION_HANDLING_SUPPORT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560172(v=vs.85).aspx
Bug Check 0xC0000218: STATUS_CANNOT_LOAD_REGISTRY_FILE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560172.aspx
Bug Check 0xC0000218: STATUS_CANNOT_LOAD_REGISTRY_FILE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560177(v=vs.85).aspx
Bug Check 0xC000021A

: STATUS_SYSTEM_PROCESS_TERMINATED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff560177.aspx
Bug Check 0xC000021A

: STATUS_SYSTEM_PROCESS_TERMINATED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560180(v=vs.85).aspx
Bug Check 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560180.aspx
Bug Check 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560183(v=vs.85).aspx
Bug Check 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560183.aspx
Bug Check 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560185.aspx
Bug Check 0xC2: BAD_POOL_CALLER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560187(v=vs.85).aspx
Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560187.aspx
Bug Check 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560192(v=vs.85).aspx
Bug Check 0xC5: DRIVER_CORRUPTED_EXPOOL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560192.aspx
Bug Check 0xC5: DRIVER_CORRUPTED_EXPOOL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560193(v=vs.85).aspx
Bug Check 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560193.aspx
Bug Check 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560198(v=vs.85).aspx
Bug Check 0xC7: TIMER_OR_DPC_INVALID - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560198.aspx
Bug Check 0xC7: TIMER_OR_DPC_INVALID (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560202(v=vs.85).aspx
Bug Check 0xC8: IRQL_UNEXPECTED_VALUE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560202.aspx
Bug Check 0xC8: IRQL_UNEXPECTED_VALUE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560205(v=vs.85).aspx
Bug Check 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560205.aspx
Bug Check 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560209(v=vs.85).aspx
Bug Check 0xCA: PNP_DETECTED_FATAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560209.aspx
Bug Check 0xCA: PNP_DETECTED_FATAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560212(v=vs.85).aspx
Bug Check 0xCB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560212.aspx
Bug Check 0xCB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560216(v=vs.85).aspx
Bug Check 0xCC: PAGE_FAULT_IN_FREED_SPECIAL_POOL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560216.aspx
Bug Check 0xCC: PAGE_FAULT_IN_FREED_SPECIAL_POOL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560219(v=vs.85).aspx
Bug Check 0xCD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560219.aspx
Bug Check 0xCD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560226(v=vs.85).aspx
Bug Check 0xCE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560226.aspx
Bug Check 0xCE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560231(v=vs.85).aspx
Bug Check 0xCF: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560231.aspx
Bug Check 0xCF: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560236(v=vs.85).aspx
Bug Check 0xC: MAXIMUM_WAIT_OBJECTS_EXCEEDED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560236.aspx
Bug Check 0xC: MAXIMUM_WAIT_OBJECTS_EXCEEDED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560239(v=vs.85).aspx
Bug Check 0xD0: DRIVER_CORRUPTED_MMPOOL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560239.aspx
Bug Check 0xD0: DRIVER_CORRUPTED_MMPOOL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560244(v=vs.85).aspx
Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244.aspx
Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560249(v=vs.85).aspx
Bug Check 0xD2: BUGCODE_ID_DRIVER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560249.aspx
Bug Check 0xD2: BUGCODE_ID_DRIVER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560252(v=vs.85).aspx
Bug Check 0xD3: DRIVER_PORTION_MUST_BE_NONPAGED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560252.aspx
Bug Check 0xD3: DRIVER_PORTION_MUST_BE_NONPAGED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560256(v=vs.85).aspx
Bug Check 0xD4: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560256.aspx
Bug Check 0xD4: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560263(v=vs.85).aspx
Bug Check 0xD5: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560263.aspx
Bug Check 0xD5: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560267(v=vs.85).aspx
Bug Check 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560267.aspx
Bug Check 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560269(v=vs.85).aspx
Bug Check 0xD7: DRIVER_UNMAPPING_INVALID_VIEW - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560269.aspx
Bug Check 0xD7: DRIVER_UNMAPPING_INVALID_VIEW (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560271(v=vs.85).aspx
Bug Check 0xD8: DRIVER_USED_EXCESSIVE_PTES - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560271.aspx
Bug Check 0xD8: DRIVER_USED_EXCESSIVE_PTES (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560277(v=vs.85).aspx
Bug Check 0xD9: LOCKED_PAGES_TRACKER_CORRUPTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560277.aspx
Bug Check 0xD9: LOCKED_PAGES_TRACKER_CORRUPTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560282(v=vs.85).aspx
Bug Check 0xDA: SYSTEM_PTE_MISUSE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560282.aspx
Bug Check 0xDA: SYSTEM_PTE_MISUSE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560286(v=vs.85).aspx
Bug Check 0xDB: DRIVER_CORRUPTED_SYSPTES - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560286.aspx
Bug Check 0xDB: DRIVER_CORRUPTED_SYSPTES (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560293(v=vs.85).aspx
Bug Check 0xDC: DRIVER_INVALID_STACK_ACCESS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560293.aspx
Bug Check 0xDC: DRIVER_INVALID_STACK_ACCESS (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560300(v=vs.85).aspx
Bug Check 0xDEADDEAD: MANUALLY_INITIATED_CRASH1 - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560300.aspx
Bug Check 0xDEADDEAD: MANUALLY_INITIATED_CRASH1 (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560303(v=vs.85).aspx
Bug Check 0xDE: POOL_CORRUPTION_IN_FILE_AREA - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560303.aspx
Bug Check 0xDE: POOL_CORRUPTION_IN_FILE_AREA (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560308(v=vs.85).aspx
Bug Check 0xDF: IMPERSONATING_WORKER_THREAD - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560308.aspx
Bug Check 0xDF: IMPERSONATING_WORKER_THREAD (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560311(v=vs.85).aspx
Bug Check 0xD: MUTEX_LEVEL_NUMBER_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560311.aspx
Bug Check 0xD: MUTEX_LEVEL_NUMBER_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560314(v=vs.85).aspx
Bug Check 0xE0: ACPI_BIOS_FATAL_ERROR - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560314.aspx
Bug Check 0xE0: ACPI_BIOS_FATAL_ERROR (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560322(v=vs.85).aspx
Bug Check 0xE1: WORKER_THREAD_RETURNED_AT_BAD_IRQL - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560322.aspx
Bug Check 0xE1: WORKER_THREAD_RETURNED_AT_BAD_IRQL (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560324(v=vs.85).aspx
Bug Check 0xE2: MANUALLY_INITIATED_CRASH - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560324.aspx
Bug Check 0xE2: MANUALLY_INITIATED_CRASH (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560330(v=vs.85).aspx
Bug Check 0xE3: RESOURCE_NOT_OWNED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560330.aspx
Bug Check 0xE3: RESOURCE_NOT_OWNED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560336(v=vs.85).aspx
Bug Check 0xE4: WORKER_INVALID - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560336.aspx
Bug Check 0xE4: WORKER_INVALID (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560341(v=vs.85).aspx
Bug Check 0xE6: DRIVER_VERIFIER_DMA_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560341.aspx
Bug Check 0xE6: DRIVER_VERIFIER_DMA_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560344(v=vs.85).aspx
Bug Check 0xE7: INVALID_FLOATING_POINT_STATE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560344.aspx
Bug Check 0xE7: INVALID_FLOATING_POINT_STATE (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560347(v=vs.85).aspx
Bug Check 0xE8: INVALID_CANCEL_OF_FILE_OPEN - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560347.aspx
Bug Check 0xE8: INVALID_CANCEL_OF_FILE_OPEN (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560349(v=vs.85).aspx
Bug Check 0xE9: ACTIVE_EX_WORKER_THREAD_TERMINATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560349.aspx
Bug Check 0xE9: ACTIVE_EX_WORKER_THREAD_TERMINATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560350(v=vs.85).aspx
Bug Check 0xEA: THREAD_STUCK_IN_DEVICE_DRIVER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560350.aspx
Bug Check 0xEA: THREAD_STUCK_IN_DEVICE_DRIVER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560353(v=vs.85).aspx
Bug Check 0xEB: DIRTY_MAPPED_PAGES_CONGESTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560353.aspx
Bug Check 0xEB: DIRTY_MAPPED_PAGES_CONGESTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560354(v=vs.85).aspx
Bug Check 0xEC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560354.aspx
Bug Check 0xEC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560355(v=vs.85).aspx
Bug Check 0xED: UNMOUNTABLE_BOOT_VOLUME - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560355.aspx
Bug Check 0xED: UNMOUNTABLE_BOOT_VOLUME (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560358.aspx
Bug Check 0xEF: CRITICAL_PROCESS_DIED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560360(v=vs.85).aspx
Bug Check 0xE: NO_USER_MODE_CONTEXT - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560360.aspx
Bug Check 0xE: NO_USER_MODE_CONTEXT (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560365(v=vs.85).aspx
Bug Check 0xF1: SCSI_VERIFIER_DETECTED_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560365.aspx
Bug Check 0xF1: SCSI_VERIFIER_DETECTED_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560368(v=vs.85).aspx
Bug Check 0xF3: DISORDERLY_SHUTDOWN - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560368.aspx
Bug Check 0xF3: DISORDERLY_SHUTDOWN (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560372(v=vs.85).aspx
Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560372.aspx
Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560383(v=vs.85).aspx
Bug Check 0xF5: FLTMGR_FILE_SYSTEM - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560383.aspx
Bug Check 0xF5: FLTMGR_FILE_SYSTEM (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560386(v=vs.85).aspx
Bug Check 0xF6: PCI_VERIFIER_DETECTED_VIOLATION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560386.aspx
Bug Check 0xF6: PCI_VERIFIER_DETECTED_VIOLATION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560389(v=vs.85).aspx
Bug Check 0xF7: DRIVER_OVERRAN_STACK_BUFFER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560389.aspx
Bug Check 0xF7: DRIVER_OVERRAN_STACK_BUFFER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560392(v=vs.85).aspx
Bug Check 0xF8: RAMDISK_BOOT_INITIALIZATION_FAILED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560392.aspx
Bug Check 0xF8: RAMDISK_BOOT_INITIALIZATION_FAILED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560396(v=vs.85).aspx
Bug Check 0xF9: DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560396.aspx
Bug Check 0xF9: DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560399(v=vs.85).aspx
Bug Check 0xFA: HTTP_DRIVER_CORRUPTED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560399.aspx
Bug Check 0xFA: HTTP_DRIVER_CORRUPTED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560402(v=vs.85).aspx
Bug Check 0xFC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560402.aspx
Bug Check 0xFC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560404(v=vs.85).aspx
Bug Check 0xFD: DIRTY_NOWRITE_PAGES_CONGESTION - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560404.aspx
Bug Check 0xFD: DIRTY_NOWRITE_PAGES_CONGESTION (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560407(v=vs.85).aspx
Bug Check 0xFE: BUGCODE_USB_DRIVER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560407.aspx
Bug Check 0xFE: BUGCODE_USB_DRIVER (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560409(v=vs.85).aspx
Bug Check 0xFF: RESERVE_QUEUE_OVERFLOW - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560409.aspx
Bug Check 0xFF: RESERVE_QUEUE_OVERFLOW (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/ff560412(v=vs.85).aspx
Bug Check 0xF: SPIN_LOCK_ALREADY_OWNED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/ff560412.aspx
Bug Check 0xF: SPIN_LOCK_ALREADY_OWNED (Windows Debuggers)

http://msdn.microsoft.com/en-us/library/hh994433(v=vs.85).aspx
Bug Check Code Reference - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/hardware/hh994433.aspx
Bug Check Code Reference (Windows Debuggers)

(STATUS_SYSTEM_PROCESS_TERMINATED) with Verification of a known DLL failed X64_0xc000021a_c000012f - Ben Parker's Blog - Site Home - TechNet Blogs

http://msdn.microsoft.com/en-us/library/windows/hardware/ff540642(v=vs.85).aspx
Debugging CSRSS - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/windows/desktop/ff540642.aspx
Debugging CSRSS (Windows Debuggers)

http://blogs.technet.com/b/core/?pi47604=2
Die Core Leute - Site Home - TechNet Blogs

http://blogs.technet.microsoft.com/plitpro/tag/grzegorz-tworek/feed/index.html
Grzegorz Tworek – Polski TechNet Blog

http://support.hp.com/jp-ja/document/c01322724
HP Compaq Business Desktop - 「STOP 0xC000021A

unknown hard error」エラーが表示され、Windows XP が起動できない場合の対処方法 | HPRSupport

http://msdn.microsoft.com/en-us/windows/hardware/drivers/devtest/interpreting-a-bug-check-code
Interpreting a Bug Check Code

http://msdn.microsoft.com/en-us/library/windows/desktop/ff547224.aspx
Interpreting a Bug Check Code (Windows Drivers)

http://blogs.technet.microsoft.com/plitpro/tag/it-pro-blogerzy/feed/index.html
IT Pro blogerzy – Polski TechNet Blog

http://blogs.technet.com/b/trm/archive/2008/06/01/june-2008-technical-rollup-mail-platforms.aspx
June 2008 - Technical Rollup Mail - Platforms - Technical RollUp - Site Home - TechNet Blogs

http://blogs.technet.com/b/hot/archive/2008/05/13/may-6-may-12-hot-fix-kb-articles-weekly-release-windows-server.aspx
May 6 - May 12 Hot-Fix KB articles Weekly Release - Windows Server - The Hot Blog - Site Home - TechNet Blogs

http://answers.microsoft.com/en-us/feed/u/59d6cbb5-41d6-4e14-b912-6a090835dc53/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
Microsoft Community - Threads activity by TerryChuang

http://support.hp.com/jp-ja/document/c02931137
Microsoft Windows XP FAQ 一覧 (トラブルシューティング) | HPRSupport

http://blogs.technet.com/b/plitpromicrosoftcom/archive/2014/02/11/niezabijalne-procesy.aspx
Niezabijalne procesy - Polski TechNet Blog - Site Home - TechNet Blogs

http://blogs.technet.microsoft.com/plitpro/2014/02/11/niezabijalne-procesy/index.html?replytocom=1253
Niezabijalne procesy – Polski TechNet Blog

http://blogs.technet.com/b/trm/archive/2006/09/11/september-2006-technical-rollup-mail-platforms.aspx
September 2006 - Technical Rollup Mail - Platforms - Technical RollUp - Site Home - TechNet Blogs

http://blogs.technet.com/b/?pi142383=6059
TechNet Blogs

http://blogs.technet.com/b/askcore/archive/2012/04/15/troubleshooting-boot-issues-due-to-missing-driver-signature-x64.aspx
Troubleshooting Boot Issues due to missing Driver signature (x64) - Ask the Core Team - Site Home - TechNet Blogs

http://blogs.technet.com/b/supportingwindows/archive/2012/04/15/troubleshooting-boot-issues-due-to-missing-driver-signature-x64.aspx
Troubleshooting Boot Issues due to missing Driver signature (x64) - SupportingWindows - Site Home - TechNet Blogs

http://blogs.technet.microsoft.com/askcore/2012/04/15/troubleshooting-boot-issues-due-to-missing-driver-signature-x64/index.html
Troubleshooting Boot Issues due to missing Driver signature (x64) | Ask the Core Team

http://technet.microsoft.com/en-us/library/cc785339.aspx
Troubleshooting specific Stop messages

http://blogs.technet.com/b/yongrhee/archive/2010/01/06/troubleshooting-stop-0xc000021a-winlogon-exe.aspx
Troubleshooting Stop 0xC000021A

Winlogon.exe - The troubleshooters and problem solvers... - Site Home - TechNet Blogs

http://msdn.microsoft.com/ja-jp/library/windows/hardware/ff542247.aspx
Windows ブルースクリーンデータ (Windows Drivers)

http://support.hp.com/jp-ja/document/c02794236
Windows ロゴの表示から [ようこそ] 画面まで (起動しない場合の対処方法) | HPRSupport

http://ITPro.nikkeibp.co.jp/free/NT/WinReadersOnly/20040415/32/?n_cid=nbpitp_itptw_top
Windows読者限定 - システム・クラッシュではないのにWindows 2000がリブートしてしまう：ITpro

http://blogs.technet.com/b/core/archive/2012/01/04/xp-bsod-0xc000021a-w-228-hrend-des-boot-prozess.aspx
XP BSOD 0xC000021A

wahrend des System-Starts (Session Manager initialization terminated) - Die Core Leute - Site Home - TechNet Blogs

http://msdn.microsoft.com/en-us/library/ff557389(v=vs.85).aspx
(Developer Content) Bug Check 0x19: BAD_POOL_HEADER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff559239(v=vs.85).aspx
(Developer Content) Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff559329(v=vs.85).aspx
(Developer Content) Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff560185(v=vs.85).aspx
(Developer Content) Bug Check 0xC2: BAD_POOL_CALLER - Windows 10 hardware dev

http://msdn.microsoft.com/en-us/library/ff560358(v=vs.85).aspx
(Developer Content) Bug Check 0xEF: CRITICAL_PROCESS_DIED - Windows 10 hardware dev

http://msdn.microsoft.com/ja-jp/library/windows/hardware/ff547224.aspx
バグチェックコードの解釈 (Windows Drivers)

http://answers.microsoft.com/ja-jp/feed/u/59d6cbb5-41d6-4e14-b912-6a090835dc53/threads?filter=AlmostAll&threadType=All&blogRequestType=BlogPost
マイクロソフトコミュニティ - スレッド活動者 TerryChuang

http://support.microsoft.com/en-us/kb/180854/en-us
Access Violation in Winlogon with Third-Party Gina.dll対象製品：Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT 4.0 Service Pack 3, Microsoft Windows NT Server 4.0 Enterprise Edition

http://support.microsoft.com/ja-jp/kb/832002/ja
Atapi.sys ATA エラーレジスタビット 01 h にマップすると stop エラーメッセージが発生します。対象製品：Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/171777/en-us
BLU: Getadmin.exe Causes a STOP 0xC000021A

対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/137400/en-us
Changing Default Permissions Causes STOP 0xC000021A

対象製品：Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/183840/ja
Ctrl + Alt + Del でタスクマネージャを起動したときの Stop 0xC000021A

エラー対象製品：Microsoft Windows NT Server 4.0 Terminal Server, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/en-us/kb/112455/en-us
Err Msg: STOP Message 0xC000021A

Starting Windows Application対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1

http://support.microsoft.com/en-us/kb/295087/en-us
Error message cites "Stop error code 0xC000021A

(STATUS_SYSTEM_PROCESS_TERMINATED)" event

http://support.microsoft.com/en-us/kb/330303/en-us
Error message in Windows 2000: "STOP: c000021a (Fatal System Error)"対象製品：Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Server

http://support.microsoft.com/en-us/kb/327020/en-us
Error Message Occurs When You Start Disk Management After Extending a Hardware Array対象製品：Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

http://support.microsoft.com/en-us/kb/294728/en-us
Error message: "Stop error code 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED)" in Win32k.sys or a "Stop error code 0xC000021A

"対象製品：Microsoft Windows 2000 Server, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/156669/en-us
How to troubleshoot a "STOP 0xC000021A

" error対象製品：Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows XP Professional, Microsoft Windows XP Media Center Edition 2005 Update Rollup 2, Microsoft Windows XP Tablet PC Edition

http://support.microsoft.com/en-us/kb/194834/en-us
List of bugs fixed in Windows NT 4.0 and Terminal Server Edition Service Pack 4 (Part 2)対象製品：Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT 4.0 Service Pack 4, Microsoft Windows NT Server 4.0 Enterprise Edition

http://support.microsoft.com/en-us/kb/241211/en-us
List of bugs fixed in Windows NT 4.0 Service Pack 6/6a (Part 1)

http://support.microsoft.com/en-us/kb/240331/en-us
List of Bugs Fixed in Windows NT Server 4.0, Terminal Server Edition, Service Pack 5

http://support.microsoft.com/en-us/kb/133321/en-us
List of Fixed Bugs in Windows NT Version 3.51対象製品：Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/237399/ja
NTFS のデフォルトのアクセス許可は、NTFS に変換したブートパーティションには適用されない対象製品：Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

http://support.microsoft.com/en-us/kb/173060/en-us
Performance Monitor Counters Cause Stop or Error Messages対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/155267/en-us
Registry Editors Installed by Windows NT 4.0対象製品：Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/en-us/kb/171033/en-us
Remote Performance Monitor Changes Under Windows NT 4.0 SP3対象製品：Microsoft Commercial Internet System 1.0 Service Pack 2

http://support.microsoft.com/en-us/kb/109076/en-us
Removing Permissions to an NTFS Partition May Prevent Startup対象製品：Microsoft Windows NT Workstation 3.1

http://support.microsoft.com/en-us/kb/234658/en-us
STOP 0xC000021A

in CSRSS After Attempting to Free an Already Freed Screen Buffer対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/195027/en-us
STOP 0xC000021A

in Winlogon Caused by PCAnywhere対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/en-us/kb/238495/en-us
STOP 0xC000021A

in Winlogon.exe on a Terminal Server

http://support.microsoft.com/en-us/kb/183840/en-us
Stop 0xC000021A

When Starting Task Manager with CTRL+ALT+DEL対象製品：Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/ja-jp/kb/160658/ja
STOP C000021A MoveFileEx を使用しての MOVEFILE_DELAY_UNTIL_REBOOT対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/832002/en-us
Stop Error Messages Occur When Atapi.sys Maps ATA Error Register Bit 01h対象製品：Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/116405/en-us
STOP Message: 0xC000021A

During Logon Because of Bad PATH対象製品：Microsoft Windows NT Workstation 3.1

http://support.microsoft.com/en-us/kb/116404/en-us
STOP Message: 0xC000021A

or Other Problems with Long PATH対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Server 3.5

http://support.microsoft.com/ja-jp/kb/116404/ja
STOP メッセージ: 0xC000021A

または長整数型 (Long) の PATH に関するその他の問題対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Server 3.5

http://support.microsoft.com/ja-jp/kb/240331/ja
Terminal Server Edition Service Pack 5 修正一覧対象製品：Microsoft Windows NT Server 4.0 Terminal Server Service Pack 5

http://support.microsoft.com/en-us/kb/237399/en-us
The Default NTFS Permissions Are Not Applied to a Converted Boot Partition対象製品：Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

http://support.microsoft.com/en-us/kb/137396/en-us
Unable to Copy Files During Windows NT 3.51 Upgrade対象製品：Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/171033/ja
Windows NT 4. 0 SP3 でのリモートパフォーマンスモニターの変更対象製品：Microsoft Commercial Internet System 1.0 Service Pack 2

http://support.microsoft.com/ja-jp/kb/194834/ja
Windows NT 4.0 および Terminal Server Edition Service Pack 4 で修正された問題の一覧 (第 2 部)対象製品：Microsoft Windows NT Server 4.0 Terminal Server, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT 4.0 Service Pack 4, Microsoft Windows NT Server 4.0 Enterprise Edition

http://support.microsoft.com/ja-jp/kb/238495/ja
Windows NT 4.0 で Winlogon.exe を実行すると STOP 0xC000021A

のエラーが発生する対象製品：Microsoft Windows NT Server 4.0 Terminal Server, Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4

http://support.microsoft.com/ja-jp/kb/818896/ja
Windows NT Server 4.0 を実行しているコンピュータの使用中に Csrss.exe で "0xC000021A

" Stop エラーが発生する対象製品：Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/ja-jp/kb/133321/ja
Windows NT Version 3. 51 で固定バグの一覧対象製品：Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/883275/ja
Windows Server 2003、Windows XP または Windows 2000 でアクセス許可を変更した後コンピュータを起動できない対象製品：Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional, Microsoft Windows XP Professional, Microsoft Windows XP Home Edition

http://support.microsoft.com/en-us/kb/261318/en-us
Winlogon May Cause an Access Violation with Long Environment Variables対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/ja-jp/kb/195027/ja
Winlogon の PCAnywhere が原因で stop 0xC000021A

します。

http://support.microsoft.com/ja-jp/kb/261318/ja
Winlogon 長整数型 (Long) の環境変数で、アクセス違反が発生します。対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/en-us/kb/329484/en-us
Winlogon.exe Access Violation When KillScreenSaver Function Calls CloseObjectMonitorObject with "ScreenSaverData->Monitor = NULL"対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT 4.0 Service Pack 6, Microsoft Windows NT 4.0 Service Pack 6a, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT 4.0 Service Pack 6, Microsoft Windows NT 4.0 Service Pack 6a

http://support.microsoft.com/ja-jp/kb/329484/ja
Winlogon.exe アクセス違反 KillScreenSaver 関数の呼び出しで CloseObjectMonitorObject と"モニター > ScreenSaverData NULL ="対象製品：Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT 4.0 Service Pack 6, Microsoft Windows NT 4.0 Service Pack 6a, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT 4.0 Service Pack 6, Microsoft Windows NT 4.0 Service Pack 6a

http://support.microsoft.com/en-us/kb/307866/en-us
You cannot log on to the computer after you run a repair process if SRP is installed

http://support.microsoft.com/en-us/kb/883275/en-us
You cannot start your computer after you modify the permissions in Windows Server 2003, in Windows XP, or in Windows 2000対象製品：Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows XP Professional, Microsoft Windows XP Home Edition

http://support.microsoft.com/en-us/kb/818896/en-us
"0xC000021A

" Stop error in Csrss.exe while you are using a computer that is running Windows NT Server 4.0対象製品：Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/ja-jp/kb/156669/ja
"STOP 0xC000021A

" エラーのトラブルシューティング方法対象製品：Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows XP Professional, Microsoft Windows XP Media Center Edition 2005 Update Rollup 2, Microsoft Windows XP Tablet PC Edition

http://support.microsoft.com/ja-jp/kb/173060/ja
[NT] パフォーマンスモニタによる STOP エラー対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/ja-jp/kb/171777/ja
[NT]Getadmin.exe インストール後 STOP 0xC000021A

が発生する対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

http://support.microsoft.com/ja-jp/kb/180854/ja
[NT]Gina.dll による Winlogon でのアクセス違反対象製品：Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT 4.0 Service Pack 3, Microsoft Windows NT Server 4.0 Enterprise Edition, Microsoft Windows NT Server 4.0 Terminal Server

http://support.microsoft.com/ja-jp/kb/295087/ja
エラーメッセージ「エラーコード 0xC000021A

(STATUS_SYSTEM_PROCESS_TERMINATED) を停止する」イベントを評価しました

http://support.microsoft.com/ja-jp/kb/307866/ja
セキュリティロールアップパッケージがインストールされていると修復プロセスの実行後にコンピュータにログオンできない対象製品：Microsoft Windows NT 4.0 Service Pack 6a, Microsoft Windows NT 4.0 Service Pack 6a, Microsoft Windows NT Workstation 4.0 Developer Edition

http://support.microsoft.com/ja-jp/kb/327020/ja
ハードウェアアレイの拡張後 [ディスクの管理] を起動するとエラーメッセージが表示される対象製品：Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional

http://support.microsoft.com/ja-jp/kb/112455/ja
メッセージ 0xC000021A

http://support.microsoft.com/ja-jp/kb/155026/ja
状態 c00000005 を持つ Windows サブシステムで 0xC000021A

を停止します。対象製品：Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/137400/ja
変更の既定のアクセス許可と STOP 0xC000021A

対象製品：Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/2746140/ja
You receive "0x0000006B" and "0xC000021A

" Stop error message after uninstalling McAfee Agent 4.6.2 in Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008 R2対象製品：Windows Vista Home Basic, Windows Vista Home Premium, Windows Vista Business, Windows Vista Ultimate, Windows Vista Service Pack 2, Windows Server 2008 Standard, Windows Server 2008 Standard without Hyper-V, Windows Server 2008 Enterprise, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 Datacenter, Windows Server 2008 Datacenter without Hyper-V, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 Service Pack 2, Windows 7 Home Basic, Windows 7 Home Premium, Windows 7 Professional, Windows 7 Enterprise, Windows 7 Ultimate, Windows 7 Service Pack 1, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Standard without Hyper-V, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Enterprise without Hyper-V, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Datacenter without Hyper-V, Windows Server 2008 R2 for Itanium-Based Systems, Windows Server 2008 R2 Service Pack 1

http://support.microsoft.com/en-us/kb/134798/en-us
Screen Saver Causes STOP 0xC000021A

Under Windows NT対象製品：Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/195027/ja
Winlogon の PCAnywhere が原因で stop 0xC000021A

します。

http://support.microsoft.com/ja-jp/kb/294728/ja
エラーメッセージ:"Stop エラーコード 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED)"Win32k.sys で「Stop エラーコード 0xC000021A

」に

http://support.microsoft.com/ja-jp/kb/295087/ja
エラーメッセージ「エラーコード 0xC000021A

(STATUS_SYSTEM_PROCESS_TERMINATED) を停止する」イベントを評価しました

http://support.microsoft.com/ja-jp/kb/134798/ja
スクリーンセーバーと Windows NT で 0xC000021A

を停止します。対象製品：Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Server 3.51

http://support.microsoft.com/ja-jp/kb/234658/ja
既に解放済みの画面バッファーを解放しようとするいると CSRSS で stop 0xC000021A

します。

スポンサードリンク

一覧に戻る

0xc000021aエラーコード(16進数8桁)： 関連のページ

0xc000021aエラーコード(16進数8桁)：関連のページ