Microsoft MVP성태의 닷넷 이야기
글쓴 사람
정성태 (techsharer at outlook.com)
홈페이지
첨부 파일
 
(연관된 글이 1개 있습니다.)

Hyper-V 서비스 시작 오류 - Not enough storage is available to complete this operation.

결론부터 말씀드리면 이 오류는 해결하지 못했습니다. 잘 되던 Hyper-V 서비스가 갑자기 다음과 같은 오류를 발생하며 "시작" 상태로 진입하지 못했습니다.

Windows could not start the Hyper-V Virtual Machine Management service on Local Computer.

Error 14: Not enough storage is available to complete this operation.

이벤트 로그에도 동일한 오류가 남을 뿐 그다지 별 도움이 되지 않았습니다.

Log Name:      System
Source:        Service Control Manager
Date:          2014-01-06 오전 9:20:01
Event ID:      7023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      testpc.testad.com
Description:
The Hyper-V Virtual Machine Management service terminated with the following error: 
Not enough storage is available to complete this operation.

검색해 보니 다음의 글이 그나마 관련이 있었는데요.

The Hyper-V Virtual Machine Management service terminated with the following error: Not enough storage is available to complete this operation. 
; http://social.technet.microsoft.com/Forums/windows/en-US/c137fe1a-e34d-469a-9e98-2a2c2199ced2/the-hyperv-virtual-machine-management-service-terminated-with-the-following-error-not-enough?forum=w8itprovirt

제 경우에 실제로 다음과 같은 결과를 보였고 하드 디스크의 일부 데이터가 손실된 듯 합니다.

c:\>chkdsk /scan

Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on C:
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
                                                                                       
                                                                                       
  266496 file records processed.                                                         File verification completed.
                                                                                       
                                                                                       
  1925 large file records processed.                                                                                                                           
                                                                                       
  0 bad file records processed.                                      
Stage 2: Examining file name linkage ...
Read failure with status 0xc000000d at offset 0x1364119000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\addons\APPXLOB-Server <0x1,0x2e227>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\addons\APPXLOB-Server <0x1,0x2e227>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136417a000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\legacy <0x1,0x2e229>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\legacy <0x1,0x2e229>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1364185000 for 0x1000 bytes.
    Found a bad index "$I30" in directory "\Windows\System32\spp\tokens\ppdlic <0x1,0x2e22b>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1452871000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\ppdlic <0x1,0x2e22b>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x90 is invalid.
15 49 03 00 00 00 01 00 90 00 74 00 01 00 00 00  .I........t.....
2b e2 02 00 00 00 01 00 ea 83 56 70 34 9f ce 01  +.........Vp4...
ea 83 56 70 34 9f ce 01 77 b0 75 07 b4 af ce 01  ..Vp4...w.u.....
ea 83 56 70 34 9f ce 01 00 10 00 00 00 00 00 00  ..Vp4...........
70 0b 00 00 00 00 00 00 20 00 00 00 00 00 00 00  p....... .......
19 00 4c 00 53 00 41 00 2d 00 4c 00 69 00 63 00  ..L.S.A.-.L.i.c.
65 00 6e 00 73 00 65 00 2d 00 70 00 70 00 64 00  e.n.s.e.-.p.p.d.
6c 00 69 00 63 00 2e 00 78 00 72 00 6d 00 2d 00  l.i.c...x.r.m.-.
6d 00 73 00 00 00 00 00 ff ff ff ff ff ff ff ff  m.s.............
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\ppdlic <0x1,0x2e22b>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136418b000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\skus\csvlk-pack <0x1,0x2e22e>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\skus\csvlk-pack <0x1,0x2e22e>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136419d000 for 0x1000 bytes.
    Found a bad index "$I30" in directory "\Windows\System32\spp\tokens\skus\ServerStandard <0x1,0x2e22f>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x13641a0000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\skus\ServerStandard <0x1,0x2e22f>"
        ... queued for offline repair.
