Windows 10: BSOD show the exact stop core error 0x00000027

Dear all,

there is a BSOD show the exact stop core error 0x00000027. Any idea or if there is solution. thank you.

Here is the memory dump analysis result.

MODULE_NAME: rdbss

FAULTING_MODULE: fffff80132400000 nt

FOLLOWUP_IP:
rdbss!RxReleaseFcbResourceInMRx+6238
fffff801`37737988 488b4870 mov rcx,qword ptr [rax+70h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: rdbss!RxReleaseFcbResourceInMRx+6238

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: rdbss.sys

STACK_COMMAND: .cxr 0xffff96009131ad70 ; kb

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


Regards,

KCKCKC

:)

 

BSOD - Registry Error

Your BSOD code is 0X000000051

Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

+1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

Run a Diskchk /R (I know you already ran one, so you can skip this)

Run SFC /SCANNOW

Report back.

 

True core and memory clock on my GFX...what should I trust?

i have the list of nvidia core and shader steppings if you like, it shows the requested clockspeed versus the effective clockspeed.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.