My gaming pc has never been stable for the past 2 years

[aBigGoofyGamer]

I've been a pc gamer for 2 years and honestly, it's been a 50/50 experience. Half the older games id play on my Xbox don't run in any capacity on my pc (batman arkham city) and other games crash to the point of me finding them unplayable. (witcher series). Sometimes my hardware will just give up(oculus rift s and ram...) The good expirences I've had on my computer are unfortunately few and far between. It's causing me and my family untold amounts of anguish. I don't know what to do anymore. I've tried repair places, to the point of being a regular at a few of them, and nothing. They say it's fixed or that there isn't any issues only for my pc to ♥♥♥♥ up again a few days later. I don't know what to do anymore...

http://speccy.piriform.com/results/OhXlA7hXRRPigfrXzAXEYrR Here are my specs.

[Carlsberg]

Is that cpu overclocked? it should be on a 37 multiplier no, 3.7 normal and 4.6 boost?

Ram speed looks good.

[_I_]

looks like your using the beta bios
https://www.msi.com/Motherboard/support/B450-GAMING-PRO-CARBON-AC

1c is the last stable release

save the bin file to the root of a usb stick, boot to bios, update from the usb stick
after its updated, boot back to bios, reset to defaults and set ram to xmp profile, and set the boot order

and get the mobo chipset/lan/audio drivers
windows takes a guess and often gets one close enough to work, but rarely correct

might fix the idle crashing/freezing if its how windows is waking/sleeping the cpu to/from idle states

[aBigGoofyGamer]

Carlsberg eredeti hozzászólása:

Is that cpu overclocked? it should be on a 37 multiplier no, 3.7 normal and 4.6 boost?

Ram speed looks good.

shouldn't be. As far as I know i got a regular ryzen 5 so it shouldn't be factory oc'd either

[aBigGoofyGamer]

_I_ eredeti hozzászólása:

looks like your using the beta bios
https://www.msi.com/Motherboard/support/B450-GAMING-PRO-CARBON-AC

1c is the last stable release

save the bin file to the root of a usb stick, boot to bios, update from the usb stick
after its updated, boot back to bios, reset to defaults and set ram to xmp profile, and set the boot order

and get the mobo chipset/lan/audio drivers
windows takes a guess and often gets one close enough to work, but rarely correct

might fix the idle crashing/freezing if its how windows is waking/sleeping the cpu to/from idle states

I might be. I think I updated my bios because of stuff like that so I'm not sure the bios is the issue. I'll still downgrade just in case. Also something odd i just realized- i never had to set the boot order after updating my bios. I'll also grab those drivers just in case. I haven't done that before, safe for the audio one. That one I always reinstall as windows grabs the wrong one

[Illusion of Progress]

ShadowX1312 eredeti hozzászólása:

Illusion of Progress eredeti hozzászólása:

Pretty much, yes. Just saying "my PC has given me problems for a while" is rather vague. Specific errors can be more helpful in finding out the cause to that specific problem.

The above is a good consideration, too. Maybe try running without the XMP profile settings. Yes, you'll lose RAM "speed" as it will be 2,133 MHz instead of 3,800 MHz, but the lower timings will somewhat counteract this, and it will mostly be for testing anyway (even if somewhat long term). If this solves your problem, you could try setting the timings manually to a lower one your board supports, but above the 2,133 MHz base speed, so you get back the performance mostly.

Ok, heres a more specific list of stuff that's gone wrong
gaming-
witcher 1,2,and 3 crash. 3 gives me a exemption access violation.
Batman arkham city is a stuttery unplayable mess. Massive slowdowns everywhere
dark souls 2 crashed twice within 100 hrs of gameplay (not a big deal)
Resident evil 7 crashes upon going to Zoe's trailer. The only crashes I've had from the game have all occured here
Re2 remake crashed once in about 50-100 hours.
Metro 1-2 crash during specific animations (going through a window, opening a door, etc)
Dishonored 1 froze in the menu
far cry 1 froze
Games will forget my graphics settings occasionally and I'll have to reset them again (Doom Eternal, Metro redux games)
doom 2016 stutters every now and again with an accompanying audio freeze. Only for a moment though. Doesn't happen too often

