Need help analyzing dump file and solving BSODs :)

macmiller97

Reputable
Jan 24, 2016
3
0
4,510
I have had almost daily blue screens lately. Usually on startup or when returning from sleep mode. I tried to analyze one of the dmp files but I am not an expert. I used WinDbg and eventually got the following information. If anyone knows how to analyze this kind of message it would be greatly appreciated:??:.


UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff802b4bb7e70
Arg3: 00000000b4bae847
Arg4: fffff8002c349312

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: GE72 2QD

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: REV:1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: E1792IMS.113

BIOS_DATE: 07/17/2015

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: MS-1792

BASEBOARD_VERSION: REV:0.B

DUMP_TYPE: 2

BUGCHECK_P1: 8

BUGCHECK_P2: fffff802b4bb7e70

BUGCHECK_P3: b4bae847

BUGCHECK_P4: fffff8002c349312

BUGCHECK_STR: 0x7f_8

TRAP_FRAME: fffff802b4bb7e70 -- (.trap 0xfffff802b4bb7e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000108 rbx=0000000000000000 rcx=ffffe0013ba98190
rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8002c349312 rsp=00000000b4bae847 rbp=0000000000000000
r8=0000000000000002 r9=0000000000000001 r10=0000000000000038
r11=fffff802b4bae8e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
Wdf01000!FxObject::DisposeChildrenWorker+0x102:
fffff800`2c349312 cc int 3
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: a86

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 47

CPU_STEPPING: 1

CPU_MICROCODE: 6,47,1,0 (F,M,S,R) SIG: D'00000000 (cache) D'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: SEXY

ANALYSIS_SESSION_TIME: 03-18-2016 12:00:00.0606

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

BAD_STACK_POINTER: 00000000b4bae847

UNALIGNED_STACK_POINTER: 00000000b4bae847

LAST_CONTROL_TRANSFER: from fffff802b2b6c2e9 to fffff802b2b61760

STACK_TEXT:
fffff802`b4bb7d28 fffff802`b2b6c2e9 : 00000000`0000007f 00000000`00000008 fffff802`b4bb7e70 00000000`b4bae847 : nt!KeBugCheckEx
fffff802`b4bb7d30 fffff802`b2b6a373 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff802`b4bb7e70 fffff800`2c349312 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb3
00000000`b4bae847 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxObject::DisposeChildrenWorker+0x102


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 8c12304084188e945be728d262a38d41088992be

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7af19be548464fe0d2b8e81ab23039fbaa99c043

THREAD_SHA1_HASH_MOD: aa11e928c8cd33bcadf3b52b3e271a069b218f8b

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b3
fffff802`b2b6a373 90 nop

FAULT_INSTR_CODE: 6666c390

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 56cd4410

IMAGE_VERSION: 10.0.10586.162

BUCKET_ID_FUNC_OFFSET: b3

FAILURE_BUCKET_ID: 0x7f_8_STACKPTR_ERROR_nt!KiDoubleFaultAbort

BUCKET_ID: 0x7f_8_STACKPTR_ERROR_nt!KiDoubleFaultAbort

PRIMARY_PROBLEM_CLASS: 0x7f_8_STACKPTR_ERROR_nt!KiDoubleFaultAbort

TARGET_TIME: 2016-03-18T16:41:57.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-02-23 21:48:00

BUILDDATESTAMP_STR: 160223-1728

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728

ANALYSIS_SESSION_ELAPSED_TIME: 20b61

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7f_8_stackptr_error_nt!kidoublefaultabort

FAILURE_ID_HASH: {c5b9990d-856b-1bb5-7662-4621e5941c84}

Followup: MachineOwner
---------

0: kd> !analyze -v
 
Solution
The first thing you'll need to do is disable automatic device driver updates, update your BIOS, update the device drivers and also make sure you've installed the latest version of your killer drivers or disable it in BIOS if you're not using the onboard Ethernet port.

That being said, which SKU do you have? I've seeing Nvidia GPU drivers across the board and you are ending up with AMD related errors in your post. Use this guide to reinstall your GPU drivers after you've downloaded the latest drivers from Nvidia.

Lutfij

Titan
Moderator
The first thing you'll need to do is disable automatic device driver updates, update your BIOS, update the device drivers and also make sure you've installed the latest version of your killer drivers or disable it in BIOS if you're not using the onboard Ethernet port.

That being said, which SKU do you have? I've seeing Nvidia GPU drivers across the board and you are ending up with AMD related errors in your post. Use this guide to reinstall your GPU drivers after you've downloaded the latest drivers from Nvidia.
 
Solution