bsod при подключении отладчика
От: skeptic  
Дата: 06.08.14 18:58
Оценка:
Всем привет!

Ситуация следующая — есть window 8.1 и virtual box 4.3.12 в которой крутиться windows server 2012 r2.
При попытке поднять виртуалку под отладчиком ( WinDBG 6.3.9600.17237 AMD64) виртуалка падает в bsod.
Судя по всему, виной всему VBox, но всё таки интересно, сталкивался ли кто нибудь с подобным?
Раньше всё нормально работало (до win8/server 2012r2).
Ниже инфа об ошибке:

....
Windows 8 Kernel Version 9600 MP (1 procs) Free x64
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
....
IOINIT: Built-in driver \Driver\sacdrv failed to initialize with status — 0xC0000037
KDTARGET: Refreshing KD connection
*** Fatal System Error: 0x00000124
(0x0000000000000003,0x0000000000000000,0x0000000000000000,0x0000000000000000)
....
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000003, Non-maskable Interrupt
Arg2: 0000000000000000, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:
ffffd000`8f1c3758 fffff803`fb5f3a46 : 00000000`00000000 00000000`00000000 ffffd000`8f1c38c0 fffff803`fb4608cc : nt!DbgBreakPointWithStatus
ffffd000`8f1c3760 fffff803`fb5f3357 : 00000000`00000003 00000000`00000003 fffff803`fb577f80 00000000`00000124 : nt!KiBugCheckDebugBreak+0x12
ffffd000`8f1c37c0 fffff803`fb56a0a4 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheck2+0x8ab
ffffd000`8f1c3ed0 fffff803`fb5d68c5 : 00000000`00000124 00000000`00000003 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx+0x104
ffffd000`8f1c3f10 fffff803`fbbd6fad : ffffd000`8f1c4130 ffffd000`8f1c4130 00000000`00000001 00000000`00000000 : nt!WheaReportHwError+0x2cd
ffffd000`8f1c3f70 fffff803`fb5f709c : ffffd000`8f1c4130 00000000`00000001 00000000`00000000 fffff803`fb5f819b : hal!HalHandleNMI+0xfe
ffffd000`8f1c3fa0 fffff803`fb5734c2 : 00000000`00000000 ffffd000`8f1c41b0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x150
ffffd000`8f1c3ff0 fffff803`fb573336 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffd000`8f1c4130 fffff803`fb56b772 : 00000052`5cfabcb1 ffffd000`8f1b8180 00000000`00000000 00000000`00000002 : nt!KiNmiInterrupt+0x176
ffffd000`8f1e1ab0 fffff803`fbbba7ef : fffff803`fb4cc2da 00390032`0039002d 00630034`00610039 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x82
ffffd000`8f1e1c48 fffff803`fb4cc2da : 00390032`0039002d 00630034`00610039 00000000`00000000 00000000`00000000 : hal!HalProcessorIdle+0xf
ffffd000`8f1e1c50 fffff803`fb56dabc : ffffd000`8f1b8180 ffffd000`8f1b8180 00000000`00000000 00000052`5cfabcb1 : nt!PoIdle+0x3ca
ffffd000`8f1e1da0 00000000`00000000 : ffffd000`8f1e2000 ffffd000`8f1dc000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: _NOERRREC

BUCKET_ID: _NOERRREC

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:_noerrrec

FAILURE_ID_HASH: {971b1c44-6671-1d2a-bc8e-a0f6a11a5e3d}

Followup: MachineOwner
---------
 
Подождите ...
Wait...
Пока на собственное сообщение не было ответов, его можно удалить.