Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: Xas1953NC on January 27, 2015, 02:11:46 pm
-
Hello Shane, I had made notes on the various sequences I have used in starting up Vista. These include stopwatched stages. I also have repair log results, cbs.log results, chkdsk.log results and performance event logs of what happens in starting and closing down Vista. Rather than display them here and therefore taking up screen space would you rather I zipped them under one folder for you to look at and then you could then decide what to show if need be? Thanks.
-
You can zip them up and attach them, there is a 4 mb size limit per file, so if they are big you might want to zip them up into multiple files.
What exactly is going on that you want me to check on?
Shane
-
Hello Shane, you previously said it could be a dying hdd and I thought if I sent you the data from the software side you may be able to pin down the cause. The thing is that once the computer startup is successful further restarts and power down and power up again actions do so without a hitch unless the computer is turned off and an amount of time has passed. Then the problem starts over again. Leaving the computer on for 48 hours or so has no detrimental affect during the run. Last night I downloaded your test file which you developed regarding another user's cbs.log issues. I ran it and all packages came up with no corruptions. I'll start to compile the data I have and send it zipped. Thanks.
-
Have you used a tool to look at the smart status of the hard drive and see what it reports?
Shane
-
You mean a profile tool such as Speccy?
-
If it pulls the smart status then yes, otherwise if the drive is a seagate or western digital, they have tools for free that can read the smart status of the drive.
Shane
-
Have just pulled down latest version of Speccy. It shows C Drive as status good and temp 35c as good. I have an attached self powered usb drive which show temp as bad at 59c. On one of the tests I removed all ext drives and the printer prior to the first initial startup of the day and the computer exhibited the same problems as when all peripherals were connected.
-
One of the repair logs states
Root cause found: Unspecified changes to system configuration might have caused the problem.
-
Yeah but the smart data off of a drive will show what its internal stats say, including spin up times, bad sectors and any other problems.
What hard drive do you have?
Shane
-
Do not have a program to show spinup times. These are the C, D,S Drives in tower. Data from Speccy profiler.
Storage
Hard drives
WDC WD6400AAKS-22A7B0 ATA Device
Manufacturer Western Digital
Form Factor GB/3.5-inch
Business Unit/Brand Desktop/WD Caviar
Heads 16
Cylinders 77,825
Tracks 19,845,375
Sectors 1,250,258,625
SATA type SATA-II 3.0Gb/s
Device type Fixed
ATA Standard ATA8-ACS
Serial Number WD-WCASY0719613
Firmware Version Number 01.03B01
LBA Size 48-bit LBA
Power On Count 1890 times
Power On Time 850.0 days
Features S.M.A.R.T., AAM, NCQ
Max. Transfer Mode SATA II 3.0Gb/s
Used Transfer Mode SATA II 3.0Gb/s
Interface SATA
Capacity 596 GB
Real size 640,135,028,736 bytes
RAID Type None
S.M.A.R.T
Status Good
Temperature 40 °C
Temperature Range OK (less than 50 °C)
S.M.A.R.T attributes
Partition 0
Partition ID Disk #0, Partition #0
File System NTFS
Volume Serial Number F4DE1251
Size 14.7 GB
Used Space 8.13 GB (55%)
Free Space 6.52 GB (45%)
Partition 1
Partition ID Disk #0, Partition #1
Disk Letter C:
File System NTFS
Volume Serial Number 5245E47C
Size 232 GB
Used Space 130 GB (56%)
Free Space 102 GB (44%)
Partition 2
Partition ID Disk #0, Partition #2
Disk Letter S:
File System NTFS
Volume Serial Number A2DB42E6
Size 348 GB
Used Space 304 GB (87%)
Free Space 44 GB (13%)
WDC WD6400AAKS-22A7B0 ATA Device
Manufacturer Western Digital
Form Factor GB/3.5-inch
Business Unit/Brand Desktop/WD Caviar
Heads 16
Cylinders 77,825
Tracks 19,845,375
Sectors 1,250,258,625
SATA type SATA-II 3.0Gb/s
Device type Fixed
ATA Standard ATA8-ACS
Serial Number WD-WCASY1594132
Firmware Version Number 01.03B01
LBA Size 48-bit LBA
Power On Count 1892 times
Power On Time 852.5 days
Features S.M.A.R.T., AAM, NCQ
Max. Transfer Mode SATA II 3.0Gb/s
Used Transfer Mode SATA II 3.0Gb/s
Interface SATA
Capacity 596 GB
Real size 640,135,028,736 bytes
RAID Type None
S.M.A.R.T
Status Good
Temperature 41 °C
Temperature Range OK (less than 50 °C)
S.M.A.R.T attributes
Partition 0
Partition ID Disk #1, Partition #0
Disk Letter D:
File System NTFS
Volume Serial Number 40ACF239
Size 596 GB
Used Space 66 GB (11%)
Free Space 529 GB (89%)
-
As an aside, the external usb hdd, drive J Graphic drive, is one that shows red temp of 60c. Sometimes this drive will not be recognized or it will take 2 minutes or so for it to be recognised. Seagate Dashboard considers hdd as ok. In the past I have set the spin down time to 15 min when not being accessed but what happened is that even if I were not accessing the drive it's led would fluctuate and I would be unable to carry out particular actions as I was greeted with "not corresponding" messages. Things returned to normal when the fluctuating stopped. I assumed the fluctuating was due to the drive attempting to spin up and failing to do so right away as sometimes I had to wait about 10 minutes before it stabilised. I then set the spin down time to "Never" and that resolved the fluctuating. The downside could be the 60c red temp. The drive is only half full so has not intruded into the 20% area. I have now disconnected it and will connect to my wife's computer as she has room on her external usb hdd to copy across from the J drive. Quite a few years ago I problems starting up my previous XP computer and found it was a faulty mouse. As I said regarding the current problem, removing all peripherals and then starting up did not resolve the issue.
-
Post what western digitals tool shows
http://download.wdc.com/windlg/WinDlg_v1_28.zip?v=7990
Reason why I want to see the data is you said that the drive acts fine once it has been on for a bit and stays fine. It isnt until it has been off for a while that it seems to be very slow before getting back to speed. So I am curious if there is a hardware problem with the components inside, where when they are cold they are not spinning the platters are easily as they should. But once the components heat up then it gets to full speed.
Looking at the actual smart data might let me see if any numbers line up with something like that happening.
Shane
-
Thanks for the prog. I installed it and it showed a list of WD hdds. I did a quick test on the 2x640 gb ones but do not know if any files are made to send to you. I tried to use a scroll window screen grab prog but it was not capable of doing so.
-
Sorry Shane, I forgot to mention that they both had green ticks against them in the drive view list before and after the test
-
This is what HDDScan3.3 gives for mine - would this be better for the info you want Shane ?
http://hddscan.com/
These all had green lights next to them and to copy & paste I just right clicked in a blank area to the right of the grid - clicked on Select all to highlight then pasted into the reply box - so no attachments to chew on with.
HDDScan S.M.A.R.T. Report
Model: TOSHIBA MK6465GSXN
Firmware: GH101M
Serial: 91RXT06ST
LBA: 1250263728
Report By: HDDScan for Windows version 3.3
Report Date: 28/01/2015 23:20:18
Num Attribute Name Value Worst Raw(hex) Threshold
001 Raw Read Error Rate 100 100 0000000000-0000 050
002 Throughput performance 100 100 0000000000-0000 050
003 Spin Up Time 100 100 0000000000-084A 001
004 Start/Stop Count 100 100 0000000000-14DC 000
005 Reallocation Sector Count 100 100 0000000000-0000 050
007 Seek Error Rate 100 100 0000000000-0000 050
008 Seek time Perfomance 100 100 0000000000-0000 050
009 Power-On Hours Count 076 076 0000000000-25A8 000
010 Spin Retry Count 204 100 0000000000-0000 030
012 Device Power Cycle Count 100 100 0000000000-14D5 000
191 G-sense Rate/Servo tracking 100 100 0000000000-0046 000
192 Emergency Retract Count 100 100 0000000000-004F 000
193 Load/unload Cycle Count 082 082 0000000002-D71C 000
194 HDA Temperature 100 100 30 C 000
194 HDA Temperature Maximum 100 100 53 C 000
194 HDA Temperature Minimum 100 100 11 C 000
196 Reallocation Event Count 100 100 0000000000-0000 000
197 Current Pending Errors Count 100 100 0000000000-0000 000
198 Uncorrectable Errors Count 100 100 0000000000-0000 000
199 UltraDMA CRC Errors 200 200 0000000000-0000 000
220 Disk Shift 100 100 0000000000-0036 000
222 Loaded Hours 082 082 0000000000-1D46 000
223 Load Retry Count 100 100 0000000000-0000 000
224 Load Friction 100 100 0000000000-0000 000
226 Load-in Time 100 100 0000000000-0146 000
240 Heads Flying Hours 100 100 0000000000-0000 001
-
Hello Boggin, I downloaded the prog and unzipped and clicked on HDDScan exe but nothing happened.
-
I already have it in my Downloads folder and after opening the folder, just double click on the HDDScan - Application - but will dump what I have and then download it again to refresh my memory.
I'm back.
Right - clicked on the Download button and selected Save
Closed the web site and view Downloads box then went to my Downloads folder - clicked on the .zip - Open - clicked on HDDScan 3.3 - Extract.
Clicked on HDDScan File Folder - Open - then double clicked on HDDScan for Type Application (7th one down the list) then follow the prompts.
Click on the black S.M.A.R.T. button to produce its analysis similar to mine.
-
That is what I did but no joy. I did notice Avast icon rotate a few times but no resulting reason.
-
Try it in Safe Mode with Networking - Avast may not like it.
When I downloaded that program that Shane had linked, my Norton 360 didn't like that and popped up a window advising me to remove it but also with the choice to run it anyway - similar to what Windows Smart Screen Filter does sometimes.
-
Ok, Boggin, thanks for your help. I'm signing off now as have to be up early tomorrow. Thanks
-
Hello Boggin, the prog worked ok after a reboot. That was last night. I turned on the computer this morning and it went into start normally or Repair. I chose repair and restore. It booted up ok then but was was deleted was the exe of HDDScan and the exe of the prog Shane put a link to, WDdiag. They were both in the Download folder. I moved them to my external HDD Master Storage folder and unzipped them again so both are working. Whereas last night I had to reboot to get your one working, today it ran without a reboot. I have also managed to screen grab the results of both so will prepare them for Shane to have a look. Thanks
-
Although I have tried various computations in endeavoring to get the computer to start I have only shown here the most recent attempt and the results. 27-01-2015: Computer finally started at 11.45am. Computer running ok. 29-01-2015: powered down at 12.50am taking 2m.40s to do so. Powered up again without a hitch at 12.54am. This took 4m.50s. Final powered down at 2.11am.
29-01-2015: 1st. startup of the day at 8.54 am. After 9m.30s computer closed itself down without a sign of power on led or drive led. The only thing that does light up are the leds behind the Acer Aspire tower nameplate. At 9.05am I turned computer on. After 5m.30s power led lights up and Acer screen appeared on monitor and then screen goes black (this is the normal prelude to booting up to show the progress bar but on the first startup of the day it does not happen)and the Acer screen appeared again followed by the choice to start a repair or start normally. I chose Repair followed by Restore. Computer then boots up successfully. The computer startup procedure does not always follow the same pattern. This is the first time for quite a while that I have let the computer run from start without my interaction to turn it off if nothing happens for 6 min, turn on again, turn off again and so on with stopwatched increments. Sometimes it can take from first startup plus my interactions to finally bootup something in like 40 or so minutes so this latest effort took took less time! I found a website that has a collection of sounds made by hdds on their way out but none appertained to my problem. I wonder if there is a failure of sorts that energising capacitors within the circuitry do not hold a charge initially to kickstart the computer up and that turning off and on by the power button builds up a charge where it will bootup. Here is the resulting srtTrail.log showing the Repair operation. Also enclosed are the hdd scans that you asked for, Shane. Thanks.
Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: 1/29/2015 12:56:11 AM (GMT)
Number of repair attempts: 1
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1
Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms
Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 94 ms
Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms
Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 94 ms
Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 2059 ms
Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 172 ms
Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms
Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms
Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 1248 ms
Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 3135 ms
Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code = 0x0
Time taken = 1576 ms
Test Performed:
---------------------------
Name: Access control test
Result: Completed successfully. Error code = 0x0
Time taken = 20093 ms
Test Performed:
---------------------------
Name: File system test (chkdsk)
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: Software installation log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: Fallback diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Root cause found:
---------------------------
Unspecified changes to system configuration might have caused the problem.
Repair action: System Restore
Result: Completed successfully. Error code = 0x0
Time taken = 72057 ms
---------------------------
---------------------------
-
Thanks for the screen shots.
Ok so if I read your post correctly, there is times where it is almost 6 mins before you even see the Windows loading screen correct? Then you said it reboots and asks to do a repair, that means it blue screened on you and is set to auto reboot. You need to disable the auto reboot to see what the blue screen says, you can also use the WhoCrashed program to have it check and see what is most likly the cause of the blue screen.
http://www.resplendence.com/download/whocrashedSetup.exe
Let me know what the whocrashed report says.
I do have a computer in my house that after it has been off for a while I go to turn it on and it is a black screen and windows never boots, I hit the reset key on the tower (I dont turn it off) and it starts up like normal, Windows asks me if I want to repair I say no.
For this system I traced it to the video card. It is my old video card and it has done this at random times ever since I bought it 2 years ago. They tried to blame the power supply but it wasnt it. It is just the card it self needed a few more sec to fully power itself up before the motherboard goes on, so when i do the reset everything is fine, I can play any game and I have no crashes. This only happens on a fresh turn on of the tower.
So it is possible that it is hardware problem for you, but it may not be the hard drive for sure. Lets see what is causing those blue screens and go from there. :wink:
Shane
-
Hello Shane, no, it not a 6 min issue but there are variables that occur even if I stick to a pattern of turning on and off the computer endeavoring to get it to start up. For example:
29-01-2015. 1st. startup of the day at 8.45 am. After 9m.30s computer turned itself off. I turned it on again approx. 4min later.
After 5m.30s Power led came on and Acer logo appeared on monitor. 30s later choice of Repair or Start Normally screen appeared.
I chose Repair followed by Restore. Result was booted up ok.
30-01-2015. Computer soft shutdown at 1.37am which took 3m to do so. No problems during this long ontime.
31-01-2015. 1st. startup of the day at 1.13.pm. After 11m.30s computer turned itself off. I turned it on again approx. 2min later.
After 30.m nothing happening so I turned off computer and turned it back on again after 2 min.
30s later power led and Acer logo appeared on monitor.
2m.5s later "Preparing Desktop" appeared followed by booting up ok.
This time there was no choice screen to Repair or Start Normally.
Computer does not have a reset button so I have to use the power off button.
I ran the Whocrashed prog which said there were no minidumps. I also have Nirsoft's BlueScreenView prog and it has never found any problems during the period of time these startup problems have appeared.
Although I waited 30m on this last attempt the computer may have possibly booted up in less time If I had turned it off sooner as it has done so in previous sessions where I have turned it off if nothing happens after 6 min. and then turned it on again and so on.
There have been previous sessions where I have ignored Repair and chosen Start Normally. Sometimes the bootup has been succesful and other times the bootup has resulted in the System Network icon in the taskbar having a cross on it, this in tandem with only 5 of the 9 icons that are normally shown. Because of this I have had to reboot again which results in a successful bootup taking approx. 10min.
I tend to clear Event Perfomance logs prior to finally shutting down computer and check what logs have been made on the 1st. startup of the day at the next session. Thanks
-
It's obviously having problems loading some drivers.
It could be worth going to your computer support site and downloading the Chipset drivers (Video drivers if AMD), but also check for a BIOS update.
You could create a Boot Log and copy & paste that.
You can do this by going Start - type msconfig and press enter.
Under the Boot tab check the radio button for Boot log and if you want to see the boot process, also check the one for OS boot information - Apply - OK - Restart.
With OS boot info checked, you should be able to see where it's sticking.
You can view the report in Windows\ntbtlog
Double click on ntbtlog and it will open in Notepad.
You will need to go back into msconfig to uncheck those items for it to boot "normally".
-
Thanks Boggin but I will wait to hear from Shane in case he may have another lead to what is going on but I will keep your advice in mind.
I don't know if the following is any help in resolving the problem:
I soft shutdown the computer at approx. 8.56pm tonight which took 2m.20s. I started it up again at approx. 9.03pm which took 6 min.
It booted up without any problems. I don't know if the Performance Event logs will be of any help but here they are after the shutdown and starting up at 8.56pm and 9.03pm respectively.
Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 31/01/2015 09:05:52 PM
Event ID: 101
Task Category: Boot Performance Monitoring
Level: Warning
Keywords: Event Log
User: LOCAL SERVICE
Computer: home-PC
Description:
This application took longer than usual to start up, resulting in a performance degradation in the system startup process:
File Name : explorer.exe
Friendly Name : Windows Explorer
Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Total Time : 9231ms
Degradation Time : 6212ms
Incident Time (UTC) : 31/01/2015 09:01:02 PM
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{cfc18ec0-96b1-4eba-961b-622caee05b0a}" />
<EventID>101</EventID>
<Version>1</Version>
<Level>3</Level>
<Task>4002</Task>
<Opcode>33</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2015-01-31T21:05:52.889Z" />
<EventRecordID>18</EventRecordID>
<Correlation ActivityID="{00000000-86C8-0000-B3BD-A305993DD001}" />
<Execution ProcessID="2728" ThreadID="3932" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
<Computer>home-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="StartTime">2015-01-31T21:01:02.765Z</Data>
<Data Name="NameLength">13</Data>
<Data Name="Name">explorer.exe</Data>
<Data Name="FriendlyNameLength">17</Data>
<Data Name="FriendlyName">Windows Explorer</Data>
<Data Name="VersionLength">39</Data>
<Data Name="Version">6.0.6000.16386 (vista_rtm.061101-2205)</Data>
<Data Name="TotalTime">9231</Data>
<Data Name="DegradationTime">6212</Data>
<Data Name="PathLength">24</Data>
<Data Name="Path">C:\Windows\explorer.exe</Data>
<Data Name="ProductNameLength">37</Data>
<Data Name="ProductName">Microsoft® Windows® Operating System</Data>
<Data Name="CompanyNameLength">22</Data>
<Data Name="CompanyName">Microsoft Corporation</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 31/01/2015 09:05:52 PM
Event ID: 100
Task Category: Boot Performance Monitoring
Level: Error
Keywords: Event Log
User: LOCAL SERVICE
Computer: home-PC
Description:
Windows has started up:
Boot Duration : 90866ms
IsDegradation : false
Incident Time (UTC) : 31/01/2015 09:01:02 PM
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{cfc18ec0-96b1-4eba-961b-622caee05b0a}" />
<EventID>100</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>4002</Task>
<Opcode>34</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2015-01-31T21:05:52.889Z" />
<EventRecordID>17</EventRecordID>
<Correlation ActivityID="{00000000-86C8-0000-B3BD-A305993DD001}" />
<Execution ProcessID="2728" ThreadID="3932" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
<Computer>home-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="BootTsVersion">2</Data>
<Data Name="BootStartTime">2015-01-31T21:01:02.765Z</Data>
<Data Name="BootEndTime">2015-01-31T21:05:35.215Z</Data>
<Data Name="SystemBootInstance">2431</Data>
<Data Name="UserBootInstance">2405</Data>
<Data Name="BootTime">90866</Data>
<Data Name="MainPathBootTime">72366</Data>
<Data Name="BootKernelInitTime">24</Data>
<Data Name="BootDriverInitTime">5160</Data>
<Data Name="BootDevicesInitTime">9525</Data>
<Data Name="BootPrefetchInitTime">33081</Data>
<Data Name="BootPrefetchBytes">502403072</Data>
<Data Name="BootAutoChkTime">0</Data>
<Data Name="BootSmssInitTime">20596</Data>
<Data Name="BootCriticalServicesInitTime">3120</Data>
<Data Name="BootUserProfileProcessingTime">1203</Data>
<Data Name="BootMachineProfileProcessingTime">178</Data>
<Data Name="BootExplorerInitTime">27698</Data>
<Data Name="BootNumStartupApps">18</Data>
<Data Name="BootPostBootTime">18500</Data>
<Data Name="BootIsRebootAfterInstall">false</Data>
<Data Name="BootRootCauseStepImprovementBits">129</Data>
<Data Name="BootRootCauseGradualImprovementBits">0</Data>
<Data Name="BootRootCauseStepDegradationBits">8388608</Data>
<Data Name="BootRootCauseGradualDegradationBits">0</Data>
<Data Name="BootIsDegradation">false</Data>
<Data Name="BootIsStepDegradation">false</Data>
<Data Name="BootIsGradualDegradation">false</Data>
<Data Name="BootImprovementDelta">133923</Data>
<Data Name="BootDegradationDelta">0</Data>
<Data Name="BootIsRootCauseIdentified">true</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 31/01/2015 09:05:38 PM
Event ID: 203
Task Category: Shutdown Performance Monitoring
Level: Warning
Keywords: Event Log
User: LOCAL SERVICE
Computer: home-PC
Description:
This service caused a delay in the system shutdown process:
File Name : DPS
Friendly Name : WDI Diagnostic Policy Service
Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Total Time : 6984ms
Degradation Time : 3754ms
Incident Time (UTC) : 30/01/2015 11:34:59 PM
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{cfc18ec0-96b1-4eba-961b-622caee05b0a}" />
<EventID>203</EventID>
<Version>1</Version>
<Level>3</Level>
<Task>4007</Task>
<Opcode>41</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2015-01-31T21:05:38.975Z" />
<EventRecordID>16</EventRecordID>
<Correlation ActivityID="{00000000-86C8-0000-B2BD-A305993DD001}" />
<Execution ProcessID="2728" ThreadID="3880" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
<Computer>home-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="StartTime">2015-01-30T23:34:59.135Z</Data>
<Data Name="NameLength">4</Data>
<Data Name="Name">DPS</Data>
<Data Name="FriendlyNameLength">30</Data>
<Data Name="FriendlyName">WDI Diagnostic Policy Service</Data>
<Data Name="VersionLength">42</Data>
<Data Name="Version">6.0.6001.18000 (longhorn_rtm.080118-1840)</Data>
<Data Name="TotalTime">6984</Data>
<Data Name="DegradationTime">3754</Data>
<Data Name="PathLength">28</Data>
<Data Name="Path">C:\Windows\system32\dps.dll</Data>
<Data Name="ProductNameLength">37</Data>
<Data Name="ProductName">Microsoft® Windows® Operating System</Data>
<Data Name="CompanyNameLength">22</Data>
<Data Name="CompanyName">Microsoft Corporation</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 31/01/2015 09:05:38 PM
Event ID: 201
Task Category: Shutdown Performance Monitoring
Level: Warning
Keywords: Event Log
User: LOCAL SERVICE
Computer: home-PC
Description:
This application caused a delay in the system shutdown process:
File Name : spoolsv.exe
Friendly Name : Spooler SubSystem App
Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Total Time : 232ms
Degradation Time : 120ms
Incident Time (UTC) : 30/01/2015 11:34:59 PM
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{cfc18ec0-96b1-4eba-961b-622caee05b0a}" />
<EventID>201</EventID>
<Version>1</Version>
<Level>3</Level>
<Task>4007</Task>
<Opcode>41</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2015-01-31T21:05:38.975Z" />
<EventRecordID>15</EventRecordID>
<Correlation ActivityID="{00000000-86C8-0000-B2BD-A305993DD001}" />
<Execution ProcessID="2728" ThreadID="3880" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
<Computer>home-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="StartTime">2015-01-30T23:34:59.135Z</Data>
<Data Name="NameLength">12</Data>
<Data Name="Name">spoolsv.exe</Data>
<Data Name="FriendlyNameLength">22</Data>
<Data Name="FriendlyName">Spooler SubSystem App</Data>
<Data Name="VersionLength">39</Data>
<Data Name="Version">6.0.6000.16386 (vista_rtm.061101-2205)</Data>
<Data Name="TotalTime">232</Data>
<Data Name="DegradationTime">120</Data>
<Data Name="PathLength">32</Data>
<Data Name="Path">C:\Windows\System32\spoolsv.exe</Data>
<Data Name="ProductNameLength">37</Data>
<Data Name="ProductName">Microsoft® Windows® Operating System</Data>
<Data Name="CompanyNameLength">22</Data>
<Data Name="CompanyName">Microsoft Corporation</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 31/01/2015 09:05:38 PM
Event ID: 201
Task Category: Shutdown Performance Monitoring
Level: Warning
Keywords: Event Log
User: LOCAL SERVICE
Computer: home-PC
Description:
This application caused a delay in the system shutdown process:
File Name : Mini_Monitor.exe
Friendly Name : CleanMem Mini Monitor
Version : 2.5.0.0
Total Time : 2654ms
Degradation Time : 2207ms
Incident Time (UTC) : 30/01/2015 11:34:59 PM
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{cfc18ec0-96b1-4eba-961b-622caee05b0a}" />
<EventID>201</EventID>
<Version>1</Version>
<Level>3</Level>
<Task>4007</Task>
<Opcode>41</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2015-01-31T21:05:38.975Z" />
<EventRecordID>14</EventRecordID>
<Correlation ActivityID="{00000000-86C8-0000-B2BD-A305993DD001}" />
<Execution ProcessID="2728" ThreadID="3880" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
<Computer>home-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="StartTime">2015-01-30T23:34:59.135Z</Data>
<Data Name="NameLength">17</Data>
<Data Name="Name">Mini_Monitor.exe</Data>
<Data Name="FriendlyNameLength">22</Data>
<Data Name="FriendlyName">CleanMem Mini Monitor</Data>
<Data Name="VersionLength">8</Data>
<Data Name="Version">2.5.0.0</Data>
<Data Name="TotalTime">2654</Data>
<Data Name="DegradationTime">2207</Data>
<Data Name="PathLength">43</Data>
<Data Name="Path">C:\Program Files\CleanMem\Mini_Monitor.exe</Data>
<Data Name="ProductNameLength">22</Data>
<Data Name="ProductName">CleanMem Mini Monitor</Data>
<Data Name="CompanyNameLength">14</Data>
<Data Name="CompanyName">PcWinTech.com</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 31/01/2015 09:05:38 PM
Event ID: 200
Task Category: Shutdown Performance Monitoring
Level: Critical
Keywords: Event Log
User: LOCAL SERVICE
Computer: home-PC
Description:
Windows has shutdown:
Shutdown Duration : 76957666ms
IsDegradation : false
Incident Time (UTC) : 30/01/2015 11:34:59 PM
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{cfc18ec0-96b1-4eba-961b-622caee05b0a}" />
<EventID>200</EventID>
<Version>1</Version>
<Level>1</Level>
<Task>4007</Task>
<Opcode>40</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2015-01-31T21:05:38.975Z" />
<EventRecordID>13</EventRecordID>
<Correlation ActivityID="{00000000-86C8-0000-B2BD-A305993DD001}" />
<Execution ProcessID="2728" ThreadID="3880" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
<Computer>home-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ShutdownTsVersion">1</Data>
<Data Name="ShutdownStartTime">2015-01-30T23:34:59.135Z</Data>
<Data Name="ShutdownEndTime">2015-01-31T20:57:36.802Z</Data>
<Data Name="ShutdownTime">76957666</Data>
<Data Name="ShutdownUserSessionTime">21292</Data>
<Data Name="ShutdownUserPolicyTime">339</Data>
<Data Name="ShutdownUserProfilesTime">151</Data>
<Data Name="ShutdownSystemSessionsTime">10677</Data>
<Data Name="ShutdownPreShutdownNotificationsTime">6524</Data>
<Data Name="ShutdownServicesTime">1997</Data>
<Data Name="ShutdownKernelTime">76925696</Data>
<Data Name="ShutdownRootCauseStepImprovementBits">0</Data>
<Data Name="ShutdownRootCauseGradualImprovementBits">0</Data>
<Data Name="ShutdownRootCauseStepDegradationBits">0</Data>
<Data Name="ShutdownRootCauseGradualDegradationBits">0</Data>
<Data Name="ShutdownIsDegradation">false</Data>
<Data Name="ShutdownTimeChange">0</Data>
</EventData>
</Event>
-
I have just run Nirsoft's Crash Report. Here it is.
-
I'll leave those for Shane to peruse.
The Chipset drivers links the OS to the motherboard and the BIOS tells Windows what to load, so if the BIOS is playing up then either resetting it or looking for an update could resolve the loading process - but create and post the Boot log.
-
Just worked on a computer today, needed a new power supply, put it in and new hard drive. I install Windows 7 and I have odd problems at random different areas. Odd things crashing and even the windows setup failing the first time but finishing the next.
When this happens on a install I know it is hardware related. I tested the memory and sure enough I had a bad stick of memory. That bad memory caused the system to reboot on its own, no blue screen, no dump file.
So since you have the same, a reboot with now crash file, it makes me want to check the rest of the hard ware, Have you done a memory test yet?
If not then please do and if you need a memory tester you can use the one from MS. :wink:
https://technet.microsoft.com/en-us/magazine/2008.09.utilityspotlight.aspx
Shane
-
Hello Shane, I could not grasp how to setup the https://technet.microsoft.com/en-us/magazine/2008.09.utilityspotlight.aspx prog to run so used the Vista built in memory tester instead. I did not press F1 to setup any parameters but just run it as is. During the part 1 and part 2 scans it said nothing found and on the auto restart there was no indication of the result. I Googled for some info and went to Event Viewer and Diagnostics result but the page was blank.
-
This what Speccy comes up with on the Ram specification. I have 2 slots each with 2 gb of matched memory sticks. Vista shows total of 4 gb of memory on the spec page.
RAM
Memory slots
Total memory slots 4
Used memory slots 2
Free memory slots 2
Memory
Type DDR2
Size 4096 MBytes
Channels # Dual
DRAM Frequency 533.1 MHz
CAS# Latency (CL) 7 clocks
RAS# to CAS# Delay (tRCD) 7 clocks
RAS# Precharge (tRP) 7 clocks
Cycle Time (tRAS) 24 clocks
Bank Cycle Time (tRC) 32 clocks
Command Rate (CR) 2T
Physical Memory
Memory Usage 25 %
Total Physical 3.25 GB
Available Physical 2.41 GB
Total Virtual 6.73 GB
Available Virtual 4.98 GB
SPD
Number Of SPD Modules 2
Slot #1
Slot #2
-
Some methods to run the memory test and where the results would be http://www.bleepingcomputer.com/tutorials/using-vista-windows-memory-diagnostics-tool/
-
Yes, you need to run an actual memory test.
Try as Boggin suggested and let me know :wink:
Shane
-
Hello Shane, I do not have a Vista CD/DVD and I did use the method of clicking on the Start button, typing memory, clicking on the resulting memory icon and selecting the recommended check on a restart. During the checking prior to the computer completing booting up nothing showed on the monitor of any problems. I could not finding a resulting log file to tell me the result of the memory test.
-
It should have given the status in the memory check window as it was checking.
Go back to my post in how to create and post a Boot log and post that.
-
Hello Bogginn, here is the bootlog file. There are loads of drivers not load but I wonder if they become active when called for. I have been making C Drive backups onto an external drive buit then stopped making them temprarily whilst trying to resolve the startup problems. I do have 5 self powered external usb hdds connected to the Vista and this setup has been working fine for at least 2 years and my previous computer, os XP, had a similar setup and that ran for 10 years. I have reverted back to normal by unticking the boot boxes and selected apply and ok. Here is the ntbtlog. Thanks a lot.
-
The SASKUTIL and SASDIFSV.sys are for your SuperAntiSpyware and are probably on demand items.
The PCOUFFIN Device for 32 bit systems is something to do with VSO devices - whatever they are but it certainly has had problems loading the Nvidia graphics and Realtek Audio drivers.
Go into Device Manager and check for any yellow alerts for the Display Adapter and Sound, video and game controllers.
If they look okay then I would repeat my suggestion to go to your computer support site and download the Chipset drivers and look for a BIOS update.
If Chipset drivers aren't listed, then download the Nvidia drivers or you could go into Device Manager, expand Display adapters - right click on the Nvidia and select Update Driver Software and see if Windows can find a suitable update, but Graphics drivers - especially Nvidia, are best downloaded from the computer support site in the case of OEM machines, as they tend to be OEM modified and those direct from Nvidia can cause BSODs.
You can compare any BIOS update version to what you have by going Start - type msinfo32 and press enter and it will be displayed in the Summary page.
If you have the latest then it won't reinstall it so you will need to Google for how to reset the BIOS for your make and model of computer as they can get screwed up occasionally.
-
I assume the Acronis drivers are for the external devices that you use to back up to and if you don't or no longer use Bluetooth devices, that will be why they aren't loaded - the same will go for your Canon printer if it isn't switched on when you boot up.
-
Hello Boggin, yes you are right. I switched off Bluetooth because of expiring and I use cable connexion when using Mobileedit for my phone stuff. I have also just checked device manager even though I have on previous occasions and all ok. I use Chemtables free prog to disable particular stuff I do not want active and that includes the Acer's own stuff as I do not use it. There is nothing I can think of that installation wise that has coincided with the startup problems occuring. I have slimdfrivers free installed and although it does list stuff it says need to be updated I am loathe to do so, not knowing the source of downloads.
-
I occasionally install Slimdrivers to check if I need updates but go to the driver manufacturers site for the updates as I've noticed that when I've used Slimdrivers to update Network drivers, I still have what I had before the update.
Does Slimdrivers list any Controllers as needing updating ? these are either Chipset or Video driver related.
When Windows has problems loading drivers it's either Chipset or BIOS related.
If you find an updated BIOS version and you are using a laptop, you must install the battery as well as AC to prevent any loss of power during the upgrade as that will brick the computer.
-
Yes it does. SlimDrivers shows a total of 12 various updates. Driver Identifier shows 17! My Desktop computer is an Acer Aspire M5201 bought in 2008. I went to the Acer Update site where it indicated Realtek 6.0.1.5591 update but I could not pull it down.
-
Do you have all of your Windows Updates installed, including SP2 ?
That could be an older audio driver to what you have installed, but I don't think it's a problem with the actual Realtek Audio device - Windows is unable to load that and the Nvidia drivers.
You can try the audio driver download from http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=24&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false but I don't think it will make much difference.
-
Yes, updates and SP2 installed.
-
Actually you dont need the vista cd to do the memory test. When that computer is first turned on start hitting the F8 button repeatedly until you see the Windows boot manager, when it comes up you can hit the tab key to go down to memory diagnostics and then hit enter and you will get a screen like I attached.
I did this with vista in vmware to confirm and get the screen shot so you would know what to look for :wink:
Shane
-
Hello Shane, that is the screen I got when I did the memory test but I could not find any log file at the end of the test.
-
It will be in the event viewer, this is for 7 but it is the same on vista
http://www.sevenforums.com/tutorials/95368-memory-diagnostics-tool-read-event-viewer-log.html
Shane
-
Thanks Shane, I will check on it.
-
I have just done a memory diagnostic. There was no screen info to say there were any problems. On the resulting auto restart there was no indication on the taskbar of the results. I then follwed the instructions as per Shane's link. The section that said right click on the System link showed the resuling panel but the Find was greyed out. I left clicked on the the System link and the resulting panel showed the Find link as active. I could not copy and paste the MemoryDiagnostics-Results as there was'nt one showing.
-
I did a search in Windows and found this file but it is dated 2011. Microsoft-Windows-MemoryDiagnostics-Results%4Debug.evtx. Another 2 items I found were in the Problems and Solutions section and these are dated at the time I did the Memory test. Here are the screen grabs.
-
I have just looked at the shutting down and startup performance logs. Could the resulting problems thus incurred caused the loss of the MemoryDiagnostic-Results log? Here is the zipfile results.
-
Re my last reply-I did the memory test after the computer had been on for 60 hours so I did not have to go through the aggro of getting it to startup with increments of hard shutdown and startup sessions to get it to finally bootup.
Today Sunday 08-02-2015 I did the 1st. startup of the day at 11.32 am and it actually powered up after 29m.30s without carrying out the usual shutdown and startup increments. At 1min after power up the Acer screen appeared then the progress bar for a few seconds. 1 min.50s later the Acer screen appeared again and 2min.30s later the choice of Repair/Start Normally appeared. I chose Start Normally which resulted in a full bootup ok. There were no further entries in the Problems and Solutions section. When the computer does finally bootup, further shutdown/restarts actions are not open to the foibles of the initial startup of the day and the average time to bootup from a shutdown/restart averages about 9 min.
-
Have you ever uninstalled anything from Device Manager or in Device Manager/View/Show hidden devices are there any yellow alerts, red crosses or downward black arrows ?
-
Hi Boggin, No I have not unstalled anything. I have just now shown all hidden devices and made a screen grab to show those with the yellow and ! indicator. I have noticed something else so will overprint the grab with a bit of info and post it. Thanks.
-
Here is the Show Hidden Devices screengrab
-
I also use a Logitech wireless mouse and other than the HID compliant mouse, it just lists the other as a PS/2 Compatible mouse.
I'm not familiar with those Portable Devices but plugging them in then uninstalling them from Device Manager then clicking on Action/Scan for hardware changes will reinstall their drivers, but create a restore point before doing so.
Just try uninstalling one at a time before Action/Scan for hardware changes and create a restore point after each if its reinstatement is successful.
When you uninstall some items from Device Manager, you may see an entry for Unknown Device but as drivers are reinstated, this should disappear.
If Windows is trying to load something on Start and it's defective or missing, that will add to the Boot time.
This was alluded to when you got that error message that the problem could be caused by a change in configuration.
When you right click on each prior to selecting Uninstall, click on Properties and under the General tab will be an error code for its status.
-
OK, will do that. Disregard my bit about a flashdrive changing a letter to L. I have just done a test and as I use one usb socket only for such things it is the letter P that is replaced by the letter M and of course it reverts back to the lettern P upon removing the flashdrive.
-
Hello Boggin, before commencing I thought it best to do a restart. I then went to Device Manager, show hidden, and the only one with a yellow and ! was the Microsoft PS/2 one. I exited and returned 3 times and all is clear bar the PS/2 one again, the error being "This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)"
-
There's something very strange going on here ????
If you have an old PS/2 mouse then you could plug that in and try the same with that, but right click on it and select Update driver software to see if Windows will find anything for it - also do a manual check for Windows Updates - it's amazing how they can detect when you have an out of date driver.
-
OKI, will do. Thanks
-
I've been doing some experimenting which may do something for you if you don't have a PS/2 mouse.
I created a restore point and uninstalled my PS/2 Compatible mouse driver and after the reboot it was still there in Device Manager but with a yellow alert next to and no amount of Scan for hardware changes would reinstate it and when I did the Update driver software bit - it returned that I had the latest drivers.
A Google found http://www.driverscape.com/download/microsoft-ps-2-mouse
The Mouse Driver Installer just gives you an Updater program which is a paid for job for it to update drivers, but the actual Driver download below that gave me a Synaptics Touchpad driver for my Toshiba laptop (10 mins to download when I clicked on Run)
After I ran the Set up and checked Device Manager after the reboot, the yellow alerted PS/2 Compatible mouse driver had been replaced with Synaptics PS/2 Port Touchpad.
Not exactly what I was expecting, but as I don't have a PS/2 mouse to try the reinstate, that seems the best it could do for my laptop but it may give something more apt for you as it recognizes your OS.
It's possible that your screwed PS/2 is the cause of all of your problems so getting any update to get rid of the yellow alert may sort your Boot problems.
-
Thanks for that. If a usb mouse is used would that make it run via a generic driver if a software disk is not part of the package. Both keyboard and mouse are directly usb connected and not by a PS/2-usb convertor.
-
No, it would need to be one of the older ones that use the 15 pin (I think) PS/2 port/socket.
Try the driver download from the link I'd posted after creating a restore point to see what you get - I take it Windows was unable to find one when you used the Update driver software option.
-
Before the final closing down of the day I clear the Event Performance logs so on the next startup I can check for any anomolies that have occured during startup. I have not seen anything to do with the PS/2 problem.
-
It may not do but could have a knock-on effect.
Your Device Manager has certainly been topsy-turvy.
Create a restore point and see what that PS/2 driver download does for you in getting rid of the yellow alert and then see what happens with a fresh boot in the morning.
I'm off to bed now.
-
Still no results of the memory test.
You either have bad memory, bad sectors on the hard drive or the vista install is toast.
I forget, did you say you had a vista with sp2 disk or not?
I am also curious as to why you cant find the memory test results. And since we are 5 pages in on this, I cant remember if I had you check for bad sectors on the drive yet.
Shane
-
Hello Shane, yes I do have sp2. I have carried out the tests regarding bad sectors, scannow etc. The only improvement if you can call it that is for two consecutive days I have let the computer startup on the first try of the day without me having to stop start various times until it kicks in. Yesterday it ran continuously for 29m.30s before the power kicked in and today it took 26m before the power kicked in. Both times there was a failed attempt to startup and then a successful startup took place. Each time from successful startup to finish took 9m. Powering down the computer takes on average about 2m.30s. I do not have master disks so if system is shot then that is that. About a year after using the computer I was getting bsod's and I did make a self booting memtest cd which disclosed faulty memory sections. I replaced both sticks with matched 2 gb ones and all went well. Are there any actions in your Windows Repair program that may be of benefit? Thanks.
-
Do you still have that yellow alert in Device Manager and if so, have you tried that driver download as I've suggested ?
-
Hello Boggin, yes but I am looking in my stock box for a PS\2 mouse or a spare usb one as I have a PS\2 to usb converter in the stock box. At the moment I am taking apart 3 hdd from a few years back so as to break the disks before binning them.
-
Plugging in a PS/2 mouse may force Windows to install the driver.
I've been looking in Device Manager/Action/Add legacy hardware but haven't been able to find anything for a PS/2 driver, but as yours is listed as a MS one, you may have better luck.
-
although I do not use the PS/2 connexion that is why I am looking for a mouse to connect.
-
although I do not use the PS/2 connexion that is why I am looking for a mouse to connect.
I understand that and is why I suggest that you download that driver after creating a restore point if you can't find a PS/2 mouse.
While it gave me something different, probably because I'm using a laptop, it may give you the correct driver but should get rid of that yellow alert regardless.
As long as Windows keeps trying to load that missing driver, you are going to have Boot problems.
-
Thanks Boggin. I shall ask my son as he has some stuff in his stock box too.
-
I dont know if my Windows Repair will help with this or not. If it is hardware related then it isnt going to help. If Windows is just shot then a fresh install would be best, because then the drive could be wiped and formatted to make sure the file system and the boot manager are all intact properly.
When I asked if you had SP2 I didnt mean if you had SP2 installed, I mean if you have a vista install disk you want one that has SP2 already on it.
So looking over old posts, and what of the logs you posted, it looks like you are on vista home prem. 32 bit. I found the ISO you need which has SP2 already on it
https://docs.google.com/open?id=0B1bjzCHZkpy9ejgzMllaMlM4T2M
Its over 3GB download so it will take some time. Once you have the ISO (ISO is a dvd image file) you will need a program like imgburn to burn it to a dvd or you can use a program like rufus to take the iso and put it on a usb thumb drive that you can boot off of and install vista.
https://rufus.akeo.ie/
Shane
-
Hello Shane, so does that mean that the link you supplied will result in a disk that will re-install vista inclusive of SP2? Will it go back to factory standard meaning I shall have to reinstall my programs again? I clicked on the link and a page came up with "sorry no preview available" and below that a download button. At the moment I am validating data of stuff I moved from when ext usb drive to another and that will finish at midnight. I would prefer to go to the link and download without any other stuff going on in the background. Thanks.
-
I take it your son didn't have a PS/2 mouse either ?
If you are going to go to the bother of a reinstall and all of that entails, download that PS/2 driver to see if it resolves your boot problems.
I can't quite understand your reluctance/resistance to trying this.
If your machine has a recovery partition, then factory resetting it would be another option to the reinstall, but you would have back up your personal stuff as well as reinstalling any programs.
If you have any paid for programs, you will need their product keys and you should check to see if the COA sticker key is the same as the vendor's generic key should you opt for the reinstall, as sometimes the COA sticker key if different from the generic won't activate a retail install.
You may want to back up your drivers folders from Windows\System32 as well.
Belarc Advisor will list the product keys. http://www.belarc.com/free_download.html
-
That ISO is a dvd image of the Vista setup disk that already has SP2 part of it, so when you install SP2 is already on it.
It isnt a factory install, it is the normal, fresh, nothing extra install. But if you do a repair install with it you can keep your programs and a repair install would be the first one to try. If it doesnt fix it then a fresh install (You wipe everything) would be the last resort.
The reason why you need a normal install disk with sp2 already on it is because a repair install is basically doing an upgrade to the same version. So you cant have a setup disk that isnt as current as the system, in this case SP2.
But the repair install is easy once you have the disk, you just follow this
http://www.vistax64.com/tutorials/88236-repair-install-vista.html
Shane
-
Thanks, Shane. This is totally new ground for me so I will print off the info in the latest link. I will start in the morning and\take it from there.
-
Hello Boggin, as you can see Shane has thrown me a lifeline so that will be the action set for tomorrow morning. I found a PS\2 mouse in my stock box a little while ago so will try that as a taster to see if a difference is made. Although I have been into computing for quite a long time, Tandy TRS 80, Amstrad, Amiga and in 2000 MS I have never had any problems where I have had to delve deep. I admit I relied on my son for things that were beyond me as he did a 9 month college course and obtained a few certificates on the way. He got married and moved not too far away but I do not see him as much. I shall be 80 at the end of this year and perhaps a birthday present of a new computer would be a nice present! :wink:
-
Hello Boggin, as you can see Shane has thrown me a lifeline so that will be the action set for tomorrow morning. I found a PS\2 mouse in my stock box a little while ago so will try that as a taster to see if a difference is made. Although I have been into computing for quite a long time, Tandy TRS 80, Amstrad, Amiga and in 2000 MS I have never had any problems where I have had to delve deep. I admit I relied on my son for things that were beyond me as he did a 9 month college course and obtained a few certificates on the way. He got married and moved not too far away but I do not see him as much. I shall be 80 at the end of this year and perhaps a birthday present of a new computer would be a nice present! :wink:
Perhaps a few hints to your son about how much trouble you've had with this one may get the penny to drop :smiley:
-
Good idea. The earlier I drop the hint the more time it will give him to start saving for it! Thanks for your input re my computer situation.
-
Hello Boggin, I have just powered down and inserted the PS\2 mouse and restarted. During the restart when the mouse cursor appeared I was able to move it with both mice. On completion of booting up there was no indication of new device found etc. Device Manager showed the PS\2 driver intact and working ok. I will be able to gauge if there will be any effect on the first bootup of the day in about 8 hours time.
-
I think you would only have gotten notification when a new 3rd party device is plugged in, but the PS/2 adapter is practically part of the system so other than Windows reinstating the driver, it was using built in technology.
It would be similar if when using a wireless mouse or other USB device and you pulled the USB and then plugged it back in - you'd hear the bdumps but no notification as it was using an existing driver - but hope it has cured the hang on boot.
I don't know if having two types of mouse plugged in would have any affect, but now that it doesn't have to struggle with the PS/2 driver you shouldn't need the PS/2 mouse plugged in - although you could try the boot with just each plugged in.
-
Hello Shane, I have not yet proceeded with the iso file situation as I would first like your opinion on the following:
I started afresh with the CBS.log situation. I selected C Drive properties/tools and ticked the two boxes check system files and scan for bad errors. Nothing showed amiss. I then used the scannow function. The end result was the last line in the log that read
"2015-02-11 20:36:24, Info CSI 000001f2 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired" Would you still advise the use of the resulting DVD made from the iso file? I have not turned off the computer and restarted again to see if there has been an improvement in the loading time but will know on the first startup of the day tomorrow. The first startup of the day today was at 4.15 pm (I did not get to bed until 4.00am this morning) and that took a continuous run of 31 minutes before the power light came on followed by two attempts of the computer to auto bootup and then the choice screen coming up from which I chose Start Normally with the computer finally booting up ok, totalling 45 minutes from start to finish. I have, since this bootup installed MS windows updates and restarted ok within 9 minutes, though this was before the chkdsk and sfc actions. As you can see by my convo with Boggin the PS\2 driver problem has not arisen since the plugging in of a PS\2 mouse. Thanks.
-
You could try booting up into the Advanced Boot options by tapping F8 (usually) as you switch on and select Repair your Computer then navigate to the Recovery Environment and select Startup Repair to see if that comes up with anything - although I've never really seen it achieve anything.
Or, you could create a bootable Paragon Rescue Disk http://www.paragon-software.com/home/rk-free/
This is really for when you can't boot up at all but it does have a Boot Corrector as well as other tools you could let it run through.
Click on the Downloads & Manuals link on the left and you can download a tutorial for it.
You will need to change the Boot order which you can do a one off by usually tapping F12 as you switch on, but when you switch on normally you will see which keys apply to your machine.
It is usually F2 for Set up which is the BIOS and F12 for the Boot order change but look carefully the next time you boot up, although the time it is taking to boot up, you may have plenty of time to read what it gives.
Select ODD (DVD player) insert the disk and press enter.
The disk may boot straight up or you could get a prompt to press any key to boot from CD/DVD
Did the sfc /scannow report that it had repaired all files or just some at the end of its scan ?
-
Hello Boggin,
"All files and registry keys listed in this transaction have been successfully repaired" I shall wait until Shane responds as he may deem the iso file is not required although I will have to wait until tomorrow to see if startup has improved timewise. It will be too late tonight as I must get an early night. I shall leave the PS\2 mouse plugged in as it can be a backup.
-
You can get that message at the bottom of the CBS log even when the scan has reported that it was unable to repair all files and is why I asked what it reported on the completion of its scan.
-
I would still do the repair install no matter what.
Shane
-
OK, Shane, will do so tomorrow. Thanks
-
Do a backup before hand just in case. Even though it is suppose to keep your files, you never know if something will go wrong, so better safe than sorry :-)
Shane
-
Hello Shane, I have backed up C and D drive to an ext usb hdd using Acronis. I noticed that Acronis does not backup certain files on the C drive as they appear empty on the backup. I used double driver to backup drivers also to the backup drive. Reading the directions of using the iso file burned to a dvd has made me tentative as I cannot grasp every step. I will wait until my son visits and get him to do it. I have no master disks at all and have nothing to fall back on if there is a failure and reading some of the comments users have experienced worries me further still. I shall let you know the outcome. Thanks for your help.
-
Grab imgburn if you havent yet
http://www.majorgeeks.com/files/details/imgburn.html
Put in a blank dvd-r into your dvd burner. Then open imgburn and choose write image file to disk. Then when you click that click the browse button and choose the iso file you downloaded and thats it, have it start the burn process.
Once done you should see the files on the dvd disk inside my computer. Is so follow the directions I gave you :-)
Shane
-
Hello Shane I have already made the disk. Do I click on setup and select repair mode from a menu? Thanks.
-
Follow the instructions on the page i gave you :-)
Shane
-
okay, Shane. I have read but still cannot grasp the info so will have to get my son to do it for me. Thanks.