Multiple BSOD problems.

Hello and welcome Xendrix first up what memtest did you used because there is only really one that is of any use http://www.memtest.org/ and also if you used this one how many passes did you le tit run for? because less than 8 passes is worthless.

Now to let us see the dump files use these two tutorials to collect the data and post it back to us to have a look at
https://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
&
https://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

To check out the power see my little ditty when you get the Sensors to run scroll down to the section where the voltages and current capabilities are listed

Using HW Info

You can test the volts on the PSU with HWInfo HWiNFO, HWiNFO32/64 -Download < download the right bit version andclose the right hand window select Sensors and scroll down to the power sectionwhere you will see what the volts are doing see my pic.
For laptops use the Sensor button and then scroll down to the battery section (usually at the bottom)
Voltages should always be within 5% of the required voltage otherwise the machine will not function properly or at all see this Power Supply 101: A Reference Of Specifications - Power Supplies (section 2 is the part to read)

The original right hand window shows themachine running and is handy for that but for looking at the components in some detail close it and use themain left hand side panel

FOR OTHER COMPONENTS

Open each + down into the componentitself and then click on it - in theright hand side will appear all sorts of details including brands speeds andother essential info that device. See pic/s for example.

Hmm I didn't notice before but I see you are running 8.1 now it might be best to ask in that forum (run by same people by the way) but although you have run a memory test I am guessing it was the Windows feature because you have memory corruption in the logs see below.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
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: fffff6806cd0e148
Arg3: 0000000000008000
Arg4: 0000000000000000
Debugging Details:
------------------

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump
MEMORY_CORRUPTOR:  ONE_BIT
BUGCHECK_STR:  0x1a_41792
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
ffffd000`23b5f7c8 fffff802`4efedbd3 : 00000000`0000001a 00000000`00041792 fffff680`6cd0e148 00000000`00008000 : nt!KeBugCheckEx
ffffd000`23b5f7d0 fffff802`4eec64ad : 00000000`00000008 00000000`00000001 00000000`00000001 ffffe000`02c61de8 : nt! ?? ::FNODOBFM::`string'+0xea33
ffffd000`23b5fa30 fffff802`4f233e31 : ffffe000`078244f0 000000d9`a1070000 ffffe000`00000000 7fffffff`00000000 : nt!MiDeleteVad+0x22d
ffffd000`23b5fb20 fffff802`4f233747 : 00000000`00000000 fffff680`00000008 000000d9`a1070000 00000000`00001001 : nt!MiUnmapViewOfSection+0xf9
ffffd000`23b5fbf0 fffff802`4efda4b3 : ffffe000`02e11080 000000d9`8d81f430 00000000`00000000 ffffe000`02c61900 : nt!NtUnmapViewOfSectionEx+0x73
ffffd000`23b5fc40 00007ffd`ce297ffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000d9`8d81cbf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`ce297ffa

STACK_COMMAND:  kb
SYMBOL_NAME:  ONE_BIT
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit
FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwne

So I would suggest running the memtest again and make sure you are using the only test worth running because it has more than one problem.


MEMTEST

The memtest you will need to make abootable disk / stick and set the BIOS to boot from the optical or USB and itwill take a fair time to run- some leave it overnight.

This is the current version http://www.memtest.org/ please use thisas any other test is useless - the Windows one sadly is not worth even athought about.

But one thing is very important you mustlet the test run for at least 8 passes any less and the findings are no good. Now if errors come upstraight away then you can stop it - see my pics. Now if there are errors andyou have more than one stick of RAM in then you will need to test each stick ieremove the sticks and replace stick 1 in slot 1 and test no errors do thesame in slot 2 with stick 1 no errors then repeat the process with stick 2 -that will show up the faulty stick - the other thing is it could be a faultyslot but most unusual. With more than two sticks the process is even longer asone may realize.

It is a very lengthy and tedious processbut worth it if you have errors.

See what comes up because this test is for all OS's

Well if it were me I would sign up in that forum - I use my same ID and avatar etc for the 8 and 10 forums like I sadi it is run by the same admin and most of us are in all three to some degree or other. I prefer 7 but each to his own.

I suppose a simple copy paste would do it when you open a thread in 8 after putting a title to it.

If you have 31 errors already you can stop the test, there's a problem with the RAM. If you're only testing one stick then move it to another DIMM slot and test again, if it shows errors again then the RAM is faulty, if it gets through 8 passes with no issues then the problem is with the original DIMM slot.

As Boozad says mate and as I said in my ditty and showed in my pics the errors can come at any time - the real job is finding out whether it is the sticks or the slots.

So for example if you have say 4 slots and 2 sticks and get errors you need to test #1 stick in #1 slot if no errors then move on to test #2 stick in #1 slot. That would mean to me the problem lies within a slot because no errors with either stick have thrown errors.

Then you move on to #1 stick in slot#2 no errors then stick #2in slot#2 no errors - repeat the process in slots #3 and then #4 with both sticks until the errors come up. Running each for 8 passes as you can imagine is very tedious and will test your patience.

But it has to be done simply because if the errors do not come with either stick in slot #1 then as I said it points to a faulty slot.

Having said that this does not happen very often it is usually the sticks that are at fault.