Question My PC crashes repeatedly ?

[Reaser714]

My computer was working fine until the last 5 months. At first, the red CPU LED lit up while I was working in Windows. Then I cleaned the PC and the issue went away for a few months. But a few days ago, Windows started crashing, and then the blue screen appeared , followed by the red CPU LED turning on again.
Windows even crashes in Safe Mode.

Now, when I try to turn off the computer using the power button, it doesn't respond at all.

My specs:
Motherboard: MSI B450 Carbon AC
RAM: Corsair Vengeance RGB DDR4 RAM 32 GB 3600 MHz
CPU: Ryzen 5 3600
GPU: Asus ROG Strix GeForce RTX 2060 Super 8G
SSD: Samsung SSD 970 EVO Plus 500 GB (for Windows only)
HDD: WD Blue 1TB
PSU: BitFenix Whisper M 750w
CPU cooler: stock

https://imgur.com/a/lM95RTU

 

[Ralston18]

This:

"Now, when I try to turn off the computer using the power button, it doesn't respond at all."


Take a look in Reliability History/Monitor. Are there any error codes, warnings, or informational events being captured just before or at the time of the crashes?

There are other places to looki but for now simply focus on Reliability History/Monitor and the presented timeline. Look for errors, warnings, informational events and patterns.

Note and post error codes.

= = = =

Do you normally turn off the computer by right-clicking the Windows icon and then selecting the "Shutdown" menu choice?

For the most part that is how Windows should be shutdown.

However, BSOD's etc. can force end users to do some sort of hard power off.

Which can and does cause file corruption problems.

After the next successfull boot run "dism" and "sfc /scannow" to find and repair file problems.

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

If that does not work then the next step would be to properly power down (if possible), unplug, and open the case.

Verify that all connections, plugs, jumpers, RAM, and case connectors are fully and firmly in place.

Current objective being to narrow down the potential culprits.

 

[Reaser714]

This:

"Now, when I try to turn off the computer using the power button, it doesn't respond at all."


Take a look in Reliability History/Monitor. Are there any error codes, warnings, or informational events being captured just before or at the time of the crashes?

There are other places to looki but for now simply focus on Reliability History/Monitor and the presented timeline. Look for errors, warnings, informational events and patterns.

Note and post error codes.

= = = =

Do you normally turn off the computer by right-clicking the Windows icon and then selecting the "Shutdown" menu choice?

For the most part that is how Windows should be shutdown.

However, BSOD's etc. can force end users to do some sort of hard power off.

Which can and does cause file corruption problems.

After the next successfull boot run "dism" and "sfc /scannow" to find and repair file problems.

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

If that does not work then the next step would be to properly power down (if possible), unplug, and open the case.

Verify that all connections, plugs, jumpers, RAM, and case connectors are fully and firmly in place.

Current objective being to narrow down the potential culprits.

omg thanks so much, but how could Windows issues prevent the bios to post ?

 

[Ralston18]

Corrupted files.

When Windows shuts down it does some preparation for the next boot. If that preparation is not done or interrupted then windows will not be directly ready to restart and/or files become corrupted.

When boot is attempted the corrupted file bring the process to a halt,

There may or may not be some "verbose" setting that can be enabled during the boot process that makes the system report/display, step by step, what is happening or trying to happen during boot.

FYI:

https://www.baeldung.com/cs/computer-boot-process

There are other similar tutorials and explanations online.

= == =

You can use Safe Boot or some recovery drive to work around such problems.

However, if a button is not working then it is quite possible that the button is broken or the applicable connections are at fault in some manner.

My view is that any error codes, warnings, and informational events may provide some clue....

For example, your posted crash dump file indicates some problem with FLTMGR.SYS

I found this:

"The fItmgr.sys file, also known as the Microsoft File system Filter Manager file responsible for making sure that the data on the hard drives is readable and accurate. If your operating system fails to read the data on your hard drive because of an issue with the fItmr.sys file, you may encounter a Bluescreen of Death (BSOD) that lists fItmr.sys as the culprit."

Source:

https://www.makeuseof.com/what-is-the-fltmgrsys-stop-code-and-how-to-get-rid-of-it-on-windows-1011/

There are other members here that are much more knowledgeable about reading and understanding crash dump files. And what the contents may indicate or reveal.

I will defer to those members accordingly.

 

[Ralston18]

OP requested thread deletion.

Per Forum rules threads are not deleted.

Closing thread to further posts.

 

[Ralston18]

Per PM from member - problem is still occurring and the thread is being unlocked.

 

[Reaser714]

good evening
i still have this issue but this time theres no BSOD its just the red CPU LED lit up after 5-8h and i have to shutdown the pc through PSU button cause shutdown and restart button not responding at all and no they're not broken , they work fine within those 5-8h and i have to wait i dont know how long because i go to sleep
all the light on the MB and RAM and GPU and case working fine

things has been done during those few days
- installed new OS through micrsoft and updated the chipset and all driver to latest
-update the bios to latest one and oldest one
-swapped my kit of Ram to another 8g ram i had around
-unplugged all the cables and plugged them again even i swapped the cpu cable with one i never used , and did some cable management
-swapped my DP cable to DHMI
- my PSU doing weird sound just like in this video

