|
MrTicker
|
 |
« Reply #60 on: June 29, 2010, 12:32:05 AM » |
|
Hi there,
If the registry keys do not exist then you can create them like this:
Navigate to here: HKEY_CURRENT_USER\Control Panel\Desktop
With DESKTOP in the left pane highlighted click EDIT>NEW>STRING VALUE and enter WaitToKillAppTimeout
Next click EDIT>MODIFY and in the Value Data box Enter the value that Bradley suggested.Click OK.
Next with DESKTOP in the left pane still highlighted click EDIT>NEW>STRING VALUE and enter HungAppTimeout
Next click EDIT>MODIFY and in the Value Data box Enter the value that Bradley suggested.Click OK.
Close Registry Editor, now you are good to go, let us know the results.
Always Remember to Back Up The Registry First Before Making Changes.
Cheers,HTH,
ticker
|
|
|
|
« Last Edit: June 29, 2010, 12:49:38 AM by MrTicker »
|
Logged
|
|
|
|
|
|
|
BJseal91
|
 |
« Reply #61 on: June 29, 2010, 12:37:02 AM » |
|
yes Do what Ticker Said They May Have Been Not Copied and see if this makes a diffrence
Bradley
|
|
|
|
|
Logged
|
|
|
|
xyy
Newbie

Posts: 37
|
 |
« Reply #62 on: June 29, 2010, 04:59:06 PM » |
|
alright did everything mentioned earlier. Noticed a bit of change. I found out earlier that I haven't reactivated my version of windows after I reinstalled it. I thought that might have been the problem but I got it activated and there wasn't much change at all. The only real problem I'm having with the computer is that the startup and shutdown times are seriously unbearably long and ridiculous. Using the computer for basic web browsing and running basic apps is tolerable. What could possibly be wrong? I just don't get it. Again thank you all for your continued support! Really appreciate it. I hope we can find a solution really soon 
|
|
|
|
|
Logged
|
|
|
|
|
|
|
BJseal91
|
 |
« Reply #63 on: July 01, 2010, 04:54:25 AM » |
|
Have you checked the processesser has the correct percentage how long is it actually taking to complete the task and have you tried windows updates and check in the device manager and make sure there is no issues showing up in the hardweare
if the processesser is high then I have got answers if not I am running out of answers other than checking the disk for errors it could be related to a bad hard drive or loss of power to the mothboard there is a few things to check now you are having this problem.
run a couple of tests on the computer
go start
in the searchbar type CMD
right clcik on cmd and run as administrator
type the following
chkdsk /f
if it asks to restart before doing the test type y
restart and let us know the result
Kind Regards
BJseal91
|
|
|
|
|
Logged
|
|
|
|
xyy
Newbie

Posts: 37
|
 |
« Reply #64 on: July 02, 2010, 09:10:19 AM » |
|
okay the strange thing that happened when I put in the chkdsk /f command was that it made me restart the computer to start the test, but it never went to a test. It just went straight to booting up windows as normal (normal being a 10 minute+ boot up time for me). Would there be any reason why it wouldn't run the test at all? Even when I try to start HP's built recovery by pressing F11 nothing happens and the system starts booting windows.
|
|
|
|
|
Logged
|
|
|
|
|
MrTicker
|
 |
« Reply #65 on: July 02, 2010, 03:40:33 PM » |
|
Hi, xyy,
Have you managed to get CHKDSK to run on restart yet? If not let us know so we can help you further.
Cheers HTH
ticker,
|
|
|
|
|
Logged
|
|
|
|
xyy
Newbie

Posts: 37
|
 |
« Reply #66 on: July 02, 2010, 04:24:03 PM » |
|
That's exactly the problem. I can't get it to run on restart. It just goes straight to booting windows. Is there any commands I could put in or hold down a particular button to force it to start running chkdsk?
|
|
|
|
|
Logged
|
|
|
|
|
MrTicker
|
 |
