help me?

[inahandbasket]

Ok, I'm having issues.
I figure that this is a good place to run to. :o)
(yes, I do tech support too...)

Ok.
Brand new AMD 1ghz, Asus MB.
I had win2k running fine on my old machine. I swap all hardware to the new machine listed above.
Can't install win2k, gets "Physical memory dump" error, Blue screens and freezes.
I've looked everywhere on the net and can't find anything about it. Was hoping that maybe someone in here would have had a similar issue and found workaround. Maybe I need the service packs? It's a 1.0 win2k CD.
I'd go Linux but I love Diablo2 too much. *sigh*
Any ideas, please!

Comments

swapping MBs

[synthe.livejournal.com]

If you swapped motherboards on Win2k, you are probably going to need to format and reinstall. It installs a lot of specific motherboard drivers during first run in the setup process, and now lots of those devices have changed memory addresses or changed completely. Plus, if your old board wasn't ACPI and your new one is, you would even be using a new NT kernel.

Re: swapping MBs

[inahandbasket]

oops,
should have included that I formated the HD when I upgraded, so it's a completely fresh install, etc.
I'm going to try upgrading the BIOS tonight, see if that makes a difference. I was surfing the web and found that a bunch of other people have been having a similar probem with the MB win2k combo, and one or two said that updating the BIOS did it.
So...
as soon as I get home, pop goes the BIOS.
:o)

pc

[hakangit.livejournal.com]

I figure no overclocking? (yet anyway)

I had some win2k problems too. Every time I shut down it bluescreens and says Driver Power State failure... and i've gone and downloaded all the signed drivers now to still the same. damn ACPI.

Good luck with the bios upgrade that should probably at least help

[inahandbasket]

Well, i updated the bios and tried again.
No luck.
So I pulled out my old video card that has a PCI interface and I'm currently formatting the hard drive for another go at the bitch.
It worked fine with my old setup.
*sigh*
so go the perils of upgrading.
Hopefully it'll like the PCI interface better.
Next thing to try is swapping out the RAM stick for a different one. Perhaps I got a bad one. It happens.
*crosses fingers*
hopes not.
Anyway, I'm going to get some food while it formats. Takes the stupid thing ages to format.
*shrug*
big drive.
Anyway, hopefully tomorrow I'll have good news on this front.

[suppafly.livejournal.com]

are you sure the hardware is good?

[inahandbasket]

Doh, forgot to post in here.
Got it working after 3 days.
The 256mb stick of PC133RAM that I'd just bought (and was tested good before I installed it) was actually bad.
I yanked it and swapped in an old 128 PC100 that I had laying around.
Install ran fine.
Threw in the 256 on top of the 128 after I had win2k up and running and guess what!
BSOD.
BSOD.
BSOD.

So in my expert opinion, RAM is a pain in the ass.
Luckily it has a lifetime warranty. cha-ching!
Thanks for all the advice folks, appreciate it muchly!

Re:

[suppafly.livejournal.com]

i would have guessed it was the ram since i always have similar problems when the ram is bad.. i learned the hardway that you should always check the ram heh.. i spent hours trying to fix some girls computer that had bad ram before realizing what the problem was..