Windows 10: Constant crashing with and without BSOD.

Hello!I recently acquired a new computer, just last month.Within the first week i've been having constant crashes at random intervals, with and without the BSOD.It's always related to error code volmgr 161, followed by Kernel-Power 41.I've tried looking for similar problems and fixes, but since im having trouble finding a solution i was hoping i might get help here.Here you can find the most recent minidump file: https://drive.google.com/drive/folders/1EnqiZe7erdNwJLs7l2TIdKWTEcYYRLJn?usp=sharingRegardKristian

:)

 

KernelBase.dll is broken constant BSOD's constant game crashing.

Hi Darry,

User Profile corruption is one of the possible reasons why you are experiencing constant BSOD's on your computer. You mentioned that you ran the
System File Checker (SFC) tool, but is still getting a stop code. To further troubleshoot the issue, we suggest that you create a new User Profile and check if the issue persists.

To create a user profile, follow these steps:

• Go to Settings. Click Accounts.
• Select Family & other people.
• Select the Add someone else to this PC tab.
• Name the user as Test.
• Leave the password field blank.
• Hit Next.
• Sign in as Test user.

You may also check this link
to fix BSOD errors. Choose the situation when you experienced the problem and follow the troubleshooting steps.

 

Constant BSOD and Random Crashing

I'm sorry to hear about the issues you're facing with your computer. Random crashes and Blue Screen of Death (BSOD) errors can be frustrating to troubleshoot, but analyzing minidump files can provide valuable information about the underlying causes.

Unfortunately, as a text-based AI model, I'm unable to directly access or analyze files or attachments. However, I can provide you with some general guidance on how to analyze minidump files yourself or suggest alternative troubleshooting steps.

1. Analyzing minidump files:
   
   • To analyze minidump files, you'll need a debugger tool like WinDbg, which is part of the Windows Software Development Kit (SDK). Install the SDK and WinDbg on your computer.
     
   • Open WinDbg and go to "File" > "Open Crash Dump." Browse and select the minidump file you want to analyze.
     
   • WinDbg will load the minidump and display information about the crash. Look for the error message or the faulting module that caused the crash. This information can help identify the potential cause of the problem.
     
   • If you're unfamiliar with WinDbg or analyzing minidump files, you can search for specific error messages or faulting modules online or seek help from forums and communities dedicated to Windows troubleshooting.
     
2. Alternative troubleshooting steps:
   
   • Since you suspect faulty RAM, testing it with new RAM modules is a good step. Faulty RAM can cause various stability issues, including crashes and BSOD errors. Consider ordering new RAM and replacing the existing modules to see if it resolves the problem.
     
   • Ensure that all your drivers, including motherboard chipset drivers, graphics card drivers, and other hardware drivers, are up to date. Outdated or incompatible drivers can lead to system instability.
     
   • Monitor your computer's temperature using software like HWMonitor or Core Temp. Overheating components can cause crashes. Make sure your computer's cooling system is working properly and clean any dust buildup on the CPU cooler and other components.
     
   • Check for any recently installed software or drivers that may be causing conflicts. Uninstalling or rolling back recent changes can help isolate the problem.
     
   • If the issues persist, you may want to consider seeking assistance from a professional computer technician or contacting the customer support of your computer's manufacturer.
     

Remember to always back up your important data before making any major changes to your system or replacing hardware components.

I hope these suggestions help you in troubleshooting and resolving the issues you're experiencing with your computer.

 

Constant BSOD crashes

Post #6 had the details for drive testing.