Solved Fixed AMD Turion mobo is still freezing up.

May 16, 2012 at 09:08:45
Specs: Windows XP home edition version 2002 service pack 2, 1.61 GHz, 1.93 GB RAM
It started freezing on a black screen, than had trouble starting at all. I managed to do a hard disk self test which stated it was missing OS loader? I asked forum help but am not a techie at all, so took it to get fixed... it's starting and launching and I get connectivity, I'm stoked!!, then it freezes. And in random screens, not my opened window. Sorry, just got it back yesterday and I'm fut-less..I will run self test & memory test etc. I read bit's of the repair manual online, but I think I need lot's of help... I do have a detailed invoice of what work was done on it though! Mahalo's to anyone in advance for replying!

See More: Fixed AMD Turion mobo is still freezing up.

Report •

May 16, 2012 at 11:00:16
If you had it repaired & it's still not working properly, take it back.

Report •

May 16, 2012 at 12:10:40
✔ Best Answer
See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:

Then run a memory diagnostics program.

If you want to try a memory diagnostic utility that takes a lot less time to run a full pass than memtest86 does, this one is pretty good - Microsoft's
Windows Memory Diagnostic:
Windows Memory Diagnostic is limited to testing only the first 4 gigabytes (GB) of RAM.
It can be toggled (press T) to do a standard or a more comprehensive set of tests - use the default 6 test one first - if it passes one pass of that, use the latter one. A few of the tests in the latter set are intentionally slower.
If you don't have a floppy drive, see the Quick Start Information at that Microsoft link for how to make a bootable CD of the Windows Memory Diagnostic (you need Windiag.iso - you don't necessarily need to use the program they mention to add it to the CD).

If the memory test finds ram errors, that does NOT necessarily indicate the ram is BAD.

All the ram modules installed must be 100% compatible with using them in your mboard model

Ram that works in another mboard , or any ram you buy or have lying around, may not work properly, or sometimes, not at all - even if it physically fits and is the right overall type (e.g. SDram, DDR, DDR2, etc.; PCxxxx, xxx mhz) for your mboard. In the worst cases of incompatibility your mboard WILL NOT BOOT all the way with it installed, and the mboard may not even beep - the ram has to be compatible with the mboard's main chipset, or in the case of recent mboards, compatible with the memory controller built into the cpu.

If you still have the ram that was installed when the system worked fine, try installing just that ram.

See response 5 in this for some info about ram compatibilty, and some places where you can find out what will work in your mboard for sure:
Correction to that:

Once you know which module ID strings (part numbers) work in your mboard, you can get them from anywhere you like that has ram with those ID strings.

If you have brand name ram, it is usually easy to look up whether it's ID string (part number) is in a list of compatible modules found by using your mboard or brand name system model number.
If the ram is generic, that may be difficult or impossible.

Some ram manufacturer's modules do not strictly adhere to the JEDEC standards that most mboards bioses use to determine ram settings.
In that case, the ram settings in the bios Setup that the bios has automatically chosen may not be correct.
Check the ram settings in your bios - the ram voltage, and the ram timing numbers - those should be the same as for the specs for the modules themselves. Often the ram voltage and timing numbers are printed on the label on the modules.

If the voltage setting or timings settings in the bios are different from the specs for the ram, change them in the bios. The timing numbers must be as close as you can get to the same, or slower timings (higher numbers = slower) - you won't notice the difference the slower settings make.

If you have a mix of different modules
- don't mix ram that different voltages are specified for - the bios will force the ram to use the lowest voltage, if "by spd" or similar is used (default settings) - ram that a higher voltage is specified for is more likely to not work properly in that situation.
- the bios settings must be those for the slowest timing settings of all the modules, or slower (higher numbers = slower).

When the ram passes the memory diagnostics test,

- check your data cable connections.

Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and on the mboard, or on the drive controller card - it should not move when you merely brush your hand against it near the socket - if it does, mere vibration can cause a poor connection of it - use another SATA data cable that does "latch", or tape the connector in place.
(There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged)

