NVME SSD BSOD system store exception (when GPU is underclocked to 914mhz everything works normally)

Jul 31, 2018
23
0
20
I am getting system store exception bsod when i am running windows 10 from my nvme ssd (on my hdd i don't get any bsod-s, and sometimes i get critical proces died bsod too)

PC specs:
CPU:G4560
GPU:RX 560
MOBO: Z170 D3H
RAM:2X4GB DDR4 HYPER X FURY

 
Solution
I fixed this problem/s. First thing I did is that I don't use any extension cord that fixed BSOD but I was still getting a red screen which I fixed by changing PCIe slot in which my GPU is because I have two PCIe slots.
Jul 31, 2018
23
0
20
Just writing an update screen went red just red I couldn't do anything after that I got system store exception BSOD. After that, I tried another graphics card but same BSOD so it's still something with SSD because of both GPU-s work on windows on HDD.

Edit: also I forgot to mention my SSD is a Patriot Scorch 128gb.
 
Jul 31, 2018
23
0
20
Seems that I found a fix for this problem when I underclock my GPU to 914mhz everything is working normally no BSOD nothing everything works. So I thought it is maybe a driver problem tried older ones same thing at stock clock and then I tried installing the driver to HDD and when I play games that are on SSD at the start they are stuttering at stock clock and windows starts to "fall apart" and when I underclock GPU everything is normal. Any ideas what's causing this to happen?
 
if you can boot, then start cmd.exe or powershell and run
dism.exe /online /clean-image /restorehealth

I think one of the things it does is repair the windows component store (WinSxS folder)
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
(might tell you what is wrong with component store but I have never used it)


if changing the gpu timing had any effect I would be looking to update the motherboard sound drivers.
versions that came out in 2017 tend to work while the older versions would crash the gpu sound driver and crash the GPU
(update motherboard sound driver from the motherboard vendors website)

 
Jul 31, 2018
23
0
20


This is what i get when i type in dism.exe /online /clean-image /restorehealth

Microsoft Windows [Version 10.0.17134.165]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Windows\system32>dism.exe /online /clean-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.165


Error: 87

The clean-image option is unknown.
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

And this is what I got when I typed Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

C:\Windows\system32>Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.165

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 8.67 GB

Actual Size of Component Store : 8.24 GB

Shared with Windows : 5.72 GB
Backups and Disabled Features : 2.33 GB
Cache and Temporary Data : 192.31 MB

Date of Last Cleanup : 2018-04-12 01:45:02

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : Yes

The operation completed successfully.

And I am running latest audio drivers from gigabyte. Also, I am getting new BSOD which sais SYSTEM SERVICE EXCEPTION when on stock clock on GPU.

edit: I also tried to reinstall windows and create new windows installation and install it again, but still same problems.
 
Jul 31, 2018
23
0
20


I don't think it is a PSU problem because when I boot windows on HDD everything works fine on stock clock but on SSD it doesn't, also I borrowed from my friend evga supernova 750W g2 PSU and the same thing is happening.
 
sorry /clean-image should have been /cleanup-image

you should provide the memory dump file from c:\windows\minidump directory
sometime people have drivers installed that are know to corrupt memory data structures. these are pretty easy to spot in a memory dump file when using a debugger
 
Jul 31, 2018
23
0
20


There is no minidump directory. Maybe because when I get BSOD it never gets past 0%?
 
make sure your system is configured to save a memory dump, also make sure your system has a pagefile.sys (virtual memory) and has plenty of free space on the drive.

generally if the memory dump can not be saved and you have a valid configuration the problem will be in the storage subsystem. (sata controller driver, firmware of the bios or ssd, or bad connections to the storage device)

it might be good to google "how to force a memory dump with a keyboard" then make the registry changed and force a memory dump to confirm your settings work before the machine hits a real bugcheck.



 
Jul 31, 2018
23
0
20


It is configured to save memory dumb but whenever I get any BSOD it won't get past 0%. And now I am getting critical process died, system store exception and one more system store something I forgot what it said BSOD. Even on 914mhz underclock.
 
kernel in page error means that some driver could not read from storage.
the bugcheck code parameter 1 might provide a clue as to the type of failure.

basically, you would update the bios, the sata drivers, the firmware of the SSD, check power connections, data connections make sure the drive is not using some strange port number. Make sure there is plenty of free space on a SSD so that the firmware does not get behind in doing its internal cleanup. Sometimes, just boot into bios and leave the drive idle for a few hours to allow the drive to do its cleanup.
scan for malware infecting the storage driver.

force a memory dump while the machine is working then provide the memory dump. A memory dump of a working system can still be checked for corruption using a windows debugger.








 
Jul 31, 2018
23
0
20
I fixed this problem/s. First thing I did is that I don't use any extension cord that fixed BSOD but I was still getting a red screen which I fixed by changing PCIe slot in which my GPU is because I have two PCIe slots.
 
Solution