i just got 3rd bsod since end of last month

i bought laptop on jan 2019. i put new nvme ssd in my laptop in june 2019 and i installed windows on it. i used it for 1 year after i put new nvme ssd and all was perfect and no bsod and then bsod suddenly started happening end of last month

on june 27 i got kmode_exception_not_handled bsod
on july 3 i got system_thread_exception_not_handled bsod
today i got memory_management bsod

i did macrium reflect restore to image file which i made on june 21 after i got second bsod and i just got bsod again now. something is wrong because i got 3 bsod in around 1 month. i ran memtest86 at the end of last month. all was ok

DESKTOP-IFPCRCC-(2020-07-17_18-40-48).zip - Google Drive is log for last bsod which i just got

can someone please analyze the log and tell me what caused the bsod? if there is proof in the logs pointing towards memory issue then i will repeat memtest86

Dump shows:

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffff83006b0d0968
Arg3: 0000001008100000
Arg4: 0000000000000000

A corrupted PTE has been detected. This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.

You can try memtest86+ again but I don't expect the results to be any different. A better test would be to remove half of your ram and test that way for awhile. If you get a failure then swap installed an duninstalled ram and test some more.

Also, in the system event log I see this:

Code:

Event[1728]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2020-07-17T17:32:46.905
  Event ID: 105
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-IFPCRCC
  Description:
Power source change.

Event[1729]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2020-07-17T17:33:00.194
  Event ID: 105
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-IFPCRCC
  Description:
Power source change.

Event[1730]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2020-07-17T17:33:12.122
  Event ID: 105
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-IFPCRCC
  Description:
Power source change.

Event[1731]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2020-07-17T17:33:22.997
  Event ID: 105
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-IFPCRCC
  Description:
Power source change.

A power setting change event occurs when there is a change in the value of a power setting. For example, the user changes the power plan from High Performance to Balanced in the Power Options application in Control Panel. In this case, the system would broadcast an event that indicates that the power plan has changed.

Does your system sleep after a set period of time? If so, it looks like it's waking up, probably to do some scheduled task. See this (old) forum thread to see if you can eliminate what ever is waking up the system:

Windows 10 keeps waking up from sleep in the middle of the night!

Might be a good time to give Driver Verifier a try:

Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

If you have questions, see this additional tutorial which may help to clear things up.

Enable and Disable Driver Verifier in Windows 10

By the way, your PM inbox is full, you need to make some space:

To cleanup your Personal Message Inbox to free up some space, do the following.

Click on Personal Messages at the top left of the page:



Select the messages you want to delete:



Scroll down, expand Selected Messages, check Delete then click on Proceed:



Repeat as needed.

Sounds like the computer is not sleeping then but the Power source changes events indicate it is, very strange.

Any driver can cause a BSOD if it's got a bug in it. Oct 2019 is not that old though but if you found an updated version that's a good thing to try.

Would you fill out your specs under My Computer please?

How to fill out System Specs for tenforums.

See here: System Specs - Fill in at Ten Forums

Fill out as much as you can, especially the Manufacture and full model number of the computer if purchased or the system board if custom built.