sudden change in computer speed and function

I recently purchased a used HP Probook to use for pro tools mp9 recording software. it exceeded the system requirements by a long ways, and worked flawlessly until last week. I started getting an error message (DAE error 9073-disc to slow or fragmented-can't get audio from the drives fast enough) in the avid/protools forums, the primary fix mentioned was to defrag the hard drive, so I tried it and still got this error. another fix was to uninstall and reinstall pro tools, which I also tried, to no avail. additionally, after the re-install, my boot up time went from 45 seconds to over 6 minutes, and when I do a restart of the computer, I end up at a black screen with a blinking cursor in the upper left had corner. I can get back to operation of the computer by turning it off, and then back on with the power switch, and I have full internet capability, but protools never would function correctly. another thing I noticed was that preferences I had set before the uninstall, were present after the reinstall. I had thought that it could have been a malware issue, but the malware forum here tells me my machine is clean. after the reading I have done, all I can come up with is a registry problem, and I have piriform ccleaner, but I am reluctant to try the registry cleaner in ccleaner without some guidance, and perhaps you have other ideas. I currently have the protools software(and hardware drivers) uninstalled, sinced reinstalling them again at this juncture seemed pointless. since this probook has an i5 quadcore a 7,200rpm hard drive, and 8 gigs of ram I don't understand how it could be a resource issue. any help would be greatly appreciated by this starving musician

 

Hi platteriversand

First you need to tell us which operating system you are using - Windows 7 ?, etc.

Please do not try to fix this by manually manipulating the registry.
The registry cleaner in CCleaner is regarded as the safest to use, however IMHO that should not be the first remedy.

I did not see that you have run a full chkdsk procedure.
I think you should do that.

Also, it seems that the uninstall process did not do a good cleanup.
There are remedies for that, such as Revo Uninstaller, but someone else would better advise you about that.

 

my probook is running windows 7 professional 64 bit. I have never used a registry cleaner, so, as I said, I won't do anything without being directed to. I will run the chkdsk now. will you want to see the results? something I forgot to mention was I saw a thread about bootlogs, and when I viewed mine, there were 3 critical, and at least a dozen serious errors listed, however, I have no idea what the info in the report represented.

 

chkdsk reported no errors in the file system.
should I attempt to use the uninstaller posted in the first response?

 

Could you post the bootlogs for us?

 

I'm pretty sure that I found the boot log using the event viewer, but I don't know how to find this file using the browse function in the add link to reply, and it seems that I am unable to copy the text to my clipboard to paste it in a reply

 

I can get as far in the file system as computer>local disc C>Windows>System32 and then I'm lost

 

The boot log should be in C:\Windows\ntbtlog.txt

or

%WinDir%\ntbtlog.txt

 

there must be one more folder between windows and the log file. the folders start at addins, and continue through winsfx, followed by 40 or 50 individual files, but I don't see ntblog.txt, and using the search function shows no results for that file. and likewise for %WinDir%ntblog.txt

 

System

- Provider

[ Name] Microsoft-Windows-Diagnostics-Performance
[ Guid] {CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}

EventID 102

Version 1

Level 3

Task 4002

Opcode 33

Keywords 0x8000000000010000

- TimeCreated

[ SystemTime] 2012-08-23T00:17:56.045209600Z

EventRecordID 597

- Correlation

[ ActivityID] {00000100-0000-0002-E7C7-06ACC380CD01}

- Execution

[ ProcessID] 1712
[ ThreadID] 1312

Channel Microsoft-Windows-Diagnostics-Performance/Operational

Computer riverrat

- Security

[ UserID] S-1-5-19

I can't copy all the data with the errors, but this is the details text that caused me to think the file would be in system32. there are tons of critical, error, and warning entries labeled as boot performance, etc.



- EventData

StartTime 2012-08-23T00:10:15.671600300Z
NameLength 7
Name Serial
FriendlyNameLength 21
FriendlyName Serial Device Driver
VersionLength 38
Version 6.1.7600.16385 (win7_rtm.090713-1255)
TotalTime 500
DegradationTime 415
PathLength 39
Path C:\Windows\system32\DRIVERS\serial.sys
ProductNameLength 37

 

not sure what happened on that last post, this is the tyext I was trying to copy

EventData

BootTsVersion 2
BootStartTime 2012-04-18T20:53:33.609200200Z
BootEndTime 2012-04-18T20:54:21.298483900Z
SystemBootInstance 2
UserBootInstance 1
BootTime 76666
MainPathBootTime 66766
BootKernelInitTime 20
BootDriverInitTime 3579
BootDevicesInitTime 3178
BootPrefetchInitTime 30437
BootPrefetchBytes 472576000
BootAutoChkTime 0
BootSmssInitTime 9456
BootCriticalServicesInitTime 3231
BootUserProfileProcessingTime 1292
BootMachineProfileProcessingTime 867
BootExplorerInitTime 37525
BootNumStartupApps 6
BootPostBootTime 9900
BootIsRebootAfterInstall false
BootRootCauseStepImprovementBits 0
BootRootCauseGradualImprovementBits 0
BootRootCauseStepDegradationBits 16448
BootRootCauseGradualDegradationBits 16448
BootIsDegradation false
BootIsStepDegradation false
BootIsGradualDegradation false
BootImprovementDelta 0
BootDegradationDelta 0
BootIsRootCauseIdentified true
OSLoaderDuration 3760
BootPNPInitStartTimeMS 20
BootPNPInitDuration 3350
OtherKernelInitDuration 2556
SystemPNPInitStartTimeMS 5886
SystemPNPInitDuration 3407
SessionInitStartTimeMS 9314
Session0InitDuration 5732
Session1InitDuration 1228
SessionInitOtherDuration 2495
WinLogonStartTimeMS 18771
OtherLogonInitActivityDuration 8310
UserLogonWaitDuration 1423

 

ok, sorry about my last two befuddled replies. I did some reading, and found out that I had to enable bootlogging in order to have a boot log to find. I'm just a dumb musician, but I can learn if I put my mind to it, and here is my bootlog.

 

another thing I thought I should mention is the "pro tools optimizations" I followed the optimization instructions before installing pro tools mp9 and the avid usb interface, and when I started getting the 9073 error, I went through the recommended procedures as well. it's p[ossible that I made an error in the process, since my computer skills are minimal at best. but last night, after I posted the bootlog link, my cat jumped up on the keyboard, and managed to bring up start>control panel>add/delete programs, and the windows help index, and my problems started the morning I went to see what my roomie rocorded, and found the program closed, and my desktop icons scrambled, so as crazt as it seems to me, could my cat have started something that I made worse by following the pro tools troubleshooting procedures in this link. http://avid.force.com/pkb/articles/en_US/troubleshooting/en349411?popup=true