My pc keeps bsod

[techsaint]

Hello everyone,

 

i am new here so firstly i do apologize if this is not the right place. 
 

My computer keeps bsod. The backstory, a few months (October) ago my house was hit by lightning luckily only electronics were damaged. Of course my pc included. After getting it checked only the mobo and psu died. So i got them replaced and everything worked fine until a few weeks ago. 4 out of the 6 usb ports in the back of my mobo died i dont know the cause but yeah that happened and then my gen4 m.2 died. The speeds were extremely slow and it couldnt even load windows without causing a bsod. I removed it and reformatted my pc onto another ssd. After the fresh install of windows and installing all new drivers my keyboard and mouse started stuttering and the pc would still bsod randomly. 
 

i dont know if this was a good explanation but im willing to provide more details. 

 

I am not sure what caused it but i am assuming its the mobo or cpu but i have no way of confirming. 
 

The build:

Ryzen 7 5800x

MSI mortar b550

Ddr4 hyperx 3600 mhz

geforce gtx 1070

 

it was previously oc’d but after the reinstall it was just stock. 
 

 

thank you in advance 

[Hinjima]

2 minutes ago, techsaint said:

Hello everyone,

 

i am new here so firstly i do apologize if this is not the right place. 
 

My computer keeps bsod. The backstory, a few months (October) ago my house was hit by lightning luckily only electronics were damaged. Of course my pc included. After getting it checked only the mobo and psu died. So i got them replaced and everything worked fine until a few weeks ago. 4 out of the 6 usb ports in the back of my mobo died i dont know the cause but yeah that happened and then my gen4 m.2 died. The speeds were extremely slow and it couldnt even load windows without causing a bsod. I removed it and reformatted my pc onto another ssd. After the fresh install of windows and installing all new drivers my keyboard and mouse started stuttering and the pc would still bsod randomly. 
 

i dont know if this was a good explanation but im willing to provide more details. 

 

I am not sure what caused it but i am assuming its the mobo or cpu but i have no way of confirming. 
 

The build:

Ryzen 7 5800x

MSI mortar b550

Ddr4 hyperx 3600 mhz

geforce gtx 1070

 

it was previously oc’d but after the reinstall it was just stock. 
 

 

thank you in advance 

Download this program right here, it will log the files that caused the BSOD and give us more information to go from. BSOD has to happen for it to log. Also gives you some codes you can google yourself to see if anyone has fixed a similar issue.
https://www.nirsoft.net/utils/blue_screen_view.html

[techsaint]

Thank you I will do that!

[Hinjima]

7 minutes ago, techsaint said:

Thank you I will do that!

No problem. Let's try to figure this out!

[Radium_Angel]

Alternately, upload the minidump crash files here and I can deconstruct them and tell you what's going on

[Hinjima]

30 minutes ago, Radium_Angel said:

Alternately, upload the minidump crash files here and I can deconstruct them and tell you what's going on

I wish I had to knowledge to do that.

[Radium_Angel]

4 minutes ago, Hinjima said:

I wish I had to knowledge to do that.

https://www.technlg.net/windows/windows-crash-dump-memorydmp-file/

Only need the mini dump ones, if you have full crash dumps, they will be too big for here and would need to be uploaded to something like Google Drive

[techsaint]

Good Morning, I would love to do that but this morning turning on my pc i got into a bsod boot loop could even make it into windows now. 
 

i am assuming my windows corrupted from all the crashes. 
 

i did take pictures of the error codes as they changed everytime. 

[techsaint]

Good Morning, I would love to do that but this morning turning on my pc i got into a bsod boot loop could even make it into windows now. 
 

i am assuming my windows corrupted from all the crashes. 
 

i did take pictures of the error codes as they changed everytime. 
 

 

edit: windows tried to repair and got this message

[techsaint]

It is crazy because im getting different bsod every time. 
 

now i got memory_management bsod

[Radium_Angel]

On 3/19/2023 at 4:33 AM, techsaint said:

It is crazy because im getting different bsod every time. 
 

now i got memory_management bsod

