Sorry in advance if this is in the wrong place.
I feel like I’ve been chasing my tail with errors and problems ever since I got my system. Which funny enough I got to replace an aging Toshiba that was erroring out daily too, because the onboard video was no longer getting driver updates. The near daily crashes are really making it hard to function and I’m officially waving a white flag on trying to solve it solo.
I have explored a number of methods to stop having BSOD errors
- removed my hub and external drive
- switched to logitech bluetooth devices for external mouse and kb just in case my off-brand usb devices were a problem
- gone down to 1 newer external monitor (after my older dell became perma-stuck in 640x480 generic driver mode) plugged in via an official hdmi expansion card
- turned off all forms of hardware acceleration I could (in browsers, bios, etc)
- started using a cooling pad at all times regardless of heat reported by utilities
- replaced the ram with a stick off the approved list, there were no reported errors, it was just in case
- ran memtest64 a few times, once for over 24 hours without error
- started using intel utilities to make sure windows wasn’t shortchanging me on current drivers
- not used any antivirus but defender
- not permitting background apps (to the best of my ability, adobe is very greedy)
- fully updated bios (3.10)
- run sfc /scannow repeatedly, sometimes with fixes, sometimes without
- uninstalled and reinstalled drivers
- disabled all “sleep modes” I could to ensure no crashes on wake up
- sdd utility reports no errors
- defender says i’m okay but it’s possible it’s compromised, haven’t run malware bytes but I probably should!
And about once a day I get one of a rotating list of BSOD errors, sometimes preceded by mouse jitters, sometimes not.
- (corrupt dump) LiveKernelReports\PdcLockWatchdog
Ordered DIY edition March 3rd 2022 - I’m not sure how to determine what batch that is?
Processor: Intel® Core™ i5-1135G7
WiFi: Intel® Wi-Fi 6E AX210 No vPro®
Windows Version 10.0.19044 Build 19044
System SKU FRANBMCP0A
BIOS Version/Date INSYDE Corp. 03.10, 7/19/2022
SMBIOS Version 3.3
Embedded Controller Version 255.255
BIOS Mode UEFI
Installed Physical Memory (RAM) 16.0 GB
Total Virtual Memory 39.2 GB
Crucial 16GB 260-Pin DDR4 SO-DIMM DDR4 3200 CT16G4SFRA32A
SABRENT Rocket Q 1TB NVMe PCIe M.2 2280
Page File Space 23.4 GB (Manually increased to see if it would stop the crashing)
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: WinRE is not configured
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
most recent chkdsk and sfc
The type of the file system is NTFS.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure …
1255936 file records processed.
File verification completed.
Phase duration (File record verification): 11.26 seconds.
9630 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.26 milliseconds.
Stage 2: Examining file name linkage …
875 reparse records processed.
Index entry fࡦmpeg.dll in index $I30 of file A1657 is incorrect.
1718266 index entries processed.
Index verification completed.
Phase duration (Index verification): 38.55 seconds.
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
The ffmpeg.dll issue in the chkdsk results is new. So is the Store Data Structure Corruption error.
Also I started writing this on Wednesday, decided against posting it, and today I’ve had to run SFC and DISM after my system menu became inaccessible unexpectedly. Then a minute ago I got another page fault BSOD.
At this point my plan is to back up all my regular files, browser prefs, etc and wipe the whole machine, start over. While I was writing this, I got an IRQL not less or equal BSOD.
This is getting kind of difficult to deal with!