Windows 10: Frequent BSOD, the dump file is never created

Unfortunately, I frequently experience BSOD on my laptop. The drivers are up-to-date, as is the BIOS version. I have reinstalled the system multiple times, but the BSOD still appears.I have also run the memTest86+ program several times for 12 hours, but it never found any errors.I don't know what could be causing this, but I would like to claim warranty for my laptop.However, this won't be possible because the issue is not frequent enough for the service center to observe it during their inspection.Another important point is that a dump file is never created. I have already set it to create

:)

 

BSODs with no dump file created

I get a UNEXPECTED_STORE_EXCEPTION bsod whenever I'm playing Apex Legends or while using Origin launcher.The the main issue I'm facing is that there are not dump files created after this bsod.I have setup my dump config according to this thread:Intermittent BSODs with no dump file created
I also tested it using a manual crash in Who Crashed and the dump was successfully created for this crash but it doesnt work for UNEXPECTED_STORE_EXCEPTION. Please help

- - - Updated - - -

Can anyone suggest any ways I could solve this please

 

Driver verifier not creating dump file

I'm getting frequent BSOD. I started the driver verifier as suggested.

At first, windows stuck at the boot loop, It didn't even show any BSOD. It just kept booting and turning off again and again. It didn't go past motherboard logo.

After some changes in the verifier, It was able to show windows logo but crashed before fully booting to "Driver verifier detected violation"

And it didn't even create any dump file. (All dump file setting are correct one ) As it is known that a driver is causing BSOD. How to know which one?

 

Windows 11 BSOD error with not creating dump file .

I have turn on Driver verifier as per your suggestion. If I get an error again, I will see if a new dump file has been created. If so, I will give it. BSOD stop code is unexpected store exception and another thing is that I went to the event viewer and got some information such as BugCheckCode 340 .