Windows crashes on startup only when powering on system

My guess is to set it as manual like you did, put it at 1.2 and change offset to 0.00

Have been reading through the thread and missed the last few posts.

First four settings:
8
8
8
25

Command Rate - CR to 2T

You are correct, change CPU/NB to Manual and 1.20v and offset back to 0.00.

CPU/NB voltage of 1.20v is a safe setting for your system, max should be 1.40v.
Is that the first red setting?

For now, just get the RAM settings changed.

The below information is for reference and should be looked at after the RAM settings are changed and tested.
They will likely need adjusting before we move on.

I will continue editing this post...

Thanks for the clarification essenbe, those are the timing settings that need changed.

You mentioned your BIOS is set to RAID, that is good. RAID actually uses AHCI and will have all of the benefits.

Do you still have the front case USB port cable unplugged from the motherboard?

From reading through the thread, there are a couple of questions.

MelancholyRose said:

Okay, well, I plugged the optical drive back in, and I got a BSOD while Windows was starting up.

STOP 1E
fltmgr.sys

Disconnect SATA and power cables for testing.

Stop 1E.
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a fairly general Stop code.

Stop 3B.
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Things in common with the other stop code are drivers and memory.
Did you get the graphics driver updated?

When the system has a crash and can't find the cause, it usually blames a kernal driver. These are rarely to blame it's just that the crash logs don't know what else to blame.
ntoskrnl is a kernal driver.

MelancholyRose said:

I've done that already. It found nothing wrong.

I tried disabling some non-Microsoft system services and powering on after shutting down and it still crashed every time. The dump files are all contained in this folder.

Since it will cleanly boot up the very first time if something else is booted before it, it makes me think there's something wrong with boot files, but the system doesn't find a single corrupted or missing file. I can't explain it.

I know that ntoskrnl pops up in a LOT of these, too.

From the last dump file in this post.
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check.
Again, driver, graphics card, memory are listed.

Error code 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002d8e945, The address that the exception occurred at
Arg3: fffff88003185a48, Exception Record Address
Arg4: fffff880031852a0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObpProcessRemoveObjectQueue+29
fffff800`02d8e945 488b7b08        mov     rdi,qword ptr [rbx+8]

EXCEPTION_RECORD:  fffff88003185a48 -- (.exr 0xfffff88003185a48)
ExceptionAddress: fffff80002d8e945 (nt!ObpProcessRemoveObjectQueue+0x0000000000000029)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000009
Attempt to read from address 0000000000000009

CONTEXT:  fffff880031852a0 -- (.cxr 0xfffff880031852a0)
rax=fffffa8006f3d2a0 rbx=0000000000000001 rcx=0000000000001d10
rdx=fffff880009aa000 rsi=fffffa8003c49b60 rdi=0000000000000000
rip=fffff80002d8e945 rsp=fffff88003185c80 rbp=0000000000000000
 r8=000000000000e880  r9=0000000000000080 r10=fffff80002a5d000
r11=00000000000005d0 r12=fffff80002c85180 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ObpProcessRemoveObjectQueue+0x29:
fffff800`02d8e945 488b7b08        mov     rdi,qword ptr [rbx+8] ds:002b:00000000`00000009=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000009

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0c100
 0000000000000009 

FOLLOWUP_IP: 
nt!ObpProcessRemoveObjectQueue+29
fffff800`02d8e945 488b7b08        mov     rdi,qword ptr [rbx+8]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff80002ae7021 to fffff80002d8e945

STACK_TEXT:  
fffff880`03185c80 fffff800`02ae7021 : fffff800`02d8e91c fffff800`02c7a260 fffffa80`03c49b00 00000000`00000003 : nt!ObpProcessRemoveObjectQueue+0x29
fffff880`03185cb0 fffff800`02d7932e : 00000000`00000000 fffffa80`03c49b60 00000000`00000080 fffffa80`03b54040 : nt!ExpWorkerThread+0x111
fffff880`03185d40 fffff800`02ace666 : fffff880`02f70180 fffffa80`03c49b60 fffff880`02f7afc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03185d80 00000000`00000000 : fffff880`03186000 fffff880`03180000 fffff880`031859e0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpProcessRemoveObjectQueue+29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

STACK_COMMAND:  .cxr 0xfffff880031852a0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!ObpProcessRemoveObjectQueue+29

BUCKET_ID:  X64_0x7E_nt!ObpProcessRemoveObjectQueue+29

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

If you haven't updated ahcix64s.sys, let me know what you have tried.
This driver was flagged, and should be updated.
The default MS AHCI driver is preferred by many for AMD boards, we might come back to this.

Post #59, crashes.
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Again Graphics card and RAM.


When running tests on your HDDs, use Western Digital Lifeguard – Quick Test and Extended Test.

That's good news and seems to be an improvement. Keeping my fingers crossed for you.

Can you confirm the BIOS settings?

Did you set the first four RAM timings to:
8
8
8
25

Command Rate - CR to 2T

CPU/NB to Manual and 1.20v and offset back to 0.00.

CPU/NB voltage of 1.20v is a safe setting for your system, max should be 1.40v.
Is that the first red setting?

All these settings are important, let us know exactly how you set them.

If it seems stable run memtest86+ for a full 8 passes, best to run overnight.
If you get any errors you can stop the test.

Let us know the results.

Well, I would like to think that no news is good news. I did uncross my fingers. It makes it hard to type, but my legs are crossed.