Persistent BSOD ntoskrnl.exe

Page 13 of 16 FirstFirst ... 31112131415 ... LastLast

  1. Posts : 90
    Windows 10 Pro 64-bit - Build 17134
    Thread Starter
       #121

    Yes it does and thanks. I'll dive into the manual this weekend, create a strategy based on your suggestion and report back when appropriate. Thanks much.
      My Computer


  2. Posts : 90
    Windows 10 Pro 64-bit - Build 17134
    Thread Starter
       #122

    Okydoky I've been running since this morning on half RAM and so far so good. If I'm BSOD free tomorrow morning then there's a good chance it's the other group of RAM and I'm thinking 48hrs (or essentially Tue. morning) of normal use without BSOD should be a good indication of RAM health (assuming it's the RAM that's causing the BSODs). Does this seem reasonable? If the current group of RAM makes it to Tuesday is it safe to assume that the other batch of RAM is faulty? Finally should I test the other bad group to confirm it's bad?
      My Computer


  3. Posts : 261
    Windows 10 Home 21H2
       #123

    That sounds reasonable. I'd suggest making sure you're using CINEMA 4D.exe at some point as that seemed to show up quite often as the owner of the thread that crashed in the dump files you made available previously.

    I can't say it definitively means there's a bad DIMM in the other group of DIMMs but it very well might. The only reliable way to check is to swap them out and try the same test, in my opinion. Things could get complicated if neither group causes the system to become unstable but we'll cross that bridge if we come to it.
      My Computer


  4. Posts : 90
    Windows 10 Pro 64-bit - Build 17134
    Thread Starter
       #124

    No BSODs as of this morning and now going about a regular work day with fingers crossed.
      My Computer


  5. Posts : 90
    Windows 10 Pro 64-bit - Build 17134
    Thread Starter
       #125

    Okydoky we made it to Tuesday morning. As I'm in the middle of a project now I think I'm going to try the other RAM group on Friday evening. This up-time is nice... :)
      My Computer


  6. Posts : 261
    Windows 10 Home 21H2
       #126

    No rush on my end. Assuming it is a memory problem I would think the problem would show up sooner rather than later since there is less memory for the fault to be hiding in so perhaps this is a good sign. I'm wondering about a dual channel memory configuration versus quad channel - do you notice a significant slowdown using dual channel with your programs?
    Last edited by cwsink; 02 Oct 2018 at 10:32.
      My Computer


  7. Posts : 90
    Windows 10 Pro 64-bit - Build 17134
    Thread Starter
       #127

    Haven't noticed a difference at all. I invested in the full 128gb for multitasking (running After Effects and C4D concurrently) as well as longer RAM previews in AE.
      My Computer


  8. Posts : 90
    Windows 10 Pro 64-bit - Build 17134
    Thread Starter
       #128

    Up-time is addictive. The project I'm currently on is currently ramping into high gear and given that I havn't had nary a single BSOD since the extraction I feel I need to continue working as is until my project wraps. Thanks for sticking with me and I'll be back in a couple of weeks.
      My Computer


  9. Posts : 261
    Windows 10 Home 21H2
       #129

    No worries. I'm glad the system is solid for you in the current configuration. Thank you for letting us know.
      My Computer


  10. Posts : 90
    Windows 10 Pro 64-bit - Build 17134
    Thread Starter
       #130

    I'm back and I switched RAM sets. Interestingly enough I had to replace my Liqtech 360 because the pump died. I replaced it with the Liqtech II 280 and at almost 24 hrs of uptime I'm getting decent idle temps at approx. 30degC. More importantly (and frustratingly) no BSODs. This is also after initiating the same GPU render which was what I thought was originally causing the BDODs. Does this indicate my processor? Should I fire up Prime?
      My Computer


 

  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 12:45.
Find Us




Windows 10 Forums