Question PC has developed stability issues with no clear consistent cause or behaviour ?

Jan 14, 2025
13
0
10
This is an ongoing problem that pops up quite inconsistently, taking days to resurface. It could therefore take a while before i can verify whether anything that's been attempted works. I'm keeping a regular log of events. What i've got so far is this:

Me and my girlfriend have a pair of almost identical PCs which we've been using for about 1.5 years. Hers has a slightly better GPU, and an M2 SSD instead of my SATA. I will post the exact specs later once i can have a look at them. She might also have a better power supply, but i'm not sure. They are both running on windows 10. Hers has recently developed a variety of problems that i can't seem to find an explanation for. The current sequences of events is this (dates are not exact, but near enough insofar i can remember):

- Dec 19th: I updated the BIOS to prevent CPU damage as per the recent trouble with intel CPUs. I performed the update for both PCs in the exact same way, applying default settings on both. There were no immediate problems, and my system runs fine.

- Jan 10th: Her PC bluescreened during regular browsing. The percentage indicated on there remained at 0%, and the system rebooted afer a while on its own, into BIOS. The BIOS could not find the boot drive. I messed around with it for a bit (reboots, exploring menus, more reboots, but changed no settings), and finally settled on trying to arrange for a system recovery/repair, when the problem fixed itself before i did anything. We could just boot into windows as normal, and i did not do a repair.

There is no dump file for the BSOD. Logs were already enabled, and there is a file for the 4th of january, but nothing for the 10th. I'm positive that it did not happen on the 4th. I'm assuming this is because it never got past 0%, and had no drive to write it to at the time. Some older logs were also present.

- Jan 11th: Just in case, i switched the SSD to a different M2 port. According to the motherboard manual, this should be fine. The PC booted with no issues. I took the opportunity to run a health check for the drive using Samsung Magician, and it all came back healthy. Maybe the SSD is fine, but the system struggles to reliably access it? i don't know.

- Jan 14th: At 10:00, The PC booted, but was unable to properly load windows. It got past the login screen, but then entered an endless cycle of crashing and loading explorer. This was accompanied by the screen flashing black, but with visible cursor. She tried again at 11:00, but that time only got as far as the login screen. I have videos of both events if you want them. Another attempt to boot was made at around 14:00.

At 18:00 or so, i tried booting the system myself, and was able to boot normally, as if nothing was wrong. After that i did the following things:
- I ran sfc/ scannow. This seemed to fix some things, though i can't make much sense of the log. It seemed to just repair some duplicates.
- Ran dism /online /cleanup-image /restorehealth. Found nothing.
- I changed the memory dump settings to a small memory dump, and told to PC to not automatically restart on a system failure. This is in case it BSODs again.
- I did a startup repair. This failed because it found nothing to repair, judging by the log file.
- I explored the event viewer, which revealed some things: There are occasional series of memory access errors, mostly (if not all) from the time of the explorer crash loop. There were also a few WHEA-logger errors, ID 3. One of those dates to May last year, the other 3 up to a few weeks after the BIOS update. My system does not have these events.
- I ran the Windows Memory Diagnostic tool. 2 passes, no errors.
- I updated the graphics drivers, and removed Armoury Crate.
- Given that our systems are largely identical, i swapped our RAM sticks to see if it would transfer the problem to my PC. The systems booted as normal.

No new crashes as of the 16th. Still working on / following your advice. See post #15 for the logs. Post #4 for hardware.
 
Last edited:
The first step is to post the full specs and OS information for both systems.

Very important to start with as much information as possible.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how fulll?

= = = =

The common starting point of the problems being the BIOS updates - correct? BIOS update source? Link?

You mentioned Event Viewer. That is good.

However, also look in Reliabiity History/Monitor. Much more end-user friendly and the timeline format may reveal some patterns.

Look in Update History for failed or problem updates.

Keep in mind that "almost identical" means that what worked on one system may not necessarily work on the other.

Treat each system as a separate problem. The problems are mostly with her system - correct?

If swapping components for troubleshooting change only one thing at a time and keep good notes on what was changed.

More information needed.
 
The first step is to post the full specs and OS information for both systems.

