happy halloween last night :)
ok next idea?? the cpu is still maxing itself out in the performance monitor with the image i sent previously. I'm running the security check now using security essentials and will reboot after just to make sure everything is back as it needs to be.
OK, then run the system file checker when you are done.
Open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
oh right i remember that. running now. Just a couple of bits of info..
when i run in safe mode, it's fine and happy
when i run using msconfig and have it not load anything it gives me the same issues.
so what drivers are loaded between safe mode and when the rest of the startup process loads??
its' done - windows resources did not find any integrity violations. so that's good...
Basically, Safe Mode only loads enough drivers for the system to run. Most of the third party drivers are bot loaded, mostly only the Microsoft System drivers.
makes sense....
so what would you suggest as the next step?
and no using it for target practice isn't an option at this point
If it runs fine in Safe Mode I would suggest Creating a restore point using the link in the first warning box. Do not be surprised when it seems slow and sluggish. That is perfectly normal and to be expected. It is putting extra stress on all the drivers, trying to cause a BSOD in order to catch the offending driver. Run it for 24 hours of actual use. You can do anything you want with it, especially anything that usually causes a BSOD. But, Be sure to create the system restore point before enabling DV, and make sure you have the installation disk or the repair disk. You may need them to disable it in case you can't boot.
WarningBe sure to create a System Restore point before proceeding further System Restore Point - Create
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.
What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.
Warning
Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.
Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode, do a System Restore to a point you made earlier.
Let us know the results, with the subsequent crash dumps, if any.
ok cool - will have to find the installation disk - it SHOULD be at the office - any way to create a repair disk from the laptop?
Another question - blue screen said - physical memory dump FAILED with status 0xC000009C. Is there any way to enable it?
You can create a repair disk by going to Control panel. backup my computer and in the left column is create repair disk. All you should need is a blank CD. I'll look at the error in a minute.
Quote