The down pointer of current index entry with length 0xa8 is invalid.
45 49 03 00 00 00 01 00 a8 00 8c 00 01 00 00 00  EI..............
2f e2 02 00 00 00 01 00 0b 5a 5b e6 51 9f ce 01  /........Z[.Q...
0b 5a 5b e6 51 9f ce 01 f1 94 a1 07 b4 af ce 01  .Z[.Q...........
0b 5a 5b e6 51 9f ce 01 00 30 00 00 00 00 00 00  .Z[.Q....0......
5f 2a 00 00 00 00 00 00 20 00 00 00 00 00 00 00  _*...... .......
25 00 53 00 65 00 72 00 76 00 65 00 72 00 53 00  %.S.e.r.v.e.r.S.
74 00 61 00 6e 00 64 00 61 00 72 00 64 00 2d 00  t.a.n.d.a.r.d.-.
52 00 65 00 74 00 61 00 69 00 6c 00 2d 00 31 00  R.e.t.a.i.l.-.1.
2d 00 70 00 6c 00 2d 00 72 00 74 00 6d 00 2e 00  -.p.l.-.r.t.m...
78 00 72 00 6d 00 2d 00 6d 00 73 00 00 00 00 00  x.r.m.-.m.s.....
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\skus\ServerStandard <0x1,0x2e22f>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1364206000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\sr-Latn-CS <0x1,0x2e231>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\sr-Latn-CS <0x1,0x2e231>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136427c000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\sr-Latn-RS <0x1,0x2e232>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\sr-Latn-RS <0x1,0x2e232>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1452d7b000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\sv-SE <0x1,0x2e233>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\sv-SE <0x1,0x2e233>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1b03e000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\Sysprep <0x1,0x2e234>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Sysprep <0x1,0x2e234>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1360683000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Active Directory Rights Management Services Client <0x1,0x2e23b>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Active Directory Rights Management Services Client <0x1,0x2e23b>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x690d0000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\CertificateServicesClient <0x1,0x2e241>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\CertificateServicesClient <0x1,0x2e241>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x142f982000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Customer Experience Improvement Program <0x1,0x2e243>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Customer Experience Improvement Program <0x1,0x2e243>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0xbb45c7000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Data Integrity Scan <0x1,0x2e245>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Data Integrity Scan <0x1,0x2e245>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x142f98e000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Plug and Play <0x1,0x2e252>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Plug and Play <0x1,0x2e252>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x142f996000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform <0x1,0x2e25c>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform <0x1,0x2e25c>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x13a6c52000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\WS <0x1,0x2e26f>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\WS <0x1,0x2e26f>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1453603000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\th-TH <0x1,0x2e270>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\th-TH <0x1,0x2e270>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1453605000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\tr-TR <0x1,0x2e271>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\tr-TR <0x1,0x2e271>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1453607000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\uk-UA <0x1,0x2e272>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\uk-UA <0x1,0x2e272>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x13643d8000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\wbem <0x1,0x2e273>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wbem <0x1,0x2e273>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136719d000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\wbem\en-US <0x1,0x2e275>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wbem\en-US <0x1,0x2e275>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x14311e2000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\wbem\Repository <0x1,0x2e27a>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wbem\Repository <0x1,0x2e27a>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0xbb0b06000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\wdi\LogFiles <0x1,0x2e27e>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wdi\LogFiles <0x1,0x2e27e>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1455a56000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Win

하단에 "wbem" 관련 폴더도 눈에 띄는데요. WMI 관련 서비스에 의존하는 WindowSMART 프로그램을 실행하니 다음과 같은 오류 메시지만 출력할 뿐이었습니다.

WMI Failure Predicted: False
The Microsoft storage driver is reporting False over WMI for the flag "failure predicted." The storage driver is not detecting any problems.

윈도우 백업 서비스를 이용해 시스템 전체 백업이 되어 있었지만 지난 백업 날짜로 C 드라이브를 통째로 돌려도 마찬가지 문제가 발생했습니다. 가정을 해보자면, 지난번 부팅 이후로 파일 시스템이 깨진 곳이 있었고 백업도 그것을 포함해서 된 것 같습니다. (백업 하드 용량이 작은 관계로 백업이 2개 정도만 보관된 것도 문제였고. ^^;) 그러다가 이번에 재부팅이 되면서 wbem 관련 문제가 발생해 Hyper-V 서비스가 시작하지 못하게 된 것입니다.

어쩔 수 없이! Hyper-V 호스트 운영체제만 새로 설치를 하는 것으로 문제를 우회했습니다. (역시 VM으로 서비스들을 뽑아놓으니 복구가 빠르게 되는군요. ^^;) 해결책 찾는 것보다 새로 설치하는 것이 더 빨랐습니다.




[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]

[연관 글]






[최초 등록일: ]
[최종 수정일: 6/27/2021]

Creative Commons License
이 저작물은 크리에이티브 커먼즈 코리아 저작자표시-비영리-변경금지 2.0 대한민국 라이센스에 따라 이용하실 수 있습니다.
by SeongTae Jeong, mailto:techsharer at outlook.com

비밀번호

댓글 작성자
 




... [106]  107  108  109  110  111  112  113  114  115  116  117  118  119  120  ...
NoWriterDateCnt.TitleFile(s)
11274정성태8/22/201719411.NET Framework: 674. Thread 타입의 Suspend/Resume/Join 사용 관련 예외 처리
11273정성태8/22/201721634오류 유형: 415. 윈도우 업데이트 에러 Error 0x80070643
11272정성태8/21/201724826VS.NET IDE: 120. 비주얼 스튜디오 2017 버전 15.3.1 - C# 7.1 공개 [2]
11271정성태8/19/201719268VS.NET IDE: 119. Visual Studio 2017에서 .NET Core 2.0 프로젝트 환경 구성하는 방법
11270정성태8/17/201730735.NET Framework: 673. C#에서 enum을 boxing 없이 int로 변환하기 [2]
11269정성태8/17/201721504디버깅 기술: 93. windbg - 풀 덤프에서 .NET 스레드의 상태를 알아내는 방법
11268정성태8/14/201721095디버깅 기술: 92. windbg - C# Monitor Lock을 획득하고 있는 스레드 찾는 방법
11267정성태8/10/201725158.NET Framework: 672. 모노 개발 환경
11266정성태8/10/201724970.NET Framework: 671. C# 6.0 이상의 소스 코드를 Visual Studio 설치 없이 명령행에서 컴파일하는 방법
11265정성태8/10/201753202기타: 66. 도서: 시작하세요! C# 7.1 프로그래밍: 기본 문법부터 실전 예제까지 [11]
11264정성태8/9/201724139오류 유형: 414. UWP app을 signtool.exe로 서명 시 0x8007000b 오류 발생
11263정성태8/9/201719613오류 유형: 413. The C# project "..." is targeting ".NETFramework, Version=v4.0", which is not installed on this machine. [3]
11262정성태8/5/201718260오류 유형: 412. windbg - SOS does not support the current target architecture. [3]
11261정성태8/4/201720837디버깅 기술: 91. windbg - 풀 덤프 파일로부터 강력한 이름의 어셈블리 추출 후 사용하는 방법
11260정성태8/3/201718959.NET Framework: 670. C# - 실행 파일로부터 공개키를 추출하는 방법
11259정성태8/2/201718195.NET Framework: 669. 지연 서명된 어셈블리를 sn.exe -Vr 등록 없이 사용하는 방법
11258정성태8/1/201719031.NET Framework: 668. 지연 서명된 DLL과 서명된 DLL의 차이점파일 다운로드1
11257정성태7/31/201719182.NET Framework: 667. bypassTrustedAppStrongNames 옵션 설명파일 다운로드1
11256정성태7/25/201720664디버깅 기술: 90. windbg의 lm 명령으로 보이지 않는 .NET 4.0 ClassLibrary를 명시적으로 로드하는 방법 [1]
11255정성태7/18/201723223디버깅 기술: 89. Win32 Debug CRT Heap Internals의 0xBAADF00D 표시 재현 [1]파일 다운로드3
11254정성태7/17/201719603개발 환경 구성: 322. "Visual Studio Emulator for Android" 에뮬레이터를 "Android Studio"와 함께 쓰는 방법
11253정성태7/17/201719972Math: 21. "Coding the Matrix" 문제 2.5.1 풀이 [1]파일 다운로드1
11252정성태7/13/201718466오류 유형: 411. RTVS 또는 PTVS 실행 시 Could not load type 'Microsoft.VisualStudio.InteractiveWindow.Shell.IVsInteractiveWindowFactory2'
11251정성태7/13/201717179디버깅 기술: 88. windbg 분석 - webengine4.dll의 MgdExplicitFlush에서 발생한 System.AccessViolationException의 crash 문제 (2)
11250정성태7/13/201720735디버깅 기술: 87. windbg 분석 - webengine4.dll의 MgdExplicitFlush에서 발생한 System.AccessViolationException의 crash 문제 [1]
11249정성태7/12/201718557오류 유형: 410. LoadLibrary("[...].dll") failed - The specified procedure could not be found.
... [106]  107  108  109  110  111  112  113  114  115  116  117  118  119  120  ...