RAM issues, yet RAM is supposedly fine.

Carlos_39

Commendable
Apr 12, 2016
3
0
1,510
I don't know what to do, I just built a computer and it's consistenly crashing. I get the following type of errors: MEMORY_MANAGEMENT IRQL_NOT_LESS_OR_EQUAL and a couple of others. I ran memtest86 all day and it told me my RAM memory is fine. I then thought maybe some issue with my hard drive as it consistently happens when I save a Football Manager Game (Those use a lot of memory though). Hard Drive also looks fine. Please let me know what should I do. I really need help.

32 gb GeIL EVO POTENZA 16GB (4 x 8GB) 288-Pin DDR4 SDRAM DDR4 2400 (PC4 19200) Desktop Memory Model
6700k
ASROCK Z170 Extreme6
Sapphire R9 390
SeaSonic X Series X-850 (SS-850KM3 Active PFC F3) 850W ATX12V v2.3 / EPS 12V
480 gb ssd Sandisk Ultra 2
3 TB Seasonic 7200 rpm

On Wed 4/13/2016 12:08:26 AM GMT your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1A (0x41792, 0xFFFFF680ED010B28, 0x1000000000000, 0x0) Error: MEMORY_MANAGEMENT Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Sun 4/10/2016 1:20:55 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\041116-4500-01.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xA (0x48F, 0x2, 0x1, 0xFFFFF800F3AE55F7) Error: IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Carlos,

A simple test, lower the working speed of your memory modules, in your bios settings of your motherboard.
And test for a period of time at the lower speed setting, see if the errors go away.

Next time you post include what motherboard you are using, it`s name and model number.
The cpu you are using.
The memory you are using, brand, and the speed of the memory modules and model part number.
What power supply you are using, it`s brand, and the amount of wattage it is.
And the graphics card if Pci-e based brand, and model number.
Hard drives and or SSD drives of the system.
Also state if you did a fresh install of the OS on the new system build.

Then post back.
 

Carlos_39

Commendable
Apr 12, 2016
3
0
1,510


I updated post with all that :)