Finished the memtest86 with WDV off. All 4 passes were good. Thoughts?
Threads Exceptions BSOD after Windows reinstall
.zip dump file: https://drive.google.com/file/d/1r4i-TIIkrmbFzS6mmtHa9buEZwk8-pJA/view?usp=sharing
I have a lot of BSOD recently from IRQL, Resource not owned, DPC Watchdog, and Kernel Security Check Failure. This started happening occassionally about 2 months ago and become more and more frequent. There is no major update like BIOS or driver that I believe caused the problem
From Windbg, it has been narrowed down to be a thread exception problem where a program tries to access or release a thread it has no access to. I ran verifier for 24 hours to get the same types of BSOD at the same frequency.
There is no driver verifier violation from BSOD and in the dump files (using recommended verifier settings) from windbg, so perhaps the driver is not the issue. Often the debugger say the culprit is various programs from sysinternals, my VPN, or a random .exe process. I did a full reinstall using media creation tool that removes all apps and personal files. I thought this was a problem with corrupted windows file that sfc or dism or chkdsk could not repair or detect. I still have the problem of getting BSOD every few hours (sometimes every few minutes) after the reinstall, but windbg gives a more consistent blame: ntkrnlmp.exe
This is followed with nt!ExpReleaseResourceSharedForThreadLite+(Hex number)
I have the newest bios from HP and windows is up to date
BSOD can happen instantly or is followed by severe lag a few seconds before it happens. There is no overheating by the CPU (hover around 70C, can spike to 90C but drop down to 60C quickly). Did windows memory integrity check, both RAM stick pass. Have not done memtest86 and prefer not to unless there is a strong reason of RAM problem
HP hardware diagnostic did not return any error (the one you run without going into windows)
A good pattern I see is that sfc /scannow ocassionally reports and repairs a corrupted file (but not all the time, even after a BSOD)
The following is the CBS folder with the log. Maybe the file that it repairs can help solve the problem: https://drive.google.com/drive/folders/1XEZLPCoyGIBh0-KF-kHr1eH6SJc8vgcR?usp=sharing
My computer is an HP Laptop about 3 years old, AMD Ryzen 5500u, 32 GB RAM (2 x 16GB Crucial 3200MHz) DDR4, no dedicated GPU, 2TB Crucial SSD (new SSD, no bad sectors.. BSOD also happens before I upgraded my SSD)
BIOS: UEFI
BIOS Version/Date: AMI F.30, 4/21/2023
Processor AMD Ryzen 5 5500U with Radeon Graphics, 2100 Mhz, 6 Core(s), 12 Logical Processor(s)
SMBIOS Version 3.3
Windows Version 10.0.19045 Build 19045 (Windows Home)
System Model HP Laptop 14-fq1xxx
Let me know if any of the links are not working of if the dump file is corrupted
Thx
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
52 answers
Sort by: Most helpful
-
Anonymous
2023-08-24T03:56:25+00:00 -
Anonymous
2023-08-24T03:54:36+00:00 Finished memtest86. The only RAM in the system was CT16G4SFD832A.M16FRS which was the only one in the system for the past couple of days. All test 4 passes were good, no errors. What does this mean?
In the meantime, I will run another pass on this RAM.
-
Anonymous
2023-08-23T18:52:55+00:00 Make sure that WDV is off.
See the post: questions_Replied on August 21, 2023 to test one RAM module at a time in the same DIMM.
-
DaveM121 933.9K Reputation points Independent Advisor2023-08-23T13:24:19+00:00 The new minidump files all indicate RAM corruption as the cause of the latest system crashes, it is time to run MemTest86 to test your RAM, I know you indicated you would prefer not to, but it is the next step, run a full 4 pass scan with that to test your RAM for physical errors
-
Anonymous
2023-08-23T13:11:25+00:00 Already uninstalled it. I uploaded minidumps and their logs
The last 3 BSODs had verifier on and no NordVPN. It was a bit more stable, but the problem is still there
Link to minidump: https://drive.google.com/drive/folders/1nJWwExHz8ap6BLWgOadLJnG3kzH\_h3ZZ?usp=sharing
Link to V2 logger: https://drive.google.com/file/d/19gVr20NPdWM2-8LFno0PeglX-2TElewO/view?usp=drive\_link