BSOD Randomly

Page 3 of 3 FirstFirst 123

  1. Posts : 38,430
    windows 10 professional version 1607 build 14393.969 64 bit
       #21

    If there is another bsod crash perform the following steps:
    a) run the beta log collector > post a new zip into the thread
    b) open file explorer > this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp > if the file size is , 1.5 GB then zip and post a share link into the thread using one drive, drop box, or google drive
      My Computer


  2. Posts : 16
    64-bit Windows 10 Home Build 17134
    Thread Starter
       #22

    Blue screened again. Log attached

    Tenforums - Google Drive
    Memory dump file = 2GB
    Wouldn't let me zip. Copy and pasted instead and then zipped.
      My Computer


  3. Posts : 38,430
    windows 10 professional version 1607 build 14393.969 64 bit
       #23

    Download and install: Everything
    Everything - voidtools
    Use everything to search for: win32k.sys-20181101-0031.dmp
    Zip the file > post a share link into the thread




    Code:
    win32k.sys-20181101-0031.dmp     01/11/2018 00:31:23   1530.87
      My Computer


  4. Posts : 16
    64-bit Windows 10 Home Build 17134
    Thread Starter
       #24

    Link win32k.sys...
    Tenforums - Google Drive
      My Computer


  5. Posts : 38,430
    windows 10 professional version 1607 build 14393.969 64 bit
       #25

    Running and dps displayed the Kaspersky AV software drivers.
    These were seen in the prior mini dump BSOD crashes.
    There was also a hardware driver in the latest crash.

    The win32 crash debugging displayed the hardware driver.

    All of the software drivers can be uninstalled.
    The hardware driver can be uninstalled and reinstalled.
    Both of these can be done at the same time.

    The BSOD crashes have displayed more than 10 different types of bugchecks.

    For academic purposes one of the above can be performed then wait to see if there is another crash.
    This could possibly narrow down which driver caused the crash rather than the driver that participated in the crash.



    win32 running

    Code:
     30    ffffad01ea440180  ffff818bc5613080 (15)                       ffffad01ea450800  ................
    
     # Child-SP          RetAddr           Call Site
    00 ffffbd0f`e11c6c20 fffff800`f337e327 nt!IopLiveDumpCorralDpc+0x42
    01 ffffbd0f`e11c6c60 fffff800`f337d97b nt!KiExecuteAllDpcs+0x2e7
    02 ffffbd0f`e11c6da0 fffff800`f34513e5 nt!KiRetireDpcList+0x1db
    03 ffffbd0f`e11c6fb0 fffff800`f34511e0 nt!KxRetireDpcList+0x5
    04 ffffbd0f`e23928c0 fffff800`f3450963 nt!KiDispatchInterruptContinue
    05 ffffbd0f`e23928f0 fffff80e`8027c389 nt!KiDpcInterrupt+0x2a3
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    06 ffffbd0f`e2392a88 fffff80e`803e63f7 atikmdag+0x107c389
    07 ffffbd0f`e2392a90 fffff80e`803e5516 atikmdag+0x11e63f7
    08 ffffbd0f`e2392ad0 fffff80e`803e6726 atikmdag+0x11e5516
    09 ffffbd0f`e2392b10 fffff80e`80345581 atikmdag+0x11e6726
    0a ffffbd0f`e2392b50 fffff80e`802f9af1 atikmdag+0x1145581
    0b ffffbd0f`e2392b80 fffff80e`801b814a atikmdag+0x10f9af1
    0c ffffbd0f`e2392bb0 fffff80e`801b7de1 atikmdag+0xfb814a
    0d ffffbd0f`e2392c20 fffff80e`801b7b91 atikmdag+0xfb7de1
    0e ffffbd0f`e2392ca0 fffff80e`801b5203 atikmdag+0xfb7b91
    0f ffffbd0f`e2392cf0 fffff80e`801b53f7 atikmdag+0xfb5203
    10 ffffbd0f`e2392e20 fffff80e`7f2ad300 atikmdag+0xfb53f7
    11 ffffbd0f`e2392ef0 fffff80e`7f2251a1 atikmdag+0xad300
    12 ffffbd0f`e2392f50 fffff80e`7f22b4eb atikmdag+0x251a1
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    13 ffffbd0f`e2392f90 fffff80e`7bbe06a5 atikmdag+0x2b4eb
    14 ffffbd0f`e2392fc0 fffff80e`7a96570c atikmpag+0x106a5
    15 ffffbd0f`e2392ff0 fffff80e`7a952321 dxgkrnl!ADAPTER_DISPLAY::DdiIsSupportedVidPn+0x150
    16 ffffbd0f`e23930b0 fffff80e`7a951ff4 dxgkrnl!VIDPN_MGR::_IsSupportedVidPn+0xb9
    17 ffffbd0f`e23930f0 fffff80e`7a95adf4 dxgkrnl!VIDPN_MGR::FormalizeVidPnChange+0x58
    18 ffffbd0f`e2393130 fffff80e`7aa328ab dxgkrnl!DXGDMM_VIDPNTOPOLOGY_INTERFACE_V1_IMPL::PinPathContentScaling+0xe4
    19 ffffbd0f`e23931a0 fffff80e`7aa34b97 dxgkrnl!OBTAIN_MODES_ON_SOURCE::operator()+0x5ab
    1a ffffbd0f`e2393410 fffff80e`7a9f5928 dxgkrnl!GetActiveVidPnBasedDisplayModeList+0x4bf
    1b ffffbd0f`e23936a0 fffff80e`7a9acf0f dxgkrnl!ADAPTER_DISPLAY::CreateModeList+0xd4
    1c ffffbd0f`e2393710 fffff80e`7a9df608 dxgkrnl!DxgkpGetDisplayModeList+0x6417b
    1d ffffbd0f`e2393820 fffff80e`7a946be6 dxgkrnl!DxgkpAdapterCheckStereoMode+0x4af98
    1e ffffbd0f`e2393950 ffffbf0b`c6264db0 dxgkrnl!DxgkGetAdapterDeviceDesc+0xb6
    1f ffffbd0f`e23939a0 ffffbf0b`c6265c60 win32kbase!DrvpDisplayConfigGetDisplayDeviceInfo+0x38
    20 ffffbd0f`e2393a00 ffffbf0b`c6265975 win32kbase!DrvDisplayConfigGetDeviceInfo+0x120
    21 ffffbd0f`e2393a40 fffff800`f345ab43 win32kbase!NtUserDisplayConfigGetDeviceInfo+0x185
    22 ffffbd0f`e2393b00 00007fff`62048264 nt!KiSystemServiceCopyEnd+0x13
    23 00000008`3347e8b8 00000000`00000000 0x00007fff`62048264

    memory.dmp

    dps

    Code:
    ffff8d0f`d174d438  ffff8d0f`d174e9a0
    ffff8d0f`d174d440  ffff8d0f`d174d580
    ffff8d0f`d174d448  fffff802`2cc6e04b nt!RtlpLookupFunctionEntryForStackWalks+0x1bb
    ffff8d0f`d174d450  fffff801`58cf555b*** ERROR: Symbol file could not be found.  Defaulted to export symbols for klflt.sys - 
     klflt!PstUnregisterFilter+0x207
    ffff8d0f`d174d458  000001f0`23bcd1a0
    ffff8d0f`d174d460  ffff8d0f`d174e160
    ffff8d0f`d174d468  fffff802`2cc713eb nt!KeQueryCurrentStackInformation+0x2b

    Code:
    ffff8d0f`d174e370  ffffa980`dfa9c442
    ffff8d0f`d174e378  ffffa980`dfa9c72a
    ffff8d0f`d174e380  ffffa980`dfa9c1d0
    ffff8d0f`d174e388  fffff801`5edf1565*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     atikmdag+0x21565
    ffff8d0f`d174e390  ffffd508`0ddc9980
    ffff8d0f`d174e398  fffff802`2cd83775 nt!RaspCreateSegmentList+0x189
    ffff8d0f`d174e3a0  00000000`00000001
    ffff8d0f`d174e3a8  ffffa980`dfa9c72a
    ffff8d0f`d174e3b0  00000000`00000020
    ffff8d0f`d174e3b8  ffff8d0f`d174e748
    ffff8d0f`d174e3c0  00000000`00000015
    ffff8d0f`d174e3c8  00000000`00000000
    ffff8d0f`d174e3d0  00000000`00000038
    ffff8d0f`d174e3d8  00000000`00000015
    ffff8d0f`d174e3e0  ffffa980`dfac0078
    ffff8d0f`d174e3e8  fffff801`5edf2288 atikmdag+0x22288
    ffff8d0f`d174e3f0  ffffd508`0ddc9980
    ffff8d0f`d174e3f8  ffffa980`dfac0078
    ffff8d0f`d174e400  00000000`00000054
    ffff8d0f`d174e408  ffffd508`0ddc9980
    ffff8d0f`d174e410  00000000`00000038
    ffff8d0f`d174e418  fffff802`000001b1
    ffff8d0f`d174e420  00000000`0000021d
    ffff8d0f`d174e428  ffffa980`dfa9cf60
    ffff8d0f`d174e430  ffffa980`dfac0078
    ffff8d0f`d174e438  fffff801`5b333e64*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
     atikmpag+0x13e64
    ffff8d0f`d174e440  00000000`00000015
    ffff8d0f`d174e448  ffff8d0f`d174e5e0
    ffff8d0f`d174e450  00000000`00000000
    ffff8d0f`d174e458  0000005c`00000054
    ffff8d0f`d174e460  ffffa980`00000054


    running

    Code:
    # Child-SP          RetAddr           Call Site
    00 ffff8d0f`d15c1110 fffff802`2cd0c915 nt!MiGetProtoPteAddress+0x33
    01 ffff8d0f`d15c1140 fffff802`2cccaad4 nt!MiQueryAddressState+0x4b5
    02 ffff8d0f`d15c1330 fffff802`2d0fa3a6 nt!MiQueryAddressSpan+0xb4
    03 ffff8d0f`d15c13d0 fffff802`2d0f9c41 nt!MmQueryVirtualMemory+0x756
    04 ffff8d0f`d15c1570 fffff802`2cdc9b43 nt!NtQueryVirtualMemory+0x25
    05 ffff8d0f`d15c15c0 fffff802`2cdbce90 nt!KiSystemServiceCopyEnd+0x13
    *** ERROR: Module load completed but symbols could not be loaded for klif.sys
    06 ffff8d0f`d15c17c8 fffff801`595b1a7d nt!KiServiceLinkage
    07 ffff8d0f`d15c17d0 fffff801`595b194f klif+0x31a7d
    08 ffff8d0f`d15c1840 fffff801`595b18c6 klif+0x3194f
    09 ffff8d0f`d15c18b0 fffff801`595b222d klif+0x318c6
    0a ffff8d0f`d15c18e0 fffff801`595b1f05 klif+0x3222d
    0b ffff8d0f`d15c1920 fffff801`595b0ecc klif+0x31f05
    0c ffff8d0f`d15c1960 fffff801`595e0966 klif+0x30ecc
    0d ffff8d0f`d15c1a00 fffff801`595d5409 klif+0x60966
    0e ffff8d0f`d15c1ab0 fffff801`58cc7278 klif+0x55409
    0f ffff8d0f`d15c1b60 fffff801`58cf2abe klflt!EvProcessEventWithSetEx2AtDpcLevel+0x42c
    10 ffff8d0f`d15c1c60 fffff801`58cf295f klflt!EvProcessEventEx3+0xe6
    11 ffff8d0f`d15c1ce0 fffff801`595af8e0 klflt!EvProcessEventEx+0x33
    12 ffff8d0f`d15c1d20 fffff801`595acb9d klif+0x2f8e0
    13 ffff8d0f`d15c1d80 fffff801`5966a936 klif+0x2cb9d
    14 ffff8d0f`d15c1df0 fffff801`58cf555b klif+0xea936
    15 ffff8d0f`d15c1e60 fffff801`58cf55e9 klflt!PstUnregisterFilter+0x207
    16 ffff8d0f`d15c1e90 fffff801`58ccb2bd klflt!PstUnregisterFilter+0x295
    17 ffff8d0f`d15c1ed0 fffff802`2d1a0733 klflt!PstUnregisterProcess+0x1419
    18 ffff8d0f`d15c1f10 fffff802`2d0b54e4 nt!PspCallThreadNotifyRoutines+0xc3
    19 ffff8d0f`d15c1f50 fffff802`2d0b4441 nt!PspInsertThread+0x3f8
    1a ffff8d0f`d15c2010 fffff802`2d0b3fc1 nt!PspCreateThread+0x251
    1b ffff8d0f`d15c22c0 fffff802`2cdc9b43 nt!NtCreateThreadEx+0x1f5
    1c ffff8d0f`d15c2a90 00007ffd`a017b654 nt!KiSystemServiceCopyEnd+0x13
    1d 0000009a`ef9fe2b8 00000000`00000000 0x00007ffd`a017b654
    
      7    ffffa980e0000180  ffffd508150a6080 (10)                       ffffa980e0010800  ................
    
     # Child-SP          RetAddr           Call Site


    Code:
     22    ffffa980e0939180  ffffd50817974700 ( 9)                       ffffa980e0949800  ................
    
     # Child-SP          RetAddr           Call Site
    00 ffff8d0f`d14f5960 fffff802`2cc713a4 nt!KeQueryCurrentStackInformation+0x17961e
    01 ffff8d0f`d14f5990 fffff802`2d0fbcc3 nt!RtlpGetStackLimits+0x14
    02 ffff8d0f`d14f59c0 fffff802`2cdc100d nt!PspGetSetContextInternal+0xc3
    03 ffff8d0f`d14f6000 fffff802`2d0fc4be nt!PspGetSetContextSpecialApc+0x6d
    04 ffff8d0f`d14f6110 fffff802`2d38e2b1 nt!PspGetContextThreadInternal+0xee
    05 ffff8d0f`d14f6830 fffff801`595b08af nt!PsGetContextThread+0x11
    06 ffff8d0f`d14f6870 fffff801`595b0f9b klif+0x308af
    07 ffff8d0f`d14f68b0 fffff801`595b21be klif+0x30f9b
    08 ffff8d0f`d14f68e0 fffff801`595b1f05 klif+0x321be
    09 ffff8d0f`d14f6920 fffff801`595b0ecc klif+0x31f05
    0a ffff8d0f`d14f6960 fffff801`595e0966 klif+0x30ecc
    0b ffff8d0f`d14f6a00 fffff801`595d5409 klif+0x60966
    0c ffff8d0f`d14f6ab0 fffff801`58cc7278 klif+0x55409
    0d ffff8d0f`d14f6b60 fffff801`58cf2abe klflt!EvProcessEventWithSetEx2AtDpcLevel+0x42c
    0e ffff8d0f`d14f6c60 fffff801`58cf295f klflt!EvProcessEventEx3+0xe6
    0f ffff8d0f`d14f6ce0 fffff801`595af8e0 klflt!EvProcessEventEx+0x33
    10 ffff8d0f`d14f6d20 fffff801`595acb9d klif+0x2f8e0
    11 ffff8d0f`d14f6d80 fffff801`5966a936 klif+0x2cb9d
    12 ffff8d0f`d14f6df0 fffff801`58cf555b klif+0xea936
    13 ffff8d0f`d14f6e60 fffff801`58cf55e9 klflt!PstUnregisterFilter+0x207
    14 ffff8d0f`d14f6e90 fffff801`58ccb2bd klflt!PstUnregisterFilter+0x295
    15 ffff8d0f`d14f6ed0 fffff802`2d1a0733 klflt!PstUnregisterProcess+0x1419
    16 ffff8d0f`d14f6f10 fffff802`2d0b54e4 nt!PspCallThreadNotifyRoutines+0xc3
    17 ffff8d0f`d14f6f50 fffff802`2d0b4441 nt!PspInsertThread+0x3f8
    18 ffff8d0f`d14f7010 fffff802`2d0b3fc1 nt!PspCreateThread+0x251
    19 ffff8d0f`d14f72c0 fffff802`2cdc9b43 nt!NtCreateThreadEx+0x1f5
    1a ffff8d0f`d14f7a90 00007ffd`a017b654 nt!KiSystemServiceCopyEnd+0x13
    1b 00000099`fa9fdfc8 00000000`00000000 0x00007ffd`a017b654
    
     24    ffffa980e0a79180  ffffd5081c6ed080 ( 8)                       ffffa980e0a89800  ................
    
     # Child-SP          RetAddr           Call Site
    00 00000000`2f82efb8 00000000`00000000 0x779f21cb
    
     26    ffffa980e0ba4180  ffffd5081ed70080 (11)                       ffffa980e0bb4800  ................
    
     # Child-SP          RetAddr           Call Site
    00 ffff8d0f`d03beca0 fffff802`2cdc0136 nt!SwapContext+0x39b
    01 ffff8d0f`d03bece0 fffff802`2cc495d6 nt!KiSwapContext+0x76
    02 ffff8d0f`d03bee20 fffff802`2cc48dcb nt!KiSwapThread+0x2c6
    03 ffff8d0f`d03beef0 fffff802`2cc47cc7 nt!KiCommitThreadWait+0x13b
    04 ffff8d0f`d03bef90 fffff801`58cf8277 nt!KeWaitForMultipleObjects+0x467
    05 ffff8d0f`d03bf070 fffff801`595e135a klflt!DlWaitForDataLogEx+0x7b
    06 ffff8d0f`d03bf110 fffff801`595e14b9 klif+0x6135a
    07 ffff8d0f`d03bf1b0 fffff801`595d0a1f klif+0x614b9
    08 ffff8d0f`d03bf200 fffff801`59593615 klif+0x50a1f
    09 ffff8d0f`d03bf2c0 fffff801`5966dcd6 klif+0x13615
    0a ffff8d0f`d03bf620 fffff801`5968153d klif+0xedcd6
    0b ffff8d0f`d03bf670 fffff801`5701b656 klif+0x10153d
    0c ffff8d0f`d03bf6d0 fffff801`5704b09b FLTMGR!FltpFilterMessage+0xca
    0d ffff8d0f`d03bf730 fffff801`570151f9 FLTMGR!FltpMsgDispatch+0x16b
    0e ffff8d0f`d03bf7a0 fffff802`2cc4aef9 FLTMGR!FltpDispatch+0xe9
    0f ffff8d0f`d03bf800 fffff802`2d0f61cb nt!IofCallDriver+0x59
    10 ffff8d0f`d03bf840 fffff802`2d0f585f nt!IopSynchronousServiceTail+0x1ab
    11 ffff8d0f`d03bf8f0 fffff802`2d0f6006 nt!IopXxxControlFile+0x66f
    12 ffff8d0f`d03bfa20 fffff802`2cdc9b43 nt!NtDeviceIoControlFile+0x56
    13 ffff8d0f`d03bfa90 00000000`779a1e4c nt!KiSystemServiceCopyEnd+0x13
    14 00000000`051cf278 00000000`00000000 0x779a1e4c
    
     28    ffffa980e0c65180  ffffd50815264700 ( 9)                       ffffa980e0c75800  ................
    Last edited by zbook; 03 Nov 2018 at 17:41.
      My Computer

  6. philc43's Avatar
    Posts : 5,006
    64bit Win 10 Pro ver 20H2 Build 19042.868 and W10 Insider Preview Build 21343
       #26

    Can I ask why you have the memory speed set at 3200MHz? I am concerned that this is set too high. Can you adjust it down to 2667MHz as specified for the CPU. https://www.amd.com/en/products/cpu/amd-ryzen-threadripper-1950x

    A number of the crashes have been analysed as being due to memory corruption, incompatible speeds can be a reason for this and overclocking in general.
      My Computers


  7. Posts : 38,430
    windows 10 professional version 1607 build 14393.969 64 bit
       #27

    1) Please uninstall during the troubleshooting.
    a) MSI afterburner
    b) Asus AI Suite 3

    2) Make sure that there is no overclocking during the troubleshooting.
      My Computer


  8. Posts : 16
    64-bit Windows 10 Home Build 17134
    Thread Starter
       #28

    philc43 - Oh. I didn't think I had any problems running at 3200mhz and the RAM was on the QVL so I thought it would be OK. Ill change it back.

    zbook - Uninstall done!
      My Computer


  9. Posts : 16
    64-bit Windows 10 Home Build 17134
    Thread Starter
       #29

    Hey Guys,

    Sorry for not posting for a few days, I've been away for work.

    Update: No more BSODs, but my screen is still randomly turning off and forcing me to hard reset. Going to take out 2 ram modules tonight and run memtest.
      My Computer


  10. Posts : 16
    64-bit Windows 10 Home Build 17134
    Thread Starter
       #30

    Hey guys,

    So I've taken off my custom loop temporarily and bought a fan and cheap gpu. I took out my RAM modules and tested them one at a time in memtest and got 0 errors for each one. I decided to run all 4 again in the same slots as before, but this time I got 0 errors. I'm also not getting crashes with this temp fan and gpu.

    Module 1
    Attachment 215970

    Module 2
    Attachment 215971

    Module 3
    Attachment 215972

    Module 4
    Attachment 215973

    All 4
    Attachment 215974
      My Computer


 
Page 3 of 3 FirstFirst 123

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:09.
Find Us




Windows 10 Forums