Solved Getting BSODs on Win 11 laptop.

[brambedkar59]

Briefly explain your current issue(s)

getting BSOD

Steps taken to resolve, but have been unsuccessful

changed AVs, ran sfc /scannow, updated graphics drivers

Since last month or so I am getting frequent BSODs on my Win11 (22621.1265) Laptop (Asus Tuf F17 FX706HE BIOS: 311). It's never the same error. I have attached last 2 dump files in this link.

So far I have changed AVs (Malwarebytes, Emsisoft and now on Bitdefender), ran sfc /scannow, updated graphics drivers (now back to drivers from Asus website) but nothing seems to work.

Thanks for your help. Let me know if you need more info.

Edit: I checked with Whocrashed it says this:

Bugcheck name: DPC_WATCHDOG_VIOLATION Driver or module in which error occurred: intelppm.sys (intelppm+0x156f)

Edit: 2
BlueScreenView says ntoskrnl.exe caused crash. Dunno which one is right.

Edit:3 Things ruled out so far-
1. AV (happens with MB, Emsi BD, Defender & no AV)
2. Ram module (Windows Memtest came clean)
3. Corrupt system files (sfc /scannow came clean)
4. Undervolting by ThrottleStop (happens even when task is disabled)

 

[ForgottenSeer 98186]

Answer Line: Can a BSoD hurt my computer?

zyrrahXD asked the Windows forum if a Blue Screen of Death can severely damage a PC.

www.pcworld.com

A BSOD nuked this MalwareTips member's machine. So it is possible.:

Solved - veracrypt broke my Cpu and ssd

I was encrypting my C drive with veracrypt when the pc had a bsod

malwaretips.com

 

[oldschool]

@brambedkar59 Nowhere in this thread have I seen you tried to diagnose with DISM. When was the last time your machine was OK? Have you tried a factory reset?

 

[brambedkar59]

@brambedkar59 Nowhere in this thread have I seen you tried to diagnose with DISM.

You mean this cmd "DISM /online /cleanup-image /restorehealth"? I didn't ran it earlier because "sfc/ scannow" didn't find anything. DISM cmd checks for the health of windows component store and not the actual system files (It is basically the backup against which sfc cmd checks the system files). If sfc doesn't find anything I don't see the point of running DISM.
Well I ran it just now for fun, didn't find anything.

@brambedkar59 When was the last time your machine was OK? Have you tried a factory reset?

Don't have an accurate date but this issue started around a month ago. BSODs were not that frequent earlier so I mostly tolerated them. I would clean install (or restore a clean image) if this is not fixed in the next two weeks. I am feeling confident that this Realtek Ethernet driver was the real culprit.

A BSOD nuked this MalwareTips member's machine. So it is possible.:

Solved - veracrypt broke my Cpu and ssd

I was encrypting my C drive with veracrypt when the pc had a bsod

malwaretips.com

BSOD is just a symptom of hardware/software failure, not the actual problem. Just like fever in humans is not the actual disease just its symptom. In this case the OPs hardware must be dying due to some other issue.

 

[oldschool]

You mean this cmd "DISM /online /cleanup-image /restorehealth"? I didn't ran it earlier because "sfc/ scannow" didn't find anything. DISM cmd checks for the health of windows component store and not the actual system files (It is basically the backup against which sfc cmd checks the system files). If sfc doesn't find anything I don't see the point of running DISM.

It sometimes find things for me that sfc/scannow doesn't. That's why I asked. BTW: I usually run DISM /online /cleanup-image /checkhealth.

Well I ran it just now for fun, didn't find anything.

oh well ...

I would clean install (or restore a clean image) if this is not fixed in the next two weeks. I am feeling confident that this Realtek Ethernet driver was the real culprit.

Sounds good.

 

[Abdel-Rezak]

Are you usig Shadow Defender, it gave me BSOD's the last 2 or 3 times I tried it.

NO, if you want to use shadow defender( Windows 11), reboot your system and try again and it should be fine.

 

[ForgottenSeer 98186]

