BSOD windows 8.1 copied and pasted dump file

[mjhui90]

Hi everyone my computer been crashing randomly for god knows how long... it might be a ram problem because I've done an amd platform swap to intel (full reformat) swapped everything but one stick of ram and a hard drive. The hard drive was once my primary but i reformatted it and it ended up being a storage because I got an SSD. Before I RMA anything I would like some feed back first. Thank you very much for your time!

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80141214000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 53fe6f2e

TRAP_FRAME: ffffd000206ef850 -- (.trap 0xffffd000206ef850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe000f30da958 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe000f1fb0158 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80141391e60 rsp=ffffd000206ef9e0 rbp=ffffd000206efae0
r8=0000000000000102 r9=0000000000000000 r10=fffff80141516f80
r11=0000007c89cde61e r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!CcTestControl+0x21b28:
fffff801`41391e60 cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffffd000206ef7a8 -- (.exr 0xffffd000206ef7a8)
ExceptionAddress: fffff80141391e60 (nt!CcTestControl+0x0000000000021b28)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff8014136ece9 to fffff801413631a0

STACK_TEXT:
ffffd000`206ef528 fffff801`4136ece9 : 00000000`00000139 00000000`00000003 ffffd000`206ef850 ffffd000`206ef7a8 : nt!KeBugCheckEx
ffffd000`206ef530 fffff801`4136f010 : 00000073`0000000a ef1be99f`eb4470cc ffffe000`ef5df6a0 00000000`00000002 : nt!setjmpex+0x37e9
ffffd000`206ef670 fffff801`4136e234 : fffffff6`00000002 fffff801`83f5e16c 00000004`00000005 00000000`40203e50 : nt!setjmpex+0x3b10
ffffd000`206ef850 fffff801`41391e60 : 00000000`00000002 00000000`0032c087 ffffd000`206c6180 ffffd000`206c6180 : nt!setjmpex+0x2d34
ffffd000`206ef9e0 fffff801`41366cea : ffffd000`206c6180 ffffd000`206c6180 ffffd000`206d22c0 ffffe000`efe7a880 : nt!CcTestControl+0x21b28
ffffd000`206efc60 00000000`00000000 : ffffd000`206f0000 ffffd000`206ea000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x2efa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!setjmpex+37e9
fffff801`4136ece9 90 nop

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!setjmpex+37e9

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

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

1: kd> lmvm nt
start end module name
fffff801`41214000 fffff801`419aa000 nt (export symbols) ntkrnlmp.exe
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Wed Aug 27 19:52:14 2014 (53FE6F2E)
CheckSum: 007311DE
ImageSize: 00796000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[WinOutreach2]

In order to analyze the dump files, you will need to provide a link to the uploaded .dmp files. The pasted text does not include any information because WinDbg did not have the proper symbol files to decode the file. You can enter !symfix in the console to resolve the symbol issues, then save the workspace, close WinDbg, and then reopen and open the dump file. You should see more detailed information provided (and not the symbol errors seen in this text). You can also run analyze -v (there will be a link to click to run it) which might be useful if only ntkrnlmp.exe is given as the faulting module.

 

[patrickIT]

step1; please run mdsched.exe to see if ram is the culprit.

step2; run cmd and then type chkdsk /f

step3; run cmd and then type verifier then from graphical user interface >>> Automatically select all drivers installed on this computer

download this tool to analyze BSOD http://www.resplendence.com/downloads download free edition of whocrashed the output this program gives you should be enough to solve your problem.

please answer to this topic I'm sure this issue will be resolved.