New
#31
Oh, FFS, it looks like they stuffed the WPT tools into the SDK download at some point during the last week or so
Now it's necessary to install the WPT manually. Can't stop progress I guess:
Installation
Oh, FFS, it looks like they stuffed the WPT tools into the SDK download at some point during the last week or so
Now it's necessary to install the WPT manually. Can't stop progress I guess:
Installation
hmm will I have to download the full ISO or something, I used the web installer and I can't find the xperf msi installers
is there some place where i can get the xperf msi online?
i even downloaded the ISO and cannot find this xperf iso file :S
man they must've made a lot of changes in one week!
the installation method that you told me to refer is to confusing
it says the MSI files are located at SDKROOT\<path-goes-here>\xperf.
I have no clue where that is lol
Sorry mate. It looks like they rolled the WPT into that 4GB ISO image of the SDK somewhere, and that was done literally within the last few days.
I can't imagine it's a good idea to force everybody who'd like to use Xperf to download 3.98GB of additional gunk they almost certainly don't need, so eventually it'll probably once again become available as a separate download.
I'll write up a different way to collect similar info in a few hours... a bit tied up right now.
Sure thing man,
Thanks a lot for your help btw :)
Also since I've run the scandisk my computer hasn't frozen yet ...lets just hope it lasts however to save us both the trouble lol
so here's my latest discovery,
like I said yesterday my computer was working fine without any freezes. Today it was working fine as well no freezes at all. So thinking the error was gone, I uninstalled the SDK and shortly after the freeze happened not once but twice! The first time the event logger logged nothing but the second time this came up:
The driver detected a controller error on \Device\Ide\IdePort1.
Source: atapi
Event ID: 11
I'm not sure if initially the SDK had fixed the problem or if it was pure coincidence. Because when I said the problem had mysteriously dissapeared, the SDK was installed. I'm reinstalling the SDK to test out my theory. What can be done regarding that error?
The SDK is just a whole heap of files, most of them text. "Uninstalling" the SDK does little except to delete the files and remove some start menu links. Unfortunately, I'm 99.99% certain that the presence of the SDK has nothing to do with the symptom. It's just coincidence.
Those controller errors are hardware. If a substantial percentage of those "freeze" periods are accompanied by the event in question, I'm afraid the most likely explanation is broken hardware.
Can you search back through the event log for other instances of the error? (Right-click the log, "filter", select attributes that match the event.)
I'll check the exact number when I'm home from work, but I remember seeing quite a few occurrences of that error. However the freeze only happened once with that error being logged. I saw about 4-5 occurrences in a row of that same error but didn't experience any freezing during those times. I'll check to make sure however but I do remember seeing more than one :S
its been a full day almost since I reinstalled the SDK and so far I have had no freezes occur...no atapi errors have come up in the events log since then either!
this is a wierd issue :S
ok so H2SO4,
it happened again...ya it was stupid for me to assume that the SDK somehow magically fixed it, but man I was so happy there for a second until it happened again
The freeze just occurred right now but once again no error was logged....any way to debug this sort of error without xperf or anywhere where i can get xperf?
I have a feeling that when the hard drive reaches a certain point in the data, it freezes then...maybe part of the disc is messed, but then again you are the expert :)