BSOD MEMORY_MANAGEMENT 0x0000001a (msahci.sys)

janzak

Honorable
Nov 4, 2013
10
0
10,510
Been getting BSODs when subjecting my computer to heavy tasks such as heavy 3D rendering or physics simulations.

I thought I'd managed to get them under control by setting my RAM in slots 1 and 2, and reverting to an older, brand specific GPU driver.

I am still getting the occasional BSOD though, and I'm a bit worried it might have something to do with a bent CPU pin on the mobo that caused RAM slots 1-3 to malfunction.

I gently restored the pin and have been good since then with the exception of the occasional BSOD.

Anyway here's a minidump; http://www.sendspace.com/file/ntk81z

I looked at it using BlueScreenView but I'm not getting any cleverer..

Specs;
Mobo: Asrock Z87 Extreme4
CPU: Intel i7-4770K @ 3.50 GHz
GPU: Gigabyte GeForce GTX 760 OC 4GB
RAM: Corsair Vengeance Low Profile 8GB DDR3 PC3-12800 1600MHz

And finally a CPUZ report;
http://pastebin.com/wvW2ZnS9
 
Thank you.

On Fri 2013-11-22 20:55:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112213-56331-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x5100, 0xFFFFF6FC4001DAB8, 0x1, 0x80000001DADF2963)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
 
It says that "The allocation bitmap is corrupt. The memory manager is about to overwrite a virtual address that was already in use." but I'm not sure what that means.

I enabled Driver Verifier and rebooted my computer. I re-ran the test that crashed my computer before and I got a new BSOD this time.

On Sat 2013-11-23 14:51:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-54428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0xFFFFF87FE7488044, 0x2, 0x8, 0xFFFFF87FE7488044)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
 
I installed the plugin and missing drivers, then ran the same thing that crashes the computer, and I get BSODs with different error messages every time. They all seem to be memory related though, so I ran memtest86 and got 1122 errors at test 5 between 3072.1MB and 3455.8MB (8gb RAM installed)

Maybe if I'd let it run for longer I'd get more errors at different addresses. I'm going to start running each stick separately and see what I get.

Is errors at test 5 very bad?

Pic: http://i42.tinypic.com/2buo2r.jpg
 

TRENDING THREADS