« Reply #67 on: July 02, 2010, 05:54:06 PM » |
|
There xyy,
So CHKDSK won't run on reboot so obviously something is stopping it performing that action, what we have gotta do is find out what that something is and prevent it doing it again. When we have achieved this, hopefully you will also have a machine that is performing properly also. At least for the moment you can boot into Windows,albeit slowly, but that will do for now.
To start with, begin by following these steps after firstly booting into Windows,
then:
1. Set up a new System Restore Point:click Start>Rt Click My Computer>Properties>Advanced System settings>System Protection>Create and name your restore point.Click>Create. 2. Start>Run>Type 'msconfig' in the box>OK 3. Select the'Boot' tab 4. Tick the 'Boot log' and 'OS boot information'boxes>Apply>OK 5. Click>Restart. Look for and note down any messages that you see during boot up.
(Leave out all quote marks when typing)
When you are back in the system after boot up, look for this log file here C:\WINDOWS\ntbtlog.txt or ntbootlog.txt.
What you are looking for here is 1 or more of these drivers being loaded that causes CHKDSK to say "Cannot open volume for direct access."
When you have done this,post up all your results and we can take it from there.
Cheers, HTH,
ticker
|
|
|
|
|
Logged
|
|
|
|
xyy
Newbie

Posts: 37
|
 |
