Windows 10: constant BSOD unless in safe mode -- with dump file info

Hi,


i've removed both my graphics cards from the machine, alternated my two ram sticks (still should probably test with brand new ram), swapped the sole drive with another known working drive, unplugged all peripherals. and consistently get a BSOD (green) about a minute after startup. haven't crashed yet in safe mode. crash in safe mode with networking. I've updated MB firmware to latest, as well as Intelchipset, IntelRst, IntelLan and Realtek_wifi.




I have a ton of different dump files -- here's one below:


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: ffffc301e850ffd0
Arg3: fffdf08b188572e0
Arg4: fffff8013e0fd226

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1002

BIOS_DATE: 07/02/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: ROG STRIX Z370-G GAMING (WI-FI AC)

BASEBOARD_VERSION: Rev X.0x

DUMP_TYPE: 2

BUGCHECK_P1: 8

BUGCHECK_P2: ffffc301e850ffd0

BUGCHECK_P3: fffdf08b188572e0

BUGCHECK_P4: fffff8013e0fd226

BUGCHECK_STR: 0x7f_8

TRAP_FRAME: ffffc301e850ffd0 -- (.trap 0xffffc301e850ffd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8013dec8be0 rbx=0000000000000000 rcx=0000000000000001
rdx=ffff9e80e3d8e090 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8013e0fd226 rsp=fffdf08b188572e0 rbp=fffdf08b18857330
r8=0000000000000001 r9=0000000000000001 r10=0000000000000028
r11=fffff8013e00e7cf r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!EtwpLogContextSwapEvent+0xce:
fffff801`3e0fd226 e8a55cf0ff call nt!guard_dispatch_icall (fffff801`3e002ed0)
Resetting default scope

CPU_COUNT: 6

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 96'00000000 (cache) 96'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP

ANALYSIS_SESSION_TIME: 08-22-2018 19:17:12.0057

ANALYSIS_VERSION: 10.0.17134.12 amd64fre

LAST_CONTROL_TRANSFER: from fffff8013e00d529 to fffff8013dffa430

STACK_TEXT:
ffffc301`e850fe88 fffff801`3e00d529 : 00000000`0000007f 00000000`00000008 ffffc301`e850ffd0 fffdf08b`188572e0 : nt!KeBugCheckEx
ffffc301`e850fe90 fffff801`3e007d4f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffc301`e850ffd0 fffff801`3e0fd226 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x38f
fffdf08b`188572e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!EtwpLogContextSwapEvent+0xce


THREAD_SHA1_HASH_MOD_FUNC: 4c9f445e9f658ba401cf1fc5027a275e8b9fbe7d

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9ff572e3861dbc7bfebba7110e4336eb887e5f68

THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+38f
fffff801`3e007d4f 90 nop

FAULT_INSTR_CODE: 6666c390

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+38f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5a7e7659

IMAGE_VERSION: 10.0.16299.248

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 38f

FAILURE_BUCKET_ID: 0x7f_8_VRF_nt!KiDoubleFaultAbort

BUCKET_ID: 0x7f_8_VRF_nt!KiDoubleFaultAbort

PRIMARY_PROBLEM_CLASS: 0x7f_8_VRF_nt!KiDoubleFaultAbort

TARGET_TIME: 2018-08-22T22:40:46.000Z

OSBUILD: 16299

OSSERVICEPACK: 248

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-02-09 23:34:33

BUILDDATESTAMP_STR: 170928-1534

BUILDLAB_STR: rs3_release

BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534

ANALYSIS_SESSION_ELAPSED_TIME: 1b4a

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7f_8_vrf_nt!kidoublefaultabort

FAILURE_ID_HASH: {2575f830-7dd8-52d7-e1be-20f8274db764}

Followup: MachineOwner

:)

 

Password not accepted in Safe mode

Hi,

Thank you for posting your query on Microsoft Community forum.

Have you tried all the above steps suggested by Sangeeta Sarkar on September 13, 2015.

I would suggest you to provide some information to help you better.

• Are you trying to login the Microsoft account or the Local account in safe mode?
• Did you try with only safe mode or safe mode with networking?
• What is the critical error you are getting?

If you are using Windows 10. To go to safe mode you have to follow the below steps.

If you are able to go to login screen in normal mode try the below steps to go to safe mode with networking.

• 
  At the login screen click on the power symbol.
  
• 
  Hold SHIFT + Click Restart.
  
• 
  After restarting your system, select the Troubleshoot option.
  
• 
  Select advanced options under
  Troubleshoot screen.
  
• 
  Click on Startup Settings.
  
• 
  Click Restart and follow the onscreen steps to go to
  Safe Mode with networking and check if you are able to login.
  

[*]

Please get back with more information, we will be glad to help you further.

 

BSOD dump analysis request

Hi,

Thank you for posting your query in Microsoft Community.

I can understand how frustrating it could be when things go unusual.

I will certainly help you.

Please provide us the following details:

• 
  Have you made any changes to the computer prior to this issue?
  
• 
  When exactly you get these errors?
  

A blue screen error (also called a stop error) can occur if a problem causes your PC to shut down or restart unexpectedly.

The BAD_POOL_HEADER bug check has a value of 0x00000019.

The issue occurs because the Hdaudio.sys driver tries to process the audio information when the uninitialized internal firmware memory within the video card is set in a certain manner. The result is internal pool corruption.

As we are analyzing the dump files, let us try the following steps as a workaround and check if it makes any difference.

Step 1: Initially, I suggest you to start your computer in safe mode with Networking and check if the issue appears there as well. If it does not appear in safe mode with Networking place the computer in clean
boot state to identify the culprit program running in the background creating this error.

Safe Mode is a diagnostic mode that starts your computer in a limited state. Only the basic files and drivers necessary to run Windows are started.

Refer the article below:

Start your PC in safe mode in Windows 10

http://windows.microsoft.com/en-in/windows-10/start-your-pc-in-safe-mode

Step 2: Let us follow the steps suggested in the following article and check if it helps in resolving the issue.

Troubleshoot blue screen errors

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Hope it helps.

Let us know the status, we are glad to assist you further.

 

Help with BSOD, Dump files and system info attached.

Hi,

There are many factors that could cause BSOD on your
PC. Since you have the Dump File, we could give you the procedures on how to find and upload the files we need so that we'll be able to help you repair your PC. To find and fix BSOD, kindly follow the steps indicated in this

link. Useful knowledge regarding BSODs are also indicated on that link.

Let us know how things goes with your issue.

Regard.s