MEMORY_MANAGEMENT Blue Screens on new Build

Toggle sidebar Toggle sidebar
M

Msolwold

Reputable
Dec 23, 2014
18
0
4,510
Hey all,

I've been beating my head up against a wall for the past few days and I'm at the end of my rope.

System:

Link...

For some reason the RAM wasn't listed correctly but I have this insalled:

Link...

Situation:

Randomly since about 2 days after the build was finalized I started to experience random BSOD's. The most common error being "MEMORY_MANAGEMENT" but I have also seen IRQl_not_less_or_equal a few times when it would crash on startup. I have links to the most recent Dump files at the end.

Attempts to fix:

RAM: Fairly Certain this is not the cause


  • Ran memtest to 4 passes - No Errors
    Swapped Sticks to different slots
    Ran each stick separately

Video Card: Possibility


  • Ran on board card - This didn't result in a Blue Screen but...
    Ran with an Old AMD GPU - This did Blue Screen me.
    I haven't tested without the GPU again yet but my assumption is that since it BSOD'd with the old card that ran fine in my previous build I just didn't wait long enough when running off the on-board graphics. Will try again if someone feels this could be an issue

Hard Drive: Certain this isn't the cause


  • I went out and bought a new SSD and installed Windows on it. I needed a new one anyway.

Dump Files:

Since I recently swapped in a new drive i don't have the old Dump files. As I BSOD I will update this list.