- temps are fine i did some cpu stress test for 5-10min and its was fine within those 5-8h the pc running fine with no issue , i even play heavy cpu games like destiny 2 , you might see the Vcore voltage is low that because i disabled the turbo boost through bios so the cpu running at 3.6ghz the stock one

update : I reset the cpu and the cooler now it's even worse its crash in the bios when it's boot sometime and take around 3 to 2min to crash and cpu led lit red , i also tried to unpluge everything vga ssd and hdd ,also i tried to touch the cpu to check if it's getting warm or not and yea its getting warm

 

[Reaser714]

Ralston18 fixed i think , i just had to replace the thermal paste , i didn't reapply it since i think 5y.​

but my question how could be the temps of core are 40-50 and its can be thermal issue ? maybe part of cpu was getting hot but not the core itself ?

 

[digitaldata77]

Hi I firstly respect Ralston18's advice and expertise. Please follow their advice first as my info is a suggestion. As you have already reseated and repasted the CPU. I was going to suggest removing the CPU and cooler and firmly reseat the CPU and repaste and install the CPU cooler. Then start your PC and have HW monitor software running always on top while you test run games and applications to check the temperatures to insure they are in acceptable parameters for your system. This should eliminate the crashing issues. Hope it runs well for you. Cheers.

 

[Reaser714]

Hi I firstly respect Ralston18's advice and expertise. Please follow their advice first as my info is a suggestion. As you have already reseated and repasted the CPU. I was going to suggest removing the CPU and cooler and firmly reseat the CPU and repaste and install the CPU cooler. Then start your PC and have HW monitor software running always on top while you test run games and applications to check the temperatures to insure they are in acceptable parameters for your system. This should eliminate the crashing issues. Hope it runs well for you. Cheers.

yea i dont get any crash now after repaste it , the only issue i have now is booting sometime when i start the pc the cpu led lit ( sometime not always ) every 2 days 4 days its just random
i did something i dont know what that did to fix the booting , i hold down the shutdown button when starting the pc for 5-10s the pc restarted then boost normally , what that mean ? and do i have to do that evertime that happen , i believe they call that cold boot , but i have latest bios 7B85v1H4(Beta version) , but theres something i dont understand what could make the power button and restart to not respond when you press them when cpu led lit if im sure they're not broken

i found a post talking about cold boot issue and applied the setting in the bios that recommended

following settings will solve the problem 100% of the time:

• Update to 7B85v1B
• Go to BIOS->overclocking->CPU features and set following settings to:
  • "Power Supply Idle Control" to 'Typical Current Idle'
  • "Collaborative Power Performance Control" to 'enabled'
  • "Cool'n'Quiet" to 'disabled'
  • "C-state" to 'disabled'

 

[digitaldata77]

Did you reset the CMOS? This can help to eliminate boot issues. This will set the board to default settings. Then you can try tweaking for best performance following the instructions for your board. This has worked for my rigs. It may be worth a try. See how it does in default mode then tweak it to the performance level you need for your games and productivity applications.

 

[Reaser714]

Did you reset the CMOS? This can help to eliminate boot issues. This will set the board to default settings. Then you can try tweaking for best performance following the instructions for your board. This has worked for my rigs. It may be worth a try. See how it does in default mode then tweak it to the performance level you need for your games and productivity applications.

its happened again today when i startup the pc the cpu led lit red its seems its every 2 days or something the only way that make the red light go away is by resetting the bios , i dont know whats wrong , i wont bother with xmp for now i just switched windows os to uefi and disabled core performance boost , anything else i should do for now , i also downgraded my bios to latest 3000 bios update 2020 update

 

[Reaser714]

still need help . i still have same issue i set everything to default with 2 sticks of ram but cpu led lit red the next day when starting the system - restarting and shutdown the system in same day from successfully posting work fine it just when i try to start the system next day , i had to unplug and plug the cable over and over to make it post , the only thing i change in the bios is enabling secure boot , should i keep everything in default and not change anything ?

 

[Reaser714]

i fixed this issue by disable secure boot - but i don't understand why secure boot lock my entire pc i couldn't even shutdown the pc by pressing power button or even restart button when cpu led lit red when i had this issue - my setting in secure boot was changing csm to uefi and then secure boot was enabled by default and secure boot mode was customs by default i didn't change any of that

 

[Ralston18]

The concept of secure boot is simple: to ensure that only trusted software is allowed to launch and run.

Implementing that is not simple when so many things can happen or not happen when a system boots.

Could be just a matter of buggy or corrupted software, faltering hardware, end-user configurations , some mix even - all too common.

Not to mention the pitfalls of pirated software and malware getting in....

Disabling secure boot did not stop or end the problem. All that was accomplished was to bypass protections that are now no longer protecting the system. Potentially leading to making the situation even worse. May have already done so.

There are many online explanations about secure boot. Do some searches and read a few articles and tutorials to learn more about Secure Boot. Read articles from known technical sources - including Microsoft. There may be some fix to be found - however, that depends on finding the root cause(s) of the problem.

