Blue screen kernel memory error
|
since two patches ago, after playing PoE for roughly 30 minutes or so it blue screens telling me there is a kernel memory error and it requires to shut down my computer to protect my data.
I've been playing other games and letting my pc run for 16 hours non-stop in the mean time without any functionality issue's or new blue screens. It only seems to happen when running PoE. Any suggestions? Peace, -Boem- Freedom is not worth having if it does not include the freedom to make mistakes Last bumped on May 19, 2018, 10:00:20 AM
| |
|
Bluescreen view and copy paste the full error.
The only BSoD i've had recently was due to some janky interaction between corsair link and the PC, Link being a fan control program and RGB led colour selector...there should be nothing in it that causes a BSoD but it was freezing stuff hard enough that it would cause one (mainly one boot before even doing anything giving graphical artefacts, one just straight up BSoDing) Since uninstalling it the PC has been fine. Ancestral Bond. It's a thing that does stuff. -Vipermagi
He who controls the pants controls the galaxy. - Rick & Morty S3E1 |
|
|
first blue screen
Dump File : 051618-24414-01.dmp
Crash Time : 16/05/2018 12:28:14 Bug Check String : MEMORY_MANAGEMENT Bug Check Code : 0x0000001a Parameter 1 : 00000000`00041287 Parameter 2 : 00000000`00000000 Parameter 3 : 00000000`00000000 Parameter 4 : 00000000`00000000 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+a44a0 File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Processor : x64 Crash Address : ntoskrnl.exe+a44a0 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\051618-24414-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 7601 Dump File Size : 407.088 Dump File Time : 16/05/2018 12:29:33
second blue screen
Dump File : 051818-19234-01.dmp
Crash Time : 18/05/2018 15:17:29 Bug Check String : MEMORY_MANAGEMENT Bug Check Code : 0x0000001a Parameter 1 : 00000000`00041201 Parameter 2 : fffff682`1e677950 Parameter 3 : ce100002`cb8cb947 Parameter 4 : fffffa80`12a4c2d0 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+a44a0 File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 6.1.7601.24117 (win7sp1_ldr_escrow.180422-1430) Processor : x64 Crash Address : ntoskrnl.exe+a44a0 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\051818-19234-01.dmp Processors Count : 8 Major Version : 15 Minor Version : 7601 Dump File Size : 407.048 Dump File Time : 18/05/2018 15:18:37 Hope this helps, cheers lagwin \o Peace, -Boem- Freedom is not worth having if it does not include the freedom to make mistakes
| |
|
This MEMORY_MANAGEMENT 0x0000001a is showing possibly as a ram error.
The recommended things to do is to run memtest for 4 hours as a diagnostic tool. Running as admin Windows memory diagnostic And the SFC Scanner.
Spoiler
The SFC/SCANNOW command is Microsoft’s tool for resolving various system problems. Even if it doesn’t sound like an actual solution, a lot of users who received this error message, even after multiple restarts, said that the SFC/SCANNOW command resolved the problem.
Here’s exactly what you need to do to run this command: Right-click on the Start Menu button and go to Command Prompt (Admin) Enter the following line into Command Prompt and press Enter: sfc/scannowmemory management fix Wait until the process is finished (it may take a while) and see if any errors are fixed Unfortunately, as is the way with BSoD's the other help devolves into non specific stuff which is unlikely to help. Ancestral Bond. It's a thing that does stuff. -Vipermagi
He who controls the pants controls the galaxy. - Rick & Morty S3E1 |
|
" thanks a bunch dude, i'll let this process run tomorrow and see if it resolves the issue. Bless you for your time sir \o Peace, -Boem- Freedom is not worth having if it does not include the freedom to make mistakes
| |
|
It is also possible that the RAM is badly seated and liable to intermittent contact issues. Certainly worth while to remove it and carefully reinstall.
The error you list is "usually" memory related. I am presuming all RAM chips you have are properly matched. In any case running a full check on memory will usually tell you if there are faults with RAM. OCEANIC EXILES https://www.pathofexile.com/forum/view-thread/581434
|
|
" So i have done the sfc/scannow command (i tried copy pasting what you suggested sfc/scannowmemory but that didn't do anything? :p) and the windows memory diagostic tool both found no errors and came back clean. I'm gonna hold of on the memtest since my pc is going to the store next thursday for a new gpu card and to fit in an SSD hard drive. I'm gonna tell them about this and will let them do the other necessary test's. Cheers for the help both of you, i'll resurrect this thread if it still persists after i get my pc back from the store, i am hoping they can resolve this issue. Peace, -Boem- Freedom is not worth having if it does not include the freedom to make mistakes
|