Memory Management:


  • BSOD_1
    ==================================================
    Dump File : 090815-4703-01.dmp
    Crash Time : 9/8/2015 3:50:46 PM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00041201
    Parameter 2 : fffff680`00276180
    Parameter 3 : b2a00001`f29e6847
    Parameter 4 : ffffe001`3d289a50
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+14cc20
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.10240.16384 (th1.150709-1700)
    Processor : x64
    Crash Address : ntoskrnl.exe+14cc20
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\090815-4703-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 10240
    Dump File Size : 356,736
    Dump File Time : 9/8/2015 3:53:08 PM
    ==================================================

    BSOD_2
    ==================================================
    Dump File : 090815-5171-01.dmp
    Crash Time : 9/8/2015 4:48:57 PM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00041793
    Parameter 2 : fffff680`771c6490
    Parameter 3 : 00000000`0000000b
    Parameter 4 : 00000000`0000000a
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+14cc20
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.10240.16384 (th1.150709-1700)
    Processor : x64
    Crash Address : ntoskrnl.exe+14cc20
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\090815-5171-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 10240
    Dump File Size : 354,624
    Dump File Time : 9/8/2015 4:50:14 PM
    ==================================================

    BSOD_3 (It didn't prompt a Blue Screen but this was in the Blue Screen View)

    ==================================================
    Dump File : 090815-4890-01.dmp
    Crash Time : 9/8/2015 5:35:07 PM
    Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code : 0x0000001e
    Parameter 1 : ffffffff`c0000005
    Parameter 2 : fffff800`7e43720c
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00100010
    Caused By Driver : NTFS.sys
    Caused By Address : NTFS.sys+9720c
    File Description : NT File System Driver
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.10240.16384 (th1.150709-1700)
    Processor : x64
    Crash Address : ntoskrnl.exe+14cc20
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\090815-4890-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 10240
    Dump File Size : 355,752
    Dump File Time : 9/8/2015 5:38:08 PM
    ==================================================

    BSOD_4

    ==================================================
    Dump File : 090815-4468-01.dmp
    Crash Time : 9/8/2015 5:38:47 PM
    Bug Check String : KERNEL_DATA_INPAGE_ERROR
    Bug Check Code : 0x0000007a
    Parameter 1 : 00000000`00000001
    Parameter 2 : ffffffff`c0000005
    Parameter 3 : ffffe001`e0a98580
    Parameter 4 : fffff6bf`fe945000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+14cc20
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.10240.16384 (th1.150709-1700)
    Processor : x64
    Crash Address : ntoskrnl.exe+14cc20
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\090815-4468-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 10240
    Dump File Size : 349,648
    Dump File Time : 9/8/2015 5:39:34 PM
    ==================================================

Thank you in advance to anyone who is able to help. Do not hesitate to ask any questions.

Current Fix:


  • Updating BIOS, waiting for the issue to repeat itself or Friday afternoon. If it doesn't reacur by Friday afternoon i will select rdg1101's answer as the solution.
 
Sort by date Sort by votes
M

Msolwold

Reputable
Dec 23, 2014
18
0
4,510
Quick Update:

It just BSOD'd again but this time it actually acted up beforehand.

I was letting it sit at the desktop and the Taskbar started flashing and acting very strange. I waited for a second and moved my character in World of Warcraft and it Blue Screened.

Dump File:

==================================================
Dump File : 090815-5171-01.dmp
Crash Time : 9/8/2015 4:48:57 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041793
Parameter 2 : fffff680`771c6490
Parameter 3 : 00000000`0000000b
Parameter 4 : 00000000`0000000a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14cc20
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10240.16384 (th1.150709-1700)
Processor : x64
Crash Address : ntoskrnl.exe+14cc20
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090815-5171-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 10240
Dump File Size : 354,624
Dump File Time : 9/8/2015 4:50:14 PM
==================================================

Looks like a different Perimeter?
 
Upvote 0 Downvote
M

Msolwold

Reputable
Dec 23, 2014
18
0
4,510
It is running 1.00, I'll update it.

It also just randomly Froze, had to force shut down and upon startup it BSOD'd almost immediately with these in Blue Screen View:

When it Froze:

==================================================
Dump File : 090815-4890-01.dmp
Crash Time : 9/8/2015 5:35:07 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`7e43720c
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00100010
Caused By Driver : NTFS.sys
Caused By Address : NTFS.sys+9720c
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10240.16384 (th1.150709-1700)
Processor : x64
Crash Address : ntoskrnl.exe+14cc20
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090815-4890-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 10240
Dump File Size : 355,752
Dump File Time : 9/8/2015 5:38:08 PM
==================================================

On Startup:

==================================================
Dump File : 090815-4468-01.dmp
Crash Time : 9/8/2015 5:38:47 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 00000000`00000001
Parameter 2 : ffffffff`c0000005
Parameter 3 : ffffe001`e0a98580
Parameter 4 : fffff6bf`fe945000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14cc20
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10240.16384 (th1.150709-1700)
Processor : x64
Crash Address : ntoskrnl.exe+14cc20
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090815-4468-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 10240
Dump File Size : 349,648
Dump File Time : 9/8/2015 5:39:34 PM
==================================================

I will update the BIOS drivers and post the results. Thank you for the advice.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
error codes: c0000005 = bad memory address, unable to read data from storage
error codes: 00041793 = some internal error code coming from COM/OLE Interface management

I would guess you have memory corruption caused by a driver or bad RAM timings.

I would start by running by updating the BIOS or resetting it to defaults and and run memtest86 to confirm your memory is good,
then boot windows, run cmd.exe as an admin then run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth

windows 10 upgrade do tend to show corruptions, where a clean install does not. you have to look at the logs but the ones I looked at were not the issue.


because of the data inpage error (the system could not read data from storage) you should run crystaldiskinfo.exe and read your smart data to see if your drive has problems. otherwise, look for a update for your SATA drivers, check drive data and power connections, maybe change the port your drive is connected to (use a primary slower port, they tend to be supported by the CPU chipset rather than a external chipset driver)
the error code was (0xc0000005) so it could also be memory corruption in the drivers data held in RAM. (memory hardware problem or device driver overwriting the contents of the memory, you can not tell without running verifier or memtest86)
 
Upvote 0 Downvote
M

Msolwold

Reputable
Dec 23, 2014
18
0
4,510
I haven't disappeared, just haven't ran into any issues since updating the BIOS. I haven't had much of a chance to test it out long term but it was stable for 8+ hours last night. Thank you for that suggestion because as of now it seems to have been the fix.

@Johnbl - I'll keep this in mind if the problem returns. Thank you very much for your detailed response.

EDIT: I will select rdg1101's answer as the solution if there are no crashes by Friday. Thank you to anyone else who shows interest in the thread.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom