Page 3 of 4 FirstFirst 1234 LastLast
  1.    18 Sep 2017 #21
    Join Date : Jan 2016
    Posts : 52
    Windows 10 Version 1703 (x64)
    Thread Starter

    Yeah, i may have installed/uninstalled some apps, but i changed the settings you mentioned, ran ccleaner, and then used DM Log Collector tool after. So, what do you think i should do next?

    I am gonna try to enable
    Windows Error Reporting using Regedit:
    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting

    Here we go, hopefully there is something "different" this time:
    BSOD Critical Error After Installing a New RAM Attached Files
      My ComputerSystem Spec
  2.    18 Sep 2017 #22
    Join Date : Apr 2017
    Posts : 8,561
    windows 10 professional version 1607 build 14393.969 64 bit

    That worked as there are now 2 entries.
      My ComputerSystem Spec
  3.    18 Sep 2017 #23
    Join Date : Jan 2016
    Posts : 52
    Windows 10 Version 1703 (x64)
    Thread Starter

    Cool, so, anything interesting..?
      My ComputerSystem Spec
  4.    18 Sep 2017 #24
    Join Date : Apr 2017
    Posts : 8,561
    windows 10 professional version 1607 build 14393.969 64 bit

    If you use the computer the logs will be produced when there are problems.
    Then if they are not deleted we can troubleshoot them.
    So please use the computer as much as possible.
    This includes using demanding programs.
      My ComputerSystem Spec
  5.    18 Sep 2017 #25
    Join Date : Jan 2016
    Posts : 52
    Windows 10 Version 1703 (x64)
    Thread Starter

    Will do mate, hopefully you'd be around if things went south, thanks again for your time, have a good one!.
      My ComputerSystem Spec
  6.    23 Sep 2017 #26
    Join Date : Jan 2016
    Posts : 52
    Windows 10 Version 1703 (x64)
    Thread Starter

    Hi there, I've been using my PC for the past couple of days without any issues, but unexpectedly and out of nowhere, i ran into a BSOD :
    BSOD Critical Error After Installing a New RAM Attached Files
      My ComputerSystem Spec
  7.    23 Sep 2017 #27
    Join Date : Apr 2017
    Posts : 8,561
    windows 10 professional version 1607 build 14393.969 64 bit

    In order to properly troubleshoot we need to be able to view the Windows logs.
    The logs are still being deleted by software programs.
    Windows error reporting
    Windows log files
    Please fix these settings.
    As an alternative you can completely uninstall Ccleaner during the troubleshooting process so that it does not interfere with the logs.
      My ComputerSystem Spec
  8.    23 Sep 2017 #28
    Join Date : Jan 2016
    Posts : 52
    Windows 10 Version 1703 (x64)
    Thread Starter

    Hey zbook, I got CCleaner uninstalled yesterday, after I heard that there had been some kind of a vulnerability/attack going on, also the Disk cleanup tool is showing that there is lots of logs stored:

    Click image for larger version. 

