Windows 10: Bugcheck 139, keep getting BSOD and do not understand dump file

Windows 10 version 10.0.19045 I've put zip of dump file here: MEMORY DMP.zipAny help would be appreciated.

:)

 

(BSOD) bugcheck was: 0x000000a0 INTERNAL_POWER_ERROR

Has any one got this BSOD when stress testing a overclock before? i can get the minidump if some one can read it for me i was trying for 4.5Ghz @ 1.31v and after around 20min of stressing i would get this BSOD and it would shut my system down not even sure i saw a BSOD just a shutdown?

 

Got Error code BugCheck 139 on WIndows 10

Hi all,

Recently, i got BSOD after boot on about 5 - 6 minutes.

The minidump file is :

https://drive.google.com/open?id=0B1pNCTx7OkYQbkczMlpreVFPMjQ

BugCheck 139, {3, ffffed8baa14d700, ffffed8baa14d658, 0}

 

Want to figure out BSOD, but there is no dump file or entry in system log file

I recently got a Blue Screen of Death on my Windows 10 laptop. I took a photo of the QR code, but it took me to a generic and useless Microsoft web page. My QR code app only keeps a history of the links, not the photos, so I do not remember what the stop code was.

I want to know why this BSOD occurred and if it might be a hardware or software problem. Here is how I have the crash handling configured:





As you can see, the "Write an event to the system log" box is checked, and a dump file named C:\WINDOWS\MEMORY.DMP should be created.

However, when I looked at the System log in Event Viewer, I didn't see anything that seemed related to the BSOD around the time of the crash. I read that there should be an entry from Source "BugCheck" for a BSOD, so I tried to filter the events with "Event sources"=BugCheck, but nothing was found.

There is also no file under C:\WINDOWS named MEMORY.DMP.

Why did Windows 10 not put an entry in the system log for the BSOD, and why didn't it create a dump file? How else might I be able to determine what the bugcheck code was, and what caused it?

EDIT: Additional information:

• There is over 300 GB of free disk space on the C drive, so a lack of space is not the reason why the dump file wasn't created.