« Reply #68 on: July 03, 2010, 01:04:57 AM » |
|
okay i'm just going to paste the results:
Microsoft (R) Windows (R) Version 6.1 (Build 7600) 7 3 2010 00:16:21.375 Loaded driver \SystemRoot\system32\ntoskrnl.exe Loaded driver \SystemRoot\system32\hal.dll Loaded driver \SystemRoot\system32\kdcom.dll Loaded driver \SystemRoot\system32\mcupdate_AuthenticAMD.dll Loaded driver \SystemRoot\system32\PSHED.dll Loaded driver \SystemRoot\system32\CLFS.SYS Loaded driver \SystemRoot\system32\CI.dll Loaded driver \SystemRoot\system32\drivers\Wdf01000.sys Loaded driver \SystemRoot\system32\drivers\WDFLDR.SYS Loaded driver \SystemRoot\system32\DRIVERS\ACPI.sys Loaded driver \SystemRoot\system32\DRIVERS\WMILIB.SYS Loaded driver \SystemRoot\system32\DRIVERS\msisadrv.sys Loaded driver \SystemRoot\system32\DRIVERS\pci.sys Loaded driver \SystemRoot\system32\DRIVERS\vdrvroot.sys Loaded driver \SystemRoot\System32\drivers\partmgr.sys Loaded driver \SystemRoot\system32\DRIVERS\compbatt.sys Loaded driver \SystemRoot\system32\DRIVERS\BATTC.SYS Loaded driver \SystemRoot\system32\DRIVERS\volmgr.sys Loaded driver \SystemRoot\System32\drivers\volmgrx.sys Loaded driver \SystemRoot\System32\drivers\mountmgr.sys Loaded driver \SystemRoot\system32\DRIVERS\atapi.sys Loaded driver \SystemRoot\system32\DRIVERS\ataport.SYS Loaded driver \SystemRoot\system32\DRIVERS\msahci.sys Loaded driver \SystemRoot\system32\DRIVERS\PCIIDEX.SYS Loaded driver \SystemRoot\system32\DRIVERS\amdxata.sys Loaded driver \SystemRoot\system32\drivers\fltmgr.sys Loaded driver \SystemRoot\system32\drivers\fileinfo.sys Loaded driver \SystemRoot\System32\Drivers\Ntfs.sys Loaded driver \SystemRoot\System32\Drivers\msrpc.sys Loaded driver \SystemRoot\System32\Drivers\ksecdd.sys Loaded driver \SystemRoot\System32\Drivers\cng.sys Loaded driver \SystemRoot\System32\drivers\pcw.sys Loaded driver \SystemRoot\System32\Drivers\Fs_Rec.sys Loaded driver \SystemRoot\system32\drivers\ndis.sys Loaded driver \SystemRoot\system32\drivers\NETIO.SYS Loaded driver \SystemRoot\System32\Drivers\ksecpkg.sys Loaded driver \SystemRoot\System32\drivers\tcpip.sys Loaded driver \SystemRoot\System32\drivers\fwpkclnt.sys Loaded driver \SystemRoot\system32\DRIVERS\volsnap.sys Loaded driver \SystemRoot\System32\Drivers\spldr.sys Loaded driver \SystemRoot\System32\drivers\rdyboost.sys Loaded driver \SystemRoot\System32\Drivers\mup.sys Loaded driver \SystemRoot\System32\drivers\hwpolicy.sys Loaded driver \SystemRoot\system32\DRIVERS\hpdskflt.sys Loaded driver \SystemRoot\System32\DRIVERS\fvevol.sys Loaded driver \SystemRoot\system32\DRIVERS\disk.sys Loaded driver \SystemRoot\system32\DRIVERS\CLASSPNP.SYS Loaded driver \SystemRoot\system32\DRIVERS\cdrom.sys Loaded driver \SystemRoot\System32\Drivers\Null.SYS Loaded driver \SystemRoot\System32\Drivers\Beep.SYS Loaded driver \SystemRoot\System32\drivers\vga.sys Loaded driver \SystemRoot\System32\DRIVERS\RDPCDD.sys Loaded driver \SystemRoot\system32\drivers\rdpencdd.sys Loaded driver \SystemRoot\system32\drivers\rdprefmp.sys Loaded driver \SystemRoot\System32\Drivers\Msfs.SYS Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS Loaded driver \SystemRoot\system32\DRIVERS\tdx.sys Loaded driver \SystemRoot\system32\drivers\afd.sys Loaded driver \SystemRoot\System32\DRIVERS\netbt.sys Loaded driver \SystemRoot\system32\DRIVERS\wfplwf.sys Loaded driver \SystemRoot\system32\DRIVERS\pacer.sys Loaded driver \SystemRoot\system32\DRIVERS\vwififlt.sys Loaded driver \SystemRoot\system32\DRIVERS\netbios.sys Loaded driver \SystemRoot\system32\DRIVERS\wanarp.sys Loaded driver \SystemRoot\system32\DRIVERS\termdd.sys Loaded driver \SystemRoot\system32\DRIVERS\rdbss.sys Loaded driver \SystemRoot\system32\drivers\nsiproxy.sys Loaded driver \SystemRoot\system32\DRIVERS\mssmbios.sys Loaded driver \SystemRoot\System32\drivers\discache.sys Loaded driver \SystemRoot\System32\Drivers\dfsc.sys Loaded driver \SystemRoot\system32\DRIVERS\blbdrive.sys Loaded driver \SystemRoot\system32\DRIVERS\tunnel.sys Loaded driver \SystemRoot\system32\DRIVERS\amdppm.sys Loaded driver \SystemRoot\System32\drivers\dxgkrnl.sys Loaded driver \SystemRoot\system32\DRIVERS\atikmdag.sys Loaded driver \SystemRoot\system32\DRIVERS\HDAudBus.sys Loaded driver \SystemRoot\system32\DRIVERS\athrx.sys Loaded driver \SystemRoot\system32\DRIVERS\vwifibus.sys Loaded driver \SystemRoot\system32\DRIVERS\Rt64win7.sys Loaded driver \SystemRoot\System32\Drivers\fastfat.SYS Loaded driver \SystemRoot\system32\DRIVERS\usbohci.sys Loaded driver \SystemRoot\system32\DRIVERS\usbehci.sys Loaded driver \SystemRoot\system32\DRIVERS\i8042prt.sys Loaded driver \SystemRoot\system32\DRIVERS\kbdclass.sys Loaded driver \SystemRoot\system32\DRIVERS\mouclass.sys Loaded driver \SystemRoot\system32\DRIVERS\CmBatt.sys Loaded driver \SystemRoot\system32\DRIVERS\Accelerometer.sys Loaded driver \SystemRoot\system32\DRIVERS\wmiacpi.sys Loaded driver \SystemRoot\system32\DRIVERS\CompositeBus.sys Loaded driver \SystemRoot\system32\DRIVERS\AgileVpn.sys Loaded driver \SystemRoot\system32\DRIVERS\rasl2tp.sys Loaded driver \SystemRoot\system32\DRIVERS\ndistapi.sys Loaded driver \SystemRoot\system32\DRIVERS\ndiswan.sys Loaded driver \SystemRoot\system32\DRIVERS\raspppoe.sys Loaded driver \SystemRoot\system32\DRIVERS\raspptp.sys Loaded driver \SystemRoot\system32\DRIVERS\rassstp.sys Loaded driver \SystemRoot\system32\DRIVERS\swenum.sys Loaded driver \SystemRoot\system32\DRIVERS\umbus.sys Loaded driver \SystemRoot\system32\DRIVERS\usbhub.sys Loaded driver \SystemRoot\System32\Drivers\NDProxy.SYS Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS Loaded driver \SystemRoot\system32\drivers\HdAudio.sys Loaded driver \SystemRoot\system32\drivers\ksthunk.sys Loaded driver \SystemRoot\system32\DRIVERS\usbccgp.sys Loaded driver \SystemRoot\System32\Drivers\usbvideo.sys Loaded driver \SystemRoot\system32\DRIVERS\cdfs.sys Loaded driver \SystemRoot\system32\DRIVERS\monitor.sys Loaded driver \SystemRoot\system32\drivers\luafv.sys Loaded driver \SystemRoot\system32\drivers\WudfPf.sys Loaded driver \SystemRoot\system32\DRIVERS\lltdio.sys Loaded driver \SystemRoot\system32\DRIVERS\nwifi.sys Loaded driver \SystemRoot\system32\DRIVERS\ndisuio.sys Loaded driver \SystemRoot\system32\DRIVERS\rspndr.sys Loaded driver \SystemRoot\system32\drivers\HTTP.sys Loaded driver \SystemRoot\system32\DRIVERS\bowser.sys Loaded driver \SystemRoot\System32\drivers\mpsdrv.sys Loaded driver \SystemRoot\system32\DRIVERS\mrxsmb.sys Loaded driver \SystemRoot\system32\DRIVERS\mrxsmb10.sys Loaded driver \SystemRoot\system32\DRIVERS\mrxsmb20.sys Loaded driver \SystemRoot\system32\drivers\peauth.sys Loaded driver \SystemRoot\System32\Drivers\secdrv.SYS Loaded driver \SystemRoot\System32\DRIVERS\srvnet.sys Loaded driver \SystemRoot\System32\drivers\tcpipreg.sys Loaded driver \SystemRoot\System32\DRIVERS\srv2.sys Loaded driver \SystemRoot\System32\DRIVERS\srv.sys Did not load driver \SystemRoot\System32\DRIVERS\srv.sys
Hope this helps
|
|
|
|
|
Logged
|
|
|
|
|
Britec
|
 |
