Extremely random BSOD

[MapDitto]

Hi,
So to start off I am extremely new when it comes to posting on forums, this is probably my first post ever, please bear with me.

Currently, my gaming desktop would give me a BSOD at random times, I can't figure out what is triggering it. Most of the time, these BSOD occurs when I'm playing my games. I'll be playing games like Overwatch, down to simple a game like Old School Runescape, and it would cut out. Some sessions could last 6-8 hours without a problem, other times it can give-out within first 15 minutes. On the rare occasions it would crap out when I'm watching a movie or doing uni work. I would say that I'm a pretty tech savvy guy and know my way around a computer, but this problem is a little more in-depth for me to figure out. My best googling skills had me using BlueScreenViewer and that led to a dead-end, then I used WinDbg(x64) to see if that would show something. I skimmed through its analysis, but it also came up with "Unknown_Image (ANALYSIS_INCONCLUSIVE). So I just copied and paste stuff from that report, which led me here. Hopefully that's a detailed enough scenario. I'm not sure what to do anymore, I've taken it to two different computer repair guys and they haven't been able to pinpoint it either. **I also attached what the WinDbg pulled out.

---------------------------------------------------------------------------------------------------------
· OS - Windows 10
· x64
· Original OS: Windows 8.1
· Full retail version, installed it myself.
· Full set is around 2 years old

-Originally built with Gtx 960, then upgrade to Gtx 1060 when they came out
​

· OS was 8.1, then used the free windows 10 upgrade
· AMD: FX-8350 Series 8
· GTX 960 -> GTX 1060 6gb (current)
· Motherboard: Asus M5A99X EVO R 2.0
· Power Supply: XFX TS SERIES P1550SXXB9 550W
· Desktop---------------------------------------------------------------------------------------------------------

View attachment SysnativeFileCollectionApp.zip
View attachment Bug check analysis.txt

 

[x BlueRobot]

Could you please provide a kernel memory dump file? It should be found in the following directory:

%systemroot%\MEMORY.DMP

The file will be rather large (possibly a few GB), and therefore, I would recommend you zip the file and upload it to a file sharing site such as Dropbox. Please post the URL to the file in your next post.

 

[MapDitto]

Could you please provide a kernel memory dump file? It should be found in the following directory:

%systemroot%\MEMORY.DMP

The file will be rather large (possibly a few GB), and therefore, I would recommend you zip the file and upload it to a file sharing site such as Dropbox. Please post the URL to the file in your next post.

Earlier this morning I tried looking for the dump, it wasn't anywhere to be found. So I tried doing my usual routine to see if I can trigger a BSOD. I was able to make it crash, while it was in the rebooting process, it crashed at least 2 more times, each with different exceptions. The final crash was a KMODE_EXCEPTION_NOT_HANDLED. I let it sit their at 100% while I go to work, came back home 5 hours later and it was still the same screen. Hopefully me giving you these details help a bit, if not I'll stop mentioning them. I was able to get a memory.dmp after focing my computer to turn off, but the file is barely under 100MB.

Link: Dropbox - Memory Dump.zip

Thanks

 

[cwsink]

Looking at the system events it seems like you've been getting quite a variety of bugchecks since early December last year. There is also a 0x124 bugcheck which suggests a hardware problem. Looking at the CPU information it would appear that yours is overclocked if this is correct:

