So how can we confirm the source of the problem? Isn't it possible to see what's the cause from the dump files?
Btw, there are threads with similar problems (bsod w/ no dump files created) and in one thread the problem was a faulty motherboard.
Oh, and sometimes my system just freezes, without a bsod. Maybe this can be a clue?
I would suggest to replace the CPU.
When it comes down to hardware a dump usually doesn't give much if it is not memory related.
That is also possible yes, but the motherboard is usually 1 of the last things to look at.
System freezes could be caused by many things, from drivers to software to hardware.
Before I replace the CPU, could you please take a look at these new dump files?
Windows has been crashing a lot, and giving a few new errors. Most bsod's occur when trying to install the system update readiness tool (to try and finish the win update that keeps failing) and when I render a video in Adobe Media Encoder.
I updated every driver, the BIOS, I set the RAM to the correct frequency in the bios, changed the min powersetting on the cpu to 50%, but all to no avail. I don't really see a connection between the cpu and installing windows update.
Too much of dumps to go through now, but looking at how many different stop codes there are it has some meanings.
When there are many different stop codes with many different causes it usually means that there is a hardware problem (from experience said)
Most occuring I noticed is 0x101 which is by myself known for a hardware(related(drivers, dust, overheating, etc.))/bios crash.
My system is now stable, haven't had a single crash in 36 hours. The windows system readiness tool, that used to freeze/bsod my pc, is now actually installed (I let it run overnight), and I can use After Effects and Media Encoder without crashing, even when rendering.
Here's the only thing that I did: I started the Driver Verifier and selected every driver except the microsoft ones. That's it. Weird, as it's supposed to stress-test the drivers untill it crashes right? Well, it's doing the opposite.
When I turn the verifier off (delete the settings) my system becomes unstable again and crashes constantly. I get a couple of one-second freezes every now and then, at times when I used to get bsod, but it only lasts a second.
So there we have it I guess.. time to return that replacement cpu I just bought lol
I'll keep testing this for the coming days/weeks to see if it's really resolved now.
Actually not very weird, sometimes driver verifier is used to get the system more stable to be able to troubleshooting.
So I got another BSOD again, which means the verifier thing wasn't a permenant solution (also my system got a little slow, especially at startup)
So last week I replaced the CPU with the new one I bought, and the problem is gone completely! Aparently it was a hardware problem, not software.
Thanks for all the help, axe0
Driver verifier is not meant as a solution to prevent crashes, so it is never permanent, not sure why you thought that.
Quote