athlon 64

  • Thread starter Thread starter Usarian Skiff
  • Start date Start date
U

Usarian Skiff

I just put a hard drive with windows xp installed on it into an athlon 64
machine. The hard drive came from an emachine.

It begins to boot then blue screens. The last file accessed when starting
in safe mode is ipvmon.sys

I'm trying to upgrade someone's machine. I have done it this way before
with no problems, but never an athlon 64 before. Do I need to install some
driver or something first?

Thanks!
Usarian
 
Thanks guys, that worked, but now I'm getting a blue screen error about
memory (which is brand new)

0x00000007

(I might have the zero count off there)

I turned off all the bios options, but it just takes longer to give me the
message now. any ideas?

Thanks!
Usarian
 
In Usarian Skiff <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Thanks guys, that worked, but now I'm getting a blue screen error
about memory (which is brand new)

0x00000007

(I might have the zero count off there)

I turned off all the bios options, but it just takes longer to give
me the message now. any ideas?

Thanks!
Usarian
Click to expand...

Give us more information :) 0x0000007? What type of error about memory? Just
because the RAM is new does NOT, in fact, mean that it's any good, seated
properly, configured properly in the BIOS, or even compatable with the
system...

If you're unable to provide (or unwilling) more information then this is the
best site I know of (don't thank me, thank Jim) for debugging those insane
errors.

http://aumha.org/win5/kbestop.htm

Galen
 
Hi,

I had similar problems when I switched to an Athlon64 on an MSI Neo2 FIR
mainboard.
There is a high probability that you have memory timing problems. Use the
BIOS to relax them. The Athlon 64 has a built-in memory controller. Quite
often, the timings stored in the RAM stick SPD are good for a chipset
controller, but too agressive when the A64 is used.
Browse your mainboard manufacturer web site, and check the forums, this
subject is probably well covered.
Run a standalone memory diagnostic utility, such as memtest86 or Docmemory
(google ...) and see if tey report errors.

Fred
 
Back
Top