BSOD crashes inconsistent on Win10 21H1 (19043.1081)

Hi all,

I need some guidance. I've been getting BSOD crashes very often and the stop codes are not consistent. I've seen PAGE_FAULT_IN_NONPAGED_AREA (most common), KMODE_EXCEPTION_NOT_HANDLED, and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. I am getting them more frequently (multiple per day) than I used to. I haven't made any recent changes (new software, new hardware) except typical Windows Updates. BSOD can happen immediately when Windows starts, opening an app (like Edge or Chrome) or when idling (I usually come back in the morning to a BSOD, I have auto-restart disabled).

• Speccy link: http://speccy.piriform.com/results/c...Osu7doiU3RDO6t
• V2 Log Collector: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Typical errors are:

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffd0, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff805814082b6, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

or this one:

Code:

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8025ad0e507, The address that the exception occurred at
Arg3: fffff8025f9f5118, Parameter 0 of the exception
Arg4: fffff8025fa04920, Parameter 1 of the exception

Here are the steps I've taken so far over the last few days (to no avail):
1. Updated to latest BIOS for MSI H270M Bazooka (v2.7).
2. Re-installed all drivers from MSI Support page (removed first, rebooted, installed latest directly from site one by one).
3. Tested memory using Windows Memory Diagnostics and memtest86. It did not find errors. I also removed RAM modules one at a time and switched slots to see if BSOD still occurs, it does.
4. Ran chkdsk, sfc, and Windows troubleshooter.
5. Ran (tried to) Intel Processor Diagnostic Tool. It shows a box saying "Please wait while we start.." and then disappears. Since that's not working, I ran OCCT with options recommended by Tom's Hardware. No errors reported on that (ran it for a few hours).
6. Uninstalled a bunch of software that I rarely use.

Any ideas?

1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create standard settings"
3. Select "Select driver names from a list"
4. Tick all 3rd party drivers
5. Apply changes and reboot computer

It identified igdkmd64.sys. I have updated this from 21.20.16.4565 to 27.20.100.9466 using the download directly from Intel.

After updating (required 3 reboots), I re-applied the Driver Verifier settings. While I no longer get BSOD from Driver Verifier, the original blue screen errors still occur.

Please upload a new V2 logfile.

I did see another blue screen with the graphics driver so updating the driver didn't fix that but I'm still getting all other kinds of blue screens. Updated V2 Logs attached Attachment 340088 and on OneDrive. Thank you.

I've uninstalled several applications and am noticing BSOD are less frequent. I'm not sure how else to pinpoint remaining issues and I'm wondering if this could be hardware related (CPU)? I took a new log collector with the latest BSOD and uploaded to my OneDrive.

There are a number of hardware tests you can run if you suspect hardware failure. All I can see from the latest logs is a possible HDD/SDD or RAM issue.

Diagnostic Test

 RAM TEST

Run MemTest86to analyse your RAM.

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. For the free version of Memtest86 you need to run it for 4 passes twice in succession. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

Diagnostics Test

 HDD TEST

Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.
  
  

Thanks for those suggestions. All tests passed with no errors.

memtest
Attachment 340426

HDTune Error Scan
Attachment 340424

HDTune Health
Attachment 340425

HDTune Benchmark
Attachment 340423

Prime95
Attachment 340427

I ran the memtest overnight (4 passes), it passed but since I wasn't able to start another run right away I ran it again (2x4 passes). Still no errors on anything hardware related so that makes me think that it's probably a buggy software driver. Blue screens definitely happening less frequently after uninstalling a bunch of stuff but I also haven't been using it much since I'm running all these test. Thanks in advance.

I'm closing this because the BSOD are infrequent enough. Thanks for all the help, folks!