Various BSODs all hinting towards drivers?

Page 9 of 12 FirstFirst ... 7891011 ... LastLast
  1. Matthew Wai's Avatar
    Posts : 5,096
    Windows 10 Home 20H2
       #81

    zbook said:
    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 > save to the downloads folder > zip
    Right-click on the Start button --> Windows PowerShell.
    Run the following command:

    Code:
    Compress-Archive -Path "$env:homeDrive\Windows\MEMORY.DMP" -DestinationPath "$env:homeDrive$env:homePath\Desktop\Memory_dmp"

    If "MEMORY.DMP" exists, it will be put into "Memory_dmp.zip" on the desktop.
    Note that PowerShell cannot zip a file larger than 2 GB.
      My Computer


  2. Posts : 55
    Windows 10 Pro
    Thread Starter
       #82

    Hey,
    I started WDV with the one test. After ~5 minutes my screen just went black and I couldn't revive it.. displayport cable out/in changed nothing. So I rebooted the PC and stopped WDV. No BSOD.dmp was created. I still did run V2 log... idk if that can tell anything here.

    I will try WDV again and see if it happens again.

    - - - Updated - - -

    I checked reliability history and there it actually says (I think for the first time) "Hardwarefehler" ("hardwarefailure" .. idk why it is still in german).

    - - - Updated - - -

    Hi again,
    I got another crash after ~10 minutes of WDV. This time screen did freeze before going all black. Again no dmp created / no BSOD. And again, it says "hardwarefailure" Code: 1a1 in reliability history.

    V2 log attached.
    Attached Thumbnails Attached Thumbnails Various BSODs all hinting towards drivers?-hardwarefailure.png  
    Various BSODs all hinting towards drivers? Attached Files
      My Computer


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

    Restart WDV 5 - 10 more times to see if it will produce a dump file.

    If there is no dump file formed then restart WDV with all customized tests except Randomized low resources simulation.
      My Computer


  4. Posts : 55
    Windows 10 Pro
    Thread Starter
       #84

    Hey, thanks. I restarted WDV.

    - - - Updated - - -

    And the first crash instantly gave me a BSOD this time :)
    Here is V2 and dmp:
    MEMORY4.zip - Google Drive

    I think it shows graphicscard as the issue, which is weird because graphicscard is actually the only thing that I have changed already (had an old graphicscard earlier until I was able to get a 3070 and already had BSODs with that card).
    Various BSODs all hinting towards drivers? Attached Files
      My Computer


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

    Did the command in post #81 collect the memory dump?

    Please restart WDV with all customized tests except Randomized low resources simulation.

    Run the tool continuously for 48 hours.
      My Computer


  6. Posts : 55
    Windows 10 Pro
    Thread Starter
       #86

    Hi,

    I restarted WDV with all tests.

    No, I collected the full dmp as usual by hand.

    I already did let the pc run with all tests which resulted in post #75. And I think we haven't changed the system since.
    Should I still let it run again until bsod? :)
    And thank you again! I wouldn't know what to do without you investing that much time into this.
      My Computer

  7. Matthew Wai's Avatar
    Posts : 5,096
    Windows 10 Home 20H2
       #87

    ferchi said:
    No, I collected the full dmp as usual by hand.
    Which one of the following does your "No" mean?

    (1) No, the command in post #81 did not work. I collected the .dmp file manually.
    (2) No, I did not run the command in post #81. I collected the .dmp file manually.
      My Computer


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

    ferchi said:
    I restarted WDV with all tests.
    I already did let the pc run with all tests which resulted in post #75. And I think we haven't changed the system since.
    Should I still let it run again until bsod? :)
    Please run WDV for 48 hours continuously to see whether the computer is BSOD free, has BSOD caused by the tool, or spontaneous BSOD.


    For any BSOD:

    a) run the V2 log collector to collect new log files

    b) run the command in post #81 to collect any memory dump.
      My Computer


  9. Posts : 55
    Windows 10 Pro
    Thread Starter
       #89

    Matthew Wai said:
    (1) No, the command in post #81 did not work.
    (2) No, I did not run the command in post #81.
    I forgot about the command at that point and did it by hand like before. So option (2) it is.

    zbook said:
    Please run WDV for 48 hours continuously to see whether the computer is BSOD free, has BSOD caused by the tool, or spontaneous BSOD.
    Thanks for the explanation! I just was not sure. WDV is running. I will report back after the 48 hours or BSOD :)
      My Computer


  10. Posts : 55
    Windows 10 Pro
    Thread Starter
       #90

    Hi again,

    I just stopped the WDV after 51 hours without BSOD.

    Before I started the 48 hours run I got another BSOD which I upload now just for completeness. Dmp collected with PowerShell this time.
    Memory_dmp.zip - Google Drive
    Various BSODs all hinting towards drivers? Attached Files
      My Computer


 
Page 9 of 12 FirstFirst ... 7891011 ... LastLast

  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 23:00.
Find Us




Windows 10 Forums