The same thing applies for the SATA power connection.

It is common to un-intentionally damage IDE data cables, especially while removing them - the 80 wire ones are more likely to be damaged. What usually happens is the cable is ripped at either edge and the wires there are either damaged or severed, often right at a connector or under it's cable clamp there, where it's hard to see - if a wire is severed but it's ends are touching, the connection is intermittent, rather than being reliable.
Another common thing is for the data cable to be separated from the connector contacts a bit after you have removed a cable - there should be no gap between the data cable and the connector - if there is press the cable against the connector to eliminate the gap.
80 wire data cables are also easily damaged at either edge if the cable is sharply creased at a fold in the cable.

Try another data cable if in doubt.

80 wire data cables must have the proper end connector connected to the mboard IDE header - usually that's blue, but in any case it's the one farther from the middle connector on a 3 connector data cable.

- test the hard drive by using a hard drive manufacturer's diagnostics program.

Seagate's Seatools will test (almost) any brand of hard drive.
Do the long test.

The bootable Dos versions of SeaTools can be used even if Windows is not working properly.

If the hard drive itself tests okay, any data problems found can be fixed, one way or another.

Report •

May 16, 2012 at 12:43:36
Yes, my boyfriend agree's I guess I had to hear it from someone else. It's my 10 yr old sons computer, his name is Rhyder. Guess it's a sign, Thank you!

Report •

Related Solutions

May 16, 2012 at 13:11:25
Thank You Tubesandwires for the info, since the Computer guy is not answering his phone!, I'm going to try all I can to figure it out. Your knowledge is greatly appreciated.

Report •

May 17, 2012 at 11:39:41
Mr Tubesandwires, I have to Thank You for the little added courage I got after reading your response to my problem. I ran the hard disk test and it passed, than I restored the factory default settings which didn't work so good it took me to the "we apologize but windows didn't start successfully" screen. So I went to boot options and switched the order a couple times (cause I really had no clue!) but I kinda missed what happened (kid's) a blue screen was up saying windows is looking for a disk or something like that. Whatever it was, it did the trick my son's laptop is up and running like a champ. I was about ready to quit and send my boyfriend to get our $ back from Mr. Comp. Tech., when I got your post. Thank You again for the inspiration and confidence I'm just so glad I didn't HAVE to check on any of those modules! Now I can have my Touchsmart back to myself... Again, Much Mahalo's from a VERY HAPPY MOM on Kaua'i

Report •

May 17, 2012 at 12:46:37
Thanks for the Thank yous .

We're glad to hear you solved your problem !

I'm in Alberta, Canada myself. Everything's presently greening up nicely and the temperature is reasonable outside most days.

"....took me to the "we apologize but windows didn't start successfully" screen.

When you're getting that message, it's Windows that's generating the message, not the computer's bios. That indicates the computer itself is booting fine and the bios is finding that the hard drive has a bootable partition and it has attempted to load Windows, but something in Windows was not quite right. That can be caused by the memory modules producing small amounts of memory errors, or many other things.

"So I went to boot options and switched the order a couple times (cause I really had no clue!) ..."

There was nothing wrong with your Boot Order or similar settings.
You can get yourself in trouble if you set those wrong.

"my son's laptop is up and running like a champ."

For a laptop or notebook computer, see response 1 in this:

"I kinda missed what happened (kid's) a blue screen was up saying windows is looking for a disk or something like that. Whatever it was, it did the trick my son's laptop is up and running like a champ."

I have no idea what the blue screen said unless you quote what it said on the screen that is unique.

Hopefully whatever the problem was won't happen again, but if it does, quote what it said on the blue screen that is unique.

It's also still possible the ram has a poor connection in it's slots.

See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:

For a laptop, or netbook, you must remove both its main battery and AC adapter before you do that.

For a brand name computer, see the Owner's or User's manual if you need to - how to remove or replace the ram is usually in that - it may already be in your installed programs. If you can't get into Windows, it may be on a disk that came with the computer, or you can go online and look at it or download it - it's in the downloads for your specific model.

Report •

Ask Question