bugchecks following June updates

Topic

New Reply

Has anyone experienced bugchecks / BSOD’s after installing the June updates?

I waited for the all clear, installed the June 2021 updates on a home built PC.  I2700k (not overclocked), Asus P8P67 Deluxe B3 mobo, 16 gb ram, Corsair Gold 850PSU, Samsung 860 500gb SSD system drive, Nvidia 1650 Super graphics.  Well cooled.  20H2 Pro.  Stable system.  After the June updates I’ve had a series of bug checks, each different.  Nvidia, Intelppm, Logitech and a few others.  I’m away from home for a few days, but I will mem test the ram as soon as I can.  SFC and DISM and chkdsk and SMART show no errors.  I’ve updated the Nvidia drivers.  Also the Logitech mouse software and drivers.  I specifically mention that because on the one bugcheck crash I actually saw (the rest were with the system idling) I had the mouse freeze up, then the system crashed.

My question is simple – do we know of anything in the June updates that could cause these seemingly random bugchecks?  Or anything else?  The system is not exactly new, but it’s fast and smooth.

 

Reply | Quote

Replies

I have seen “smatterings” of reports of BSODs but nothing definitive.  Can you run it through https://www.nirsoft.net/utils/blue_screen_view.html  ?

 

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Hi Susan

I plan to once I’m back home.  I did run it through Who Crashed, which is what led to what I posted about bugchecks from NVIDIA drivers, Logitech drivers, Intelppm.  I’m curious to see whether the PC has crashed again while I was away from home, also.  Happy to try out the nirsoft tool.

Reply | Quote

I ran the Nirsoft tool; I don’t see any way to copy the content from the several crashes.  Below is what Who Crashed came up with;

<span style=”font-family: Segoe UI, Arial; font-size: large;”><b>Crash Dump Analysis</b></span>

<hr />

<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”>Crash dumps are enabled on your computer.
</span>
<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”><b>Crash dump directories:</b> </span>
<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”>C:\WINDOWS</span>
<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”>C:\WINDOWS\Minidump</span>

<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”><b>On Fri 7/2/2021 3:17:03 AM your computer crashed or a problem was reported</b>
crash dump file: C:\WINDOWS\Minidump\070221-12171-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF803638FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.

</span>
<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”><b>On Fri 7/2/2021 3:17:03 AM your computer crashed or a problem was reported</b>
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: intelppm.sys (intelppm+0x138f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF803638FB320, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.

</span>
<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”><b>On Tue 6/29/2021 2:52:35 PM your computer crashed or a problem was reported</b>
crash dump file: C:\WINDOWS\Minidump\062921-12187-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF804652C5EE8)
Bugcheck code: 0x34 (0x51384, 0xFFFF978CB845D648, 0xFFFF978CB845CE80, 0xFFFFF804652C5EE8)
Error: CACHE_MANAGER
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a problem occurred in the file system’s cache manager.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It’s suggested that you run CHKDSK.

</span>
<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”><b>On Tue 6/29/2021 2:37:55 PM your computer crashed or a problem was reported</b>
crash dump file: C:\WINDOWS\Minidump\062921-12750-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8044A8E0FC8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8044A8E0FC8, 0xFFFFFC85D2298630, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It’s suggested that you run CHKDSK.

</span>
<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”><b>On Mon 6/28/2021 8:36:10 PM your computer crashed or a problem was reported</b>
crash dump file: C:\WINDOWS\Minidump\062821-12093-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x82a980)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF803566FB320)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_4a746d937e6a7240\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 471.11
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 471.11
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 471.11 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION

</span>
<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”><b>On Sat 5/8/2021 12:38:38 PM your computer crashed or a problem was reported</b>
crash dump file: C:\WINDOWS\Minidump\050821-12937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80107C01F64, 0xFFFFCB0AE620A1C8, 0xFFFFCB0AE6209A00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

</span>
<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”>The following dump files were found but could not be read. These files may be corrupted:
</span><span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”>C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20210628-2035.dmp
</span><span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”>
</span>

<hr />

<span style=”font-family: Segoe UI, Arial; font-size: large;”><b>Conclusion</b></span>

<hr />

<span style=”color: #111111; font-family: Segoe UI, Arial; font-size: small;”>7 crash dumps have been found and analyzed. Only 6 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 471.11 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it’s not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it’s suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

</span>

Reply | Quote

Blue Screen errors – intelppm.sys – Microsoft Community

Can you run disk checks to make sure that drive is healthy?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Before my trip this week I’d run chkdsk, SFC, DISM.  All ran without any errors found.  And as noted, I’d update Logitech software and drivers, also Nvidia.  I also checked the SMART status for the system drive; it is clear.  I’d also note that the system has at this point been up for 7 days; before doing all this is was crashing minutes to a day or two apart.  I also just ran a full Defender AV scan; all it found were a few ‘minor’ threats (usually it finds one or two downloads that MS doesn’t like).  No actions were required.  I’m hoping that the problem has been fixed but since I don’t want to run into it again, let alone discover I’m wrong, I’m trying to understand what happened.  This has been a very stable system that unless I need it for work (not recently) is only lightly used.  But is kept up to date.

Reply | Quote

Run Speccy and see what it reports for your hard drive(s). If Speccy reports that the drives are good, then…

I see that you have an I7-2700k CPU? Is that correct since you wrote I2700K? Try disabling hyperthreading in BIOS. Hyperthreading was twitchy in older I7 CPU models, causing random and bizarre crashes and producing blue screen crash reports which were not accurate.

If your hard drives are good, then I strongly suspect that the June update which might have also included a CPU microcode update is causing hyperthreading issues with your CPU.

Reply | Quote

Speccy confirms what HDTune and another tool said – SMART status good on dri8ves.

Yes, sorry for typo;  I7-2600K

Hyperthreading is on, has never to date caused problems on this PC, at least until the June upgrade.  I’d note that at this time system still appears to be stable at about 7 1/2 days.  If I get more problems I could turn off hyperthreading, though I’d prefer not to.  But this leads to an obvious question – if the updates caused my rash of problems, how might SFC or DISM have fixed them?  Plus the Logitech and Nvidia updates.

Reply | Quote