since new hard drive, computer is very slow

Hello everyone. :)

So my computer's hard drive fried just a few months ago. After months of my brother scrapping parts including my NVIDIA video card and some cable tuners etc., I realized that the old laptop I had under my bed could be scrapped for the harddrive. My computer wiz friend installed the new harddrive and plugged everything else back in. I used DBAN to clear the harddrive and reinstalled W7 Ultimate.

Well long story short, with my old harddrive I could run the games I play, including League of Legends, World of WarCraft, Starcraft II, and Diablo III at low-medium setting. But with the new harddrive and 3 gbs or DDR2 ram my friend gave me, I cant run anything at the lowest setting possible and keep a FPS over 15. I installed my video card driver and my keyboard and mouse driver. The computer specs EXCEPT for the ram and video card are 6 years old. Also, the computer is really laggy for about 20 min after startup, with both cpus at 100%. But after that, the computer stays at low CPU usage.

Please help
I need a computer for Diablo 3 release :)

SPECS
Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz (2 CPUs)
297 gb HD
NVIDIA GeForce 9400 GT Videocard
Sigmatel Audio Driver
5 gbs DDR2 Ram
Windows 7 Ultimate 2.6.1.7600

It could be almost anything. A missing page file, a stick of ram not seated correctly, a HD that is failing, etc.

Latency is the easiest to test.


Latency

DPC Latency Checker
Resplendence Software - LatencyMon: suitability checker for real-time audio and other tasks


If the above are clean lets try

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7


If that finds no violations try these


* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)


Still having problems?

Whats the size and location of your page file?
How much ram does task manager see and how much free?
Has the new HD been defragmented?
Have you run Malwarebytes to ensure against malware?

etc.

James7679 said:

Download Speccy Download Speccy 1.16.317 - FileHippo.com and let us know EXACTLY what you have.

Here ya go mate.

Operating System
MS Windows 7 Ultimate 64-bit
CPU
Intel Core 2 Duo E6400 @ 2.13GHz 33 °C
Conroe 65nm Technology
RAM
5.00 GB DDR2
Motherboard
Intel Corporation DP965LV
Graphics
SyncMaster (1920x1080@60Hz)
512MB GeForce 9400 GT (EVGA) 49 °C
Hard Drives
313GB Western Digital WDC WD3200BEVT-22ZCT0 ATA Device (SATA) 32 °C
Optical Drives
HL-DT-ST DVD-RW GSA-H11N ATA Device
Audio
High Definition Audio Device

zigzag3143 said:

It could be almost anything. A missing page file, a stick of ram not seated correctly, a HD that is failing, etc.

Latency is the easiest to test.


Latency

DPC Latency Checker
Resplendence Software - LatencyMon: suitability checker for real-time audio and other tasks


If the above are clean lets try

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7


If that finds no violations try these


* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)


Still having problems?

Whats the size and location of your page file?
How much ram does task manager see and how much free?
Has the new HD been defragmented?
Have you run Malwarebytes to ensure against malware?

etc.

Well I tryed the DPC Latency Checker, and some bars are getting up to 2000-4000, with the max being 4808.
It also gave me this error message.

"Some device drivers on this machine behave bad and will probably cause drop-outs in real-time audio and/or video streams. To isolate the misbehaving driver use Device Manager and disable/re-enable various devices, one at a time. Try network and W-LAN adapters, modems, internal sound devices, USB host controllers, etc."

I also used LatencyMon, and basically the same message was given.

"Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, click or pops. One or more DPC routines belonging to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. You may have to disable wireless adapters to get better results."

Have you downloaded and installed all of the most current drivers for your motherboard? http://downloadcenter.intel.com/Sear...+Board+DP965LT

If you check the specs for that laptop drive you may find that its only a 5400 RPM drive. Most 3.5 inch desktop drives run at 7200 RPM. Its a noticeable difference. They use 5400 RPM drives in laptops to reduce heat and give you better battery life. The trade off is reduced performance

James7679 said:

Have you downloaded and installed all of the most current drivers for your motherboard? http://downloadcenter.intel.com/Sear...+Board+DP965LT

No I havent actually, to be honest, I didnt know that existed :)

Ill do that.

alphanumeric said:

If you check the specs for that laptop drive you may find that its only a 5400 RPM drive. Most 3.5 inch desktop drives run at 7200 RPM. Its a noticeable difference. They use 5400 RPM drives in laptops to reduce heat and give you better battery life.

Agreed, that's why I asked for the speccy info.