1: kd> !sysinfo cpuinfo
[CPU Information]
[COLOR=#ff0000]~MHz = REG_DWORD 4335[/COLOR]
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 21 Model 2 Stepping 0
ProcessorNameString = REG_SZ [COLOR=#0000ff]AMD FX(tm)-8350 Eight-Core Processor[/COLOR]           
Update Status = REG_SZ Newer Patch Not Available"
VendorIdentifier = REG_SZ AuthenticAMD

The specs for your CPU indicate the maximum officially supported speed is 4.2GHz and yours is at 4.335GHz. If you have any overclocking tools installed please uninstall them. I'd also recommend going into the BIOS settings menus and loading the default settings profile and then Save & Exit. From what I can tell all of the bugchecks could be explained by a CPU being pushed too hard or possibly overheating.

 

[x BlueRobot]

I was hoping that you would have another Stop 0x101, since it is more useful than a Stop 0x1E. I would suggest following cswink's advice and restoring the BIOS settings to default.

1: kd> [COLOR=#008000]!sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.7, DMIVersion 0, Size=2484]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 2501
BiosReleaseDate = [COLOR=#ff0000]04/03/2014[/COLOR]
SystemManufacturer = To be filled by O.E.M.
SystemProductName = To be filled by O.E.M.
SystemFamily = To be filled by O.E.M.
SystemVersion = To be filled by O.E.M.
SystemSKU = SKU
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = [COLOR=#ff0000]M5A99X EVO R2.0[/COLOR]
BaseBoardVersion = Rev 1.xx

Have you checked for any BIOS updates?

[COLOR=#ff0000]BugCheck 1E[/COLOR], {[COLOR=#0000ff]ffffffffc0000005[/COLOR], [COLOR=#008000]fffff80051f33f04[/COLOR], 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+14 )

The first and second parameters of the bugcheck are the most useful, however, it appears that the exception address reported in the second parameter is different to the address stored in the exception record? The exception record appears to be more accurate judging by the call stack.

1: kd> [COLOR=#008000].exr 0xffffd8856b96a908[/COLOR]
ExceptionAddress: fffff800520aa895 ([COLOR=#ff0000]nt!MI_GET_PAGE_FRAME_FROM_PTE[/COLOR]+0x0000000000000009)
   ExceptionCode: 52419000
  ExceptionFlags: fffff800
NumberParameters: -1
   Parameter[0]: fffff800520aa8ec
   Parameter[1]: 0000000000000010
   Parameter[2]: 0000000000000000
   Parameter[3]: ffffd8856b96a950
   Parameter[4]: 0000000000000000
   Parameter[5]: 0000000000000000
   Parameter[6]: fffff80051f33f04
   Parameter[7]: 0000000000000010
   Parameter[8]: 0000000000010246
   Parameter[9]: ffffd8856b96a980
   Parameter[10]: 0000000000000018
   Parameter[11]: 0000000000000001
   Parameter[12]: 0000000000000001
   Parameter[13]: ffff69e9d5683403
   Parameter[14]: 0000000000000001

The rest of the exception record appears to be garbage values. The error code appears to be a form of assertion, and indicates an invalid page frame number (PFN), which is used in the translation virtual addresses (addresses accesible to processes) to physical addresses (RAM). The processor does play a large role in this address translation, and therefore could still be the culprit.

The call stack provides some further evidence of a page fault which has ended in disaster:

1: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 ffffd885`6b969f58 fffff800`51f286c9 nt!KeBugCheckEx
01 ffffd885`6b969f60 fffff800`5200c602 nt!KiDispatchException+0x239
02 ffffd885`6b96a610 fffff800`52008110 nt!KiExceptionDispatch+0xc2
03 ffffd885`6b96a7f0 fffff800`51f33f04 nt!KiGeneralProtectionFault+0x3d0
04 ffffd885`6b96a980 fffff800`51ef9363 [COLOR=#ff0000]nt!KxWaitForLockOwnerShip+0x14[/COLOR] << Likely a spinlock sychronization mechanism, fails here for some reason
05 ffffd885`6b96a9b0 fffff800`51ef7347 nt!MiUnlinkPageFromList+0xa53
06 ffffd885`6b96aa50 fffff800`51ef0aef [COLOR=#ff0000]nt!MiResolveTransitionFault+0x607[/COLOR] << Attempt to resolve the fault by creating a map to physical memory
07 ffffd885`6b96ab10 fffff800`51eeeadc nt!MiDispatchFault+0x121f
08 ffffd885`6b96acb0 fffff800`5200854e nt!MmAccessFault+0xd6c
09 ffffd885`6b96ae80 fffff800`51ecd0c4 [COLOR=#ff0000]nt!KiPageFault+0x40e[/COLOR] << Process wishes to access an address, but isn't mapped yet, so issues a page fault
0a ffffd885`6b96b018 fffff800`52375156 nt!HvpFaultCellWithClustering+0x24
0b ffffd885`6b96b020 fffff800`52374c92 nt!HvpGetCellPaged+0x76
0c ffffd885`6b96b050 fffff800`523720fa nt!CmQueryValueKey+0x282
0d ffffd885`6b96b180 fffff800`5200c003 nt!NtQueryValueKey+0x4ba
0e ffffd885`6b96b3d0 fffff800`51ffcf30 nt!KiSystemServiceCopyEnd+0x13
0f ffffd885`6b96b5d8 fffff800`523a15fa nt!KiServiceLinkage
10 ffffd885`6b96b5e0 fffff800`523a153b nt!EtwpGetGuidSecurityDescriptor+0x7a
11 ffffd885`6b96b620 fffff800`523a1820 nt!EtwpGetSecurityDescriptorByGuid+0xc3
12 ffffd885`6b96b720 fffff800`523a1fdf nt!EtwpAccessCheckFromState+0x1c
13 ffffd885`6b96b790 fffff800`523a1b99 nt!EtwpAddRegEntryToGroup+0x30f
14 ffffd885`6b96b8b0 fffff800`523a19e6 nt!EtwpSetProviderTraitsCommon+0x17d
15 ffffd885`6b96b960 fffff800`5235e0ad nt!EtwpSetProviderTraitsUm+0x162
16 ffffd885`6b96b9e0 fffff800`5200c003 nt!NtTraceControl+0x2bd
17 ffffd885`6b96ba90 00007ffa`a67c3594 nt!KiSystemServiceCopyEnd+0x13
18 0000003c`8079d7f8 00000000`00000000 0x00007ffa`a67c3594

I noticed that when I looked at the thread stack using !dpx, an !avast driver appeared to be present at the time of the crash, have you checked that you're running the latest version? Alternatively, you may wish to uninstall the program using the avast! uninstall tool (Avast Uninstall Utility | Download aswClear for Avast Removal) for testing purposes:

1: kd> [COLOR=#008000]lmvm  aswSnx[/COLOR]
Browse full module list
start             end                 module name
fffff800`f3410000 fffff800`f3508000   aswSnx     (no symbols)           
    Loaded symbol image file: aswSnx.sys
    Image path: \SystemRoot\system32\drivers\aswSnx.sys
    Image name: aswSnx.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=#ff0000]Tue Oct 31 16:40:52 2017[/COLOR] (59F8A794)
    CheckSum:         00103E0F
    ImageSize:        000F8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4