Memory Management BSOD

put your memory dump on a server that does not try to install malware.
try microsoft onedrive, google docs or media fire.

it also concerns me that this file is being loaded:
amdide64.sys
it sounds like a IDE driver, which would only be used for some older hardware designs (2006) and often gets loaded when the BIOS sata mode is set incorrectly to IDE rather than AHCI. if the system was installed under IDE mode, you would have to make a windows registry setting change before you make a BIOS sata mode change to AHCI mode.
here is the registry location: https://support.microsoft.com/en-us/kb/922976

--------------
second bugcheck was like the first but the system was up 10 mins
any idea what this driver is for:
C:\Windows\system32\drivers\BSMEM.sys Thu Jul 26 02:34:27 2012

it could be "I/O Interface driver file" by biostar
if so I would update it or remove it
------

first bugcheck was in memory management but related to virtual memory. Basically the table that tracks what files are currently in active memory (ram) and what files have been swapped to disk (virtual memory) (pagefile.sys) is corrupted. At this point I can not see why it is corrupted. The problem can come from any component involved in the process. I would go to your motherboard vendors web site and see if there are drivers for the sata controller that you can update. I would work on configuring the memory and running memtest86.
generally this bugcheck can not be debugged with a mini memory dump and requires a kernel memory dump to figure out which driver corrupted memory
(if it is a driver problem and not a memory timing problem)

the system was up for 34 minutes.



----------------
I would confirm that the memory is in the correct slots. (most boards would interleave the memory and use slot 0 and slot 2)
I would confirm the memory settings are correct.
then boot and run memtest86 to confirm your memory system is ok.

I would also confirm that your BIOS SATA mode is set correctly. Most systems would use AHCI as the correct mode.


machine info:
BIOS Version 080015
BIOS Release Date 11/25/2015
Manufacturer BIOSTAR Group
Product A960D+V2
Processor ID 200f6000fffb8b17
Processor Version AMD FX(tm)-4300 Quad-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 3800MHz
Current Speed 3800MHz

memory is in bank 0 and bank 1 (you might want to check your motherboard manual and see if these are the correct banks to put the ram in)
you should also make sure they system is using the correct ram timings and voltages.
spec indicates these settings should be used:
Tested Speed 1600MHz
Tested Latency 9-9-9-24-2N (note: often BIOS do not set the command rate correctly should be 2 N or2 T)
Tested Voltage 1.50v
Re
memory: Part Number F3-12800CL9-4GBXL running at 800MHz
http://www.gskill.com/en/product/f3-12800cl9d-4gbxl

it also concerns me that this file is being loaded:
amdide64.sys
it sounds like a IDE driver, which would only be used for some older hardware designs (2006) and often gets loaded when the BIOS sata mode is set incorrectly to IDE rather than AHCI. if the system was installed under IDE mode, you would have to make a windows registry setting change before you make a BIOS sata mode change to AHCI mode.
here is the registry location: https://support.microsoft.com/en-us/kb/922976

--------------
second bugcheck was like the first but the system was up 10 mins
any idea what this driver is for:
C:\Windows\system32\drivers\BSMEM.sys Thu Jul 26 02:34:27 2012

it could be "I/O Interface driver file" by biostar
if so I would update it or remove it
------

first bugcheck was in memory management but related to virtual memory. Basically the table that tracks what files are currently in active memory (ram) and what files have been swapped to disk (virtual memory) (pagefile.sys) is corrupted. At this point I can not see why it is corrupted. The problem can come from any component involved in the process. I would go to your motherboard vendors web site and see if there are drivers for the sata controller that you can update. I would work on configuring the memory and running memtest86.
generally this bugcheck can not be debugged with a mini memory dump and requires a kernel memory dump to figure out which driver corrupted memory
(if it is a driver problem and not a memory timing problem)

the system was up for 34 minutes.



----------------
I would confirm that the memory is in the correct slots. (most boards would interleave the memory and use slot 0 and slot 2)
I would confirm the memory settings are correct.
then boot and run memtest86 to confirm your memory system is ok.

I would also confirm that your BIOS SATA mode is set correctly. Most systems would use AHCI as the correct mode.


machine info:
BIOS Version 080015
BIOS Release Date 11/25/2015
Manufacturer BIOSTAR Group
Product A960D+V2
Processor ID 200f6000fffb8b17
Processor Version AMD FX(tm)-4300 Quad-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 3800MHz
Current Speed 3800MHz

memory is in bank 0 and bank 1 (you might want to check your motherboard manual and see if these are the correct banks to put the ram in)
you should also make sure they system is using the correct ram timings and voltages.
spec indicates these settings should be used:
Tested Speed 1600MHz
Tested Latency 9-9-9-24-2N (note: often BIOS do not set the command rate correctly should be 2 N or2 T)
Tested Voltage 1.50v
Re
memory: Part Number F3-12800CL9-4GBXL running at 800MHz
http://www.gskill.com/en/product/f3-12800cl9d-4gbxl

I would just go to the biostar website and make sure the bios, drivers and utilities installed were updated:
http://www.biostar.com.tw/app/en/mb/introduction.php?S_ID=821#download

I would think the driver is being used to allow a utility to monitor something like a temperature sensor. you would uninstall the utility to remove it.

it is very common for a BIOS not to have proper defaults for RAM settings. I would always update the BIOS to get the best default timings, test the memory and if it still fails I would put the correct values in for my RAM timings and correct voltage then re run the test. if it fails I would try to find out if it was one stick or both. I would check the motherboards qualified memory vendor list to see which ones the manufacture claims will work.

yep, any failure in a memory module can cause a driver to fail if its data is stored in the bad location in RAM.
windows will load the drivers in different orders on each boot of windows. just to make it harder to hack this means different drivers get messed up on each boot and you get different bugchecks.

can not say, there are many memory timings and each motherboard vendor can have timing variations between boards and the individual memory slots. https://en.wikipedia.org/wiki/Memory_timings
the biggest problem i see it people match the voltage, clock rate, type and the first 4 memory timings but not the command rate. (look for 1N or 1 T command rate or match the command rate to the memory you already have)

the memory you specified has this timing: 9-9-9-24-2N the 2 means it takes two clock ticks to set up a address command.
many bios versions set a default faster speed 1 N = 1 clock tick to set up the address.
I would find a different module or you might have to manually change the bios memory timing to prevent memory errors.
1 N or 1T command rate will always work, a 2n or 2T might work most of the time if the bios is set to a 1T rate by default.



------------

I've actually manually set the command rate to 2T since the default is 1T ever since i removed the faulty ram. I matched it with what's listed on my old functioning ram which has exactly the same command rate to the ram I'm planing on buying.