CPU logger

Forums › Microsoft Windows › CPU logger

1 | 2 | 3

17134 posts

Uber Geek

Lifetime subscriber

#762654 14-Feb-2013 21:29

That was way too quick. Chkdsk c: /R would take over an hour (and much much longer) on an average size drive.

Is c: the correct drive letter for your main drive?

StevieT

702 posts

Ultimate Geek

#762655 14-Feb-2013 21:31

gzt: That was way too quick. Chkdsk c: /R would take over an hour (and much much longer) on an average size drive.

Is c: the correct drive letter for your main drive?

Correct. Yes, I was a bit puzzled by the fact it produced a result so fast. The hard drive is 180GB in size....

I am currently running the memory diagnostic test.

gzt

17134 posts

Uber Geek

Lifetime subscriber

#762672 14-Feb-2013 22:00

Maybe you left off the 'c:' ? Easy to do.

Also recovery environment sometimes can assign letters for drives you would normally be unaware of. Maybe do a dir c: in the command prompt and see if the files listed are what you expect on your c: drive. If not, dir the next letter up and so on.

Btw, if you press F1 in the memdiag it will give you the option of running the extended test. That takes at least twice as long as the standard test. You can start memdiag from a command prompt with "mdsched".

StevieT

702 posts

Ultimate Geek

#766605 20-Feb-2013 17:56

I apologise for taking so long to get back.

The computer is back up and running;

I allowed the computer to take ages to load upon logging in (over night, not sure how long it took). I then ran scan disk in the morning, which then made the laptop reboot and repair C:/. The issue was resolved.

I even did the chkdsk again in shutdown /r /o mode, yet it completed as far as it did previously. Definitely the "c:" was included in the command.

Then came the issue of installing Norton 360 which involved two technicians online to do (because the installer would stop working). It was eventually installed after another registry clean, searching for the word 'Norton', in safe mode.

I am, however, interested in a logger other than Windows built in one, to ensure that current disk activity is recorded, so I know what processes etc. are using what (RAM/disk activity), how much, and when.

Hammerer

2476 posts

Uber Geek

Lifetime subscriber

#766638 20-Feb-2013 19:04

Microsoft Sysinternals are useful utilities to investigate Windows issues. You can download them for free. I don't have time to go into any detail but there is for example, a more advanced task manager:
http://technet.microsoft.com/en-us/sysinternals

StevieT

702 posts

Ultimate Geek

#768284 23-Feb-2013 20:31

Having experienced the disk activity issue since it last resolved, I found that System (NT Kernel & System) was using the most CPU/disk activity at times.

Having reviewed this link - http://helpdeskgeek.com/windows-7/fix-nt-kernel-system-process-cpu-usage-in-windows-7/ - mention is the use of KrView. However, that is no longer apart of Windows 8, plus I am unsure if I did install it how to run it via Command Prompt. Would anyone be able to run me through the commands to achieve the result of finding out how many hits are occuring in Kernel? (Performance Monitor seems to be the latest software for this task, but I am unsure how to find out what is hitting the Kernel the most)

I suspect the System task is consumed primarily by my Wireless Adapter Card, and was wanting to double check that.

As previously mentioned in another thread, installing the latest version for my adapter card resulted in WLAN auto-config issues. I then went back to an older driver and, as Microsoft advised me, sooner or later I would run into trouble considering it was intended for Windows 7.

Last night I reinstalled the driver version for Windows 8, and suspect that it may be corrupt and/or incompatible with Windows 8 - also what Microsoft said to me when I had it installed and was experiencing WLAN auto-config issues. Samsung, however, won't help me as this laptop originally came with Windows 7 (despite being told I would continue to receive driver support under Windows 8).

Oriphix

523 posts

Ultimate Geek

#768313 23-Feb-2013 21:36

Have you tried the below?

1. Log into safe mode
2. Check event logs for errors
3. Go to C:\windows\minidump use a program called WhoCrashed and analyze crash logs.
4. You can also try system restore
5. If all fails backup your data by removing the HDD and and then re-format.
6. If the problem is still there after format then hardware related.

Just my steps. Hope it helps

Also what is your system specs?

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

gzt

17134 posts

Uber Geek

Lifetime subscriber

#768314 23-Feb-2013 21:38

The easy next step is use a wlan stick with windows 8 drivers and disable the onboard. Not a great solution but a useful troubleshooting step.

StevieT

702 posts

Ultimate Geek

#768390 24-Feb-2013 08:21

