Windows 10: BSOD while on chrome, skype and league client open Solved

Page 1 of 3 123 LastLast

  1. Posts : 13
    64-Bit Windows 10 Home
       02 May 2018 #1

    BSOD while on chrome, skype and league client open

      My ComputerSystem Spec


  2. Posts : 20,009
    windows 10 professional version 1607 build 14393.969 64 bit
       02 May 2018 #2

    The log files are in a foreign language and cannot be scanned or read.
    Please re-post logs using English as the default language.
    Language - Add, Remove, and Change in Windows 10 Windows 10 Tutorials

    Use the beta log collector on the bottom of this web page:
    BSOD - Posting Instructions - Windows 10 Forums
    /attachment...-v2-beta10.zip
    Use the text and images in this thread in case there are any problems running the beta log collector: (post #5)
    DM Log tool problem Solved - Windows 10 Forums

    Update the system specs in the "My Computer" section:
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Windows 10 Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums


    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)
    /profile.php?do=extra
      My ComputerSystem Spec

  3. philc43's Avatar
    Posts : 3,561
    64bit Win 10 Pro ver 1803 Build 17134.285 and W10 Insider Build 18234
       02 May 2018 #3

    Hello,

    From what I can deduce from the crash dump this might be due to AVG being installed. For troubleshooting please uninstall this and see if the problem persists.

    Code:
    Start memory scan  : 0xffff868dbb5d3a78 ($csp)
    End memory scan    : 0xffff868dbb5d5000 (Kernel Stack Base)
    
                   rsp : 0xffff868dbb5d3a78 : 0xfffff80358abc6c9 : nt!KiDispatchException+0x239
    0xffff868dbb5d3a78 : 0xfffff80358abc6c9 : nt!KiDispatchException+0x239
    0xffff868dbb5d3a90 : 0xfffff80358b95c87 : nt!ExpInterlockedPopEntrySListFault
    0xffff868dbb5d3b40 : 0xfffff80358cd0080 : nt!MiZeroThenZero
    0xffff868dbb5d3b48 : 0xffff868dbb5d44a0 : 0xfffff80358cd0080 : nt!MiZeroThenZero
    0xffff868dbb5d3b60 : 0xfffff80358d9e000 : nt!MiSystemPartition
    0xffff868dbb5d3ba8 : 0xfffff80358b95c87 : nt!ExpInterlockedPopEntrySListFault
    0xffff868dbb5d3bd8 : 0xfffff80358ad707b : nt!KiDeferredReadyThread+0x31b
    0xffff868dbb5d3c18 : 0xfffff80358aa10b6 : nt!MiInsertLargePageInNodeListHelper+0x236
    0xffff868dbb5d3c30 : 0xfffff80358d9e000 : nt!MiSystemPartition
    0xffff868dbb5d3d68 : 0xfffff80358d9e000 : nt!MiSystemPartition
    0xffff868dbb5d3d98 : 0xfffff80358a9e0ea : nt!MiInsertPageInFreeOrZeroedList+0x1fa
    0xffff868dbb5d3e00 : 0xfffff80358d9e000 : nt!MiSystemPartition
    0xffff868dbb5d3e10 : 0xfffff80358d9eff0 : nt!MiSystemPartition+0xff0
    0xffff868dbb5d3e28 : 0xfffff80358d9e880 : nt!MiSystemPartition+0x880
    0xffff868dbb5d3e88 : 0xfffff80358a9cbde : nt!MiPfnShareCountIsZero+0x41e
    0xffff868dbb5d3eb8 : 0xfffff80358c3df35 : nt!MI_GET_PAGE_FRAME_FROM_PTE+0x9
    0xffff868dbb5d3ee8 : 0xfffff80358a9a965 : nt!MiDeletePteList+0x3a5
    0xffff868dbb5d3f28 : 0xfffff80358b5e805 : nt!KiFlushRangeTb+0xd9
    0xffff868dbb5d3f30 : 0xfffff80358d9e000 : nt!MiSystemPartition
    0xffff868dbb5d3f38 : 0xfffff80358aeff30 : nt!RtlGetExtendedContextLength+0x34
    0xffff868dbb5d3fa8 : 0xfffff80358a97e00 : nt!MiDecommitPages+0xc20
    0xffff868dbb5d4008 : 0xfffff803592ef931 : hal!HalRequestIpi+0x211
    0xffff868dbb5d4098 : 0xfffff80358ae7128 : nt!MiFlushTbList+0x518
    0xffff868dbb5d4118 : 0xfffff80358cd0080 : nt!MiZeroThenZero
    0xffff868dbb5d4128 : 0xfffff80358b9fbc2 : nt!KiExceptionDispatch+0xc2
    0xffff868dbb5d4228 : 0xfffff80358a5147a : nt!KiAbEntryGetLockedHeadEntry+0x23a
    0xffff868dbb5d4230 : 0xfffff80358cd0080 : nt!MiZeroThenZero
    0xffff868dbb5d4238 : 0xfffff80358d9e000 : nt!MiSystemPartition
    0xffff868dbb5d4278 : 0xfffff80358b95c87 : nt!ExpInterlockedPopEntrySListFault
    0xffff868dbb5d42c8 : 0xfffff80358ad3955 : nt!KiAbProcessContextSwitch+0x245
    0xffff868dbb5d42e8 : 0xfffff80358a9cc4f : nt!MiPfnShareCountIsZero+0x48f
    0xffff868dbb5d4308 : 0xfffff80358b9bd75 : nt!KiGeneralProtectionFault+0x335
    0xffff868dbb5d4408 : 0xfffff803592efd5f : hal!HalpApicRequestInterrupt+0x10f
    0xffff868dbb5d4478 : 0xfffff80358b95c87 : nt!ExpInterlockedPopEntrySListFault
    0xffff868dbb5d4490 : 0xffff868dbb5d44a0 : 0xfffff80358cd0080 : nt!MiZeroThenZero
    0xffff868dbb5d44a0 : 0xfffff80358cd0080 : nt!MiZeroThenZero
    0xffff868dbb5d44a8 : 0xfffff80358a8a881 : nt!MiGetPage+0xd1
    0xffff868dbb5d4588 : 0xfffff80358a8a3f8 : nt!MiGetPageChain+0x148
    0xffff868dbb5d4590 : 0xfffff80358d9e000 : nt!MiSystemPartition
    0xffff868dbb5d45a8 : 0xfffff80358ad6ac7 : nt!KiExitDispatcher+0x117
    0xffff868dbb5d45e0 : 0xfffff80358d9e000 : nt!MiSystemPartition
    0xffff868dbb5d4618 : 0xfffff80358a61f09 : nt!ExAcquirePushLockExclusiveEx+0xe9
    0xffff868dbb5d4628 : 0xfffff80358b89160 : nt!MiReadPteShadow+0xc
    0xffff868dbb5d4658 : 0xfffff80358c3df8c : nt!MI_READ_PTE_LOCK_FREE+0xc
    0xffff868dbb5d46a8 : 0xfffff80358a88b01 : nt!MiResolvePrivateZeroFault+0x5c1
    0xffff868dbb5d46e8 : 0xfffff80358c3df35 : nt!MI_GET_PAGE_FRAME_FROM_PTE+0x9
    0xffff868dbb5d4728 : 0xfffff80358d9e000 : nt!MiSystemPartition
    0xffff868dbb5d4748 : 0xfffff80358a9114d : nt!MiCommitExistingVad+0x7dd
    0xffff868dbb5d4778 : 0xfffff80358b1df98 : nt!KeInsertQueueEx+0xe8
    0xffff868dbb5d47a8 : 0xfffff80358a8043a : nt!MiUnlockAndDereferenceVad+0x1ca
    0xffff868dbb5d47f8 : 0xfffff80358b89160 : nt!MiReadPteShadow+0xc
    0xffff868dbb5d4808 : 0xfffff80358c3df8c : nt!MI_READ_PTE_LOCK_FREE+0xc
    0xffff868dbb5d4838 : 0xfffff80358a8700a : nt!MiResolveDemandZeroFault+0x1ea
    0xffff868dbb5d4928 : 0xfffff80358a8243f : nt!MmAccessFault+0x6cf
    0xffff868dbb5d4a28 : 0xfffff80358f1e504 : nt!NtAllocateVirtualMemory+0x44
    Unable to load image \SystemRoot\system32\drivers\avgSP.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgSP.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgSP.sys
    0xffff868dbb5d4af8 : 0xfffff80358b9c0f3 : nt!KiPageFault+0x373
    0xffff868dbb5d4b00 : 0x00000000005436b0 :  Trap @ ffff868dbb5d4b00
      My ComputersSystem Spec


  4. Posts : 13
    64-Bit Windows 10 Home
    Thread Starter
       02 May 2018 #4

    Here are the latest log files using english as default language


    DESKTOP-QBN8TTG-Πεμ_03_05_2018__44501,01.zip
    I also uninstalled AVG to test philc43 theory
      My ComputerSystem Spec


  5. Posts : 20,009
    windows 10 professional version 1607 build 14393.969 64 bit
       02 May 2018 #5

    See if you can run the BETA log collector on the bottom of the web page as it will collect more useful files:
    /attachment...-v2-beta10.zip
    (extract > open)
    Use the text and images in this thread in case there are any problems running the beta log collector: (post #5)
    DM Log tool problem Solved - Windows 10 Forums


    The log files display:
    Η υπηρεσία καταγραφής συμβάντων έχει ξεκινήσει.
    Ο χρόνος λειτουργίας του συστήματος είναι 19 δευτερόλεπτα.
    See if you can go back and forth with the language change so that the text becomes English:
    Language - Add, Remove, and Change in Windows 10 Windows 10 Tutorials
      My ComputerSystem Spec


  6. Posts : 13
    64-Bit Windows 10 Home
    Thread Starter
       03 May 2018 #6

    Latest Logs


    This is with the original log collector
    DESKTOP-QBN8TTG-Thu_05_03_2018_151541_16.zip

    And this is with the log collector v2 beta
    DESKTOP-QBN8TTG (2018-05-03 15 14).zip
      My ComputerSystem Spec


  7. Posts : 20,009
    windows 10 professional version 1607 build 14393.969 64 bit
       03 May 2018 #7

    1) 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 > under startup and recovery > system failure > un-check automatically restart
    When there is BSOD you should now see a BSOD window with : ( and a bugcheck. It may also display a misbehaving driver in the form *.sys. If you see a misbehaving driver please record it and post it into the thread.
    There may be % counter. Make sure that you allow this to rise to 100% before rebooting so that there is sufficient time to create the dump file.
    b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

    2) Uninstall iorbit and any drivers that were installed with the software
    3) Uninstall driver booster and any drivers that were installed with the software

    4) For any new BSOD > open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > zip > post a one drive or drop box share link into the thread
    Last edited by zbook; 03 May 2018 at 11:20.
      My ComputerSystem Spec


  8. Posts : 13
    64-Bit Windows 10 Home
    Thread Starter
       03 May 2018 #8

    Just had one more bsod


    i uninstalled the ionbit unninstaller and the driver booster and still got a bsod i was playing league and had twitch on chrome
    here is the latest logs
    DESKTOP-QBN8TTG-Thu_05_03_2018_192256_78.zip
      My ComputerSystem Spec


  9. Posts : 20,009
    windows 10 professional version 1607 build 14393.969 64 bit
       03 May 2018 #9

    Please post a beta log collector zip.
    For any new BSOD please use the beta log collector.
    Open file explorer > this pc > C: > in the right upper corner search for C:\widows\memory.dmp > zip > post a share link into the thread.
    Which drivers had been installed with these software?

    For drivers the best source is the computer or motherboard manufacturer.
    If drivers are not available from the computer or motherboard manufacturer the next best sources are the component manufacturers (Intel, Nvidia, AMD, Killer Networks, Relatek, etc.)
    When using driver update software you don't know what you are getting.
    We see BSOD related to drivers from these websites.
    Sometimes performing a system restore is necessary to find a period of time that predates the installation of the problematic drivers.
    Other times a clean install is necessary.

    When available please post an image of the virtual memory window (post #7)

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    6) Make sure that there is no over clocking while troubleshooting.

    7) Sometimes there are problems in the bios that produce bsod.
    The BIOS: Version/Date American Megatrends Inc. V11.7, 5/18/2015
    8) Please check to see if this is the most up to date version.

    9) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

    10) To ensure that there are no improper bios settings please reset the bios.
    11) Sometimes there can be failure to boot after resetting the bios.
    12) Backup the computer files to another drive or to the cloud.
    13) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    14) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    15) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.
    a) Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool
    The testing is done not by time but by passes.
    The more passes the better.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a test pass when there is malfunctioning RAM.
    There is 16 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM Windows 10 Tutorials

    16) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:Speccy - Free Download - Piriform: Speccy - System Information - Free
    Download Speccy | Find your computer specs, free!
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer


    Code:
    2/3/2018 6:21 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type 0
    Event Name: LiveKernelEvent
    Response: Δεν υπάρχει
    Cab Id: 15be8a06-70be-4e4c-a335-52a068f9730e
    
    Problem signature:
    P1: 141
    P2: ffffbc0faa57e010
    P3: fffff801233c6b2c
    P4: 0
    P5: 2220
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180203-0821.dmp
    \\?\C:\WINDOWS\TEMP\WER-360904109-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E1.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E1.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F1.tmp.txt
    \\?\C:\Windows\Temp\WER54A6.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b3e7bfb839995bf85dd6b4b48563942223ae5aa9_00000000_cab_39335c75
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 934c9b18-a71e-4f7a-90c2-777910d88671
    Report Status: 268435456
    Hashed bucket:2/1/2018 12:02 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type 0
    Event Name: LiveKernelEvent
    Response: Δεν υπάρχει
    Cab Id: 4f100c5d-0144-4b26-a1dd-f8c85907c745
    
    Problem signature:
    P1: 141
    P2: ffffbc0fb8134010
    P3: fffff801233c6b2c
    P4: 0
    P5: 2cf4
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180201-1402.dmp
    \\?\C:\WINDOWS\TEMP\WER-208574437-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB12A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB139.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB15A.tmp.txt
    \\?\C:\Windows\Temp\WERFCF9.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_d6faa6454e2593aa1b4b27018cd6aa81815_00000000_cab_2d2304b8
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 4c7a2f83-3913-4fa0-abbe-d785bdd8a4f0
    Report Status: 268435456
    Hashed bucket:
    1/27/2018 10:20 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type 0
    Event Name: LiveKernelEvent
    Response: Δεν υπάρχει
    Cab Id: af6d28e1-ee30-44a1-abd2-1c8596d5ac95
    
    Problem signature:
    P1: 141
    P2: ffffc508ae1811e0
    P3: fffff801fc456b2c
    P4: 0
    P5: 2e04
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180127-1219.dmp
    \\?\C:\WINDOWS\TEMP\WER-488137578-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C4E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C5E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C6F.tmp.txt
    \\?\C:\Windows\Temp\WERE2EB.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_9a9555955daf83967cff6becfb5c317cc6a320ea_00000000_cab_327ceaba
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a3183404-c221-45d7-8c46-04d42aec3761
    Report Status: 268435456
    Hashed bucket:
    3/17/2018 11:07 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type 0
    Event Name: LiveKernelEvent
    Response: Δεν υπάρχει
    Cab Id: b7262198-03d6-4f4f-b701-650bc5353811
    
    Problem signature:
    P1: 141
    P2: ffff97887a77a010
    P3: fffff807cd3bbd90
    P4: 0
    P5: 21d4
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180317-1307.dmp
    \\?\C:\WINDOWS\TEMP\WER-61981125-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA9A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA9A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREAAA.tmp.txt
    \\?\C:\Windows\Temp\WER2BCA.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_448035af9135ed1bd599aad7b0f95cdb5d918c45_00000000_cab_185e303e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 8fa8ba9a-2fc2-4a53-be5b-423306f8d09f
    Report Status: 268435456
    Hashed bucket:
    2/23/2018 7:04 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type 0
    Event Name: LiveKernelEvent
    Response: Δεν υπάρχει
    Cab Id: c08d8c35-f07d-4a78-84fb-00472a520a62
    
    Problem signature:
    P1: 141
    P2: ffff8004d4a254a0
    P3: fffff809c2736b2c
    P4: 0
    P5: 1b70
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180223-0904.dmp
    \\?\C:\WINDOWS\TEMP\WER-450900687-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5CEC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5CFC.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D0D.tmp.txt
    \\?\C:\Windows\Temp\WER84F7.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a177794cbaf2b27c2c626164bbb1a2e6f3cd150_00000000_cab_397c8832
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 2d0ecb27-23dc-45e2-8c40-81a07c2c4c1b
    Report Status: 268435456
    Hashed bucket:
    3/16/2018 1:13 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type 0
    Event Name: LiveKernelEvent
    Response: Δεν υπάρχει
    Cab Id: f266e86f-5988-41a0-9431-63692bd7ff70
    
    Problem signature:
    P1: 141
    P2: ffff868d22c09180
    P3: fffff801d78dbd90
    P4: 0
    P5: 6bc
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180316-1513.dmp
    \\?\C:\WINDOWS\TEMP\WER-67001078-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8AB0.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8AC0.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8AD1.tmp.txt
    \\?\C:\Windows\Temp\WERB01C.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_de2da43e26f5b4a49dd583f2c4648e4d594fda_00000000_cab_23a2b431
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 7fa3f257-43fb-48f8-ab95-c32386fec37a
    Report Status: 268435456
    Hashed bucket:
    1/25/2018 7:54 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type 0
    Event Name: LiveKernelEvent
    Response: Δεν υπάρχει
    Cab Id: f6c0a6aa-bd9d-4107-a0ad-432ab2f33430
    
    Problem signature:
    P1: 141
    P2: ffffc508a46464a0
    P3: fffff801fc456b2c
    P4: 0
    P5: 14bc
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180125-0953.dmp
    \\?\C:\WINDOWS\TEMP\WER-306575000-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F0F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F3E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F9D.tmp.txt
    \\?\C:\Windows\Temp\WER5C77.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_28d3160a5d85e744663d26dc73171d55e442719_00000000_cab_16866446
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 7672c911-57a9-44d3-b0d8-e4eac64786c3
    Report Status: 268435456
    Hashed bucket:
    Code:
    Event[11599]:  Log Name: System
      Source: volmgr
      Date: 2018-05-03T19:20:00.463
      Event ID: 161
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-QBN8TTG
      Description: 
    Dump file creation failed due to error during dump creation.
    Last edited by zbook; 03 May 2018 at 12:18.
      My ComputerSystem Spec

  10. philc43's Avatar
    Posts : 3,561
    64bit Win 10 Pro ver 1803 Build 17134.285 and W10 Insider Build 18234
       03 May 2018 #10

    ghost1341 said: View Post
    i uninstalled the ionbit unninstaller and the driver booster and still got a bsod i was playing league and had twitch on chrome
    here is the latest logs
    DESKTOP-QBN8TTG-Thu_05_03_2018_192256_78.zip
    There was no new mini-dump file in the logs. Did you create the new set of logs immediately after your device restarted. If so you may not have given the system enough time to generate the mini-dump files. Please try to create the logs again.
      My ComputersSystem Spec


 
Page 1 of 3 123 LastLast

Related Threads
Random BSOD - while Chrome open in BSOD Crashes and Debugging
I have been having issues over the last week or so with BSOD. Each time it's a different BSOD message -this evening it was CLOCK-WATCHDOGTIMEOUT. I can't nail down whats happening. It seems to be random. Often it happens once the PC has been on...
Hello- I get BSOD at random times throughout the day. I mostly have Revit, google chrome, and microsoft outlook open. Here are some examples of BSOD that occur often. Kernel Data Inpage Error - RTKVHD64.sys Unexpected Store Exception...
BSOD when Chrome open in BSOD Crashes and Debugging
I have had a number of times in the last three or four days where I am doing nothing other than looking at chrome with a bunch of tabs open and the screen on my second monitor will drop and if audio playing it goes to stutter and then the whole...
hhhhhhhhhhhhhhhhhhhh
Hi, I just updated to W10. If I open several files/documents I get the icon in the taskbar (the bar at the bottom of the page), hover over it and see the documents that are open. I then open Chrome and the Chrome icon appears in the taskbar and...

Tags for this Thread

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 22:24.
Find Us