Troubleshooting : Need help with Ntoskrnl thread causing high CPU

April 12, 2016, 9:55 pm

≫ Next: Process Explorer : Hang in Processs properties window

≪ Previous: Development : Memory not available after delete/free.

Author: MagicAndre1981
Subject: Need help with Ntoskrnl thread causing high CPU
Posted: 13 April 2016 at 4:55am

WPA needs a file called PDB (https://msdn.microsoft.com/en-us/library/yd4f8bd1%28v=vs.100%29.aspx). And tools not coded with Microsoft tools (Visual Studio) don't create such a file during build/compile

↧

Process Explorer : Hang in Processs properties window

April 13, 2016, 2:30 am

≫ Next: Development : Access database stops opening

≪ Previous: Troubleshooting : Need help with Ntoskrnl thread causing high CPU

Author: bartoli
Subject: Hang in Processs properties window
Posted: 13 April 2016 at 9:30am

Reproduced in 16.11 and 16.12 x64

If i close the process properties dialog when i was in the Threads tab, any future opening of a process properties by a double click in the process list will hang on incomplete dispaly of the threads tab and Process explorer won't respond anymore. Opening a different process, reopening process explorer, or restarting will change nothing.

Reopening the process propertires by the menu Process > Properties will restore the display of the first tab, so the problem disappears

My path to dbghelp.dll seems valid, if it has anything to do with it

EDIT : as in the last post of the bugs thread, closing Teamviewer makes the hang disappear

Edited by bartoli - 4 hours 27 minutes ago at 10:05am

↧

Development : Access database stops opening

April 13, 2016, 4:46 am

≫ Next: Process Explorer : Hidden windows

≪ Previous: Process Explorer : Hang in Processs properties window

Author: danielsson
Subject: Access database stops opening
Posted: 13 April 2016 at 11:46am

When you open the MDB, hold down the Shift key until the MDB is completelyopen ... and see if you still get the message. This will bypass anystartup code that may be running.

Then, open the VBA editor and from the menuDebug>>Compile and see if any errors turn up.

Please have a lookat this forum topic:

http://itknowledgeexchange.techtarget.com/itanswers/mdb-file-does-not-open-if-someone-already-opened-it/

Hope this information will be helpful for you.

↧

Process Explorer : Hidden windows

April 13, 2016, 7:40 am

≫ Next: Development : Access database stops opening

≪ Previous: Development : Access database stops opening

Author: hot2
Subject: Hidden windows
Posted: 13 April 2016 at 2:40pm

I was using EditPad Lite 7, and the window somehow disappeared.
I ran Process Explorer v16.12, which told me "No visible windows found for this process"
I saw no option to find Editpad's window from process explorer!

I discovered, with nirsoft's WinLister, that the window had somehow got hidden. WinLister was able to unhide the window.

Can you modify Process Explorer to locate a window that suddenly disappears i.e. that gets hidden.

Edited by hot2 - Yesterday at 2:44pm

↧

Development : Access database stops opening

April 13, 2016, 10:26 am

≫ Next: Development : Access database stops opening

≪ Previous: Process Explorer : Hidden windows

Author: CharlesCarter
Subject: Access database stops opening
Posted: 13 April 2016 at 5:26pm

Sorry... Stillget the same error message.

↧

Development : Access database stops opening

April 13, 2016, 10:44 am

≫ Next: Development : Access database stops opening

≪ Previous: Development : Access database stops opening

Author: danielsson
Subject: Access database stops opening
Posted: 13 April 2016 at 5:44pm

Try creating an newMDB, then import in all the objects from the problem mdb. If that doesn't work,Well, I would at this point suggest a repair service like Access RecoveryToolbox http://www.oemailrecovery.com/access_repair.html

↧

Development : Access database stops opening

April 13, 2016, 10:46 am

≫ Next: Process Explorer : ** Process Explorer Bugs **

≪ Previous: Development : Access database stops opening

Author: danielsson
Subject: Access database stops opening
Posted: 13 April 2016 at 5:46pm

Try also to restore the file using this online service. I found it inGoogle. https://onlinefilerepair.com/en/access-repair-online.html

↧

Process Explorer : Process Explorer Bugs

April 13, 2016, 3:34 pm

≫ Next: Process Explorer : ** Process Explorer Bugs **

≪ Previous: Development : Access database stops opening

Author: Hobart
Subject: ** Process Explorer Bugs **
Posted: 13 April 2016 at 10:34pm

In GPU Usage, if Engine 0 is un-checked in the "GPU Engine History" , the "GPU Usage" total always comes out flat-lined at 0.

...this means if you want to only check the "Engines" that are in use, you'll only ever see it max at 50% since you must include "Engine 0" in the totals.

It'd be nice to get a more technical explanation of the underlying set-up ... and perhaps nice if Process Explorer could, by default, ignore the "Engines" that never seem to be in use.

Process Explorer: v16.1

Windows: 10.0.10586 64-bit

Video card: AMD Radeon HD 7700 Series 16.150.2211.0

Radeon Software Version: 16.3.2

↧

Process Explorer : Process Explorer Bugs

April 14, 2016, 11:58 am

≫ Next: PsTools : PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?

≪ Previous: Process Explorer : ** Process Explorer Bugs **

Author: KindDragon
Subject: ** Process Explorer Bugs **
Posted: 14 April 2016 at 6:58pm

Process Explorer v16.12 crash after installing Win10 Linux Subsystem

Edited by KindDragon - 20 hours 18 minutes ago at 6:58pm

↧

PsTools : PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?

April 14, 2016, 1:12 pm

≫ Next: PsTools : PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?

≪ Previous: Process Explorer : ** Process Explorer Bugs **

Author: harry.schreier
Subject: PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?
Posted: 14 April 2016 at 8:12pm

I'm working with a software vendor who has said they have minimum requirements for bandwidth and latency. I'm using PSPing to gather the statistics which look like this:

Minimum = 315.28 KB/s, Maximum = 683.05 KB/s, Average = 503.27 KB/s
Minimum = 276.15 KB/s, Maximum = 710.12 KB/s, Average = 699.5 KB/s
Minimum = 314.96 KB/s, Maximum = 631.24 KB/s, Average = 494.62 KB/s
Minimum = 446.61 KB/s, Maximum = 641.53 KB/s, Average = 446.61 KB/s
Minimum = 315.22 KB/s, Maximum = 630.53 KB/s, Average = 488.48 KB/s

I'm wondering if someone can clarify for me if the output I'm seeing for the bandwidth test is either Kilobits/Second or Kilobytes/Second.

Thanks in advance

↧

PsTools : PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?

April 14, 2016, 3:06 pm

≫ Next: PsTools : PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?

≪ Previous: PsTools : PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?

Author: LMiller7
Subject: PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?
Posted: 14 April 2016 at 10:06pm

If the vendor is using standard terminology KB/s refers to bytes per second while Kb/s would refer to bits per second.

↧

PsTools : PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?

April 14, 2016, 4:17 pm

≫ Next: PsTools : telnet with psexec problem -PLS HELP -

≪ Previous: PsTools : PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?

Author: harry.schreier
Subject: PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?
Posted: 14 April 2016 at 11:17pm

So based on your response, KB is not the same as Kb. PSPing provided KB in the output, are you 100% certain that the output from PSPing is following the standard terminology and provides KiloBytes per second ?

I'm only concerned with PSPing at this time.

↧

PsTools : telnet with psexec problem -PLS HELP -

April 15, 2016, 1:06 am

≫ Next: Autoruns : Startup folder not listed

≪ Previous: PsTools : PSPing, Kilo Bits/Sec or Kilo Bytes/Sec ?

Author: IJustKnowStuff
Subject: telnet with psexec problem -PLS HELP -
Posted: 15 April 2016 at 8:06am

I actually found a way to natively use telnet via PSEXEC to see if it's successfuly or not.....sort of ;)

Here's the scripts I used. (You could roll this into one easily, it was just easier for me to have is separate)

=======

serverlist.txt

=======

List of all your servers you wish to check. Servername on each line.

======

TelnetTest.bat

======

del c:\temp\tick.txt 2> nul

telnet [server] [port]

echo %computername% > c:\temp\tick.txt

:ENDOFSCRIPT

======

PushScript.bat

======

FOR /F %%A in (serverlist.txt) do (

robocopy C:\Temp \\%%A\C$\TEMP TelnetTest.bat /r:1 /w:1

psexec -d -e \\%%A c:\temp\TelnetTest.bat)

:ENDOFSCRIPT

=======

TestScript.bat

=======

FOR /F %%A in (serverlist.txt) do if exist \\%%A\c$\temp\tick.txt (echo %%A >> C:\Temp\Failed.txt) ELSE (echo %%A >> C:\Temp\Success.txt)

:ENDOFSCRIPT

Now I had these under C:\temp on my domain controller that had access to all the servers.

Simply run PushScript.bat and it will copy the TelnetTest.bat file to the servers and run it.

Once that script has finished, simply run TestScript.bat and it will check for the "tick.txt" file which is create once the telnet proccess has finished.

Now this works based off the fact that if the TELNET command is successful, a connection will stay open, so the tick.txt file isn't created until the TELNET timeout occurs. This is 1 hour by default.

If you wait 1 hour after running the PushScript.bat, then the tick files will have been created and you will get a false result. (Results may vary if your TELNET timeout is short.)

Also the "-d" switch in the psexec process is important as that seems to be what allows the telnet process to run without failing.

Again, this could easily be rolled into one script if you wanted to.

I'd also recommend doing a clean up a few hours later once all the TELNET processes have timed out.

EDIT: Also, I know there's a lot of efficiency improvement that could be done, I just wanted to show a broken down version of how it works. One point I'd like to add is the telnet command and creation of the tick.txt file can be one line if you simply use a '&' or '&&' between the commands:

e.g. telnet [server] [port] & echo %computername% > c:\temp\tick.txt

Edited by IJustKnowStuff - 6 hours 43 minutes ago at 8:33am

↧

Autoruns : Startup folder not listed

April 15, 2016, 12:25 pm

≫ Next: Disk2vhd : cant p2v server 2003 SP2

≪ Previous: PsTools : telnet with psexec problem -PLS HELP -

Author: joe0506
Subject: Startup folder not listed
Posted: 15 April 2016 at 7:25pm

On a new Win7 x64 Pro machine, autoruns lists the
c:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ folder, but not the
c:\Users\MyUserName\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\ folder.

I suspect the problem is caused by my renaming the user profile folder and user account folder name, following the detailed instructions I found online. It seems likely that something was missed, though the renamed folder does otherwise work normally.

Any ideas on how I can get autoruns to see it?

↧

Disk2vhd : cant p2v server 2003 SP2

April 15, 2016, 1:06 pm

≫ Next: Miscellaneous Utilities : contig.exe 1.54 doesn't work with /accepteula flag

≪ Previous: Autoruns : Startup folder not listed

Author: dirkdigs
Subject: cant p2v server 2003 SP2
Posted: 15 April 2016 at 8:06pm

hello i need to p2v a 2003 server with sp2. i thought disk2vhd could p2v server 2003?

has something changed? i tried running it and it says p2v completed successfully but it completes in about 10 seconds. every time and no file gets created .

Help

↧

Miscellaneous Utilities : contig.exe 1.54 doesn't work with /accepteula flag

April 16, 2016, 10:00 am

≫ Next: Miscellaneous Utilities : contig.exe 1.54 doesn't work with /accepteula flag

≪ Previous: Disk2vhd : cant p2v server 2003 SP2

Author: grantcurell
Subject: contig.exe 1.54 doesn't work with /accepteula flag
Posted: 16 April 2016 at 5:00pm

Sorry about the epic necro, but it would appear the same is true of accesschk. I've tried both /accepteula and -accepteula and it appears to ignore both of them. Either way, the license agreement pops up. Is there a fix for that or did I miss the mark?

↧

Miscellaneous Utilities : contig.exe 1.54 doesn't work with /accepteula flag

April 16, 2016, 12:08 pm

≫ Next: Process Explorer : Process Explore crash in Windows 10 build 14316

≪ Previous: Miscellaneous Utilities : contig.exe 1.54 doesn't work with /accepteula flag

Author: pinscomputer
Subject: contig.exe 1.54 doesn't work with /accepteula flag
Posted: 16 April 2016 at 7:08pm

@grantcurell,

you could try a similar change to the registry key:

HKEY_CURRENT_USER\Software\Sysinternals\AccessChk

add a REG_DWORD named EulaAccepted and set the value to 1

↧

Process Explorer : Process Explore crash in Windows 10 build 14316

April 16, 2016, 5:32 pm

≫ Next: Process Explorer : Process Explore crash in Windows 10 build 14316

≪ Previous: Miscellaneous Utilities : contig.exe 1.54 doesn't work with /accepteula flag

Author: swinster
Subject: Process Explore crash in Windows 10 build 14316
Posted: 17 April 2016 at 12:32am

Problem is, it is set to replace Task Manager, so as soon as task manager is attempted to be open, the app crashes.

Some info from the Application log:

Log Name: Application

Source: Windows Error Reporting

Date: 17/04/2016 00:23:15

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: HPElitebook

Description:

Fault bucket 120407748216, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: procexp64.exe

P2: 16.12.0.0

P3: 56b3cb63

P4: procexp64.exe

P5: 16.12.0.0

P6: 56b3cb63

P7: c0000005

P8: 000000000001ca58

P9:

P10:

Attached files:

C:\ProgramData\Microsoft\Windows\WER\Temp\WER1498.tmp.WERInternalMetadata.xml

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_procexp64.exe_eaaa19abce75032adc495e98218f3ba4de0214_192a9979_39ce3c93

Analysis symbol:

Rechecking for solution: 0

Report ID: fc4deeaa-b6c8-4a00-9bf9-cacfa2c4bb3d

Report Status: 0

Hashed bucket: a4f036cda2333861575d1e39c5bde38b

Event Xml:

<Channel>Application</Channel>

<Computer>HPElitebook</Computer>

</System>

<Data>APPCRASH</Data>

<Data>Not available</Data>

<Data>procexp64.exe</Data>

<Data>procexp64.exe</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

C:\ProgramData\Microsoft\Windows\WER\Temp\WER1498.tmp.WERInternalMetadata.xml</Data>

<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_procexp64.exe_eaaa19abce75032adc495e98218f3ba4de0214_192a9979_39ce3c93</Data>

<Data>

</Data>

<Data>fc4deeaa-b6c8-4a00-9bf9-cacfa2c4bb3d</Data>

</EventData>

</Event>

Log Name: Application

Source: Application Error

Date: 17/04/2016 00:23:05

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: HPElitebook

Description:

Faulting application name: procexp64.exe, version: 16.12.0.0, time stamp: 0x56b3cb63

Faulting module name: procexp64.exe, version: 16.12.0.0, time stamp: 0x56b3cb63

Exception code: 0xc0000005

Fault offset: 0x000000000001ca58

Faulting process ID: 0x37b4

Faulting application start time: 0x01d19836ea9ed34f

Faulting application path: C:\Users\swin\AppData\Local\Temp\procexp64.exe

Faulting module path: C:\Users\swin\AppData\Local\Temp\procexp64.exe

Report ID: fc4deeaa-b6c8-4a00-9bf9-cacfa2c4bb3d

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Channel>Application</Channel>

<Computer>HPElitebook</Computer>

</System>

<Data>procexp64.exe</Data>

<Data>procexp64.exe</Data>

<Data>C:\Users\swin\AppData\Local\Temp\procexp64.exe</Data>

<Data>fc4deeaa-b6c8-4a00-9bf9-cacfa2c4bb3d</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

↧

Process Explorer : Process Explore crash in Windows 10 build 14316

April 16, 2016, 5:40 pm

≫ Next: Process Explorer : Hang in Processs properties window

≪ Previous: Process Explorer : Process Explore crash in Windows 10 build 14316

Author: swinster
Subject: Process Explore crash in Windows 10 build 14316
Posted: 17 April 2016 at 12:40am

OK, restored Task Manager, thanks to http://forum.sysinternals.com/how-do-i-see-my-task-manager-again_topic2606_post141317.html#141317

↧

Process Explorer : Hang in Processs properties window

April 17, 2016, 12:11 pm

≫ Next: Miscellaneous Utilities : contig.exe 1.54 doesn't work with /accepteula flag

≪ Previous: Process Explorer : Process Explore crash in Windows 10 build 14316

Author: kookaburra
Subject: Hang in Processs properties window
Posted: 17 April 2016 at 7:11pm

I confirm that Teamviewer (version 11.0.56083) and Process Explorer (v16.12) when run together on Windows-7 (x64), result in the described hang of Process Explorer. This started to happen a while ago allready, but untill now I hadn't bothered. It happens on two different systems, a desktop and a laptop. Hope somebody can fix this...

↧