Thanks for the suggestions. At the moment I am battling another issue with Norton, which is probably a result of the high disk activity and my guess it cannot function and has crashed and become corrupted.

I do notice getting inpage_kernal_errors a lot; for example, today I booted and clicked to log in. Because of the high disk activity I went away, and came back and found it had restarted. Upon being about to log in this time round, Microsoft informed me to send an error report.

I have tried disabling Virtual Memory, and re-enabling in light of the possibility the hard drive page file was corrupt.

When I return from shopping I will check out the log in Safe Mode.

(Also done a scan with Norton Power Eraser, which detected no threats)

StevieT

702 posts

Ultimate Geek

#768423 24-Feb-2013 10:30

Having turned off my computer, and returned my trip out I tried logging in. The error is KERNAL_DATA_INPAGE_ERROR. Hopefully once it restarts I can configure msconfig to boot into safe mode, and I can check error logs.

gzt

17134 posts

Uber Geek

Lifetime subscriber

#768431 24-Feb-2013 10:57

The error code from the stop is often useful in diagnosis. It will look similar to this: 0xC000016A

StevieT

702 posts

Ultimate Geek

#768439 24-Feb-2013 11:18

I have disabled my wireless adapter and laptop is connected via Ethernet.

Direct from WhoCrashed:

computer name: HONEY
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Pentium(R) CPU P6200 @ 2.13GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6229127168 total
VM: 2147352576, free: 1927516160

Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 23/02/2013 9:28:47 p.m. GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022413-64343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800AA00E80, 0x7ED9A030)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 23/02/2013 9:28:47 p.m. GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800AA00E80, 0x7ED9A030)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 23/02/2013 6:47:42 p.m. GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022413-54015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A040)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800542E010, 0xCCF0E0A)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

StevieT

702 posts

Ultimate Geek

#768440 24-Feb-2013 11:19

gzt: The error code from the stop is often useful in diagnosis. It will look similar to this: 0xC000016A

How do I find that out? When the screen appears, it only show KERNAL_INPAGE etc error. No 0x... codes.

Hammerer

2476 posts

Uber Geek

Lifetime subscriber

#768461 24-Feb-2013 12:29

StevieT:
gzt: The error code from the stop is often useful in diagnosis. It will look similar to this: 0xC000016A

How do I find that out? When the screen appears, it only show KERNAL_INPAGE etc error. No 0x... codes.

The error code should appear in the list of parameters. It's probably the second of the four, ie "0x0", as the last two are addresses:
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800542E010, 0xCCF0E0A)
[Edit: Confirmed that it is the second parameter http://answers.microsoft.com/en-us/windows/forum/windows_7-system/kerneldatainpageerror-0x0000007a/f79f0046-4c83-44f7-b98d-9598e7442009 which links to http://www.faultwire.com/solutions-fatal_error/KERNEL-DATA-INPAGE-ERROR-0x0000007A-*1137.html?order=date]

If it is 0x0 then Windows can't determine the cause of the problem because it is most likely not a disk problem like the one gzt used as an example:

0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.
0xC000000E, or STATUS_NO_SUCH_DEVICE, indicates a hardware failure or an incorrect drive configuration. Check your cables and check the drive with the diagnostic utility available from your drive manufacturer. If you are using older PATA (IDE) drives, this status code can indicate an incorrect master/subordinate drive configuration.

If it's not a disk or memory problem then that suggests that you have a problem with misbehaving software such as a driver or malware.

So what have you done to troubleshoot that issue.
As gzt suggested you could use a different wlan device?
Have you tried cable connect and/or disabling the wireless driver?
I don't think that it is a memory problem but it would normally be something that I would also check. Windows 8 in-memory structures will be somewhat different to Windows 7 and might just be hitting a bad block.

Hammerer

2476 posts

Uber Geek

Lifetime subscriber

#768465 24-Feb-2013 12:40

PS I also meant to give you another option for addressing your original issue but this is unlikely to help if it is a problem driver:

StevieT: I notice at times my computer being non responsive, with the light indicating activity on. A few minutes later whatever was happening is completed.

Is there a program that logs CPU / RAM memory / hard drive usage so I can see what services/processes occur and when, and whether I can pinpoint what exactly makes my computer non responsive for minutes at a time.

Process Lasso is free software that can help with non responsive Windows as it is designed to restrain processes to keep Windows responsive.

The free version has an evaluation period where you can trial such features as memory and CPU limits. I use the pro version for a PC that I use for testing software. It helps me to identify unruly software without having to suffer the consequences:
http://bitsum.com/howfree.php

1 | 2 | 3