Windows 10: BSOD and other crashing issues.

For the last couple of months I've noticed my PC crashing more and more frequently, I've checked administrative events on my event-logger and noticed a bunch of warnings/errors, I'm not a professional at reading these but I wanted to post some of the things I found here to hopefully get an indication of what is faulting.I've tried scanning for malware, doing a sfc /scannow, GPU and Windows updates and nothing seems to fix it.Error 1Faulting application name: dwm.exe, version: 10.0.22621.3672, time stamp: 0x85e98d33 Faulting module name: ntdll.dll, version: 10.0.22621.3733, time stamp: 0x67ca88

:)

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

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.

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.