XPS 9550 Blue Screen Error

[Jajumulaka]

I've been getting blue screen errors for months now. For the longest time, I've been doing trial and errors and thought the ram might be defective. But after a memtest and alternating between my two rams, I can now guarantee that my ram is just fine.
I've updated all the drivers and did everything I can. But something somewhere is not right. For some reason, my computer doesn't create a dump file. When it goes to a blue screen, it quickly shows the error and then restarts without loading from 0 to 100%. When it does load though (like 2% of the time), it creates a dump file. I've saved one of those and ran it through WinDbg.
Here is the dump file and
here is the debugged info text

Since I copy pasted the result, I'm not sure I copy pasted the whole debugged result. But I think everything's there. Just letting you know.

Please help me. I'm running out of ideas with what to do with this.

 

[Saltgrass]

If you have a small dump file you can zip and attach it directly. The Memory.dmp file is normally too large.

The link to the file you have posted does not work for outsiders.

 

[BigFeet]

If you don't want the PC to restart automatically on BSOD......
https://www.lifewire.com/how-do-i-disable-automatic-restart-on-system-failure-in-windows-2626067

 

[Jajumulaka]

If you have a small dump file you can zip and attach it directly. The Memory.dmp file is normally too large.

The link to the file you have posted does not work for outsiders.

Oh I'm sorry. I've done it here. Both the text file and the dump file.

 

[Saltgrass]

I am not the expert on reading dump files but it appears it is related to an NTFS situation. It is showing an NTSTATUS 0xd8cf8080 which I will have to look up.

It does mention a volume number in the report so you might put the following line in a RUN box and see if it open a partition in File Explorer. Use the entire number from the first \ to the last \. If that doesn't work, open an admin command prompt and type the command below to see if the number shows up in that listing.

\\?\Volume{8a376083-e48d-11e8-98d9-806e6f6e6963}\

mountvol

 

[Saltgrass]

You might tell us about your system configuration involving your drives and what types you are running. Have you made any changes to the default SATA controller settings?

You might check for an update to the Intel RST driver.. iaStorAC.sys Tue Feb 12 08:12:09 2019 which does appear to be the latest one.

You can check the link to see if anything might help. The suggestion to check the Event Viewer may allow you to find a repeating error showing up which could help.

Bug Check 0xEF CRITICAL_PROCESS_DIED - Windows drivers

Learn how the CRITICAL_PROCESS_DIED bug check has a value of 0x000000EF and indicates that a critical system process died.

docs.microsoft.com

You do have the QualComm driver, Qcamain10x64.sys, which folks have complained about but I see nothing in the dump file which would indicate that driver is involved.

 

[Jajumulaka]

I tried updating the RST driver. It was outdated like you said, but that didn't solve the issue. I've kept the computer in safe mode for about 20 hours and it didn't crash. Usually, in that timespan it crashes atleast once. According to experts, that means we can rule out Hardware and core windows drivers.
But I'm still clueless on how I'd narrow the problem down.

Do you think a full reboot would help? I've already done a clean install before and it didn't help. Would formatting my computer do anything different?

 

[Saltgrass]

You can use msconfig.exe to set your system to run in a diagnostic mode. Set it back to a normal boot then go to the Services tab. From there, you can hide all Microsoft services by checking the box.

Then you can disable all services shown and then start checking some for testing. For instance, the first run select 50% of the services and see if your system blue screens. If not select more or select the other 50%. If it does blue screen, start unchecking services until it stops that behavior. If it is a driver you should be able to pin down the exact service.

Did you see any reocurring events in the Events Viewer? Did you find out which partition was being mentioned in your Dump files? I would keep an eye on the drive, just in case.

 

[Jajumulaka]

You can use msconfig.exe to set your system to run in a diagnostic mode. Set it back to a normal boot then go to the Services tab. From there, you can hide all Microsoft services by checking the box.

Then you can disable all services shown and then start checking some for testing. For instance, the first run select 50% of the services and see if your system blue screens. If not select more or select the other 50%. If it does blue screen, start unchecking services until it stops that behavior. If it is a driver you should be able to pin down the exact service.

Did you see any reocurring events in the Events Viewer? Did you find out which partition was being mentioned in your Dump files? I would keep an eye on the drive, just in case.

View attachment 10334

Hmm. Thank you for your replies and interest. I'll try out these methods and obviously as you understand it'll take some time and trial and error. So give me some time to test my drivers out. I'll post when I'm done probably in another 10-15 days. Do keep an eye on this thread.