Name:	Space.png 
Views:	6 
Size:	20.5 KB 
ID:	154708

    Is there a "different" way to generate or extract those files to share them with you?.

    Thanks.

    Update: Could those reading in Control Panel > Reliability Monitor help somehow?

    Code:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ef (0xffffe60e239e87c0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: dceafe54-41e7-40f4-ab0e-0e9a7ccb12d2.
    After the crash above, lots of other things crashed too:

    Code:
    Faulting application name: DllHost.exe, version: 10.0.15063.0, time stamp: 0x4f42de92
    Faulting module name: infekt-nfo-shell.dll, version: 0.9.7.0, time stamp: 0x588db1cb
    Exception code: 0xc0000005
    Fault offset: 0x000000000002b234
    Faulting process id: 0x222c
    Faulting application start time: 0x01d33479748cde25
    Faulting application path: C:\Windows\system32\DllHost.exe
    Faulting module path: C:\Program Files\iNFekt\infekt-nfo-shell.dll
    Report Id: eb3bd7c6-26dc-4f25-8d64-55220239248b
    Faulting package full name: 
    Faulting package-relative application ID: 
    
    
    Even when i tried to use a different anti-virus:
    
    Faulting application name: kis18.0.0.405aben_12989.exe, version: 18.0.0.405, time stamp: 0x58877070
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x77580d24
    Faulting process id: 0x229c
    Faulting application start time: 0x01d3347db81c0c47
    Faulting application path: D:\Downloads\kis18.0.0.405aben_12989.exe
    Faulting module path: unknown
    Report Id: 580330eb-968e-44fb-b05a-9ab672dfe1b9
    Faulting package full name: 
    Faulting package-relative application ID: 
    
    
    Edge:
    
    Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.15063.608, time stamp: 0x59ae240c
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000604
    Fault offset: 0x0000000000000000
    Faulting process id: 0x2918
    Faulting application start time: 0x01d3347e1529951d
    Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe
    Faulting module path: unknown
    Report Id: 01efde8a-6721-4cb7-b82b-87b5adbf26ab
    Faulting package full name: Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe
    Faulting package-relative application ID: ContentProcess
    
    
    Logitech Utility:
    
    Faulting application name: Updater.exe, version: 6.70.1197.0, time stamp: 0x59b824a9
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x83485340
    Faulting process id: 0x9ec
    Faulting application start time: 0x01d3348c4abad586
    Faulting application path: C:\ProgramData\Logishrd\LogiOptions\Software\Current\Updater.exe
    Faulting module path: unknown
    Report Id: 0cdc8b52-78fd-48aa-8296-c06368e55abe
    Faulting package full name: 
    Faulting package-relative application ID: 
    
    
    Faulting application name: ruplp.exe, version: 3.1.3.621, time stamp: 0x4fce260e
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x63ab7540
    Faulting process id: 0x25fc
    Faulting application start time: 0x01d3348f8696acf6
    Faulting application path: C:\PROGRA~1\VSREVO~1\REVOUN~1\ruplp.exe
    Faulting module path: unknown
    Report Id: eab3b7cc-da30-4c81-94ec-ae254164db72
    Faulting package full name: 
    Faulting package-relative application ID: 
    
    
    Faulting application name: DllHost.exe, version: 10.0.15063.0, time stamp: 0xb54cdbe6
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x63ab7540
    Faulting process id: 0x1450
    Faulting application start time: 0x01d3348fa437531c
    Faulting application path: C:\Windows\SysWOW64\DllHost.exe
    Faulting module path: unknown
    Report Id: 6a24b450-efe4-4c92-ab1c-93e9af95dadc
    Faulting package full name: 
    Faulting package-relative application ID: 
    
    
    Faulting application name: DllHost.exe, version: 10.0.15063.0, time stamp: 0xb54cdbe6
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x63ab7540
    Faulting process id: 0x27f4
    Faulting application start time: 0x01d3348faf42e0bb
    Faulting application path: C:\Windows\SysWOW64\DllHost.exe
    Faulting module path: unknown
    Report Id: f3a31953-49b3-45da-8c74-6c00c1f0471b
    Faulting package full name: 
    Faulting package-relative application ID: 
    
    
    Is system failing?
    
    Faulting application name: PickerHost.exe, version: 10.0.15063.0, time stamp: 0xb4e867b1
    Faulting module name: KERNELBASE.dll, version: 10.0.15063.608, time stamp: 0x943cbf8b
    Exception code: 0xc0000005
    Fault offset: 0x0000000000033cf8
    Faulting process id: 0x219c
    Faulting application start time: 0x01d3348fb73a7f6b
    Faulting application path: C:\Windows\System32\PickerHost.exe
    Faulting module path: C:\Windows\System32\KERNELBASE.dll
    Report Id: 7e5a3dbd-50b0-4b65-ab8e-f6b63d0446e1
    Faulting package full name: 
    Faulting package-relative application ID: 
    
    
    Asus:
    
    Faulting application name: AvLaunch.exe, version: 17.6.3625.0, time stamp: 0x59a566c7
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x6f047540
    Faulting process id: 0x1a70
    Faulting application start time: 0x01d3348fe79fecb9
    Faulting application path: C:\Program Files\AVAST Software\Avast\AvLaunch.exe
    Faulting module path: unknown
    Report Id: fa9e6c37-03a6-4a16-8ee8-3ec197f969cc
    Faulting package full name: 
    Faulting package-relative application ID: 
    
    
    Logitech again:
    
    Faulting application name: LULnchr.exe, version: 2.40.239.0, time stamp: 0x5101f485
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x6f047540
    Faulting process id: 0x1acc
    Faulting application start time: 0x01d3348fe7d4a4e6
    Faulting application path: C:\Program Files\Common Files\LogiShrd\sp6\LU1\LULnchr.exe
    Faulting module path: unknown
    Report Id: 0501987c-9673-4d00-a13c-882b8046e419
    Faulting package full name: 
    Faulting package-relative application ID: 
    
    
    Faulting application name: DllHost.exe, version: 10.0.15063.0, time stamp: 0xb54cdbe6
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x6f047540
    Faulting process id: 0x1ba8
    Faulting application start time: 0x01d33490110d0919
    Faulting application path: C:\Windows\SysWOW64\DllHost.exe
    Faulting module path: unknown
    Report Id: da952ded-4d39-4e16-b0a0-43db9100a5ca
    Faulting package full name: 
    Faulting package-relative application ID:
      My ComputerSystem Spec
  9.    23 Sep 2017 #29
    Join Date : Apr 2017
    Posts : 8,561
    windows 10 professional version 1607 build 14393.969 64 bit

    Once the files are deleted you will need to wait for more to be generated.

    In the left lower corner search type: dxdiag
    Then go though each page and allow extra time for it to completely load.
    Save the file and view the bottom: Windows error reporting
    This was missing on your computer.

    In the left lower corner search type: msinfo32 > on the left pane expand software environment > click on Windows error reporting > the last entry on your computer was 9/18/2017.

    Somehow the Windows error reporting were deleted after 9/18/2017.

    Windows error reporting is important for troubleshooting.
      My ComputerSystem Spec
  10.    23 Sep 2017 #30
    Join Date : Jan 2016
    Posts : 52
    Windows 10 Version 1703 (x64)
    Thread Starter

    Quote Originally Posted by zbook View Post
    Once the files are deleted you will need to wait for more to be generated.

    In the left lower corner search type: dxdiag
    Then go though each page and allow extra time for it to completely load.
    Save the file and view the bottom: Windows error reporting
    This was missing on your computer.

    In the left lower corner search type: msinfo32 > on the left pane expand software environment > click on Windows error reporting > the last entry on your computer was 9/18/2017.

    Somehow the Windows error reporting were deleted after 9/18/2017.

    Windows error reporting is important for troubleshooting.

    Yeah, I get it, although things looks different here, i can actually get to see all events/errors that happened on the 23rd:

    Click image for larger version. 

Name:	Reliability Monitor.png 
Views:	3 
Size:	205.7 KB 
ID:	154721

    Click image for larger version. 

Name:	Windows Error Reporting.png 
Views:	2 
Size:	169.1 KB 
ID:	154723
    BSOD Critical Error After Installing a New RAM Attached Files
    Last edited by Surreal90; 23 Sep 2017 at 17:20.
      My ComputerSystem Spec

 
Page 3 of 4 FirstFirst 1234 LastLast


Similar Threads
Thread Forum
BSOD after installing windows 10: ntfs.sys error
Running Win 10 Pro 64 bit ver. 1703 build 15063.540 I've just reinstalled my pc with windows 10 pro and I'm receiving bsod's of ntfs.sys (which doesn't seem good to me) I need some expert help on this. OS installed on OCZ vertex 3.
BSOD Crashes and Debugging
BSOD on idle, Error: critical structure corruption
I have been getting BSODs frequently (approx. 10 min after restarting system) The BSOD is mainly "Critical Structure Corruption" I have done a memory test using the windows tool and it showed no errors. I have also run chdsk and received no...
BSOD Crashes and Debugging
Random BSOD Critical Structure Error while playing videos on youtube
Im getting some random BSOD when im watching a video on youtube can someone help me figure out the problem? here are my files:
BSOD Crashes and Debugging
BSOD while playing youtube, error 0x109-Critical Structure Corruption
Hi Guys, I have this BSOD while playing youtube. crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x109 (0xA3A01F5A6788B6B1, 0x0, 0x4CA3D042862E2DA4,...
BSOD Crashes and Debugging
BSOD after installing windows 10, BUGCODE_USB_DRIVER error
Hello, i need some help, i just did a clean installation of Windows 10 on my laptop and is getting 5 times per day the BUGCODE_USB_DRIVER error with the blue screen crash. Attach de bug dump file
BSOD Crashes and Debugging
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:02.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums