Windows 10: Consistent BSOD after Fresh windows install

Hello,I was having issues with my PC and have done multiple fresh installs on windows. Motherboard gave out so I switched Mobos. Have PBO -30 and EXPO 6000mhz on. Had memory errors in previous mobo and didn't have any in the initial install. Will test again. On windows 10. Temperatures are fine!Does the minidump show anything?Thanks!PC Part list https://pcpartpicker.com/list/BDvZLcEvent ViewerThe computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e 0xffffffffc0000005, 0xfffff8043181fed4, 0x0000000000000000,&

:)

 

windows xp installation and dual core am

could someone please list the steps they follow to install windows with a dual core processor and windows xp service pack to. I'm reletively new to amd dual core and i feel i'm missing a step. All help will be appreciated. thanx

 

BSODs, even after fresh windows install

I will try the solutions you suggested, however when you say "log files" are you referring to the minidumps or the list of issues and BSODs I wrote? If its the list I wrote then all of those issues also occur without compiling/using rust, it is simply a way I've found to reliably check if I have solved the issues since so far I have had 100% consistency with being unable to compile. Otherwise after each step I would have to wait a few minutes to a few hours for a random BSOD or other issue to occur.

I also have another suspicion that the issue lies with one or more individual CPU cores, I will be running memtest86 on each core individually to see if there is a observed difference.

Any and all troubleshooting tips are highly appreciated.

 

Consistent BSOD, even on fresh install of Windows.

This might be a little lengthy, so sorry in advance.

I recently upgraded all of the hardware in my computer except for my hard drives, and pretty much couldn't run anything on it without a BSOD.

Ultimately, I decided to do a fresh install of Windows, and that worked for a couple of days; but now, I got another BSOD. I was able to run a couple of games without program crashes previously, but today, I have had games crash multiple times, followed by this BSOD the last time a game crashed.

This (in my admittedly uneducated and frustrated opinion, so I could certainly be wrong) seems to indicate a hardware issue, and I'm trying to figure out what's faulty- but it could also be a Driver issue, and if that's the case, I'm not sure how a faulty driver keeps making it's way onto my computer.

But perhaps more importantly, in Reliability History, the critical event IS summarized as a hardware error.

I went into Device Manager and found a Display Adapter listed as PCI\VEN_1002&DEV_164E&SUBSYS_D0001458&REV_C2. I went ahead and disabled it since I definitely didn't download it and Windows seems to believe it's the source of the error, but I would like to know where it came from. Is it some kind of driver that's being downloaded by a hardware component?

I went ahead and downloaded WinDbg to try and glean any information from the dump file created by the BSOD, to discover that the Owner is listed as "Unable to display current owner."

I'm the ONLY user on this computer, so this is strange, and as far as I can tell, it won't even let me do anything in the advanced security settings to make it viewable.

So, to summarize my issue; I'm having consistent crashes (BSOD) that are tied to something, and I'm officially clueless as to what even do at this point.

If anyone can help me, I would really appreciate it. I'm nearing the brief window of time that I can mark any of the hardware components as defective, and I would really like to attempt and resolve this issue before I just have to mark everything as defective and start from scratch. (With any luck, I would prefer this be something software or driver related, but I've tried everything I can think of if it were.)

I'll also list the Description, Problem signature, and Extra information about the problem provided by Windows below.

Description

A problem with your hardware caused Windows to stop working correctly.

Problem signature

Problem Event Name: LiveKernelEvent

Code: 1b0

Parameter 1: 2

Parameter 2: ffffffffc0000001

Parameter 3: 100

Parameter 4: fffff805d7a0a684

OS version: 10_0_19045

Service Pack: 0_0

Product: 768_1

OS Version: 10.0.19045.2.0.0.768.101

Locale ID: 1033

Extra information about the problem

Bucket ID: LKD_0x1B0_DxgkrnlLiveDump:804_Status_0xC0000001_Driver_amdkmdag_failed_DdiStartDevice_AMD_StartDeviceDiag_dxgkrnl!DxgCreateLiveDumpWithDriverBlob