Windows issues-
PC has apparently been crashing when I've been away from it. Whats odd is that while these crashes are marked in reliability monitor, event viewer doesn't show them ever happening at all. I also can't remember my pc ever crashing around those times
My wallpaper on my left monitor will bug out and zoom in. If I select in that wallpaper, I can remove the corruption and reveal a slightly less corrupted ver of my wallpaper. (sounds weird but this was the only way I could explain this glitch)

Oculus rift s issues-
wavy graphics
Oculus won't display anything all of a sudden. the sensor light is permanently white.

I should mention all of these glitches survived complete reinstalls, of which I think i'm up to around 15 in a single year.

Some games might revert to default settings when the display driver changes. I know The Sims 3 does this for me.

I've heard of Arkham City having performance issues for some people.

Doom 2106 should be really smooth and light for performance. Even playing on an HDD, I saw no stutters or audio hitches. The initial menu loading is a bit stuttery but that is the case (for me anyway) even on an SSD and it's fine once it is past that.

Resident Evil 2, if this happened during a certain short cutscene, is known since you have nVidia hardware (though if this is the case it's not really a game crash but a Black screen as I believe the game continues to operate fine but the video messes up).

I can't speak for the rest, but the stuff with access violations and old stuff like the original Far cry freezing sound like a bigger overarching issue. I did get the feeling you didn't get into specifics since you suspected this, but specifics can still help.

The "apparent crashing" (what is this, exactly?) but Event Viewer not logging it is strange. Is the display driver crashing and recovering? If the whole PC is crashing it won't be apparent; you'll know. You'd return to a frozen, shut down, or BSOD state.

15 re-installs in one year is a lot but I've done a whole 2 on my main PC in ten years (Windows 7 ten years ago, and Windows 10 last year). Your issue isn't a software issue but a hardware one IMO if it persists that much.

And yes, absolutely get to the latest BIOS. As I mentioned earlier, I know firsthand that the BIOS versions that started introducing Zen 3 support (even when not using a Zen 3 CPU) to even 500 series chipsets boards were introducing stability issues for some people.

[Carlsberg]

ShadowX1312 eredeti hozzászólása:

I'll also grab those drivers just in case. I haven't done that before, safe for the audio one. That one I always reinstall as windows grabs the wrong one

Chipset drivers are important, always get them from mainboard maker especially after a bios update. and never take a beta bios unless you really have no other choice.

[aBigGoofyGamer]

Illusion of Progress eredeti hozzászólása:

ShadowX1312 eredeti hozzászólása:

Ok, heres a more specific list of stuff that's gone wrong
gaming-
witcher 1,2,and 3 crash. 3 gives me a exemption access violation.
Batman arkham city is a stuttery unplayable mess. Massive slowdowns everywhere
dark souls 2 crashed twice within 100 hrs of gameplay (not a big deal)
Resident evil 7 crashes upon going to Zoe's trailer. The only crashes I've had from the game have all occured here
Re2 remake crashed once in about 50-100 hours.
Metro 1-2 crash during specific animations (going through a window, opening a door, etc)
Dishonored 1 froze in the menu
far cry 1 froze
Games will forget my graphics settings occasionally and I'll have to reset them again (Doom Eternal, Metro redux games)
doom 2016 stutters every now and again with an accompanying audio freeze. Only for a moment though. Doesn't happen too often

Windows issues-
PC has apparently been crashing when I've been away from it. Whats odd is that while these crashes are marked in reliability monitor, event viewer doesn't show them ever happening at all. I also can't remember my pc ever crashing around those times
My wallpaper on my left monitor will bug out and zoom in. If I select in that wallpaper, I can remove the corruption and reveal a slightly less corrupted ver of my wallpaper. (sounds weird but this was the only way I could explain this glitch)

Oculus rift s issues-
wavy graphics
Oculus won't display anything all of a sudden. the sensor light is permanently white.

I should mention all of these glitches survived complete reinstalls, of which I think i'm up to around 15 in a single year.

Some games might revert to default settings when the display driver changes. I know The Sims 3 does this for me.

I've heard of Arkham City having performance issues for some people.

Doom 2106 should be really smooth and light for performance. Even playing on an HDD, I saw no stutters or audio hitches. The initial menu loading is a bit stuttery but that is the case (for me anyway) even on an SSD and it's fine once it is past that.

Resident Evil 2, if this happened during a certain short cutscene, is known since you have nVidia hardware (though if this is the case it's not really a game crash but a Black screen as I believe the game continues to operate fine but the video messes up).

I can't speak for the rest, but the stuff with access violations and old stuff like the original Far cry freezing sound like a bigger overarching issue. I did get the feeling you didn't get into specifics since you suspected this, but specifics can still help.

The "apparent crashing" (what is this, exactly?) but Event Viewer not logging it is strange. Is the display driver crashing and recovering? If the whole PC is crashing it won't be apparent; you'll know. You'd return to a frozen, shut down, or BSOD state.

15 re-installs in one year is a lot but I've done a whole 2 on my main PC in ten years (Windows 7 ten years ago, and Windows 10 last year). Your issue isn't a software issue but a hardware one IMO if it persists that much.

And yes, absolutely get to the latest BIOS. As I mentioned earlier, I know firsthand that the BIOS versions that started introducing Zen 3 support (even when not using a Zen 3 CPU) to even 500 series chipsets boards were introducing stability issues for some people.

Wait the bsod would stay on my screen until I did something to make it go away?! I thought this entire time my pc had been crashing with bsod like the reliability manager said and then restarted itself? Also I'll elaborate on the crashing. The recovery console stated that I had two hardware errors that caused windows to stop working correctly. I assume by not working correctly, the system must be crashing right? anyways, the errors occured within a half an hour of each other. This was the first one
Windows

Summary
Hardware error

Date
‎8/‎31/‎2021 12:36 AM

Status
Report sent

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

Problem signature
Problem Event Name: LiveKernelEvent
Code: 144
Parameter 1: 1020
Parameter 2: ffffee0e6e557960
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_19043
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19043.2.0.0.256.48
Locale ID: 1033

Extra information about the problem
Bucket ID: LKD_0x144_INVALID_TRANSFER_EVENT_PTR_ED_0_DUPLICATE_USBXHCI!TelemetryData_CreateReport_VEN_1022_DEV_43D5_REV_01
Server information: c3938c6e-4df5-44da-ad25-9902ff958e10

Here is the second one
Source
Windows

Summary
Hardware error

Date
‎8/‎31/‎2021 1:32 AM

Status
Report sent

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

Problem signature
Problem Event Name: LiveKernelEvent
Code: 117
Parameter 1: ffffdd0d1cd5d460
Parameter 2: fffff80468a97894
Parameter 3: 0
Parameter 4: 510
OS version: 10_0_19043
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19043.2.0.0.256.48
Locale ID: 1033

Extra information about the problem
Bucket ID: LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:13_IMAGE_nvlddmkm.sys_Ampere
Server information: f805244a-7b07-4eba-9076-d08a429fa969

[aBigGoofyGamer]

Carlsberg eredeti hozzászólása:

ShadowX1312 eredeti hozzászólása:

I'll also grab those drivers just in case. I haven't done that before, safe for the audio one. That one I always reinstall as windows grabs the wrong one

Chipset drivers are important, always get them from mainboard maker especially after a bios update. and never take a beta bios unless you really have no other choice.

Honestly, I don't think I've ever really kept up with mobo drivers. In hindsight that's probably a reason my pc is so unstable.

[_I_]

most likely driver issues, but update bios to the latest stable, non beta

[aBigGoofyGamer]

_I_ eredeti hozzászólása:

most likely driver issues, but update bios to the latest stable, non beta

I'll do that asap. also gonna make sure windows grabbed all the right drivers for my mobo and junk. I'm fairly certain my hardware is good as I just had to RMA my gpu for being apparently bad (somehow forgot to mention that in the og post, could have been the cause of some of my issues), replaced my ram to the stuff listed in my speccy/cpuz because it also was bad (memtest86 and only became bad recently), and made the cpu upgrade after all these problems I listed were occuring.

[_I_]

ya, wake/sleep and idle/load states can have issues with incorrect drivers

as for ram, if its not set correctly to xmp/amp profiles or overclocked can cause problems memtest will detect with rare problems for windows

[76561198343548661]

His RAM is up to 3600MHz but runs at 3466MHz (the real speed is half of this) . I dont think the RAM is faulty , He has so many things hooked to the PC . Disconnect something and test - a monitor, the USB memory stick

[_I_]

no, ddr = double data rate, ddr # = freq x2
ddr 3600 = 1800mhz

edit: showing fsb at 99.8 is a slight underclock
ram multi may be a little low, should be 17 x 99.8 = 1796, and it shows 1733
will not harm anything unless the rest of the timings are not set correctly

[76561198343548661]

_I_ eredeti hozzászólása:

no, ddr = double data rate, ddr # = freq x2
ddr 3600 = 1800mhz

i wrote the exact same thing above Even the kids know this

edit
Dont expect the speed to be 100% as the standard ! There s no underclocking

[Illusion of Progress]

_I_ eredeti hozzászólása:

no, ddr = double data rate, ddr # = freq x2
ddr 3600 = 1800mhz

edit: showing fsb at 99.8 is a slight underclock
ram multi may be a little low, should be 17 x 99.8 = 1796, and it shows 1733
will not harm anything unless the rest of the timings are not set correctly

The 1,733 MHz is because the board (apparently) has a maximum RAM speed support of 3,466 MHz.

If that is simply using the maximum XMP profile BUT running sower than rated (meaning it's usuing the same timings but running slower) then it's unlikely the RAM itself is unable to do those timings unless it wasn't good enough to do the rated ones to begin with. I'd personally probably set RAM back to default 2,133 MHz just to rule it out for now though.

Update the BIOS for sure.

Update the drivers. Just having outdated drivers alone won't cause instability... unless they were unstable to begin with, which matches your description, so try this.

ShadowX1312 eredeti hozzászólása:

Wait the bsod would stay on my screen until I did something to make it go away?! I thought this entire time my pc had been crashing with bsod like the reliability manager said and then restarted itself?

No, you're right too. By default, Windows will automatically restart when it encounters a BSOD, although you can disable this to make it behave like it originally did (which would just pause on that screen without automatically restarting after). I personally disable the automatic restart because sometimes a BSOD occurs and then restarts after so fast that you don't even know it was a BSOD (you can look in Event Viewer for clues after though and find out) so sometimes my mind operates as though that's the default.

If you can use a program like "WhoCrashed" it can give further information for was involved in the BSOD for the average person. The second one is referencing "nvlddmkm.sys" and "Ampere" so I presume the GPU was involved in that one. The first one has less clues but looking up the Event ID of 144 (this doesn't mean this was it) also shows a lot on information claiming it MAY be the graphics card driver. I think your GPU and/or GPU drivers OR part of the underlying system it replies on (chipset drivers or BIOS may be at play) are unstable. You're getting a lot of instability in games too which supports this.

Here's what I'd do.

First, update the BIOS. If you're not confident doing it, find someone or a service that will. As Carlsberg mentioned, you should absolutely not be on a beta BIOS unless it is entirely necessary, and I'd even recommend not to update this in normal circumstances unless you're having issues. I imagine you updated it to give your board support for that CPU so it may have been somewhat necessary at the time, and as I said, some of the earlier ones were known to cause issues, which is why I asked if you had issues before the CPU upgrade too. "Fix" this first (may not fix your issues but it's something to rectify anyway).

Secondly, disable "XMP" so the RAM is running at 2,133 MHz. Just make a note you did it so you can enable it again later. It's just a single setting to switch in the BIOS each time.

Third, update the chipset drivers and GPU drivers (and any others that may have updates, such as audio or network or whatnot). You can use "DDU" (Display Driver Uninstaller) to remove existing GPU drivers entirely before installing the new ones. I've, personally, never had to use this (I just install new over old OR do a standard uninstall if going backward to older) except maybe once back with a GeForce 4 or GeForce 6800 but I'd recommend it here. It doesn't hurt other than costing more time.

After that, it's sort of test driving.

If you have "optional" stuff that isn't necessary, you can remove them for now to rule them out. After years of no BSODs under Windows 7, Windows 10 gave me another reason to not like it by giving me the first one in forever because I disconnected a USB drive from it, so you'd be surprised what can cause it.