I understand.
I've deleted the offending software and am no longer using it. I assume that this will revert the changes in the logs as I don't know how to fix that (this software was installed by someone else).
Thank you for warning and letting me know.
This is the advice given in the thread you recommended if dump files are not being created. I've done every one of them except the page file base allocation. I have a 32GB ram, so that part shouldn't be an issue I guess.For dumps to be produced The following should be correct
Page file must be on the same drive as your operating system
Page file base allocation size must be greater than installed physical RAM
Windows Error Reporting (WER) system service should be set to MANUAL
Set page file to system managed on the OS drive
Set system crash/recovery options to "kernel memory dump"
User account control must be running.
Sometimes SSD drives with older firmware do not create DMPS (update firmware)
Cleaner applications like Ccleaner delete DMP files so don't run them until you are fixed.
Moreover like I've said before, I have got dump files when I force crashed the system using WhoCrashed. Just that when my system naturally crashes, it doesn't create one.
This time, I was watching a movie and it crashed again when I plugged in my earphones. Although, this is the first time this has happened to me and after the crash, when I plugged in my earphones, nothing happened. I got the blue screen, and since it was stuck on the blue screen for a long time (the previous thread advice told me to disable automatic restart), I took a picture of the blue screen. And yea, it didn't create a dump file either.
I'm starting to think this could be a RAM or memory issue, but have no evidence for it.
Attachment 248017
I believe this is more of a 50/50 between RAM and the hard drive, because the 0x7A is more commonly caused by a bad drive (depends actually on the second parameter of the crash (error status) which is most often an I/O error).
There is a diagnostic test you can perform which is able to test pretty much every hardware part in the laptop.
When you're booting, just before Windows starts to load, you see in the bottom of the screen a few keys you can press to enter the BIOS or to go to the boot menu. Press F12 to go to the boot menu when you see the keys.
In the boot menu you have an option 'Diagnostic Test', or something similar, choose that option. Although it is just a brief test, it may take some time to run.
After the brief test is finished you should get an option to run an extended test, I recommend to run it. Be aware that this extended test can easily take a couple of hours.
Limited crash data is pointing out to Realtek HD Audio driver, and yours is very dated:
RTKVHD64.SYS (6.0.1.7628, 4.41 MB (4,622,592 bytes), 09-03-2016 09:41 PM)
Worth getting it updated to eliminate the obvious culprits:
Latest Realtek HD Audio Driver Version [2]
I've been through the same myself - out of blue and for a good few months - and BSODs mysteriously and suddenly just stopped one day. And never returned despite me never changing / tweaking anything substantial.
I never believed that hardware could be a problem (new PC etc.), so it must have been either dodgy device driver, or then-installed Windows 10 release that simply wasn't stable (think about all these Intel vulnerabilities and microcode updates released over the years!).
Realtek equally is not renowned for the stability of their device drivers (for both audio and network devices) - the testament is rather short lifespan of each driver's version (usually couple of months at most). So in my view and based on rather limited data here (no DMP files available) it's definitely something worth giving a shot.
Just my two-pence.
EDITED TO ADD:
This sentence from the first post prompted me to look at details more closely:
When I got it, my cousin installed DriverPack in my computer and when while updating some drivers, it crashed for the first time
I have never had problems with Realtek drivers or their stability. An error code indicates a disk malfunction. And the fact that Realtek's driver was guilty may be due to the fact that the driver was in a place where the bad sector is (maybe because of that the driver has even been damaged)
Well, disk has been checked apparently - I've not seen the results myself but OP claims all was well. So I daresay issue lies elsewhere - would not trust MS codes & explanations too much without looking into DMPs...
Thus I agree with OP and would still pursue investigative avenue and try to narrow down the issue itself - so far there's nothing concrete to put finger on, it could be anything.
And whilst being here: I would suggest that whole this lot:
https://www.dell.com/support/home/us...laptop/drivers
is checked and installed either (It is XPS 15 9550, isn't it?) Dell is quite good at releasing/publishing updated drivers quite regularly and I can see another key obsolete driver on the current list already:
Intel(R) Management Engine Interface 1828.12.0.1152
https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverid=9c4p7&oscode=wt64a&productcode=xps-15-9550-laptop
Version 1846.12.0.1177, A03
OP claimed that the disk tested and there were no errors, but we did not see the actual results. And in the picture with the blue screen we only see the error code "KERNEL_DATA_INPAGE_ERROR", and we do not see these 4 parameters (although it is possible to enable them on the blue screen https://support.microsoft.com/en-us/...een-in-windows). Maybe the driver is guilty, but I bet
that this driver was in the wrong place at the wrong time
Quote