Very important to start with as much information as possible.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how fulll?

All parts were new when the system was built, unless specified. The systems are now 1.5 years old.

Her system (the subject of my post):

GPU: Asus GeForce RTX 4060 Ti DUAL-RTX4060TI-O8G
PSU: Cooler Master MWE Gold 650 Full Modular V2 PSU
Storage: Samsung 980 PRO 2TB M.2 SSD - about 40% full. This is the only storage device.
RAM: Two x G.Skill DDR4 Aegis 2x8GB 3000Mhz, so 4 sticks of 8 GB.
Motherboard: Asus PRIME B760-PLUS D4
CPU: Intel Core i5 13400F
Case: Unknown. Came from a previous build.

OS: Windows 10 Home, Version 10.0.19045 as of the 15th

My system (doesn't need fixing! I'm just using it for reference and hardware swaps!):

GPU: Asus GeForce RTX 4060 - Don't know the exact model.
PSU: Cooler Master MWE Gold 550 Full Modular V2 PSU
Storage: Samsung V-NAND 850 EVO 1TB SSD. - about 30% full. Used, but fine. This is the only storage device.
RAM: Two x G.Skill DDR4 Aegis 2x8GB 3000Mhz, so 4 sticks of 8 GB.
Motherboard: Asus PRIME B760-PLUS D4
CPU: Intel Core i5 13400F
Case: Unknown, but new.

OS: Windows 10 Home, Version 10.0.19045 as of the 15th

The common starting point of the problems being the BIOS updates - correct? BIOS update source? Link?

That's the question. I thought i'd mention it, since it's a pretty significant update, but it could have a different cause entirely. This is where i got it:

https://www.asus.com/motherboards-c.../helpdesk_bios/?model2Name=PRIME-B760-PLUS-D4

I've checked the BIOS version, and it's 1805 for both systems.

However, also look in Reliabiity History/Monitor. Much more end-user friendly and the timeline format may reveal some patterns.
Look in Update History for failed or problem updates.

From the reliability monitor, a few things stand out:
18/12: failed windows update
19/12: failed windows update
22/12: hardware error - see below:
Source
Windows

Summary
Hardware error

Date
‎22/‎12/‎2024 13:36

Status
Not reported

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

Problem signature
Problem Event Name:     LiveKernelEvent
Code: 144
Parameter 1:      3003
Parameter 2:      ffffb08ade1b75f0
Parameter 3:      40010000
Parameter 4:      0
OS version: 10_0_19045
Service Pack:     0_0
Product:    768_1
OS Version: 10.0.19045.2.0.0.768.101
Locale ID:  8192

24/12: Armoury crate stopped working
25/12: ASUS Update Helper - Unsuccesful application reconfiguration
4/1: Windows shut down unexpectedly. That's the source of the log, i guess, though i don't remember seeing such a thing happen. I'm still confident that the bluescreen happed more recently.
14/1: A lot. Mostly explorer.exe & dwm.exe stopped working, with a few other things mixed in. No surprise there.
Various dates: Local Security Authority Process Stopped Working, from 20/12 onward, after the failed windows update. It might have also done it before, but i can't look back that far.

There's a few other dates that say that windows was improperly shut down. This is weird, since we just shut it down through the start menu and then wait, but we've had random weirdness with that before. My PC never goes into low power mode; it just turns off the screen. Hers does, but it also sometimes boots back up on its own. I don't think it's related to our current problems, but it could be related to some of the errors.
 
Last edited:
Disable Armoury Crate.
Disable ASUS Update Helper.
Check Task Manager > Startup and Task Scheduler for any unexpected or unknown apps being launched at startup or triggered to run later via Task Scheduler.

The unexpected shutdowns could simply be a bad/loose component or connection somewhere.

Power down, unplug, open the case.
Clean ou dust and debris
Verify by sight and feel that all connecters, cards, RAM, jumpers, and case connections are fully and firmly in place
Use a bright flashligh to inspect everywhere for signs of damage.

Run "dism" and "sfc /scannow" agaIn.

Objective simply to simplify what all is started at boot and limit what you open thereafter.

And eliminate possible culprits due to loose connections etc..
 
  • Like
