tmoney468 Posted December 23, 2006 Share Posted December 23, 2006 Hi everyone, I recently built a PC and it's been giving me problems since day one. I think my problem may be a memory one, but I'm not sure. I have an Asus P5B-E, TWIN2X2048-6400C4 Ram, and an E6600 processor. The problem I experience is that when the computer is off and is turned on, it boots fine and Windows normally loads fine, but as soon as the Windows Login Screen shows up, a couple seconds later the PC freezes and reboots. I've tried setting the timings manually, set the voltage to 2.1V and it still freezes. I tried booting up the system with only one stick, and it did seem to boot fine that time with only one stick of ram. Should I try to reproduce that more than one, or try to run Memtest on the ram? I'm just lost because it seems weird that the PC would freeze at the Windows login, and then reboot. Link to comment Share on other sites More sharing options...
DerekT Posted December 23, 2006 Share Posted December 23, 2006 Is this a fresh install of Windows? If it is I would test each ram stick individually with memtest. http://www.memtest.org If it is not a fresh install of Windows, I would perform a fresh installation. It almost sounds as if you are trying to run a hard drive with a previous installation (from another system) on this one and that will not work. Link to comment Share on other sites More sharing options...
tmoney468 Posted December 23, 2006 Author Share Posted December 23, 2006 Yes it is a fresh install of Windows. We've actually installed Windows twice and still have had the freezing problem, all though the after the second install the PC seemed to be fine for the first 2-3 days, then the freezing began again. I should have mentioned that when it first boots and gets to the Windows screen and freezes, then reboots, it usually comes up the second time fine without any freezing (all though a couple of times it has rebooted and come up fine the next time). Link to comment Share on other sites More sharing options...
DerekT Posted December 23, 2006 Share Posted December 23, 2006 Run memtest on each stick singly. If no errors occur, then run memtest on the two sticks. Make sure you set your system on default and you memory at 800Mhz with 5 - 5 - 5 - 15 timings. Link to comment Share on other sites More sharing options...
tmoney468 Posted December 26, 2006 Author Share Posted December 26, 2006 Ran Memtest on both sticks, received two errors on the first stick and didn't receive any errors on the second stick. I thought this would solve my problem, but after starting up my PC this morning, it again froze like it always has. I guess I should still RMA the bad stick of RAM right? Do you think it could be a bad power supply that's causing the problem, or any other hardware problem? Link to comment Share on other sites More sharing options...
DerekT Posted December 26, 2006 Share Posted December 26, 2006 You would not receive memtest errors from a faulty PSU. The re-boots, yes, that could easily cause reboots. Is your Legacy USB disabled in your BIOS. Please enter your BIOS and disable Legacy USB if it is not and retest. Thanks, Derek Link to comment Share on other sites More sharing options...
tmoney468 Posted December 26, 2006 Author Share Posted December 26, 2006 Sorry I should have been more clear. Yeah, I didn't think a faulty PS would give errors in Memtest, I was just wondering if in general a faulty PS could cause freezes/reboots. I did disable legacy USB in the BIOS and got those two errors on the first stick of RAM, the second stick completed fine without errors Link to comment Share on other sites More sharing options...
The_Big_Doofy_1 Posted December 26, 2006 Share Posted December 26, 2006 have you tried kicking the crap out of it. As I've said before only experienced techs should try this as the kick spot varies from model and manufacture. I find a size 11 to be perfect for most "ghost errors" but sometimes have to get a friend with a size 14 to help out. If it's a peripheral such as cheap printer cam etc, you can do some low-level percussive maint. (stomp it to pieces and dare it to give you any more crap). These are extreme techniques, but have been known to work. I had an old Compaq server that wasn't recognizing a RAID, and -believe it or not- a good kick approx center of left side forced recognition of the array. I take no responsibility for either success or failure of these methods, only endorse them in extreme cases...or anytime Windows 9x is involved.:evil: ;): Link to comment Share on other sites More sharing options...
The_Big_Doofy_1 Posted December 26, 2006 Share Posted December 26, 2006 Although kicking the end-user may lead to law-suits and other annoyances, it often is the quickest way to solve the problem. I once spent an hour trying to explain to a user why her son's PII system wouldn't play Far-Cry. She couldn't grasp that its the parts in the tower - not the OS that enable such wonders as adequate resources for assigned task. She kept insisting that she just got a 200 G HDD, and that should take care of any problems her system had - even though only about 20 G were recognized). She didn't need an AGP card because the picture was fine, and she didn't need more RAM because "both slots already have thingies in them." And I used to wonder why techs were anti-social, sarcastic, and generally ill. Now I know, and knowing is half the battle. Yo Joe!! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.