Please Help ME!!!!!! I'm Lost At This Point

[Sm0keyDank420]

Hi there I have been hit with a crazy amount of BSODs loads of different ones I have some minidump files that I will attach if anyone can read them and understand it. I have a Asus Strix X570-E Gaming Wifi 2, Ryzen 9 5950x running stock, RTX 3090 FE, and 128GB of Trident Z Royal 3600mhz CL16 (I know its excessive, I know), I kept getting Drdebug error code 0D and the DRAM light showing up on my motherboard so I think it may have faulty DIMM slots as I've had to reseat and keep juggling them around the slots to make it work so I'm currently resorted to just running one stick at the second but I'm still getting BSODs but at least it boots atm. Any help would be much appreciated and if you need any information please ask and I will provide it!! I'm now going to do a memtest86 to double check the memory modules. I am on Windows 10 64 bit 22H2 19045.2311. Bios version says 2.20 when I'm in bios but in system information it says American Megatrends Inc. 4204, 24/02/2022.

113022-20531-01.dmp 113022-16859-01.dmp 113022-17906-01.dmp 113022-19687-01.dmp

[Radium_Angel]

Welcome to the forums. I'm at lunch right now, but when I get back to my office, I'll dig throughthe minidumps and tell you what I think is going on.

Hold tight new friend, help is on the way

 

(and run memtest on ALL of the sticks...not just one)

[Radium_Angel]

Ok, I'm going to post the relevant parts from each crash, and my thoughts at the end.

____

(crash #1)
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000404, The subtype of the bugcheck.
Arg2: ffffb6c01fe4acd8
Arg3: 8a000001d85a3863
Arg4: ffffb6c01f13acd8
 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  explorer.exe
 

SYMBOL_NAME:  nt!ExFreePool+9

IMAGE_NAME:  Pool_Corruption

IMAGE_VERSION:  10.0.19041.2311

MODULE_NAME: Pool_Corruption

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  9

FAILURE_BUCKET_ID:  0x1a_404_nt!ExFreePool

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ee7709a7-151f-37cf-a577-8f1db6a6b369}

Followup:     Pool_corruption
___

