See that huge spike in the second graph. That is your disk usage. The blue graph inside of that is the read/write queue note how it grows when you hit your peak.
EDIT: Also, your peak is rather low. 100Kbps is a low peak, mine is currently at 1Mb/s, albeit it dynamically changes but you see a rise in the queue as well which means read/writes are being delayed. Kind of odd.
EDIT: Also, your peak is rather low. 100Kbps is a low peak, mine is currently at 1Mb/s, albeit it dynamically changes but you see a rise in the queue as well which means read/writes are being delayed. Kind of odd.
Last edited:
OK, now what do I do with that insight? 9 year old, somewhat slow, short bus, right?
Why is the CPU at 100% Because its in the middle of a screen grab? Might be worth finding out if something's being a CPU hog. Got Flash enabled in a browser by any chance?
<edit> Oh, I see the 100% is just the graph scale in Resource Monitor, not an instantaneous figure. I'll go back to sleep....
<edit> Oh, I see the 100% is just the graph scale in Resource Monitor, not an instantaneous figure. I'll go back to sleep....
Last edited:
My first thought, run the system file checker I mentioned in a previous post:
9YO Instructions:
Click the Orb
In the search box type in CMD (DO NOT hit enter)
Right click on cmd.exe (may be called Command Prompt) and select Run As Administrator
Click Yes/OK to the UAC prompt
at the command prompt type: sfc /scannow
Hit enter.
Let it run.
Let me know if it says it found any errors and fixed them or found errors and couldn't fix them.
9YO Instructions:
Click the Orb
In the search box type in CMD (DO NOT hit enter)
Right click on cmd.exe (may be called Command Prompt) and select Run As Administrator
Click Yes/OK to the UAC prompt
at the command prompt type: sfc /scannow
Hit enter.
Let it run.
Let me know if it says it found any errors and fixed them or found errors and couldn't fix them.
Also, you mention it is NDIS 6.0, have you not installed SP1 on your vista machine? If not this means your system isn't near being up-to-date and there is a slight chance it could be infected. Vista SP1 mentions NDIS 6.1 as being the highest supported version. If you have it may be time to upgrade to NDIS 6.1 from NDIS 6.0.
Heh, atleast microsoft in honest.
I just ran that LatencyMon program and my pagefaults issue is worse than yours. ~300ms but the pagefaults are all by the Antivirus program, with its realtime protection. Likely it calls things that are opened for scanning after the system has closed the page out. So it is nothing to worry about. What does LatencyMon say your program that waited the longest was? If it is antivirus related I wouldn't worry to much about it. Now if it is something else, then IT may be causing issues as well.
My DPC faults are around 180uS though. Yours are much higher.
My DPC faults are around 180uS though. Yours are much higher.
OK, I hammered at it enough to get it open. It's 37 megs, 11000+ pages! Here's the last couple, to give you a feel for what I got.
f-ms", Destination = [l:214{107}]"\SystemRoot\WinSxS\FileMaps\program_files_x86_common_files_microsoft_shared_ink_1.0_5645a6a00c765d40.cdf-ms"
POQ 106 ends.
2011-01-17 22:02:56, Info CSI 000002a0 [SR] Verify complete
2011-01-17 22:02:56, Info CSI 000002a1 [SR] Verifying 100 (0x0000000000000064) components
2011-01-17 22:02:56, Info CSI 000002a2 [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:05, Info CSI 000002a3 Repair results created:
POQ 107 starts:
POQ 107 ends.
2011-01-17 22:03:05, Info CSI 000002a4 [SR] Verify complete
2011-01-17 22:03:05, Info CSI 000002a5 [SR] Verifying 100 (0x0000000000000064) components
2011-01-17 22:03:05, Info CSI 000002a6 [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:14, Info CSI 000002a7 Repair results created:
POQ 108 starts:
POQ 108 ends.
2011-01-17 22:03:14, Info CSI 000002a8 [SR] Verify complete
2011-01-17 22:03:14, Info CSI 000002a9 [SR] Verifying 100 (0x0000000000000064) components
2011-01-17 22:03:14, Info CSI 000002aa [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:24, Info CSI 000002ab Repair results created:
POQ 109 starts:
POQ 109 ends.
2011-01-17 22:03:24, Info CSI 000002ac [SR] Verify complete
2011-01-17 22:03:25, Info CSI 000002ad [SR] Verifying 16 (0x0000000000000010) components
2011-01-17 22:03:25, Info CSI 000002ae [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:26, Info CSI 000002af Repair results created:
POQ 110 starts:
POQ 110 ends.
2011-01-17 22:03:26, Info CSI 000002b0 [SR] Verify complete
2011-01-17 22:03:26, Info CSI 000002b1 [SR] Repairing 1 components
2011-01-17 22:03:26, Info CSI 000002b2 [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:26, Info CSI 000002b3 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2011-01-17 22:03:26, Info CSI 000002b4 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-17 22:03:26, Info CSI 000002b5 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2011-01-17 22:03:26, Info CSI 000002b6 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-17 22:03:26, Info CSI 000002b7 Hashes for file member \??\C:\Windows\System32\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2011-01-17 22:03:26, Info CSI 000002b8 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2011-01-17 22:03:26, Info CSI 000002b9 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
2011-01-17 22:03:26, Info CSI 000002ba Repair results created:
POQ 111 starts:
POQ 111 ends.
2011-01-17 22:03:26, Info CSI 000002bb [SR] Repair complete
2011-01-17 22:03:26, Info CSI 000002bc [SR] Committing transaction
2011-01-17 22:03:26, Info CSI 000002bd Creating NT transaction (seq 1), objectname [6]"(null)"
2011-01-17 22:03:26, Info CSI 000002be Created NT transaction (seq 1) result 0x00000000, handle @0x65c
2011-01-17 22:03:26, Info CSI 000002bf@2011/1/18:04:03:26.484 CSI perf trace:
CSIPERF:TXCOMMIT;4
2011-01-17 22:03:26, Info CSI 000002c0 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2011-01-17 22:08:32, Info CBS Scavenge: Package store indicates there is no component to scavenge, skipping.
f-ms", Destination = [l:214{107}]"\SystemRoot\WinSxS\FileMaps\program_files_x86_common_files_microsoft_shared_ink_1.0_5645a6a00c765d40.cdf-ms"
POQ 106 ends.
2011-01-17 22:02:56, Info CSI 000002a0 [SR] Verify complete
2011-01-17 22:02:56, Info CSI 000002a1 [SR] Verifying 100 (0x0000000000000064) components
2011-01-17 22:02:56, Info CSI 000002a2 [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:05, Info CSI 000002a3 Repair results created:
POQ 107 starts:
POQ 107 ends.
2011-01-17 22:03:05, Info CSI 000002a4 [SR] Verify complete
2011-01-17 22:03:05, Info CSI 000002a5 [SR] Verifying 100 (0x0000000000000064) components
2011-01-17 22:03:05, Info CSI 000002a6 [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:14, Info CSI 000002a7 Repair results created:
POQ 108 starts:
POQ 108 ends.
2011-01-17 22:03:14, Info CSI 000002a8 [SR] Verify complete
2011-01-17 22:03:14, Info CSI 000002a9 [SR] Verifying 100 (0x0000000000000064) components
2011-01-17 22:03:14, Info CSI 000002aa [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:24, Info CSI 000002ab Repair results created:
POQ 109 starts:
POQ 109 ends.
2011-01-17 22:03:24, Info CSI 000002ac [SR] Verify complete
2011-01-17 22:03:25, Info CSI 000002ad [SR] Verifying 16 (0x0000000000000010) components
2011-01-17 22:03:25, Info CSI 000002ae [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:26, Info CSI 000002af Repair results created:
POQ 110 starts:
POQ 110 ends.
2011-01-17 22:03:26, Info CSI 000002b0 [SR] Verify complete
2011-01-17 22:03:26, Info CSI 000002b1 [SR] Repairing 1 components
2011-01-17 22:03:26, Info CSI 000002b2 [SR] Beginning Verify and Repair transaction
2011-01-17 22:03:26, Info CSI 000002b3 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2011-01-17 22:03:26, Info CSI 000002b4 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-17 22:03:26, Info CSI 000002b5 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2011-01-17 22:03:26, Info CSI 000002b6 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-01-17 22:03:26, Info CSI 000002b7 Hashes for file member \??\C:\Windows\System32\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2011-01-17 22:03:26, Info CSI 000002b8 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6001.18000_none_2e976e2e5fa70844\tcpmon.ini do not match actual file [l:20{10}]"tcpmon.ini" :
Found: {l:32 b:as3OOcx5px0XiJa7f7s9BVvlW/FFlKR4NMU/T+UP/Kg=} Expected: {l:32 b:ENtKeUct91LKlHclgfWTvnCdCOHHwDe+SYrPzZTTezU=}
2011-01-17 22:03:26, Info CSI 000002b9 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
2011-01-17 22:03:26, Info CSI 000002ba Repair results created:
POQ 111 starts:
POQ 111 ends.
2011-01-17 22:03:26, Info CSI 000002bb [SR] Repair complete
2011-01-17 22:03:26, Info CSI 000002bc [SR] Committing transaction
2011-01-17 22:03:26, Info CSI 000002bd Creating NT transaction (seq 1), objectname [6]"(null)"
2011-01-17 22:03:26, Info CSI 000002be Created NT transaction (seq 1) result 0x00000000, handle @0x65c
2011-01-17 22:03:26, Info CSI 000002bf@2011/1/18:04:03:26.484 CSI perf trace:
CSIPERF:TXCOMMIT;4
2011-01-17 22:03:26, Info CSI 000002c0 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2011-01-17 22:08:32, Info CBS Scavenge: Package store indicates there is no component to scavenge, skipping.
Stepped away for a bit to spend time with the family...wow..I missed out on some info here.
Yeah, corrupt files are no bueno. That thought ran through my head when SY said it had gotten worse over time.
My previous workstation (I built myself) must have had a small hard drive problem because once a year some Windows program files would get corrupted and it would start acting squirrely on me and would just decline from there.
After rebuilding my workstation and junking the 'good' drive, all my problems faded away.
Yeah, corrupt files are no bueno. That thought ran through my head when SY said it had gotten worse over time.
My previous workstation (I built myself) must have had a small hard drive problem because once a year some Windows program files would get corrupted and it would start acting squirrely on me and would just decline from there.
After rebuilding my workstation and junking the 'good' drive, all my problems faded away.
hmm I am seeing some significant corruption. It appears the storage is also corrupted. This is caused by either a) a malware infection or b) a dying hard drive.
If you are 100% certain that your computer in not infected. We can do the following, if you aren't sure there are some things we can do to check it out. What antivirus do you run? What malware scanner do you use?
If you are 100% sure you are not infected:
Do you have your vista disk? If so, we may try to do a Startup repair which may be able to repair the corrupted files. Though if the HD is dying there is little you can do.
Step-by-step from a great site on how to do a Startup repair:
How to automatically repair Windows Vista using Startup Repair
If you are 100% certain that your computer in not infected. We can do the following, if you aren't sure there are some things we can do to check it out. What antivirus do you run? What malware scanner do you use?
If you are 100% sure you are not infected:
Do you have your vista disk? If so, we may try to do a Startup repair which may be able to repair the corrupted files. Though if the HD is dying there is little you can do.
Step-by-step from a great site on how to do a Startup repair:
How to automatically repair Windows Vista using Startup Repair
Well it depends. If you want to just reinstall Vista from scratch (not an entirely bad option but loads of work); to do the startup repair unfortunately it sucks.
EDIT: OK, download the zip file from here. This is a western digital program that scans the HD. It works just fine on my toshiba drive so it should work on ANY drive. Run the program, it will show drives in the computer. Right click on the C: drive, select run diagnostics. Select Quick Test. If it shows no issues run a full scan. If it STILL shows no issues time to look at a malware infection.
In that case, download Malwarebytes from here. Install it, run a quick scan (no need for a full scan). See if it finds anything.
If you DO find harddrive errors, that drive is dying and needs to be replaced.
EDIT: OK, download the zip file from here. This is a western digital program that scans the HD. It works just fine on my toshiba drive so it should work on ANY drive. Run the program, it will show drives in the computer. Right click on the C: drive, select run diagnostics. Select Quick Test. If it shows no issues run a full scan. If it STILL shows no issues time to look at a malware infection.
In that case, download Malwarebytes from here. Install it, run a quick scan (no need for a full scan). See if it finds anything.
If you DO find harddrive errors, that drive is dying and needs to be replaced.
Last edited:
- Status
- This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.