Recent content by ubuysa

No lights at all on the motherboard? It's likely the motherboard then. Give it a good blow out with a blower - not your mouth! - paying particular attention to the RAM and PCIe sockets. Check that all power connectors are good. I don't know what else to suggest.

The Qualified Vendor List (QVL) is a list of RAM that has been tested and verified as compatible with the motherboard and CPU combination. Other RAM may work perfectly fine, but IMO it's always wise to stick with QVL RAM because you know that it's compatible. It's also not wise to seek help...

A spark! Wow, never seen actual sparks myself. That would ring all the alarm bells for me. I really would try removing one RAM stick at a time. One other thing; your RAM is not on the QVL for the CPU/motherboard. That's often not a worry, and clearly the RAM has been working fine for some time...

I'm sorry I'm late to this, I have a lot going on at the moment. The triage analysis in those two dumps does finger nvlddmkm.sys as you rightly say, but the tirage analysis isn't always right. There is another feature of both dumps that concerns me; a checksum mismatch... *** WARNING: Check...

I'm sorry I'm a bit late to this, I have a lot going on here. I note that in post #5 you were asked to run Memtest86 and in the recent dumps that you just uploaded I am also of the opinion that bad or mismatched RAM is the likely problem here. I actually find it difficult to understand exactly...

Do you have Driver Verifier enabled as requested in post #7?

@adri95 please start your own thread.

Your problem is almost certainly a networking driver in AdGuard. We see it called several times immediately before the page fault that causes the BSOD (read this from the bottom up)... ffff9586`0faabea8 fffff802`6c425f89 nt!KiPageFault+0x489 ffff9586`0faabeb0 ffffce01`4f60a202...

As I said at the start, it's VERY common for anti-cheat tools to cause BSODs. We see it again and again. Sadly, as you say, it's their problem and only they can fix it.

I think your battery may be dying. The laptop appears to have been on mains power pretty constantly in those reports so it's hard to get meaningful battery info from them, but the interesting one is the System Power Report. If you look at entries 74 and 75 you can see in entry 74 that the...

Sorry for the delay, I have a lot going on at present. Well bddci.sys and tib_mounter.sys are not in that list, so I can only assume that the dumps I looked at were from before BitDefender and Acronis were uninstalled? How is it behaving now?

In the dumps I'm seeing misaligned instruction pointer, invalid opcode fault, and illegal instruction execution attempt. If it were not that this only happens on battery I would be looking first at RAM. However, since it does only happen on battery we need to look first at your battery. Open an...

Oh that's interesting, I didn't know that. You learn something new every day! @callofdemons please open an elevated PowerShell session and enter the following command.... DriverQuery | Out-File C:\drivers-callofdemons.txt Then upload the file drivers-callofdemons.txt that you'll find in the...

The BitDefender driver is bddci.sys, it's loaded in all but one of the dumps you just uploaded, and it's old... 11: kd> lmDvmbddci Browse full module list start end module name fffff803`90f30000 fffff803`90f89000 bddci (deferred) Image path...

Firstly, can you please follow the BSOD Posting Instructions. There is other troubleshooting data that may be useful here. Secondly, the CRITICAL_PROCESS_DIED bugcheck is most usually caused by a hardware problem. The BAD_SYSTEM_CONFIG_INFO bugcheck indicates an error in the registry. The...