(crash #2)

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8040fe5bdae, address which referenced memory
 

BUGCHECK_CODE:  a

BUGCHECK_P1: 8

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8040fe5bdae
 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2311

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  e

FAILURE_BUCKET_ID:  AV_nt!KxWaitForLockOwnerShip

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {724b07b1-4226-85fe-f372-16d33b9a3b93}

___

(crash #3)

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000148a636720, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff805340886b3, address which referenced memory
 

BUGCHECK_CODE:  a

BUGCHECK_P1: 148a636720

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff805340886b3
 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

SYMBOL_NAME:  nt!MiRestoreTransitionPte+2c3

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.2311

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  2c3

FAILURE_BUCKET_ID:  AV_nt!MiRestoreTransitionPte

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {37d4886d-fd49-86e8-3405-f2978c32f33e}
___

(crash #4)

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8058aaa27e7, The address that the exception occurred at
Arg3: ffffd08ff72a3080, Parameter 0 of the exception
Arg4: fffff8058b279590, Parameter 1 of the exception

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ArmouryCrate.Service.exe

BAD_STACK_POINTER:  ffffbe00da05a158

FAILED_INSTRUCTION_ADDRESS: 
nvlddmkm+1e27e7
 

SYMBOL_NAME:  nvlddmkm+1e27e7

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1e27e7

FAILURE_BUCKET_ID:  0x1E_c000001d_STACKPTR_ERROR_BAD_IP_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10
____

 

Ok, the first 3 crashs scream bad RAM (or XMP issues, or an OverClock gone wrong)

But the last one is different...refers to nVidia driver crashing on Armoury Crate Service (unsure what that is)

 

It might be related to the 1st 3 issues, so let's start with a FULL set of RAM being tested with Memtest. 

Report back on what MT says, we can go from there

[porina]

I'd guess your CPU's memory controller probably can't handle that ram at that speed (on that mobo). If you run the ram slower, does the BSODs go away?

[Sm0keyDank420]

Hi there thanks for such a speedy reply !! I'll stick all the memory in quickly and see what it says, just found a usb so will do it now

 

[Sm0keyDank420]

1 minute ago, porina said:

I'd guess your CPU's memory controller probably can't handle that ram at that speed (on that mobo). If you run the ram slower, does the BSODs go away?

This is how I originally got around it but after time this solution just stopped working 

 

[Sm0keyDank420]

it is memtest86 that I want right?

[-rascal-]

6 minutes ago, Sm0keyDank420 said:

it is memtest86 that I want right?

 

Yes, but you will need to let is run multiple complete passes.

With all 128GB of RAM, it can take hours...or overnight to complete.

 

I was also thinking 128GB of RAM, running at DDR4-3600 would be too much for the Integrated Memory Controller (IMC) to handle.

However, I don't think we can quite pin-point what the cause of the problem is at the moment; Motherboard, RAM, or CPU (since the IMC is inside the CPU) just yet.

Speaking of, do you have a spare kit of DDR4 RAM you can test in the system?

[Sm0keyDank420]

Just realised I don't think I'll be able to run a full ram test as I don't think it can even post to bios when it gets the error code 0d once upon a time i did get this working with all ram sticks near the start and all the memory showed up it just took a lot of reseating but like I say this was near the start when I bought it a year ago I will try to full populate it and get a test going and if I can I will post the results. I'm currently just running a test on the single stick ive been using. If I can't get all sticks to post I'll just have to the run the test one stick at a time and swap out I guess. I don't have an other ram but at this point I might just buy 64gb 2x32gb of trident neo just to test with 

[Sm0keyDank420]

By multiple complete passes do you mean just running the test multiple times ?? Is there a way at the start of the test to set this up or ?? Sorry for being a noob with this thank you for all your help 

[Radium_Angel]

54 minutes ago, Sm0keyDank420 said:

By multiple complete passes do you mean just running the test multiple times ?? Is there a way at the start of the test to set this up or ?? Sorry for being a noob with this thank you for all your help 

It'll run one full test, tell you "complete" or "errors" and continue to run until you stop it.

If you get errors, you can stop immediately, that stick is bad.

If it competes 1 pass, let it continue to run until 2 more are done.

[Sm0keyDank420]

I've got 20 errors on the run with just the 1 stick in

[Sm0keyDank420]

Could this not also mean faulty slot or no?

[Sm0keyDank420]

Okay update I Just cancelled the test on the single stick after 253 errors here's what I got on that, I've also bought new ram which should be coming in 2 days which I can use to test. I'll attach a screenshot of this as well this ram is on the qvl hopefully I've made the right choice this time jeez haha 

[Radium_Angel]

3 hours ago, Sm0keyDank420 said:

I've got 20 errors on the run with just the 1 stick in

 

3 hours ago, Sm0keyDank420 said:

Could this not also mean faulty slot or no?

A faulty slot IS a possibility, but unless you've been fiddling about with voltages and RAM timings...it's unlikely.

All the same, I'd be testing the rest of your RAM (in the same slot you started with) just to see. If they are ALL faulty...then perhaps it IS your RAM slot, but more testing will be required to determine this

[Sm0keyDank420]

I tried another ram stick and couldn't get it working except for this one slot so tried it in there with two sticks and got like 700 errors then it froze so I shut it down

[-rascal-]

1 hour ago, Sm0keyDank420 said:

I tried another ram stick and couldn't get it working except for this one slot so tried it in there with two sticks and got like 700 errors then it froze so I shut it down

 

So we still need to rule out either bad Memory kit, or bad CPU / Motherboard.

However, I am thinking it may be a bad CPU IMC / Motherboard at this point.

[Sm0keyDank420]

I tested the ram in another machine and I'm almost certain it's just these ram sticks tbf I ran memtest86 on my friends pc and still got errors I then put his ram back into his pc, ran memtest86 on them and no error occurred.

[Sm0keyDank420]

Just tried the new ram sticks and still getting drdebug error code 0d definitely DIMM slots or CPU at this point this is costing me so much I could have just built a new AM5 platform build at this point ahhh

[Sm0keyDank420]

Thought I'd slide an update in here so I reseated the cpu and components and managed to get it to boot and so far it's been running for about a week on and off. Just wanted to say thank you so much everyone for your help will definitely be using the forum again you guys were great!! After days of online tutorials and copying command line and disk part commands etc finally got my ssd converted to gpt, Windows 11 loaded and resizeable bar enabled. Just gotta rip apart the 3090FE and replace the thermal pads and repaste the gpu die as the memory temps are hitting 108/110°C wish me luck first time doing it to a gpu wish I didn't have to haha. 

[Sm0keyDank420]

Another update so I upgraded to Windows 11 I keep getting a variety of errors/ BSODs IRQL equal not equal, DCP Watchdog violation, , Memory Management BSOD's,I installed a program and it caused errors so I deleted it reinstalled windows 11 while keeping files (this took ages as I tried to do it from an image with dism but could figure out the sourcing command and kept getting failed at OS Phase Boot Operation and the installion media tool wasn't working),I eventually had to restore it by the reset pc function after doing this it then let me restore from the windows 11 media, did all the windows updates and driver updates again, I have ran SFC /scannow and fixed errors, I then ran /online /scanhealth and then /online /cleanup-image /restore health commands but am still getting random occuring BSOD's. I also ran windows memory diagnostics tool and didn't see an errors when looking but didn't see the end of the operation. I will include the minidump files and the memory diagnostics files. I ran CHKDSK and fixed any errors there on the C: drive I'm now running it on my 4TB SSHD as I'm unsure whether that's finally on the way out I had a look at the smart information but didn't have a clue how to read it  , In device manager the only conflicting driver is the blue microphone one but I have a Yeti Pro which the drivers have disappeared off their website, I have contacted the support but are awaiting to hear back to try get a download link for the drivers. Any help would be much appreciated this has been an ongoing struggle and battle but I refuse to give up it's so close xD.

011123-13031-01.dmp 011123-13062-01.dmp 011123-13078-01.dmp 011123-13187-01.dmp 011223-19484-01.dmp

[Radium_Angel]

54 minutes ago, Sm0keyDank420 said:

I also ran windows memory diagnostics tool

That is worthless. Only MemTest will tell you the real story.

AS it stands, I'll look over the crashdumps and let you know what I have found.

[Radium_Angel]

Downloads are blocked at work, and from home I"m getting a "SSL error" on the download link, which I think is a known issue here. I'll try again over the weekend

[Sm0keyDank420]

Okay thank you for getting back to me, I was gonna attach the completed chkdsk for the d drive but my computer has frozen up at the moment, I will upload it when I can. File explorer seems to be a prolific issue and locks up and freezes quite a bit

[Sm0keyDank420]

If you need me to respond them another way like wetransfer just let me know and I can