BSOD is just a symptom of hardware/software failure, not the actual problem. Just like fever in humans is not the actual disease just its symptom. In this case the OPs hardware must be dying due to some other issue.

Hey man, it's your laptop and you can believe whatever you wish, but let's keep it real and factual, OK?

A BSOD results in a sudden power cuttoff - which can damage hardware. In the microseconds around the sudden power cuttoff, spikes in voltage and amperage happen - which are the real cause of hardware damage. A power surge almost always happens during a sudden power cutoff. This is a basic fact of Electrocircuits 101.

This is the very reason that OEMs recommend power backups and surge protection.

Using the source you are using as a reference that "BSODs cannot cause hardware damage":

NOTE: For the sake of keeping it real, a sudden power cutoff caused by a BSOD has the same effect on hardware as a sudden power cutoff caused by the electrical supply. Hardware damage can result both from an internal as well as external power cutoff.

What to do when a power outage or surge damages your PC

A power outage can be bad for your PC, but a power surge can severely damage your hardware. In all but the worst cases, however, you should be able to revive the PC, or at least retrieve any files stored on it.

www.pcworld.com

 

[wat0114]

@brambedkar59

have you checked the temperatures of your hardware? There's a free utility, amongst others available, I use called CPUID HWMonitor that displays several hardware-related temperatures. It needs to be run with Admin privileges to be most effective.

HWMONITOR | Softwares | CPUID

HWMonitor for Windows® x86/x64 is a hardware monitoring program that reads PC systems main health sensors : voltages, temperatures, powers, currents, fans speed, utilizations, clock speeds ... The program handles : CPU and GPU-level hardware monitoring...

www.cpuid.com

 

[Malleable]

You mean this cmd "DISM /online /cleanup-image /restorehealth"? I didn't ran it earlier because "sfc/ scannow" didn't find anything. DISM cmd checks for the health of windows component store and not the actual system files (It is basically the backup against which sfc cmd checks the system files). If sfc doesn't find anything I don't see the point of running DISM.
Well I ran it just now for fun, didn't find anything.


Don't have an accurate date but this issue started around a month ago. BSODs were not that frequent earlier so I mostly tolerated them. I would clean install (or restore a clean image) if this is not fixed in the next two weeks. I am feeling confident that this Realtek Ethernet driver was the real culprit.


BSOD is just a symptom of hardware/software failure, not the actual problem. Just like fever in humans is not the actual disease just its symptom. In this case the OPs hardware must be dying due to some other issue.

MS lists DISM first.

Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support

Describes how to use the System File Checker tool to troubleshoot missing or corrupted system files in Windows 8.1, Windows 8, Windows 7 or Windows Vista.

support.microsoft.com

 

[show-Zi]

If it is caused by hardware failure, I think it happens frequently.

Have you tried resetting your COMOS Clear and UEFI settings? It seems irrelevant and tends to be omitted in times of trouble, but it can sometimes pay off.

 

[Pico]

When stable and clean mains voltage / power is supplied to a good quality PSU with proper load ratings then the PSU delivers stable voltages to motherboard even in case of BSODs when PSU load may fluctuate.

 

[brambedkar59]

MS lists DISM first.

Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support

Describes how to use the System File Checker tool to troubleshoot missing or corrupted system files in Windows 8.1, Windows 8, Windows 7 or Windows Vista.

support.microsoft.com

Yes, you are right MS lists DISM to be ran before SFC. But if SFC is showing a corrupt file that it can't replace it usually means Windows store component is corrupted. Then it makes sense to run the DISM cmd. At least that's how I understand these tools work.

If it is caused by hardware failure, I think it happens frequently.

Have you tried resetting your COMOS Clear and UEFI settings? It seems irrelevant and tends to be omitted in times of trouble, but it can sometimes pay off.

I haven't tried resetting UEFI settings yet. Dunno about resetting CMOS on a laptop.
Edit: Laptop battery is non-removable

 

[CyberTech]

This only happens to me due to RAM issues, did you try to remove RAM so clean up and put it back in? if it's same problem then try different RAM. however not confirm.

 

[brambedkar59]

@brambedkar59

