Number of different BSODs - Can't figure for the problem

Page 4 of 6 FirstFirst ... 23456 LastLast

  1. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #31

    When performing a clean install you can format, delete partitions, etc.

    When performing an in place upgrade repair you can fix underlying operating system problems.
    It typically does not fix registry problems.
    It has little downside and potentially can create a more secure or stable computer environment.
    This can be performed before or after the memory testing.

    Repair Install Windows 10 with an In-place Upgrade
      My Computer


  2. Posts : 29
    Windows 10
    Thread Starter
       #32

    So I had another BSOD a few days ago - was away so couldn't post the debugging data. Please find below.

    Dump : 071619-6140-01.dmp - Google Drive
    V2 Log Collector : DARTH-VADER-(2019-07-21_16-01-17).zip - Google Drive
      My Computer


  3. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #33

    The memory dump is needed for this type of bugcheck.

    It was large and may take a long time to upload and download.

    Code:
    Crash dump found at C:\WINDOWS\MEMORY.DMP
    Creation date: 07/16/2019 22:26:41
    Size on disk: 1795 MB
      My Computer


  4. Posts : 29
    Windows 10
    Thread Starter
       #34

    zbook said:
    The memory dump is needed for this type of bugcheck.

    It was large and may take a long time to upload and download.

    Code:
    Crash dump found at C:\WINDOWS\MEMORY.DMP
    Creation date: 07/16/2019 22:26:41
    Size on disk: 1795 MB
    Full memory dump here : MEMORY 21-07.zip - Google Drive
      My Computer


  5. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #35

    The memory dump was from July 14.
    Today is July 21.
    The bucheck was 133 with parameter 1
    There were no definitive misbehaving drivers seen in the crash.

    Bugchecks were:
    3B
    7E
    133


    Open a support ticket with Nvidia and ask for information about Event ID 14 with N/A.

    Code:
    Event[3265]:
      Log Name: System
      Source: nvlddmkm
      Date: 2019-07-18T09:38:05.762
      Event ID: 14
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DARTH-VADER
      Description: 
    N/A
    
    Event[3266]:
      Log Name: System
      Source: nvlddmkm
      Date: 2019-07-18T09:38:05.980
      Event ID: 14
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DARTH-VADER
      Description: 
    N/A
      My Computer


  6. Posts : 29
    Windows 10
    Thread Starter
       #36

    zbook said:
    The memory dump was from July 14.
    Today is July 21.
    The bucheck was 133 with parameter 1
    There were no definitive misbehaving drivers seen in the crash.

    Bugchecks were:
    3B
    7E
    133


    Open a support ticket with Nvidia and ask for information about Event ID 14 with N/A.

    Code:
    Event[3265]:
      Log Name: System
      Source: nvlddmkm
      Date: 2019-07-18T09:38:05.762
      Event ID: 14
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DARTH-VADER
      Description: 
    N/A
    
    Event[3266]:
      Log Name: System
      Source: nvlddmkm
      Date: 2019-07-18T09:38:05.980
      Event ID: 14
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DARTH-VADER
      Description: 
    N/A
    Quoting an NVidia rep:

    This issue is usually caused caused if your display driver has stopped responding and then successfully recovered.

    This issue could also occur if GPU is taking more time than permitted to display graphics to your monitor or if the TDR setting is set to low. Delaying the TDR time will resolve the issue.

    This issue could caused due to corrupt driver as well as due to faulty card.
      My Computer


  7. Posts : 29
    Windows 10
    Thread Starter
       #37

    Any ideas on next steps? If we're 100% certain it's something to do with the gfx card, I'm willing to go out and get a new one.
      My Computer


  8. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #38

    Post a new V2.

    See post #23 steps #1 - #4.



    How long has it been since the in place upgrade repair? How had performance changed?

    How long was safe mode used? How had performance changed?

    Was a manual crash performed? Were mini and memory dump files created?

    What hardware tests were performed? Post images of test results into the thread.
      My Computer


  9. Posts : 392
    W10
       #39

    The best test for a graphics card is to try another one.
    If you're willing to purchase one, get it from a shop that'll let you return it for your money back if it's not needed. That way you can test to see if this fixes things (without risking your money).

    Good luck!
      My Computer


  10. Posts : 29
    Windows 10
    Thread Starter
       #40

    jdc1 said:
    The best test for a graphics card is to try another one.
    If you're willing to purchase one, get it from a shop that'll let you return it for your money back if it's not needed. That way you can test to see if this fixes things (without risking your money).

    Good luck!
    My only issue is I'm running a custom loop, so it's a bit of a pain. If I were certain that's the issue though, no problem. The other problem, is that I can't reproduce the BSODs on demad. So it may take a day, a week, or two weeks for it to manifest. If I figure a way to reproduce it on demand, then it makes debugging all so much easier.

    - - - Updated - - -

    zbook said:
    Post a new V2.

    See post #23 steps #1 - #4.



    How long has it been since the in place upgrade repair? How had performance changed?

    How long was safe mode used? How had performance changed?

    Was a manual crash performed? Were mini and memory dump files created?

    What hardware tests were performed? Post images of test results into the thread.
    I had been away for nearly a week, so my PC had not been running. I've been running it since yesterday - no BSODs yet.

    What is a manual crash? How can I achieve this?

    As for hardware tests, what would you recommend I run beyond Memtest?

    - - - Updated - - -

    Just had another BSOD while using my PC and running Prime95 at the same time (may be related or not)

    V2 Collector Logs here : DARTH-VADER-(2019-08-04_13-27-05).zip - Google Drive
    Mini Dump here : 080419-6062-01.dmp - Google Drive
    MEMORY.DPM here : MEMORY 04-08.zip - Google Drive
      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 03:33.
Find Us




Windows 10 Forums