Next, steps:

"Do-over".

Reread and review the motherboard's User Guide/Manual and pay close attention to all fine print and details.

Again: double check all connectors, cards, RAM, jumpers, and case connections to ensure that all are correct, fully and firmly in place, and undamaged. Check by sight and feel and use a flashlight to inspect everything.

Note: I listened to that PSU "noise" again. Could not really hear anything but I am wondering about the positioning of that PSU. I see only half the fan and I am not sure about the grill work that is visible. Take a couple more photographs and post accordingly via imgur (www.imgur.com) Show fans and indicate air flow directions.

Replace the CMOS battery and reset CMOS by following the applicable motherboard procedures.

User Verbose mode to watch what happens when/while the system boots.

Simplify: Use only iGPU (if supported) and only the boot C: drive. Disconnect other drives from use. Basic network connectivity: just wired (preferably) or wireless access. No VPNs. No extra apps or utilities of any sort in Task Manager > Startup.

No clocking or voltage changes.

The objective being to restore the system to its' base configurations where the system will fully boot without errors and remain stable thereafter.

Allow a few boots and time between boots for Windows to update and correct itself as necessary. Watch for failed or problem updates.

Clear the Event Viewer logs. The purpose being to start with a "clean slate" and make errors or other problems stand out.

If the above does not prove sucessful you can do it all over again with a clean Windows install as a new starting point.

It will all take time, patience, and effort. Be methodical, make notes, observe carefully.

 

[Reaser714]

The concept of secure boot is simple: to ensure that only trusted software is allowed to launch and run.

Implementing that is not simple when so many things can happen or not happen when a system boots.

Could be just a matter of buggy or corrupted software, faltering hardware, end-user configurations , some mix even - all too common.

Not to mention the pitfalls of pirated software and malware getting in....

Disabling secure boot did not stop or end the problem. All that was accomplished was to bypass protections that are now no longer protecting the system. Potentially leading to making the situation even worse. May have already done so.

There are many online explanations about secure boot. Do some searches and read a few articles and tutorials to learn more about Secure Boot. Read articles from known technical sources - including Microsoft. There may be some fix to be found - however, that depends on finding the root cause(s) of the problem.

Next, steps:

"Do-over".

Reread and review the motherboard's User Guide/Manual and pay close attention to all fine print and details.

Again: double check all connectors, cards, RAM, jumpers, and case connections to ensure that all are correct, fully and firmly in place, and undamaged. Check by sight and feel and use a flashlight to inspect everything.

Note: I listened to that PSU "noise" again. Could not really hear anything but I am wondering about the positioning of that PSU. I see only half the fan and I am not sure about the grill work that is visible. Take a couple more photographs and post accordingly via imgur (www.imgur.com) Show fans and indicate air flow directions.

Replace the CMOS battery and reset CMOS by following the applicable motherboard procedures.

User Verbose mode to watch what happens when/while the system boots.

Simplify: Use only iGPU (if supported) and only the boot C: drive. Disconnect other drives from use. Basic network connectivity: just wired (preferably) or wireless access. No VPNs. No extra apps or utilities of any sort in Task Manager > Startup.

No clocking or voltage changes.

The objective being to restore the system to its' base configurations where the system will fully boot without errors and remain stable thereafter.

Allow a few boots and time between boots for Windows to update and correct itself as necessary. Watch for failed or problem updates.

Clear the Event Viewer logs. The purpose being to start with a "clean slate" and make errors or other problems stand out.

If the above does not prove sucessful you can do it all over again with a clean Windows install as a new starting point.

It will all take time, patience, and effort. Be methodical, make notes, observe carefully.

maybe im not setup secure boot properly

i watched few youtube videos about how to setup secure boot and all of them set the secure boot mode into Standard not custom like my bios doing it by default

i couldn't find anything about what's difference between standard and custom but this one

Custom is used by enterprises usually who want to set their own keys

 

[Ralston18]

BIOS: version, source?

OS: version, source?

 

[Reaser714]

BIOS: version, source?

OS: version, source?

Bios version : 7B85v1H4 2024-09-25 latest version ( https://www.msi.com/Motherboard/b450-gaming-pro-carbon-ac/support )
OS version : 24H2 26100.2605 up to date from Microsoft

i have tried 7B85v1B 2019-11-13 that i was using before the issue happen to me and still when i enable secure boot , eveything work fine for 2 or 3 days then the system refuse post untill i reset the bios , the only way to make everything work without any issue is to disable secure boot

 

[Ralston18]

This:

"eveything work fine for 2 or 3 days then the system refuse post untill i reset the bios"

That is a good pattern to work from.

Look in Reliability History/Monitor and Event Viewer for error codes, warnings, and even informational events that match that pattern.

Look in Update History as welll.

Another suggestion: After the next BIOS reset also enable Verbose Mode (the name/setting can vary).

What Verbose Mode does is display what the system is doing during boot up.

Simply watch each boot up as carefully as you can. You may discover some change or problem in the boot process that will prove helpful.

Try with Secure Boot enabled and disabled.