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

Page 3 of 4 FirstFirst 1234 LastLast

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

    Were there no changes related to enabling all available customized tests including DDI?
    No change in performance?
    No change in boot?
    No BSOD?

    There was a spontaneous BSOD on 6/30?

    Has the tool been turned off?



    Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
    Resplendence Software - WhoCrashed, automatic crash dump analyzer
    After the crash click analyze > look for deaddead in the results > post the results into the thread

    Run V2 and post the memory dump.

    After the in place upgrade repair repeat the above steps.


    After completing all of the above:

    Run Memtest86 version 8.2 for four passes.
    Repeat the test so that eight passes are performed.
    MemTest86 - Official Site of the x86 Memory Testing Tool
    Use a camera or smart phone camera to take pictures and post images into the thread.
    In case there are any problems uploading images use share links (one drive, drop box, or google drive)
    Memtest86 has a feature to produce a text report.
    Please post this in addition to the images.
      My ComputerSystem Spec

  2.    #22

    zbook said: View Post
    1) The logs displayed BSOD crashes on
    6/21
    6/23
    6/24

    2) Unfortunately no dump files were created.

    3) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    4) Find a flash drive that you can format

    5) Create a bootable windows 10 iso
    https://www.microsoft.com/en-us/soft...load/windows10

    6) Create a brand new restore point

    7) Make sure the backup image is up to date

    8) If there are no performance or boot problems then use windows driver verifier with all available customized tests.
    If there are no BSOD within six to eight hours then turn off the tool.

    9) For any BSOD:

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

    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 > post a separate share link into the thread using one drive, drop box, or google drive

    10) Perform an in place upgrade repair after completing all of the above steps:
    Repair Install Windows 10 with an In-place Upgrade

    11) After the in place upgrade repair repeat step #3.
    8 - Everything in verifier enabled. Had a crash, but again, no minidump. V2 Logs here : DARTH-VADER-(2019-07-01_21-19-33).zip - Google Drive - Also, as expected, performance is impacted.

    I'll now try step 10 and report back

    Edit: Just had another crash a few minutes after this post - no dump again.
    Edit2: Another crash. It seems to constantly crash after a few minutes with EVERYTHING enabled in Verifier. The only downside is the fact that no dumps are being created, no matter what I select - automatic dump, full dump, nothing seems to work. Link to V2 collector : DARTH-VADER-(2019-07-01_21-38-10).zip - Google Drive

    - - - Updated - - -

    I found this in V2 Log Collector under Error Reports\Kernel*

    There's a report.wer which has the following:

    Version=1
    EventType=LiveKernelEvent
    EventTime=132057484709459131
    ReportType=4
    Consent=1
    ReportStatus=2049
    ReportIdentifier=0c5a7e18-a058-4bb9-8a31-c9b9a3eecc92
    Wow64Host=34404
    NsAppName=LiveKernelEvent
    OriginalFilename=WerFault.exe
    AppSessionGuid=00000000-0000-0000-0000-000000000000
    BootId=9
    IsFatal=4294967295
    EtwNonCollectReason=1
    Response.type=4
    Sig[0].Name=Code
    Sig[0].Value=141
    Sig[1].Name=Parameter 1
    Sig[1].Value=ffffb78ceb9ce010
    Sig[2].Name=Parameter 2
    Sig[2].Value=fffff807d0b34148
    Sig[3].Name=Parameter 3
    Sig[3].Value=0
    Sig[4].Name=Parameter 4
    Sig[4].Value=4884
    Sig[5].Name=OS version
    Sig[5].Value=10_0_18362
    Sig[6].Name=Service Pack
    Sig[6].Value=0_0
    Sig[7].Name=Product
    Sig[7].Value=256_1
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.18362.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=2057
    OsInfo[0].Key=vermaj
    OsInfo[0].Value=10
    OsInfo[1].Key=vermin
    OsInfo[1].Value=0
    OsInfo[2].Key=verbld
    OsInfo[2].Value=18362
    OsInfo[3].Key=ubr
    OsInfo[3].Value=175
    OsInfo[4].Key=versp
    OsInfo[4].Value=0
    OsInfo[5].Key=arch
    OsInfo[5].Value=9
    OsInfo[6].Key=lcid
    OsInfo[6].Value=2057
    OsInfo[7].Key=geoid
    OsInfo[7].Value=242
    OsInfo[8].Key=sku
    OsInfo[8].Value=48
    OsInfo[9].Key=domain
    OsInfo[9].Value=0
    OsInfo[10].Key=prodsuite
    OsInfo[10].Value=256
    OsInfo[11].Key=ntprodtype
    OsInfo[11].Value=1
    OsInfo[12].Key=platid
    OsInfo[12].Value=10
    OsInfo[13].Key=sr
    OsInfo[13].Value=0
    OsInfo[14].Key=tmsi
    OsInfo[14].Value=3682
    OsInfo[15].Key=osinsty
    OsInfo[15].Value=3
    OsInfo[16].Key=iever
    OsInfo[16].Value=11.175.18362.0-11.0.130
    OsInfo[17].Key=portos
    OsInfo[17].Value=0
    OsInfo[18].Key=ram
    OsInfo[18].Value=32688
    OsInfo[19].Key=svolsz
    OsInfo[19].Value=476
    OsInfo[20].Key=wimbt
    OsInfo[20].Value=0
    OsInfo[21].Key=blddt
    OsInfo[21].Value=190318
    OsInfo[22].Key=bldtm
    OsInfo[22].Value=1202
    OsInfo[23].Key=bldbrch
    OsInfo[23].Value=19h1_release
    OsInfo[24].Key=bldchk
    OsInfo[24].Value=0
    OsInfo[25].Key=wpvermaj
    OsInfo[25].Value=0
    OsInfo[26].Key=wpvermin
    OsInfo[26].Value=0
    OsInfo[27].Key=wpbuildmaj
    OsInfo[27].Value=0
    OsInfo[28].Key=wpbuildmin
    OsInfo[28].Value=0
    OsInfo[29].Key=osver
    OsInfo[29].Value=10.0.18362.175.amd64fre.19h1_release.190318-1202
    OsInfo[30].Key=buildflightid
    OsInfo[30].Value=c7fc3060-ca94-4aba-916a-f493b682f2d5
    OsInfo[31].Key=edition
    OsInfo[31].Value=Professional
    OsInfo[32].Key=ring
    OsInfo[32].Value=Retail
    OsInfo[33].Key=expid
    OsInfo[34].Key=containerid
    OsInfo[35].Key=containertype
    OsInfo[36].Key=edu
    OsInfo[36].Value=0
    File[0].CabName=WATCHDOG-20190623-0827.dmp
    File[0].Path=WATCHDOG-20190623-0827.dmp
    File[0].Flags=851970
    File[0].Type=2
    File[0].Original.Path=\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20190623-0827.dmp
    File[1].CabName=sysdata.xml
    File[1].Path=WER-1190609-0.sysdata.xml
    File[1].Flags=851970
    File[1].Type=5
    File[1].Original.Path=\\?\C:\WINDOWS\TEMP\WER-1190609-0.sysdata.xml
    File[2].CabName=WERInternalMetadata.xml
    File[2].Path=WER3725.tmp.WERInternalMetadata.xml
    File[2].Flags=851970
    File[2].Type=5
    File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3725.tmp.WERInternalMetadata.xml
    File[3].CabName=WERInternalRequest.xml
    File[3].Path=WER3726.tmp.xml
    File[3].Flags=851970
    File[3].Type=5
    File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3726.tmp.xml
    File[4].CabName=memory.csv
    File[4].Path=WER3735.tmp.csv
    File[4].Flags=589826
    File[4].Type=5
    File[4].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3735.tmp.csv
    File[5].CabName=sysinfo.txt
    File[5].Path=WER3745.tmp.txt
    File[5].Flags=589826
    File[5].Type=5
    File[5].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3745.tmp.txt
    File[6].CabName=Report.zip
    File[6].Path=Report.zip
    File[6].Flags=65536
    File[6].Type=11
    File[6].Original.Path=\\?\C:\WINDOWS\system32\Report.zip
    Ns[0].Name=stopcode
    Ns[0].Value=00000141
    Ns[1].Name=p1
    Ns[1].Value=FFFFB78CEB9CE010
    Ns[2].Name=p2
    Ns[2].Value=FFFFF807D0B34148
    Ns[3].Name=p3
    Ns[3].Value=0000000000000000
    Ns[4].Name=p4
    Ns[4].Value=0000000000004884
    FriendlyEventName=Hardware error
    ConsentKey=LiveKernelEvent
    AppName=Windows
    AppPath=C:\Windows\System32\WerFault.exe
    ReportDescription=A problem with your hardware caused Windows to stop working correctly.
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=00000000000000000000000000000000
    MetadataHash=1567006783


    Having said that, those files don't seem to exist.
      My ComputerSystem Spec


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

    Earlier in the thread there were mini dumps.
    However there were no memory dumps.

    The plan now is to:
    1) see the impact of an in place upgrade repair.
    2) see the impact of a manual crash
    3) Stress test hardware
    4) Test in safe mode





    Addendum:

    In post #20 images were posted for startup and recovery system failure and virtual memory.

    The logs displayed that these settings were modified.

    Please make changes to the settings so that they match the prior images.



    There were approximately 10 BSOD crashes on 7/1/2019.


    Code:
    Event[2769]:
      Log Name: System
      Source: volmgr
      Date: 2019-07-01T18:41:39.518
      Event ID: 49
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DARTH-VADER
      Description: 
    Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

    Code:
    Event[3902]:
      Log Name: System
      Source: volmgr
      Date: 2019-07-01T21:35:19.410
      Event ID: 161
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DARTH-VADER
      Description: 
    Dump file creation failed due to error during dump creation.
    Last edited by zbook; 3 Weeks Ago at 00:28.
      My ComputerSystem Spec

  4.    #24

    I've performed the repair, but doesn't look any better. Here is my update:

    1) I've performed Driver Verifier with EVERYTHING enabled, straight after the repair but before installing any of my own (ASUS/Intel, etc.) drivers. I've had a BSOD with a minidump created. V2 Logs are here and minidump here.
    2) I've then went on to install all drivers and update BIOS. Turned on Drive Verifier with EVERYTHING on - still getting crashes, but NO minidumps this time around. V2 logs here and here.

    Edit: the minidumps in the V2 logs, seem to be ones after the repair, but before I updated all drivers.

    What are the next steps?
      My ComputerSystem Spec


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

    Please perform the following steps:

    1) Turn off Windows driver verifier

    2) Make sure that windows driver verifier is not restarted (if the tool is needed it will be communicated in the thread)

    3) Search for> PoW32kWatchdog-20190702-1940.dmp > zip > post a share link into the thread

    Code:
    Name                             LastWriteTime       Size (MB)
    ----                             -------------       ---------
    PoW32kWatchdog-20190702-1940.dmp 02/07/2019 19:40:46   1184.42


    4) Post a link for: C:\WINDOWS\MEMORY.DMP

    Code:
    Crash dump found at C:\WINDOWS\MEMORY.DMP
    Creation date: 07/02/2019 19:57:32
    Size on disk: 1259 MB


    5) Use Everything search software as needed to identify the above files: voidtools

    6) Turn off windows updates of non-Microsoft drivers:
    Enable or Disable Driver Updates in Windows Update in Windows 10

    7) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

    8) re-install the Nvidia GPU driver from the Nvidia website
    (make sure that the new driver is different from: 26.21.14.3086

    9) make sure that you check the clean install box and if available install the physx driver.

    Display Driver Uninstaller Download version 18.0.1.5 (or newer version if available)
    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    Download Drivers | NVIDIA
    Download Drivers | NVIDIA



    10) If there are recurrent BSOD related to GPU drivers/hardware:
    see if you can find a friend, neighbor, relative, or local computer store to swap the GPU card.
    The card can be Nvidia or AMD.
    If possible make two tests:
    a) test a new card in the problematic computer
    b) test the card from the problematic computer in another computer

    11) test hardware

    12) When available post:
    a) images for two Memtest86 version 8.2 tests with four passes for each test
    b) text report results for Memtest86 version 8.2 with four passes for each test
    c) make sure that for each test there are two test results: images and text reports

    13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread




    Code:
    02/07/2019 18:58	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff80fa2f1728e
    P4: ffffde86f1958828
    P5: ffffde86f1958070
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\070219-7687-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-9953-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34BC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34CC.tmp.xml
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_cac49d4e2266e3a4b1a2899cf2dac5d131c14_00000000_cab_89451530-13fc-4342-bab2-68c31b5fb018
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 92556029-09b1-4fed-8b7f-fd9b9e7c5a00
    Report Status: 2049
    Hashed bucket: 
    Cab Guid: 0
    02/07/2019 18:58	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff80fa2f1728e
    P4: ffffde86f1958828
    P5: ffffde86f1958070
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\070219-7687-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-9953-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34BC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34CC.tmp.xml
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_cac49d4e2266e3a4b1a2899cf2dac5d131c14_00000000_89451530-13fc-4342-bab2-68c31b5fb018
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 92556029-09b1-4fed-8b7f-fd9b9e7c5a00
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    02/07/2019 18:50	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff80df482728e
    P4: fffff483ff43c8f0
    P5: 0
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\070219-9265-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-11796-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C60.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C71.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5AA.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5BB.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_972bbf2ae1a75730cfb27da9adf591c29a7ebd_00000000_cab_845d5d32-d587-4377-af33-89e2c5941ba9
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a624598b-c4b5-4dbe-b652-16c61128832f
    Report Status: 2049
    Hashed bucket: 
    Cab Guid: 0
    02/07/2019 18:50	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff80df482728e
    P4: fffff483ff43c8f0
    P5: 0
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\070219-9265-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-11796-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C60.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C71.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5AA.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5BB.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_972bbf2ae1a75730cfb27da9adf591c29a7ebd_00000000_845d5d32-d587-4377-af33-89e2c5941ba9
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a624598b-c4b5-4dbe-b652-16c61128832f
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0

    Code:
    Name	NVIDIA GeForce GTX 1080
    PNP Device ID	PCI\VEN_10DE&DEV_1B80&SUBSYS_33601462&REV_A1\4&1F822D9D&0&0008
    Adapter Type	GeForce GTX 1080, NVIDIA compatible
    Adapter Description	NVIDIA GeForce GTX 1080
    Adapter RAM	(1,048,576) bytes
    Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll
    Driver Version	26.21.14.3086
    INF File	oem13.inf (Section094 section)
    Colour Planes	Not Available
    Colour Table Entries	4294967296
    Resolution	2560 x 1440 x 59 hertz
    Bits/Pixel	32
    Memory Address	0xA2000000-0xA30FFFFF
    Memory Address	0x90000000-0xDFFFFFFF
    Memory Address	0xA0000000-0xA1FFFFFF
    I/O Port	0x00003000-0x00003FFF
    IRQ Channel	IRQ 16
    Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_B49751B9038AF669\NVLDDMKM.SYS (26.21.14.3086, 20.82 MB (21,836,032 bytes), 03/07/2019 18:28)
    Code:
    nvlddmkm.sys Fri Oct 27 10:49:39 2017 (59F35593)
      My ComputerSystem Spec

  6.    #26

    zbook said: View Post
    Please perform the following steps:

    1) Turn off Windows driver verifier

    2) Make sure that windows driver verifier is not restarted (if the tool is needed it will be communicated in the thread)

    3) Search for> PoW32kWatchdog-20190702-1940.dmp > zip > post a share link into the thread

    Code:
    Name                             LastWriteTime       Size (MB)
    ----                             -------------       ---------
    PoW32kWatchdog-20190702-1940.dmp 02/07/2019 19:40:46   1184.42


    4) Post a link for: C:\WINDOWS\MEMORY.DMP

    Code:
    Crash dump found at C:\WINDOWS\MEMORY.DMP
    Creation date: 07/02/2019 19:57:32
    Size on disk: 1259 MB


    5) Use Everything search software as needed to identify the above files: voidtools

    6) Turn off windows updates of non-Microsoft drivers:
    Enable or Disable Driver Updates in Windows Update in Windows 10

    7) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

    8) re-install the Nvidia GPU driver from the Nvidia website
    (make sure that the new driver is different from: 26.21.14.3086

    9) make sure that you check the clean install box and if available install the physx driver.

    Display Driver Uninstaller Download version 18.0.1.5 (or newer version if available)
    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    Download Drivers | NVIDIA
    Download Drivers | NVIDIA



    10) If there are recurrent BSOD related to GPU drivers/hardware:
    see if you can find a friend, neighbor, relative, or local computer store to swap the GPU card.
    The card can be Nvidia or AMD.
    If possible make two tests:
    a) test a new card in the problematic computer
    b) test the card from the problematic computer in another computer

    11) test hardware

    12) When available post:
    a) images for two Memtest86 version 8.2 tests with four passes for each test
    b) text report results for Memtest86 version 8.2 with four passes for each test
    c) make sure that for each test there are two test results: images and text reports

    13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread




    Code:
    02/07/2019 18:58	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff80fa2f1728e
    P4: ffffde86f1958828
    P5: ffffde86f1958070
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\070219-7687-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-9953-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34BC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34CC.tmp.xml
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_cac49d4e2266e3a4b1a2899cf2dac5d131c14_00000000_cab_89451530-13fc-4342-bab2-68c31b5fb018
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 92556029-09b1-4fed-8b7f-fd9b9e7c5a00
    Report Status: 2049
    Hashed bucket: 
    Cab Guid: 0
    02/07/2019 18:58	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff80fa2f1728e
    P4: ffffde86f1958828
    P5: ffffde86f1958070
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\070219-7687-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-9953-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34BC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34CC.tmp.xml
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_cac49d4e2266e3a4b1a2899cf2dac5d131c14_00000000_89451530-13fc-4342-bab2-68c31b5fb018
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 92556029-09b1-4fed-8b7f-fd9b9e7c5a00
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    02/07/2019 18:50	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff80df482728e
    P4: fffff483ff43c8f0
    P5: 0
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\070219-9265-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-11796-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C60.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C71.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5AA.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5BB.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_972bbf2ae1a75730cfb27da9adf591c29a7ebd_00000000_cab_845d5d32-d587-4377-af33-89e2c5941ba9
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a624598b-c4b5-4dbe-b652-16c61128832f
    Report Status: 2049
    Hashed bucket: 
    Cab Guid: 0
    02/07/2019 18:50	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff80df482728e
    P4: fffff483ff43c8f0
    P5: 0
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\070219-9265-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-11796-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C60.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C71.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5AA.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5BB.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_972bbf2ae1a75730cfb27da9adf591c29a7ebd_00000000_845d5d32-d587-4377-af33-89e2c5941ba9
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a624598b-c4b5-4dbe-b652-16c61128832f
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0

    Code:
    Name	NVIDIA GeForce GTX 1080
    PNP Device ID	PCI\VEN_10DE&DEV_1B80&SUBSYS_33601462&REV_A1\4&1F822D9D&0&0008
    Adapter Type	GeForce GTX 1080, NVIDIA compatible
    Adapter Description	NVIDIA GeForce GTX 1080
    Adapter RAM	(1,048,576) bytes
    Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b49751b9038af669\nvldumdx.dll
    Driver Version	26.21.14.3086
    INF File	oem13.inf (Section094 section)
    Colour Planes	Not Available
    Colour Table Entries	4294967296
    Resolution	2560 x 1440 x 59 hertz
    Bits/Pixel	32
    Memory Address	0xA2000000-0xA30FFFFF
    Memory Address	0x90000000-0xDFFFFFFF
    Memory Address	0xA0000000-0xA1FFFFFF
    I/O Port	0x00003000-0x00003FFF
    IRQ Channel	IRQ 16
    Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_B49751B9038AF669\NVLDDMKM.SYS (26.21.14.3086, 20.82 MB (21,836,032 bytes), 03/07/2019 18:28)
    Code:
    nvlddmkm.sys Fri Oct 27 10:49:39 2017 (59F35593)
    Many thanks for this

    As I explained in my previous post, those mindumps were from before I installed the latest GPU drivers - so those minidumps and BSODs occurred with Windows' default driver. I wouldn't pay particular attention to those, as it seems that crash is different than the ones after.

    In any case:

    1) Done
    2) Done
    3) PoW32kWatchdog-20190702-1940.zip - Google Drive
    4) MEMORY.zip - Google Drive
    5) -
    6) Done
    7 & 8 & 9) Done
    10 & 11) Unfortunately my PC is water-cooled, so it's not simple to change my GPU for testing purposes. I can, however, use the iGPU of my 9900k, for testing purposes. Having said that:
    a) We haven't clearly identified it's a GPU issue most recent crashes (with up to date GPU drivers), don't seem to insinuate that it's down to the GPU
    b) Shall I turn ON the verifier for this? Or shall I just wait a week or so, to see if there are any crashes?
    12) Will do after GPU test is over
    13)
    a) Screenshot by Lightshot
    b) Screenshot by Lightshot
      My ComputerSystem Spec



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

    It can be easy to miss BSOD when automatically restart is checked.
    With automatically restart unchecked you should see a BSOD window with bugcheck and : (
    Sometimes you may see a misbehaving driver in the form *.sys

    For startup and recovery system failure uncheck automatically restart > reboot to maintain settings

    Once you have replaced the Nvidia GPU driver with a different version > use the computer as you typically do > make sure there is no overclocking

    Please do not use windows driver verifier

    For any BSOD:

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

    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 > post a separate share link into the thread using one drive, drop box, or google drive
      My ComputerSystem Spec

  8.    #28

    zbook said: View Post
    It can be easy to miss BSOD when automatically restart is checked.
    With automatically restart unchecked you should see a BSOD window with bugcheck and : (
    Sometimes you may see a misbehaving driver in the form *.sys

    For startup and recovery system failure uncheck automatically restart > reboot to maintain settings

    Once you have replaced the Nvidia GPU driver with a different version > use the computer as you typically do > make sure there is no overclocking

    Please do not use windows driver verifier

    For any BSOD:

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

    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 > post a separate share link into the thread using one drive, drop box, or google drive
    No BSODs yet, but I've not installed anything since the 'repair'. I've run a memtest though, and you can find below links to the results:
    - MemTest86-Report-20190704-180251.html - Google Drive
    - MemTest86.log - Google Drive
    - 20190705_071858.jpg - Google Drive
    - 20190705_071900.jpg - Google Drive
    - 20190705_071908.jpg - Google Drive

    Before moving on, would it be OK to perform a clean format and continue investigating? I'm not a fan of 'repairs' and 'roll-backs', so if it's the same thing, I'd rather do a clean format, update drivers and continue investigating that way.
      My ComputerSystem Spec


  9. Posts : 26,134
    windows 10 professional version 1607 build 14393.969 64 bit
       #29

    Memory testing has significant false negatives.
    A false negative is a test pass when there is malfunctioning RAM.
    A test with only four passes may display a test pass whereas a test with passes in the twenties may display fail.
    Memtest86 was changed in January, 2019.
    It used to be 8 passes for free.
    It now is only 4 passes for free.
    The pay version has 8 passes.

    One test result text report was seen.
    Please post a link for the second test (4 passes) text report.

    An in place upgrade repair should maintain all current drivers.
    All of the current drivers were tested with windows driver verifier.
    A clean install requires new drivers.
    The drivers may need testing again with the tool.
    Please perform an in place upgrade repair so that operating system issues can be fixed without needing new drivers.
    A clean install can be performed but it would require retesting drivers.
    It may be needed in the future.
      My ComputerSystem Spec

  10.    #30

    zbook said: View Post
    Memory testing has significant false negatives.
    A false negative is a test pass when there is malfunctioning RAM.
    A test with only four passes may display a test pass whereas a test with passes in the twenties may display fail.
    Memtest86 was changed in January, 2019.
    It used to be 8 passes for free.
    It now is only 4 passes for free.
    The pay version has 8 passes.

    One test result text report was seen.
    Please post a link for the second test (4 passes) text report.

    An in place upgrade repair should maintain all current drivers.
    All of the current drivers were tested with windows driver verifier.
    A clean install requires new drivers.
    The drivers may need testing again with the tool.
    Please perform an in place upgrade repair so that operating system issues can be fixed without needing new drivers.
    A clean install can be performed but it would require retesting drivers.
    It may be needed in the future.
    Will run a 2nd test and report back. I've not yet formatted and won't do so, until we get to the bottom of the issue.

    Thanks
      My ComputerSystem Spec


 
Page 3 of 4 FirstFirst 1234 LastLast

Related Threads
Solved Figure out the offending driver in Drivers and Hardware
On the ASRock machine in my specs, using Acronis True Image 2018, I get the following BSOD error when trying to back to one of the M.2 SSDs. Backing up to a traditional SATA 2.5" SSD works fine. "Driver IRQL not less or equal" Someone on the...
I have a BSOD that I couldn't figure out in BSOD Crashes and Debugging
Dears @ Windows 10 Forums, Peace be upon you, I have a BSOD that I couldn't figure out and I'm in need of your help, The dump files are kindly attached, Many thanks in advance
Odd one this. I have my main PC... and a PC under the TV acting as a HTPC. The 2 are directly connected by a network cable. In addition both have a Wifi dongle and both get internet via WiFi I wish to transfer files from the PC to the HTPC...
Solved can t figure it out in Graphic Cards
how do i hook my acer aspire Z-3-600 with windows 10 to my tv with hdmi hook up i did the duplicate screens and change the resalution but i can t get nothing on my tv thanks
So recently I've been getting sporadic "MEMORY_MANAGEMENT" and "PAGE_FAULT_IN_NONPAGED_AREA" BSODs. I have run memory tests on my RAM but they've come up with nothing. I used to get these same issues on windows 8 but it resolved itself after some...
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 00:06.
Find Us