have you checked the temperatures of your hardware? There's a free utility, amongst others available, I use called CPUID HWMonitor that displays several hardware-related temperatures. It needs to be run with Admin privileges to be most effective.

HWMONITOR | Softwares | CPUID

HWMonitor for Windows® x86/x64 is a hardware monitoring program that reads PC systems main health sensors : voltages, temperatures, powers, currents, fans speed, utilizations, clock speeds ... The program handles : CPU and GPU-level hardware monitoring...

www.cpuid.com

Temps are pretty normal. CPU hovers around 50-60°C while browsing (around 40-45°C idle), SSDs temps are also normal, and while gaming CPU reaches max of around 80°C (avg 70) while Nvidia GPU goes to 70°C max (avg 60).

This only happens to me due to RAM issues, did you try to remove RAM so clean up and put it back in? if it's same problem then try different RAM. however not confirm.

I ran Windows Memory Diagnostic it found no problems.

 

[roger_m]

I ran Windows Memory Diagnostic it found no problems.

In my experience, although BSODs can be caused by hardware issues, the vast majority are caused by software.

 

[CyberTech]

I ran Windows Memory Diagnostic it found no problems.

Ah you believe this? maybe a bug? lol kidding dude! and did you check Reliability Monitor? if it doesn't show up as error i would say reinstall it or restore image.

 

[wat0114]

Don't know if this applies to your situation or will help, but the article below mentions as the first step of 11, to try replacing the iastor.sys driver in Windows 10 (I know you use Win 11) for the DPC_WATCHDOG _VIOLATION BSOD you mentioned seeing in your first post.

11 Ways to Fix DPC Watchdog Violation BSoD in Windows 10 + Video

In order to fix DPC WATCHDOG VIOLATION errors on your computer, take a look at our step-by-step guide that will help you for sure.

windowsreport.com

 

[brambedkar59]

In my experience, although BSODs can be caused by hardware issues, the vast majority are caused by software.

And figuring out what's causing the issue is such a pain in the backside.

Don't know if this applies to your situation or will help, but the article below mentions as the first step of 11, to try replacing the iastor.sys driver in Windows 10 (I know you use Win 11) for the DPC_WATCHDOG _VIOLATION BSOD you mentioned seeing in your first post.

11 Ways to Fix DPC Watchdog Violation BSoD in Windows 10 + Video

In order to fix DPC WATCHDOG VIOLATION errors on your computer, take a look at our step-by-step guide that will help you for sure.

windowsreport.com

Thanks for the article but there is no mention of iastor.sys in any of minidump file.

 

[ForgottenSeer 69673]

BSOD:

Some research (googling, actually) let me to suspect that the retained shadows of the drive were somehow corrupt, so I simply deleted them (vssadmin delete shadows /for=c: /all). Since then, there have been no errors reported, new shadow snapshots were created and everything else is working OK.

 

[brambedkar59]

BSOD:

Some research (googling, actually) let me to suspect that the retained shadows of the drive were somehow corrupt, so I simply deleted them (vssadmin delete shadows /for=c: /all). Since then, there have been no errors reported, new shadow snapshots were created and everything else is working OK.

I am not using System restore, file history or Windows in-built backup. Would there still be a chance of that happening?

Edit: I just checked, I don't think there are any Shadow snapshots on my system.

 

[brambedkar59]

According to an "Independent Advisor" on answers.microsoft.com, dump files point to Realtek Ethernet driver (Latest driver from Asus). Updated them to newer generic Realtek ones with Snappy Driver Installer. And in case these doesn't work I will install older drivers from Asus website.
Link to thread

And now the wait begins

Well Realtek ethernet driver was the problem, my last BSOD was on 20th feb. I am using driver v1168.11.1206.2022 right now instead of v1168.008.0515.2022 (which I downloaded from Asus website). Hope this helps anyone else having same issue.

Thanks to everyone who tried to help me solve this.

PS I am never making fun of MS forum again, the guy there really helped diagnose the issue.

Mods can we mark the thread as solved and I can't seem to edit the thread (just to put the solution in it). Thank you.