irregular BSODs after resume from sleep

Nox997 · 24 Aug 2019

Hello @axe0,

thank you for your help!
I was not able to complete 8 passes overnight - 2 passes already took 7hours.
Anyhow, I am attaching two photos of two runs, one for 7hours, one for roughly 5hours.
I will try to run it for 8 complete passes soon.

Btw, should I use the option to enforce SMP? My first run was made without, the second with it.

One remark: I never had issues with my PC in high power. Zero - in several years.
Only after resume from sleep.

Screenshots are attached.
Attachment 244300
Attachment 244299

jdc1 · 24 Aug 2019

Memory is not only in your RAM
Prime95 stresses CPU cache and the memory controller: Prime95 - Stress Test Your CPU

There’s also memory on the video card. I suggest the Furmark stress test for that: FurMark 1.20.8.0 Download - TechSpot

axe0 · 24 Aug 2019

Furmark isn't needed (yet), because there's nothing in the dumps showing anything related to video memory.

jdc1 · 25 Aug 2019

I'm not familiar with video memory, nor am I familiar with the way that the video card interacts (if any) with other memory.
I suggest that test simply because it's another data point - and it will come in handy later on (if hardware diag's progress that far).

Nox997 · 03 Sep 2019

Hello,

update:

I did not do any further MemTest86 runs after the screenshoft that I have posted
Tried a different graphics card - a 1050Ti - BSODs persisted
I did remove two memory modules at a time and was not able to reproduce the bluescreens after wakeup. Only with all 4 modules, I was able to reproduce the bluescreen. This led me to the next point
The complete RAM was exchanged with 4 other sticks (same frequency & timings, different manufacturer - Corsair) from a colleague for a tryout. I thought at first that this solved the issue, however a bluescreen occurred again.
The last thing I did was to change one BIOS setting: "Power Loading" to "Enabled" instead of "Auto". No Bluescreens since then

I now hope that the "Power Loading" really fixes the issue. Will post an update in a few days when I can be rather certain that no BSODs are occurring anymore.

I conclude that the RAM is therefore not the issue, neither the graphics card.
What remains in my opinion is

CPU
Mainboard
Power Supply
Hard Disks

What are your opinions / conclusions from my experiments?

Edit: attached most recent BSOD zip with different RAM - just in case it shows something different this time
(ISILDUR-(2019-09-03_06-37-17).zip)

axe0 · 04 Sep 2019

Sounds like a power issue, I don't know how power loading works exactly, but from what I do know it is suggested to enable it when a system suddenly shuts down as a self-protection mechanism against low power.

Nox997 · 08 Sep 2019

Hello again,

with Power Loading enabled, I was not able to reproduce a BSOD until I enabled "Hybrid Sleep" again. With Hybrid Sleep enabled, I had two BSODs in the last days.
Could you please have a look at the logs and see if they unveil anything new?

Thank you very much in advance for your help.

axe0 · 09 Sep 2019

Please run driver verifier using the following settings for 48 hours.

Special Pool
Force IRQL checking
Pool Tracking
Deadlock Detection
Security Checks
Miscellaneous Checks
Power framework delay fuzzing
DDI compliance checking

Warning: driver verifier could cause boot issues and/or performance issues.

Make sure that you have recovery media, if needed you can create it.
Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)

In normal mode open an administrator command prompt and enter the below command
In safe mode open an administrator command prompt and enter the below command
On 3 boot failures, you'll boot automatically to the recovery options,
- click Troubleshoot
- go to the advanced options
- choose command prompt
- enter the below command
Boot with the recovery media, see above 4 steps in option 3.
Via the recovery options or recovery media, select a restore point prior enabling driver verifier

Code:

verifier /reset

Crashed when running driver verifier

Reset driver verifier
Boot in normal mode if necessary
Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

Extra information about driver verifier
When you run driver verifier, there are two things you're looking out for
1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
2. Driver verifier will find a driver violating something and thus the system will crash.

The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.

Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt

Code:

verifier /query

If the command gives a result similar to this, it means driver verifier is running.

Nox997 · 23 Sep 2019

Hi @axe0,

I started with the driver verifier run today and have two questions about it:
1) does the PC have to run the entire time?
2) Should I provoke BSODs by putting my PC to sleep and wake it up again?

thank you very much in advance.

axe0 · 23 Sep 2019

Practically the PC doesn't have to run the entire time, so long as driver verifier's settings aren't reset it will continue to run on the next boot.

Preferably provoke BSODs yes.

Something that comes to mind, it sometimes happens that when driver verifier is enabled the usual trigger for BSODs doesn't work. There's really a small chance that it will happen, I've only seen it a few times out of hundreds, but still something I thought you'd want to know in case it happens, i.e. don't be surprised if trying to provoke a BSOD doesn't crash the pc.