Reactions: Terrence Flew
I see you noticed my updates. My previous post now has all the information that was still missing, as well as all the stuff i found in the reliablity history. There seems to be some pretty important stuff in there. Sorry for making you go back and forth like this, it just worked out that way.

I uninstalled Armoury Crate on the 14th, so i guess that takes care of that. It might be worth noting that i never installed it on my own system. Did that also take care of the update helper? I don't see it anywhere.

I disabled a few things on startup in task manager, but there was nothing unexpected in there. It should now be down to the bare essentials.

As for Task Scheduler, I disabled an MMO-related piece of software. I'm not sure if it'll stay down, but i'll see. It's currently set to 'disabled', but will still trigger at the log on of any user. Is that enough?
There are two ASUS tasks in there: NoiseCancelingEngine and P508PowerAgent_sdk. I don't know what they are, so i've left them alone. I don't know what else to check for. I've never used Task Scheduler before.

I'll check for loose connectors tomorrow if that's okay. At least the RAM is seated.

Ran "dism" and "sfc /scannow" again. No errors.

I've also got you some logs. I hope you can access these.
WHEA-logger files, saved from event viewer: Deleted.
Minidump logs, including the Jan 4th log: Deleted.
SrtTrail: Deleted.
CBS.log: Deleted.
[Moderator Note: OP posted logs elsewhere per Post#15 Zip file links deleted.]


I do need to stress that while windows might say that it was improperly shut down, we didn't see such a thing happen, apart from the bluescreen and explorer crash loop.
 
Last edited by a moderator:
WARNING

For the record, I did not open any of the zipped files. A single click on the first one triggered a malware/virus warning on my system. Likewise for the last one. May be because they are .zip However, I went no further.

= = = =


Task Scheduler is just a tool/utility that automates Windows and its' hosted apps etc. Basic function is that IF "X" then"Y".

If some certain situation or condition "X" occurs then that condition triggers Windows to do "Y". If "Y "is buggy, corrupt, wrong, or malicious then that can appear as an "improper shutdown".

Very easy to check and if there are scheduled events (especially if unknown) doing things then you need to investigate further. What is the trigger and what is being triggered? You should be able to at least disable any unknown tasks or actions being triggered.

= = = =

A normal Windows shutdown uses the power icon to turn off the system or otherwise provides Windows with some notice that the host system is being shutdown.

Windows does various things for "house keeping" purposes and getting things ready for the next boot before it shutsdown. That "house keeping" may include some interim updates, saving data, resetting configurations, removal of temporary files. The time can vary - especially if there are updates involved. Or backups.

Without sucessfully completeing those actions system and data files can become corrupted and cause even more problems.

A hard power-off by switch, pulling out the wall plug, a surge protector or circuit breaker tripping, or any sort of unexpected power loss is viewed by Windows as a power loss. No matter how brief. Even a simple dip in supply voltage is a power loss and deemed an "improper shutdown".

Furthermore the voltages themselves are important. You have the wall outlete power (which varies with countries) and you have internal voltages via the PSU.

Most PSU's provide 3, 5, or 12 volts (+ or -) to various system components. Some components receive two voltages.

The loss, however brief, of any voltage results in an "improper shutdown". (That is why knowing more about the PSU is important: make, model, wattage, age, condition. The PSU could be starting to falter and fail. Especially as it nears its' designed in EOL - End of Life. Generally around when the warranties end. :)

Loose connections can have the same effect. You may not see it as a loss of power per se. You only see the blue screen and crashes.

Take your time checking for loose connections. Seat and unseat components, plug and unplug. Do leave the CPU alone for now.

Damages: look for bare conductor showing, melting of any sort, pinched or kinked wires, corrosion, loose or missing screws, cracks, swollen components, moisture, dead bugs. Anything at all that seems amiss.

If possible consider replacing the CMOS battery. Just as a matter of elimination. Follow applicable User Guide/Manual instructions to replace the CMOS battery. Likewise if doing CMOS resets.
 
start by updating your usb3 drivers to match your bios version.
then reboot. You should get the drivers from your motherboard vendor. I would update other drivers at the same time but do not install the utilities.
drivers should be in the chipset drivers package. or get them from intel https://www.intel.com/content/www/us/en/support/detect.html

not sure if you have a custom usb2 type c driver. hopefully the above link will detect it.
 
Last edited:
Looking at the last memory dump.
bugcheck cause by a 1 bit memory corruption in a pagefile

I would go into bios and check the memory timings match the actual ram chips installed. I would confirm the chips are in the best slots then boot and run memtest86 on its own boot image and see if it can find a one bit error.
The error does not have to be in the ram, it can be in the cpu, in the cache ram, in the or in the drive ram. IE any where in the sequence where the pagefile.sys gets written.
you will also want to delete your pagefile.sys each time you reboot until you figure out the cause. google "how to delete the pagefile.sys on shutdown" it will have a registry setting you can set to delete the pagefile.sys on each reboot.

for the actual bios ram timings, look at the command delay setting. it is often set incorrectly at 1n or 1T while some ram need to have it set to 2N or 2 T.
looks like you have 2 stick of
F4-3000C16-8GISB ram
you should confirm the RAM setting in bios
DDR4-3000 CL16-18-18-38 1.35V
not sure what the cmd rate should be.

note:
several of the core windows files have had the checksums removed.
Current cpu Speed 4059MHz
(strange number)

realtex network driver is very old:
rt640x64.sys Fri May 24 01:47:02 2019
nvida driver old:
nvvhci.sys Fri Apr 22 04:37:06 2022
MsIo64.sys Wed Apr 5 18:54:11 2023
CtiAIo64.sys Wed Apr 5 19:06:24 2023
(Creative Technology Innovation)
 
Last edited:
looks like all the bugchecks have the same root cause. most likely a single bit corruption being propagated to your drive. to your pagefile.sys. you might see if there is a firmware update for your drive. You might delete the pagefile.sys and make another one. you might get a new drive. These type of problems are hard to locate.
you might download crystaldiskinfo.exe and check the drive health and firmware version but the problem might be in the drives electronics.

you might even update the cpu firmware if you have not applied the update for the security fixes.

sorry, there is no clear answer. deleting the pagefile on boot will only make the problem happen less often.
note sure why several of the windows core files have had the checksums removed. usually the dism.exe command you used would fix them. maybe some tools is making the modification after they are fixed.

System Uptime: 24 days 4:35:56.813
System Uptime: 12 days 12:13:55.535
System Uptime: 0 days 11:33:35.158
System Uptime: 7 days 1:47:39.200
System Uptime: 1 days 18:36:10.673
these are how long the system ran before it bugchecked. rebooting with the registry setting to delete the pagefile.sys should make it harder to get the bugcheck. I have seen errors like this that were caused by the sleep circuits and they would take over 12 sleep/wake cycles before you started getting bugchecks.
 
Last edited:
WARNING

For the record, I did not open any of the zipped files. A single click on the first one triggered a malware/virus warning on my system. Likewise for the last one. May be because they are .zip However, I went no further.

= = = =


Task Scheduler is just a tool/utility that automates Windows and its' hosted apps etc. Basic function is that IF "X" then"Y".

If some certain situation or condition "X" occurs then that condition triggers Windows to do "Y". If "Y "is buggy, corrupt, wrong, or malicious then that can appear as an "improper shutdown".

Very easy to check and if there are scheduled events (especially if unknown) doing things then you need to investigate further. What is the trigger and what is being triggered? You should be able to at least disable any unknown tasks or actions being triggered.

= = = =

A normal Windows shutdown uses the power icon to turn off the system or otherwise provides Windows with some notice that the host system is being shutdown.

Windows does various things for "house keeping" purposes and getting things ready for the next boot before it shutsdown. That "house keeping" may include some interim updates, saving data, resetting configurations, removal of temporary files. The time can vary - especially if there are updates involved. Or backups.

Without sucessfully completeing those actions system and data files can become corrupted and cause even more problems.

A hard power-off by switch, pulling out the wall plug, a surge protector or circuit breaker tripping, or any sort of unexpected power loss is viewed by Windows as a power loss. No matter how brief. Even a simple dip in supply voltage is a power loss and deemed an "improper shutdown".

Furthermore the voltages themselves are important. You have the wall outlete power (which varies with countries) and you have internal voltages via the PSU.

Most PSU's provide 3, 5, or 12 volts (+ or -) to various system components. Some components receive two voltages.

The loss, however brief, of any voltage results in an "improper shutdown". (That is why knowing more about the PSU is important: make, model, wattage, age, condition. The PSU could be starting to falter and fail. Especially as it nears its' designed in EOL - End of Life. Generally around when the warranties end. :)

Loose connections can have the same effect. You may not see it as a loss of power per se. You only see the blue screen and crashes.

Take your time checking for loose connections. Seat and unseat components, plug and unplug. Do leave the CPU alone for now.

Damages: look for bare conductor showing, melting of any sort, pinched or kinked wires, corrosion, loose or missing screws, cracks, swollen components, moisture, dead bugs. Anything at all that seems amiss.

If possible consider replacing the CMOS battery. Just as a matter of elimination. Follow applicable User Guide/Manual instructions to replace the CMOS battery. Likewise if doing CMOS resets.
I'll try to post the first and last logs in some other way. EDIT: done! See post #15.

Given that i need to be thorough in checking the wires, i'll wait until saturday before i go check that. In the meantime, i have an idea: I'm going to try replacing the power strip. Both of our PCs are plugged into it, and i'm not having any problems, but you never know. I'll let you know when i've done that.

Replacing the CMOS battery should be easy enough. I think we've still got some of those lying around. I doubt it's to blame, since i've seen what a dying battery looks like and i'm not seeing any symptoms, but it's an easy fix.

No comments on the hardware failure? I'm guessing it's related to what johnbl said.
Source
Windows

Summary
Hardware error

Date
‎22/‎12/‎2024 13:36

Status
Not reported

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

Problem signature
Problem Event Name:     LiveKernelEvent
Code: 144
Parameter 1:      3003
Parameter 2:      ffffb08ade1b75f0
Parameter 3:      40010000
Parameter 4:      0
OS version: 10_0_19045
Service Pack:     0_0
Product:    768_1
OS Version: 10.0.19045.2.0.0.768.101
Locale ID:  8192
 
Last edited:
start by updating your usb3 drivers to match your bios version.
then reboot. You should get the drivers from your motherboard vendor. I would update other drivers at the same time but do not install the utilities.
drivers should be in the chipset drivers package. or get them from intel https://www.intel.com/content/www/us/en/support/detect.html

not sure if you have a custom usb2 type c driver. hopefully the above link will detect it.
When you say chipset drivers package, do you mean the one here?
https://www.asus.com/motherboards-c...pdesk_download/?model2Name=PRIME-B760-PLUS-D4
 
Looking at the last memory dump.
bugcheck cause by a 1 bit memory corruption in a pagefile

I would go into bios and check the memory timings match the actual ram chips installed. I would confirm the chips are in the best slots then boot and run memtest86 on its own boot image and see if it can find a one bit error.
The error does not have to be in the ram, it can be in the cpu, in the cache ram, in the or in the drive ram. IE any where in the sequence where the pagefile.sys gets written.
you will also want to delete your pagefile.sys each time you reboot until you figure out the cause. google "how to delete the pagefile.sys on shutdown" it will have a registry setting you can set to delete the pagefile.sys on each reboot.

Given that i swapped the RAM sticks between our PCs, i guess it would be better to see if the problems resurface, and where. If they continue to happen on her PC we can exclude the RAM, at least on a hardware level.

I'll look into deleting pagefile.sys like that. I can set that up tonight.

for the actual bios ram timings, look at the command delay setting. it is often set incorrectly at 1n or 1T while some ram need to have it set to 2N or 2 T.
looks like you have 2 stick of
F4-3000C16-8GISB ram
you should confirm the RAM setting in bios
DDR4-3000 CL16-18-18-38 1.35V
not sure what the cmd rate should be.

I am completely unfamiliar with stuff like that, but i can at least check the RAM settings. The systems have 4 sticks though, if that matters.
I do need to stress that my own system has the same BIOS, RAM, CPU and motherboard, and it has no issues. Could just be that i'm lucky, but still.

note:
several of the core windows files have had the checksums removed.
Current cpu Speed 4059MHz
(strange number)

Is there anything i can or need to do with this?

realtex network driver is very old:
rt640x64.sys Fri May 24 01:47:02 2019
nvida driver old:
nvvhci.sys Fri Apr 22 04:37:06 2022
MsIo64.sys Wed Apr 5 18:54:11 2023
CtiAIo64.sys Wed Apr 5 19:06:24 2023
(Creative Technology Innovation)

I'm not sure what to install in terms of the realtek network driver. Googling it gives me a lot of confusing results.
The nvidia drivers being old is weird. I'm certain she installed newer drivers than that, unless those particular ones don't get updated through the nvidia utility program (whatever its called).
 
Last edited:
looks like all the bugchecks have the same root cause. most likely a single bit corruption being propagated to your drive. to your pagefile.sys. you might see if there is a firmware update for your drive. You might delete the pagefile.sys and make another one. you might get a new drive. These type of problems are hard to locate.
you might download crystaldiskinfo.exe and check the drive health and firmware version but the problem might be in the drives electronics.
Thanks for the effort. I take it you were able to access the logs then?
I'll check for firmware updates. I wouldn't be suprised if it makes a difference, given that it's relatively new tech (by my standards, anyway).
Samsung Magician detected no problems with the drive health after various scans. I could try using crystaldiskinfo.exe as well, if you think that's not enough.

you might even update the cpu firmware if you have not applied the update for the security fixes.

What update for security fixes do you mean?

sorry, there is no clear answer. deleting the pagefile on boot will only make the problem happen less often.
note sure why several of the windows core files have had the checksums removed. usually the dism.exe command you used would fix them. maybe some tools is making the modification after they are fixed.

I think the logs i sent you might be from before i used dism.exe, though not by much. That would explain it.
EDIT: This CPU has a feature where it'll temporarily overclock for some extra performance. it's 2.5 Ghz by default, but can boost itself up to 4.6. Maybe that's what you're seeing? I didn't set this up myself; it's just a feature of the hardware.

If setting up the automatic deletion of pagefile.sys makes this thing stable enough to use (at least for now) then that's already a step in the right direction.

How familiar are you with the changes imposed by the BIOS update, regarding the intel voltage problems? I updated the BIOS rather late, all things considered. I just didn't have the chance to do it earlier. Our CPUs are at the lowest end of the range of CPUs affected, but she does play games that are at the upper end of it's capacity. Maybe it got fried? After a quick google, I'm not seeing any issues that are typical for people suffering from damaged CPUs due to the intel bug, but you'd know that better than me.
 
Last edited:
I'm trying to post the CBS.log directly, but it's way too big. Maybe this link works better (the site renames the file for some reason, but that shouldn't matter):

https://files.catbox.moe/opfncx.log

Here's a screenshot of one of the WHEA-logger events (will be deleted after 31 days):

https://postimg.cc/8J2THLLk

I'm been told by someone else that's it's unimportant, but you might have a different opinion.

SrtTrail:

https://files.catbox.moe/y1vqlj.txt

Minidumps:

https://files.catbox.moe/hb8yur.dmp (010425-5453-01)
https://files.catbox.moe/fpvogf.dmp (012324-7250-01)
https://files.catbox.moe/8f2kdg.dmp (092124-6656-01)
https://files.catbox.moe/9ldlkt.dmp (110324-5562-01)
https://files.catbox.moe/64ii18.dmp (120124-4578-01)

I'll post a list of things i've done today later, with a to-do list. That'll help us keep track of things.
 
Last edited:
I'm trying to post the CBS.log directly, but it's way too big. Maybe this link works better (the site renames the file for some reason, but that shouldn't matter):

https://files.catbox.moe/opfncx.log

Here's a screenshot of one of the WHEA-logger events (will be deleted after 31 days):

https://postimg.cc/8J2THLLk

I'm been told by someone else that's it's unimportant, but you might have a different opinion.

I'll post a list of things i've done today later, with a to-do list. That'll help us keep track of things.
nothing to worry about in the log. there were two errors but they look like bugs in the program. basically, an attempt to clear a flag failed, and a sharing violation on a file that was to be copied and deleted.

as to the Whea-logger error, my wife had a Dell machine that would produce this 8 times a minute and I could never get it fixed. I tried for months with various updates. I ended up disabling the actual log. (just to hide the errors) something was wrong but it never got worse or actually broke for the life of the laptop.
 
mentioned the cpu speed only because I generally see speeds
that are changed in units of 100MHz. often when I see speed like
4059MHz it can mean that the bios is applying the wrong voltage to a cpu. (could be a over heated cpu, bad overclock driver, psu providing voltages out of spec)

basically, the bios applies a voltage to the cpu and a circuit converts the voltage to a clock speed. you get strange clock speeds when you have a bios (or overclock driver) that do not know about a new CPU release. (sometimes cpu vendors change the voltages to the cpu, takes a while before motherboard bios or overclock tools are updated
 
Given that i swapped the RAM sticks between our PCs, i guess it would be better to see if the problems resurface, and where. If they continue to happen on her PC we can exclude the RAM, at least on a hardware level.

I'll look into deleting pagefile.sys like that. I can set that up tonight.



I am completely unfamiliar with stuff like that, but i can at least check the RAM settings. The systems have 4 sticks though, if that matters.
I do need to stress that my own system has the same BIOS, RAM, CPU and motherboard, and it has no issues. Could just be that i'm lucky, but still.



Is there anything i can or need to do with this?



I'm not sure what to install in terms of the realtek network driver. Googling it gives me a lot of confusing results.
The nvidia drivers being old is weird. I'm certain she installed newer drivers than that, unless those particular ones don't get updated through the nvidia utility program (whatever its called).
for the nvidia driver it was 2 years older than all of your other nvidia drivers. Looks like it was not updated. Sometimes it can be a problem. maybe ddu utility will update it. (not sure what the driver actually does)

best to update the Realtek network driver.

msio64.sys had a bug that is used by malware to infect your system. The bug was fixed in 2024 but your file date was in 2023. You might want to update. I think it is used for controlling LED lights on your machine.
 
the old nvidia driver is for the usb3 connection on the GPU.
Nvidia Virtual USB Host Controller driver. guess it was removed from the standard gpu driver package update.
you might try https://www.nvidia.com/en-us/drivers/
or see if your machine vendor has a update.
I'm not seeing any results, unfortunately. It can find the card, but it just leads me to the standard drivers that get installed through the Nvidia app already.
 
for the nvidia driver it was 2 years older than all of your other nvidia drivers. Looks like it was not updated. Sometimes it can be a problem. maybe ddu utility will update it. (not sure what the driver actually does)

best to update the Realtek network driver.

msio64.sys had a bug that is used by malware to infect your system. The bug was fixed in 2024 but your file date was in 2023. You might want to update. I think it is used for controlling LED lights on your machine.
I'm trying to find the Realtek network driver, but i'd really appreciate a link to the exact driver i need. The google search results are not pointing me towards any specific file; i've got like 5 different results.
 
Okay, here's what i've done today:

- I've set up the automatic deletion of pagefile.sys.
- I've installed the chipset drivers
- I've checked for firmware updates to the SSD. It was already up-to-date.
- I've taken pictures of how my RAM is configured in BIOS. Interestingly, it's at a lower clock speed than advertised:




I'm assuming the timings are different than what you said because of the different clock speed. I don't mind that the clock speed is lower, by the way, unless you think it's causing instability. I want a stable system before i start messing with clock speeds for the sake of performance.

To do:

- Replace the CMOS battery (probably tomorrow)
- Replace the power strip (will look into that asap - it's 6 years old, apparently)
- Check dust and wiring

Maybes:
- Run memtest. I think the RAM swap should tell us enough with time; we'll see.
- CPU swap. Please no.

I do have some good news: All of the parts are still within warranty, until mid 2026 at the earliest. If we can identify the culprit, it could be replaced.... or i could just send it all in.

I'm currently thinking that once i've done all the things on the to-do list, and we don't find anything else that can be easily/urgently done, i should give it some time. It's possible that the system will by then be stable enough to use in the long term. It hasn't had any visible problems since the 14th. No problems in reliability history either.
 
Last edited: