1.

Solve : new windows 7 pro build full of errors?

Answer»

Parts used:

Western Digital 1 TB Caviar Blue

Kingston 4 GB 1600 KVR16N11S8

ASUS motherboard P8H61-m LE/CSM R2.0

Lite-On DVD

Intel Core i3-3240 3.4 GHz LGA1155

Windows 7 Pro 32 bit



I built 2 computers exactly the same hardware and software.  One WORKS great, the other has problems.  Not too long after Windows installed it started giving error messages.  I reloaded Windows again.  More error messages that DLL files were missing or couldn't be loaded.  I tried a different hard DRIVE.  It worked great through installing Windows and all the drivers for the onboard components of the motherboard and part way though downloading updates for Norton Internet Security 2014.  Then it restarted itself and wanted to run chkdsk everytime and when the Windows desktop and icons should appear, it would reboot itself and was stuck in this LOOP.  A friend suggested swapping RAM and possibly power supply.  I did that, no change.  I tried a third hard drive and it is the same way except now about half the time when it loads, I have no mouse or keyboard that work.  Any ideas would be greatly appreciated.
Quote

bout half the time when it loads, I have no mouse or keyboard that work.
In view off all the other things, you have already tried,  it could be the motherboard.  ASUS motherboard P8H61-m LE/CSM R2.0
Why not contact  motherboard maker about an exchange?  Some will exchange a motherboard for a fee. Under some restrictions.

EDIT: This may offer some help. ASUS has a good warrtenty policy. But not every body thinks so! So, you have to ASK nicely and see what they say. You might mention that you have two of the same board.I also agree that it may be time to swap out the motherboard under warranty. PSU, RAM, and HDD changed out and only thing left as potential for this type of problem is motherboard.

With no video card stated I assume your using integrated video. If you do have video cards in these systems, swap the video cards and see if the problem moves. I seen once where the shared memory of a video card tapping into system memory was causing strange issues like this.


Discussion

No Comment Found