Windows 10: Bsod 0x154, help locate the issue

Hello, I've been getting bsod unexpected_store_exception with code 0x154. I noticed it happens much more frequently if I launch demanding game eg. witcher 3. While on desktop bsod doesnt appear.
The issue is that I can't locate the core of the problem as all tests I performed show me everything is alright...
Crystal Disk info show me everything is okay,
HDTune show me everything is okay,
memtest showed no issues after whole night running,
Malwarebytes did not find any malware,
chkdsk /r says everything is okay,
sfc /scannow did not find any issues,
driver verifier failed to force the crash,
my windows version is updated as well as GPU drivers
Here's some of pics regarding my system performance
Here's my bsod descriptions
==================================================
Dump File : 090218-23890-01.dmp
Crash Time : 02.09.2018 03:05:57
Bug Check String :
Bug Check Code : 0x00000154
Parameter 1 : ffffaf0e`b31f4000
Parameter 2 : ffffa085`45740490
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1a8ca0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1a8ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\090218-23890-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 17134
Dump File Size : 744 812
Dump File Time : 02.09.2018 03:07:38
==================================================

==================================================
Dump File : 090218-26328-01.dmp
Crash Time : 02.09.2018 12:57:08
Bug Check String :
Bug Check Code : 0x00000154
Parameter 1 : ffffc205`6d2de000
Parameter 2 : ffffbf83`da3d3490
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1a8ca0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1a8ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\090218-26328-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 17134
Dump File Size : 767 172
Dump File Time : 02.09.2018 12:58:37
==================================================

==================================================
Dump File : 090218-25250-01.dmp
Crash Time : 02.09.2018 13:44:40
Bug Check String :
Bug Check Code : 0x00000154
Parameter 1 : ffffe08c`5858f000
Parameter 2 : fffff28a`f7d240b0
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+d867
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1a8ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\090218-25250-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 17134
Dump File Size : 729 500
Dump File Time : 02.09.2018 13:46:10
==================================================

==================================================
Dump File : 090218-24718-01.dmp
Crash Time : 02.09.2018 13:59:47
Bug Check String : CRITICAL_PROCESS_DIED
Bug Check Code : 0x000000ef
Parameter 1 : ffffcf80`730ef340
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1a8ca0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1a8ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\090218-24718-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 17134
Dump File Size : 613 660
Dump File Time : 02.09.2018 14:01:17
==================================================

==================================================
Dump File : 090218-27531-01.dmp
Crash Time : 02.09.2018 15:24:51
Bug Check String :
Bug Check Code : 0x00000154
Parameter 1 : ffffd208`7c870000
Parameter 2 : ffff828d`4b5c4370
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1a8ca0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1a8ca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\090218-27531-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 17134
Dump File Size : 744 884
Dump File Time : 02.09.2018 15:26:43
==================================================

:)

 

Location service is greyed out

Hi Shahriar,

Thank you for responding.

Sorry for the inconvenience caused for you, I suggest you to try the below troubleshooting steps and check If it helps.

Step 1: Steps to turn on the Location settings.

• Login as an administrator.
• Press Windows key, type Location settings and select
  Change location settings.
• Check whether Location for this device is On by clicking on
  Change.
• Also turn on Location as well.

Step 2: And as you are unable to set the service Geolocation service to automatic, I suggest you to run SFC scan and check.

System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files.

Follow the below steps:

• 
  Right click on the Start button, click on
  Command Prompt (Admin).
  
• 
  Type “sfc /scannow” without the quotes and hit
  Enter.
  
• 
  After the scan, restart the computer and check for the issue.
  

Try to set the service to automatic by following the steps provided in the above post by Praveen Venugopal.

Hope it helps. Kindly update the status of the issue, we will be happy to help you.

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

Location setting

Hi,



This issue could occur due to incorrect location settings or it would depend on your IP address. We suggest you to check the location settings of your PC, and check if it helps. Here are the steps:

• Click the Start button, and select Settings.
• Go to Privacy, and choose Location.
• Make sure that the Location service is On.

If issue persists, then it has something to do with your IP address. It’s because the location detected depends on the location set on your IP address.



Let us know how it goes.