Irregular BSODs for many months.

DrakeJen said:

There are multiple download links here. Which one do I download?

The first one, SetupRST.exe

DrakeJen said:

Is this necessary? My cursory google searches indicate that and AHCI setting is better. I don't even know what it is and what they do, but I'm don't want to tweak aroung the settings too much unless they are absolutely necessary.

Well, you don't have much to lose, have you? Besides,, I do not have any more recommendations I'm afraid. Also, as I wrote: The fact that DMP file is not written upon each crash on greenfield (nearly) system is highly suspicious and quite telling... To my eyes it may be pointing out to something dodgy on controller <-> SSD front.

Finally, I've always been using Intel RAID / RST drivers and never had any problem with it.

DrakeJen said:

And as for the last one, I don't know which AHCI/RAID driver is the one for my pc.

Leave it for the time being.

- - - Updated - - -

There's been newer version of RST (17.7) released just over the last couple of days:

Download Intel(R) Rapid Storage Technology (Intel(R) RST) User Interface and Driver

Intel(R) Rapid Storage Technology (Intel(R) RST) User Interface and Driver

@krzemien
I've installed the RST driver (the updated one) and left the AHCI/RAID issue for now as suggested. Will wait for further developments.

@hawkman
At this time, I'm open to any suggestions. But as we're on the subject of battery, let me tell you that battery life on this is quite well. Nothing out of the ordinary. I get 5-7 hours of normal usage in a single full charge. But that being said, I rarely use the laptop battery and it's always kept charging.

Good.

Check also this post:

BSOD During everyday Usage

krzemien said:

Good.

Check also this post:

BSOD During everyday Usage

Sorry, but I don't exactly understand what it is I need to be doing in the final advice you gave in that thread. I made my battery settings into high powered. Is there anything else?

Also, new bsod

The next thing we want to do is disable Link Power Management in the IRST control panel. Link power management increases I/O latency, resulting in lower performance, which is why we want to disable this feature. Link Power Management is found by clicking the performance tab in IRST control panel.

After disabling, you must restart your system for the change to take effect.


What was the bug check (error code) this time?

Also, am I right in saying that you get these BSODs once your laptop was put to sleep for some time?

Finally, did you try disabling Fast Boot (not sure if it was mentioned earlier in this thread)?

How to disable Windows 10 fast startup (and why you'd want to) | Windows Central

- - - Updated - - -

Also, would you mind downloading this utility?

Download – Crystal Dew World

Direct link:

Downloading File /71535/CrystalDiskInfo8_3_1.exe - CrystalDiskInfo - OSDN

And run it & paste the main screen?

Attachment 250844

Also, can you open Device Manager, sort the view by connection, and paste the main screen, concentrating on the branch with SSD/NVMe controller and disk drive?

Attachment 250845

And from there demonstrate the driver that SSD/NVMe controller uses?

Attachment 250846

Hey guys.
I just want to say that I think the method @krzemien recommended in a thread he referred to earlier finally did the trick. Literally all I did was change the power plan from balanced (which was the default options) to high powered (my custom plan).

That and this below.

The next thing we want to do is disable Link Power Management in the IRST control panel. Link power management increases I/O latency, resulting in lower performance, which is why we want to disable this feature. Link Power Management is found by clicking the performance tab in IRST control panel.

But as I remember the setting was already disabled.
So that means it was the power option that should've helped. The reason I took this long to respond was that I simply couldn't believe that something as simple and stupid as this was what causing the blue screens. I still can't believe it. But the whole thing stopped as I changed the power setting. And I don't think I did literally anything else. I was careful about making sure that I did things in batches so that I could narrow down to what finally solved the problem.
And I think this finally did it.

I want to thank every single one of you for giving the time and effort you gave towards this. You really saved my life. I wasn't able to work and was extremely worried about this problem and didn't have the money or means to get a new computer. I hope anyone reading this thread will help solve any other XPS user who would go through something like this.
Again, I can't believe the solution was something this small and simple and stupid.

Ha!

(thinking about suitable response here really...)

It's great that it has worked for you, somebody I quoted here earlier before and possibly even myself as well. Keep an eye on things though.

Questions still worth asking are: what is actually the issue here exactly? And why it does manifest itself in this way? And why people do come across it all the time? And why OS allows for such instability regardless of its version / build and despite all built-in telemetry? Etc.

Questions still worth asking are: what is actually the issue here exactly? And why it does manifest itself in this way? And why people do come across it all the time? And why OS allows for such instability regardless of its version/build and despite all built-in telemetry? Etc.

I thought you would have the answer to these questions being the genius here :P
I swear man. I wish I could know. No seriously. If anyone else finds out the answer, do tag me and let me know. Because this is one of the most perplexing problems I've encountered in my life only to be solved by something so silly. Is there a way to alert Microsoft or whoever about the problem which apparently many people have encountered? Very very strange.