View Single Post
  #2  
Old August 9th, 2015, 06:37 AM
Meghiddo Meghiddo is offline
Senior Member
 
Join Date: Oct 2007
O/S: Windows 7 64-bit
Location: Austin , Texas
Age: 41
Posts: 243
I have installed the WinDbg tool and downloaded symbols, and updated my system to create a Kernel dump file as well the next time this happens, so hopefully I can have more useful info.
So far I have been re-downloading the game for 25 or so minutes, and no crash thus far. The only difference between the last crash and now is that in that time is when I unplugged my bad hard drive.

I ran WinDbg on the minidump file, here is the brief analysis:

BugCheck 7F, {8, 80050031, 6f8, fffff80003accd01}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner


And here is a fuller log:

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: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80003accd01

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


SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: System Version

BIOS_DATE: 03/08/2011

BASEBOARD_PRODUCT: M4A89TD PRO USB3

BASEBOARD_VERSION: Rev 1.xx

BUGCHECK_P1: 8

BUGCHECK_P2: 80050031

BUGCHECK_P3: 6f8

BUGCHECK_P4: fffff80003accd01

BUGCHECK_STR: 0x7f_8

TRAP_FRAME: 0000000000000000 -- (.trap 0x0)

CPU_COUNT: 6

CPU_MHZ: c8a

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 10

CPU_MODEL: a

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: rift.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LAST_CONTROL_TRANSFER: from fffff80003acce69 to fffff80003acd8c0

STACK_TEXT:
fffff880`0328ed68 fffff800`03acce69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`0328ed70 fffff800`03acb332 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0328eeb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`03acb332 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 556356e8

IMAGE_VERSION: 6.1.7601.18869

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

PRIMARY_PROBLEM_CLASS: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x7f_8_nt!kidoublefaultabort+b2

FAILURE_ID_HASH: {0367acc4-9bb4-ab69-5701-46a2011718e9}

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



I see "PROCESS_NAME: rift.exe", but now I am not sure what I can do with this info...

Last edited by Meghiddo; August 9th, 2015 at 06:43 AM.
Reply With Quote