« Reply #69 on: July 03, 2010, 02:20:43 AM » |
|
 xyy NDProxy.sys is a Network device driver, check device manager to see if you have a problem with your Network device driver, sometimes having multi device drivers can lead to slow boot and conflictions. if you cant see any problems, maybe just try and disable Network Driver and see if it boots up ok. Might also be a good idea to run SFC /ScannowNote: You will need a windows cd
|
|
|
|
« Last Edit: July 03, 2010, 03:29:20 AM by Britec »
|
Logged
|
|
|
|
|
BJseal91
|
 |
« Reply #70 on: July 03, 2010, 03:03:13 AM » |
|
start the command prompt in the search bar type cmd right click run as administrator type the following command sfc /scannow
this will begin a scan and tell you what problems there are if any files are missing or corrupt on the system and attemp to replace them the scan should take no longer that 2 hours.
also check the device manager like brian said.
Kind Regards
BJseal91
|
|
|
|
|
Logged
|
|
|
|
xyy
Newbie

Posts: 37
|
 |
« Reply #71 on: July 03, 2010, 11:26:32 AM » |
|
when i put in the command, "SFC /Scannow" i get this message:
Windows Resource Protection could not start the repair service. Is this where I need the windows cd?
There were four network drivers under the network adapter section of the device manager. I disabled two that weren't able to start. The other two were just for the wifi adapter and ethernet.
Restarted the computer and took just as long. :(
|
|
|
|
|
Logged
|
|
|
|
|
Britec
|
 |
« Reply #72 on: July 03, 2010, 12:24:29 PM » |
|
Fix for Error “Windows Resource Protection Could Not Start the Repair Service” When Running SFC in Windows 7 and VistaWhen you run the System File Checker using the /Scannow parameter from an elevated Command Prompt, the following error may occur. Additionally, you may experience problems running Windows Installer Setup files and installing fixes from Windows Update. Windows Resource Protection could not start the repair service This happens if the TrustedInstaller (Windows Modules Installer) service is disabled. Use these steps to reset the service startup type. 1. Click Start, type Services.msc2. Double-click Windows Modules Installer3. Set its Startup type to Manual4. Click OK.  The TrustedInstaller service has full access to Windows Resource Protection (WRP) files and registry keys, and this services needs to be running in order to restore missing or corrupted WRP resources. The TrustedInstaller service starts on-demand when running the System File Checker.
|
|
|
|
|
Logged
|
|
|
|
xyy
Newbie

Posts: 37
|
 |
« Reply #73 on: July 03, 2010, 02:29:20 PM » |
|
when i went to change the startup type for the windows module installer I noticed that it was already set to manual.
|
|
|
|
|
Logged
|
|
|
|
xyy
Newbie

Posts: 37
|
 |
« Reply #74 on: July 03, 2010, 02:30:13 PM » |
|
forgot to mention that the service status says it's stopped. Should I start it?
|
|
|
|
|
Logged
|
|
|
|
|