BSOD at random times, error 0x0000004e

[Dave76]

Use the second method - Flash AMI UEFI BIOS by MFLASH.

You can also try this method: MSI HQ Forum BIOS Flash Tool

 

[kai246]

I managed to flash the bios using the second method from the list (m flash), however upon rebooting, the same problems came up when going into the bios. It was glitchy and not all of the options were present.

I have managed to get in to the bios with everything working normally and the display looking good, at will now, as I found its just a case of taking out the hdmi wire before going into the bios (pressing delete on start up), I then put the hdmi wire back into the computer and the bios looks normal and is fully functional. Its weird that these steps need to be taken for it to work as if I were to have the hdmi wire already in the computer when turning on the computer I would come up with the errors I previously took pictures of.

Should I keep doing these steps and change the voltages as requested to do before?

 

[Dave76]

Yes, continue with the voltage adjustments.
If the BIOS flash didn't solve the issues, then it must be a BIOS deficiency, hopefully they will fix it in the next version.

 

[kai246]

The dram voltage cannot be changed to specific numbers, It has given me a list of what it can be changed to, the list is 1.3500v, 1.5000v (Currently on this), 1.6500v and 1.8000v. Shall I change it to 1.6500v?

Also Im not sure where I can change the voltage for the cpu I/O. It seems that I can actually only change the CPU Ratio, CPU core voltage and the DRAM voltage.

 

[Dave76]

Is that in the OC Genie section?

Look in Overclocking Settings > Standard Mode > DRAM Voltage, change it from 'Auto' to 'Manual' and check if you have more options.

Go to Overclocking Settings > Standard Mode, what options do you have for 'My OC Genie'?

Have you had any crashes in the last four days?
If you have post the crash reports.

Run memtest86+ again, best to run overnight, minimum of 7 full passes.
If you get any errors you can stop the test.

 

[kai246]

The same options are in each of the standard mode and overclock genie. There is no option that says manual, instead there are prefixed numbers that i can choose from a list.

It has crashed twice in the past couple of days and I've uploaded the necessary information.

Also I am running another memtest as we speak on one of my modules and will start the next module later day, so Ill get back to you with the results for that.

EDIT: Whilst running memtest I got another blue screen, however this ended in a0 which is not not something I've seen before, I have updated the information you need to include this dump as well. I had left my computer to itself so couldn't see if there was any errors but will get back to you if I see any as I have started the test again

Another EDIT: It seems I'm actually unable to do a memtest without it blue screening, after trying again it ended up blue screening, this is odd though as I used to be able to get through these tests before

 

[Dave76]

The lack of BIOS voltage options from MSI is very disappointing, since the i series came out Intel specifically warns against using 1.65v RAM, they say it can damage the CPU.
This is due to the IMC (CPU Integrated Memory Controller), which is the CPU IO voltage and is a commonly known fix for large amount of RAM.
It is also recommended to keep the DRAM and IMC voltage within 0.50v of each other, this can cause CPU damage also. So the DRAM voltage options of 1.65v and 1.80v aren't even usable.

What slot do you have the RAM in?
Try it in slot #2 if it wasn't in it already.

Have you tried memtest86+ with the other RAM card yet?

Your last three crashes.

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, memory, kernel
PROCESS_NAME:  Borderlands2.e
FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3267c
----------------------------------------------------------------------------------
STOP 0x0000004E: PFN_LIST_CORRUPT 
Usual causes:  Device driver, ?memory
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
PROCESS_NAME:  MsMpEng.exe
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
----------------------------------------------------------------------------------
STOP 0x000000A0: INTERNAL_POWER_ERROR 
The hibernation file is too small.
FAILURE_BUCKET_ID:  X64_0xA0_nt!PopWriteHiberPages+a3

First one, not much useful information.
Second is from memory corruption.
Third, if this is from the memtest86+ test, then is not the cause as the OS is not running.
Confirm you are not using the usually useless Windows memtest and are using the recommended memtest86+ for RAM testing.

RAM can be fickle and difficult to troubleshoot.
Budget/Value RAM is not known for it's reliability or stability.
Two main issues I noticed before:
1) No XMP listed in the CPUZ SPD tab, this is an Intel feature and listed in most RAM designed for Intel systems.
2) Any RAM that states it is for Intel and AMD systems usually fails on one or the other.

Try putting RAM card #1 in slot #2 and then in slot #4 and run memtest86+.
Pass or fail, run RAM card #2 in slot #2 and then in slot #4 and run memtest86+.
Let us know the results.