New Build Issues

Sep 12, 2018
7
0
10
Hi All,

I recently completed a new build. it boots up with no issues however after 30 minute - 1 hour of playing it will blue screen and restart. One error was:

- page_fault_in_nonpaged_area
- irql_not_less_or_equal
- others that I can't remember

I took out my ram and added it in one at a time and my system is stable without any blue screens. I have downloaded all the recent drivers for my motherboard and graphics card but that doesn't seem to help. I don't have another computer to run tests on.

Does anyone have any ideas what could be the issue? I don't want to buy components without knowing what could be broken.

Thanks a lot,
Dan
 
Solution
you need to remove the overclocking software and see if you can still get a bugcheck.
if you do, you need to provide the memory dump file so it can be looked at with the windows debugger.
generally you would look up the pool tag Ussx and find out what component it belongs to.
a pool tag is a 4 char txt added to all memory allocations so that the memory allocation can be tracked back to its component. generally these will be found in pooltag.txt file in the windows device driver dev kit. I normally look at https://www.osr.com to view the file but can not log in this morning.

findstr.exe /m /l Ussx *.sys
indicates the tag if from win32kfull.sys





Sep 12, 2018
7
0
10
Windows 10
Intel Core i7 7700k 4.2GHz
16GB (2 > 8) GSkill Ripjaws V 2400
Gigabyte Technology Co. Ltd. Z270XP-SLI-CF
NVIDIA GeForce GTX 1080 Ti (Gigabyte)
Samsung SSD 860 EVO 500GB
 
Sep 12, 2018
7
0
10


I also did some checking on that I found a few things. Those seem to be the common errors that I am getting either right before or during a BSOD.


  • LKD_INSTR_SESSION_POOLTAG_Ussx
    0x139_3_CORRUPT_LIST_ENTRY_nt!CmpDelayCloseWorker
    EasyTuneEngineService stopped working
    OcButtonService Stopped working
 

Ralston18

Titan
Moderator
Consider that some files have been corrupted and/or possible problems with the SSD.

Disable any related software from startup and do not launch on your own.

Determine if the system stabilizes or if other problems appear.

Run the applicable Samsung diagnostic software on the SSD.





 
Sep 12, 2018
7
0
10


I have followed the instructions below to check for corrupted files and it didn't find any. I also downloaded Samsung Magician and that didn't find any issues with my SSD. Are there other tools I can use to figure out if my SSD has corrupt files or is faulty?

https://support.microsoft.com/en-us/help/4026529/windows-10-using-system-file-checker
 
you need to remove the overclocking software and see if you can still get a bugcheck.
if you do, you need to provide the memory dump file so it can be looked at with the windows debugger.
generally you would look up the pool tag Ussx and find out what component it belongs to.
a pool tag is a 4 char txt added to all memory allocations so that the memory allocation can be tracked back to its component. generally these will be found in pooltag.txt file in the windows device driver dev kit. I normally look at https://www.osr.com to view the file but can not log in this morning.

findstr.exe /m /l Ussx *.sys
indicates the tag if from win32kfull.sys





 
Solution