~2 BSODs a day when doing regular work

Hi, thank you very much for assisting me here. Ive had around 2 BSODs a day for a few weeks and its driving me nuts. It happens when I am just doing regular computer work.

Ive tried using Windbgx64 and WhoCrashed to debug my memory dumps but I can't see to find any cause for the BSODs.

I did just get new RAM after previous RAM had issues. I am using the XMP II profile which is supposed to be the most stable XMP profile available. (Also available is XMP I and XMP tweaked, which are supposed to be less stable and tighter timings from Asus)

No GPU overclock, no CPU overclock. Temps are fine

ProArt Z690-CREATOR WIFI
Intel I9-12900KS
Nvidia 3090 TI

I do restore to a previous HD image whenever I get a BSOD (Windows ME trauma) so thats why you wont see a ton of crash dumps in the logs. There was a recent crash at 5 AM today, so that should show up in here.

Please perform the following steps: (in sequence)


1) Run Tuneup plus > post a share link






2) Make a new restore point




3) Make sure that there is no Windows cleaning or third party software cleaning during the troubleshooting



4) Run Sea Tools for Windows Long Generic test (all drives) > post images or share links





5) Run HD Tune (free or trial version) (all drives) > post images or share links
a) Health
b) Benchmark
c) Full error scan



6) Open administrative command prompt and copy and paste

chkdsk /b /v


Run these chkdsk switches on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E:

Make sure that the windows drive runs overnight while sleeping.



C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: y

Reboot as needed.



7) After completing the chkdsk switches on all drives run: chkdsk from event






8) The Intel CPU supports RAM up to 4800

At the time that the log collector ran the RAM was recorded at Speed: 6000

Turn off XMP.



9) Make sure that there is no overclocking during the troubleshooting



10) For any new BSOD post a new V2 share link

While I was originally very hesitant to turn off XMP as I had never heard of instability with XMP, this was indeed the case. memtest86 showing errors when XMP is enabled but memory is fine when XMP is disabled. Thats too bad because I paid big money for these overclocked chips. Seems like the machine is stable now with it off.

A BSOD is a computer crying out for HELP! Sounds like you found the help it needed.

Congrat's!

TM