Windows 10: Got a BSOD while gaming on new built. Decided to update bios and also analyze crash dump...

10: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_MODE_HEAP_CORRUPTION 13aThe kernel mode heap manager has detected corruption in a heap.Arguments:Arg1: 0000000000000017, Type of corruption detectedArg2

:)

 

BSOD on new computer while gaming

I just got a new computer about a month ago. Everything is new and I get BSOD (windows 10) while gaming mostly although it sometimes happens while I'm just using the computer. Sometimes the computer doesn't BSOD and just gives me a Access Violation Error. Not sure if related.

Here is the link to download output files from the V2 script.

Dropbox - windows crash - Simplify your life

Any help is appreciated

Steps I have taken:

• Updated all drivers and bios to latest versions

• Checked ram with windows memory test to see if ram is faulty. (A stick was and it was removed waiting for replacement)

• Clean Installed Windows after finding faulty ram

• I had 2 x 2080Ti installed, I removed one, tested and then swapped cards; issue still exist

 

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.

 

What to do when Windows can't get the BSOD crash dump?

So I'm running windows 10 on a Toshiba Satellite P50t-B10T laptop and getting the infamous DPC WATCHDOG VIOLATION error. The usual procedure seems to be to take the memory dump and analyze it to see which driver is causing the error.

Unfortunately, on my laptop, it gets stuck in the collecting info phase at 0% seemingly forever, as in doesn't move above 0 percent for hours and hours. If I forcefully shut it down, there is no dump to be found.

So far, this issue only occurs with the watchdog error. If I cause another type of BSOD, I get normal dumps.

So my question is: How do troubleshoot the non-generation of crash dump?

UPDATE:

Well finally something new happened. The laptop managed to restart itself after BSOD. Turns out, when it restarts itself, it won't detect its own hard drive. I need to shut it down and let it wait for a while before turning it on again. Then, it detects the HDD fine.

The BSOD only happens when playing games for a while. On the other hand, I don't think that overheating is an issue, since the system temperature doesn't go above 85 C and fan doesn't go above 85%