Different errors are a dead giveaway your RAM is bad.

Test with MemTestx86

 

Also, return your BIOS to stock, turn off XMP or DOCP.

 

[techsaint]

032123-254406-01.dmp032123-14812-01.dmp032123-12609-01.dmp

[techsaint]

On 3/19/2023 at 1:33 AM, Radium_Angel said:

https://www.technlg.net/windows/windows-crash-dump-memorydmp-file/

Only need the mini dump ones, if you have full crash dumps, they will be too big for here and would need to be uploaded to something like Google Drive

Above ihave linked the mini dump files sorry it took so long it has been a major pain

[techsaint]

On 3/20/2023 at 2:30 PM, Radium_Angel said:

Different errors are a dead giveaway your RAM is bad.

Test with MemTestx86

 

Also, return your BIOS to stock, turn off XMP or DOCP.

 

turned off all XMP still getting the same issues

[Radium_Angel]

15 minutes ago, techsaint said:

Above ihave linked the mini dump files sorry it took so long it has been a major pain

No worries, I can't access them at work, will have to wait until I get home

[techsaint]

Thank you!

[techsaint]

On 3/21/2023 at 7:51 PM, Radium_Angel said:

No worries, I can't access them at work, will have to wait until I get home

Hey Radium,

 

did you get a chance to look into the files? 
 

 

[Radium_Angel]

35 minutes ago, techsaint said:

Hey Radium,

 

did you get a chance to look into the files? 
 

 

Ummm...ahhh...errr...why yes, totally I really just (did not) download the files and look them over 

Many apologies for the delay, give me a few to look them over, and I'll post my thoughts.

 

Hold Please!

[Radium_Angel]

Ok, I'm going to post the relevant parts of the BSoDs here, and my thoughts below that.

 

Crash #1

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: fffff8025269c18f, The address that the exception occurred at
Arg3: ffffa90da125f5a8, Exception Record Address
Arg4: ffffa90da125edc0, Context Record Address
 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System
ExceptionCode: c0000005 (Access violation)

____

Crash #2

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8000e09c18f, Address of the instruction which caused the BugCheck
Arg3: fffffc0f983067b0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
PROCESS_NAME:  WerFault.exe

SYMBOL_NAME:  nt!MiFinishVadDeletion+4f4

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.1344

STACK_COMMAND:  .cxr 0xfffffc0f983067b0 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  4f4

FAILURE_BUCKET_ID:  AV_nt!MiFinishVadDeletion

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a2df16c8-e5b6-769c-9909-e3d909490283}
___

Crash #3

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.

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steam.exe

SYMBOL_NAME:  nt!MmEnumerateAddressSpaceAndReferenceImages+206

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.1344

STACK_COMMAND:  .cxr 0xffffa084dff3e840 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  206

FAILURE_BUCKET_ID:  AV_nt!MmEnumerateAddressSpaceAndReferenceImages

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3158f380-acfe-21f7-ef14-eca155652c23}
_______

 

I'm seeing random processes crash, and random BSoD reasons. To me this screams "bad hardware" (or a really fouled up OverClocking/XMP/OS install. I used to say BSoDs were impossible without failing hardware, but Windows 10 and 11 have forced me to re-consider this, as the code base is no longer stable enough IMO, to limit BSoDs to hardware only.)

 

So, if you've done a FRESH install of Windows 10/11, AND your BIOS is set to bone stock, and it's still doing this, I'd say you still have bad hardware someplace....likely the RAM.

 

 

 

[techsaint]

For the driver part is there anything i can do to uninstall all drivers and reinstall them (noting i have fresh reinstalled windows multiple times) 

 

for the ram i will just talk to my brother in law and ask for his ram just to test and see if the crashing still happens with his ram. It could be that both my sticks of ram are bad. 
 

i will keep you updated but im a little lost  

 

thank you for your time and help it does mean alot!

[techsaint]

Swapped out the ram and still seem to have the same issue. 
 

going to take my BILs pc on sunday and just start swapping parts out to find the problem. 
 

thank you again for your time and your assistance everyone