Blue Screen of Death - ntoskrnl.exe - Memory Management

OGSnow

Reputable
Mar 24, 2016
148
1
4,695
Hi. This happened today. PC was working fine as usual, ran origin in offline mode, and started mass effect 1 through desktop shortcut (game didn't opened, screen froze after double click then blue screen) and this happened. (i know it has nothing to do with origin or mass effect i'm just recreating the event)

Honestly i'm terrified of blue screen, it genuinely sent a chill down my spine.
Below the info about it.

#

A problem has been detected and Windows has been shut down to prevent damage to your computer.

The problem seems to be caused by the following file: ntoskrnl.exxe

MEMORY_MANAGEMENT

Technical Information:

*** STOP: 0x0000001a (0x0000000000041790, 0xfffffa800b942310, 0x000000000000ffff,
0x0000000000000000)

*** ntoskrnl.exe - Address 0xfffff800032c0380 base at 0xfffff80003250000 DateStamp
0x56eb24e6

#

Info from BlueScreenViewer:

Dump File: 020818-20155-01.dmp
Crash Time: 08/02/2018 20:38:59
Bug Check Code: 0x0000001a
Parameter 1: 00000000`00041790
Parameter 2: fffffa80`0b942310
Parameter 3: 00000000`0000ffff
Parameter 4: 00000000`00000000
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+70380
File Description: NT Kernel & System
Product Name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File Version: 6.1.7601.23392 (win7sp1_ldr.160317-0600)
Processor: x64
Crash Address: ntoskrnl.exe+70380
Full Path: C:\Windows\Minidump\020818-20155-01.dmp
Processors Count: 8
Major Version: 15
Minor Version: 7601
Dump File Size: 407.744
Dump File Time: 08/02/2018 20:40:13

#

Afterwards, PC rebooted, tried doing the exact same thing that caused the crash and it didn't.
Ran windows' memory diagnostic tool, rebooted, 2 scans, no error found, booted normally.
Try HD Tune, crystalinfo and Seagate tools, all according to it, both my ssd and hhds are in good shape.

I don't know what else to do and fear will happen again at a sudden moment.
I did a basic google search and apparently could be my ram sticks and i should replace it
but i'm not sure. Is the info i provided enough to narrow down the issue and solve it?

PC's been on for about 2 hours ever since and all seem normal but like i said, i'm afraid it'll pop up on me at any given time.

Any help would be greatly appreciated. Thanks for the attention.
 


The only Razer hardware i have is the Man 'O War Headset. I checked Razer Synapse and it is up to date so i do not know how to proceed. Plus, Razer? What does Razer has to do with Memory Management indicating in the error screen? I apologize if i am sounding rude i merely want to understand.

Regarding the Clonecd, i am not quite sure of what you're referring to. The only thing i can find is the Virtual Clone Drive program which i have no idea how to update it's drivers as i didn't even know it had drivers or am i mistaken? The only option i have is to uninstall the program altogether.

Thanks.
 


Wait! But what can i do about this, then? Razer Synapse is up to date i got nothing else to do!
Should i unplug my headset? Uninstall all Razer components from my PC? I always used Razer headsets
never had any problems with them! Please, there's got to be something!
 
This is all really strange to me. I will wait a little bit more for other members to check the thread for different inputs. I never had luck with costumer support. I find it difficult that Razer will do something about it.

Like i said, i will wait and HOPEFULLY more people will check the thread, multiple opinions is sure to help i am thinking.

Fingers crossed not to get this blue screen again. It sure is scary. I appreciate your help.
 
It's a shame no one else could chime in in the thread. It's been almost 10 days and thankfully the issue haven't re-appear so far and i've been playing games normally. Also cleaned my rams. I can't send Razer the dmp file and say it's crashing the system when it's not consistent. Happened once, didn't happen again. There's no way to know 100% that that service is the culprit. As of now i will leave the matter be. (will try at least, i'm paranoid by nature) rams are clean, as said before. if the issue re-appear at some point, will replace rams altogether. If even then the problem re-surfaces, then i'll throw in the towel. But as things stands, it doesn't look like it'll come to that. So, fingers crossed and hopeful. Thanks.