Page 1 of 4 123 ... LastLast
  1.    10 Oct 2017 #1
    Join Date : Oct 2017
    Posts : 18
    Windows 10 x64

    Log Collector Fails


    Hello!
    When I run the log collector and press a key when it says to, a command prompt appears but almost instantly disappears as a bunch of lines quickly flash by. After, there is a folder on my desktop called TF debug files but it is full of empty text files. A text file called 'temp' also appears, it has the statement "'reg' is not recognized as an internal or external command,operable program or batch file." repeated 6 times. There is also a script called _zipit created.
    I have tried redownloading the collector and running as an administrator.

    Thanks!
      My ComputerSystem Spec
  2.    11 Oct 2017 #2
    Join Date : Nov 2015
    Posts : 2,863
    64bit Win 10 Pro ver 1709 Build 16299.64

    Please right click on the file that you downloaded and make sure the details tab looks like this. If it doesn't you may have a corrupted download.
    Click image for larger version. 

Name:	2017-10-11.png 
Views:	45 
Size:	14.9 KB 
ID:	157454
      My ComputersSystem Spec
  3.    11 Oct 2017 #3
    Join Date : Oct 2017
    Posts : 18
    Windows 10 x64
    Thread Starter

    Yes, it looks exactly like that
      My ComputerSystem Spec
  4.    11 Oct 2017 #4
    Join Date : Oct 2016
    Posts : 322
    seL4

    Hi Jeffsun13,

    We currently are working on an updated version of the log collector, right now it is still in beta, but we'd like you to try it to see if it resolves the problem.

    For now it's not in a nice .exe format, but it is still pretty straightforward to run. Right-click the .zip, select "extract all" then in the new extracted folder double-click "log-collector" to run it.
    Log Collector Fails Attached Files
      My ComputerSystem Spec
  5.    11 Oct 2017 #5
    Join Date : Oct 2017
    Posts : 18
    Windows 10 x64
    Thread Starter

    I attached the zip, but the log collector still gave an error after every line, in the form:

    The term 'driverquery.exe' is not recognized as the name of a cmdlet, function, script file, or operable program.

    This statement showed for 'powercfg.exe', 'cscript.exe', 'inconfig.exe', 'route.exe', and 'wevtutil.exe'


    DESKTOP-3B05JDE (10-11-2017 12 47 PM).zip
      My ComputerSystem Spec
  6.    11 Oct 2017 #6
    Join Date : Oct 2016
    Posts : 322
    seL4

    That's very strange. Is your account an administrator, or are you elevating with a separate administrator account?

    Please check if the following files exist:

    "C:\Windows\System32\driverquery.exe"
    "C:\Windows\System32\powercfg.exe"
    "C:\Windows\System32\cscript.exe"
    "C:\Windows\System32\ipconfig.exe"
    "C:\Windows\System32\ROUTE.EXE"
    "C:\Windows\System32\wevtutil.exe"

    Also please run the following from PowerShell:
    Code:
    echo ($env:path).Replace(';',"`n") > "$home\Desktop\variable-path.txt"
    Code:
    &"$env:SystemRoot\System32\ipconfig.exe" > "$home\Desktop\ipconfig.txt"

    This will place "variable-path.txt" and "ipconfig.txt" on your Desktop, upload both files here or report any errors you run into.
      My ComputerSystem Spec
  7.    11 Oct 2017 #7
    Join Date : Oct 2017
    Posts : 18
    Windows 10 x64
    Thread Starter

    My account is an administrator, but none of those files exist.

    ipconfig.txtvariable-path.txt
      My ComputerSystem Spec
  8.    11 Oct 2017 #8
    Join Date : Oct 2016
    Posts : 322
    seL4

    Jeff,

    It looks like your path environment variable has been overwritten, either manually or when you installed the mathematics packages algs4 and matlab. It's missing the following entries, which would explain why it could not find the executables.

    Code:
    C:\WINDOWS\system32
    C:\WINDOWS
    C:\WINDOWS\System32\Wbem
    C:\WINDOWS\System32\WindowsPowerShell\v1.0\
    I've updated the script to include fully-qualified paths to each executable called, which should resolve this. Thanks for your help with troubleshooting and patience.

    Also, I assume you are wanting to run this log collector because you are running into a problem with your PC crashing. What issues have you been experiencing with your computer?
    Log Collector Fails Attached Files
      My ComputerSystem Spec
  9.    11 Oct 2017 #9
    Join Date : Oct 2017
    Posts : 18
    Windows 10 x64
    Thread Starter

    This is the log collector file:
    DESKTOP-3B05JDE (10-11-2017 4 50 PM).zip

    I've been experiencing random BSODs for a while, and I've tried many fixes, including several clean reinstalls of Windows and sending the laptop back into Dell, but nothing has worked. All scans of memory and the SSD have returned no errors or corrupted files. I followed one person's advice and did a clean reset but without installing the driver for Intel Rapid Storage Technology and I no longer got BSODs but it still completely froze my computer until I restarted, just without the blue screens. I ran WhoCrashed, and it said the modules ntoskrnl.exe and ntdll.sys were at fault.

    Notes: No trends for when the BSODs occur, often just when computer is completely idle and doing nothing. I've also had issues with the computer shutting down every time it goes to sleep, crashing while asleep, and not being able to charge, but all of these went away randomly or I fixed them. When BSODs occur, programs stop responding for about 20 seconds, before it shows the BSOD, and the computer tries to restart but fails and gets stuck at the logo screen.

    Thank you so much for your time!
      My ComputerSystem Spec
  10.    11 Oct 2017 #10
    Join Date : Oct 2016
    Posts : 322
    seL4

    As a start, there is a new release for your XPS' firmware. Dell marked it as "Urgent" and list "System stability enhancements" in the change log. Even if this does not resolve the issue, I am certain Dell support will request you do this before they will assist you further.

    Dell XPS 13 9350 1.5.1 BIOS Driver Details | Dell US


    Looking at the crash dump, have you noticed that most blue screens are showing "Critical Process Died" or are they across the board in their error messages? Unfortunately the minidump did not contain much information, and it would help if we could get the full dump. However the full memory dump C:\Windows\MEMORY.dmp is the size of your ram, 8GB, so it may be annoying to upload and download it, even after compressing it.

    You may want to switch your dump type to "Active" which will only store the memory in use, which will generally be a much smaller amount. Here is a guide on changing crash dump settings: Configure Windows 10 to Create Minidump on BSOD BSOD Tutorials

    I also saw that your event log reported some bluetooth issues, have you been noticing problems with that? Here are some examples:

    Code:
    Event[7]:
      Log Name: System
      Source: bcbtums
      Date: 2017-09-11T17:43:20.551
      Event ID: 1026
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-3B05JDE
      Description: 
    Failed initializing BT device, failed RAM patch download.
    Code:
    Event[8]:
      Log Name: System
      Source: BTHUSB
      Date: 2017-09-11T17:43:22.853
      Event ID: 3
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-3B05JDE
      Description: 
    A command sent to the adapter has timed out. The adapter did not respond.
    Code:
    Event[189]:
      Log Name: System
      Source: BTHUSB
      Date: 2017-09-12T21:45:36.497
      Event ID: 17
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-3B05JDE
      Description: 
    The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
    Oh and here's a fairly good guide on fixing your path environment variables..
      My ComputerSystem Spec

 
Page 1 of 4 123 ... LastLast


Similar Threads
Thread Forum
Solved Cannot run DM log Collector Tool
Hi I have had a BSOD and want to run the DM Log Collector tool as instructed in the BSOD forum, so I can post on that forum, however when I try to run the tool I get this message "This app can't run on your PC. (see attached Picture) Any ideas...
BSOD Crashes and Debugging
100% Disk: WPR_Initiated_DiagTrackAotLogger_WPR System Collector.etl
Disk usage spikes to 100% all the time with only FF browser open - and even with nothing open. Already disabled Windows Search and Superfetch. Resource Monitor shows "WPR_Initiated_DiagTrackAotLogger_WPR System Collector.etl" using 900K B/Sec: ...
Performance & Maintenance
Windows 10 start button fails, search fails restart fails
Not cause by virus .. this just started today. I tried a restore point of yesterday .. nothing. I have tried several suggestions from the web but nothing seems to do it? I know it would be better if i could name them but can't remember the exact...
General Support
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 01:28.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums