I have a question about Dealing with Bad Memory (RAM):

someone pls help: I just replaced a motherboard, everything fired up ok, except coming out of the bios, it goes into a window to ask if I should start normal, safe mode, safe mode dos prompt, etc, I tried every single one and all it does is flash the BSOD for such a short period I cant read it. I suspect bad memory because I was getting a lot of memory dump crashes and the BSOD mesg was usually along the lines of Memory issues. If memory is bad what happens? I mean can it prevent from going past the bios. All help appreciated.

[Reply or follow-up to this message]

Memory is so basic to the computer you sometimes can't finish the Bios, much less load an operating system. XP is fussy about memory. Some computers that ran 98 will reveal memory problems with XP. Try to substitute some other sticks of Ram for yours one at a time until the problem goes away. Also check your hard drive cables. Are they plugged in tight? Are they the correct type for the drive? 40 pin cables won't work on fast drives with XP, you'll get weird errors. Good Luck.


On Saturday, November 30, 2002 at 7:23 pm, Larry wrote:
>I have a question about Dealing
>with Bad Memory (RAM):

someone pls help: I just replaced a motherboard, everything
>fired up ok, except coming out of the bios, it goes into a window to ask if I should
>start normal, safe mode, safe mode dos prompt, etc, I tried every single one and
>all it does is flash the BSOD for such a short period I cant read it. I suspect
>bad memory because I was getting a lot of memory dump crashes and the BSOD mesg was
>usually along the lines of Memory issues. If memory is bad what happens? I mean can
>it prevent from going past the bios. All help appreciated.
>
>

[Reply or follow-up to this message]

Thank You Beecher, I hear a little click somewhere on the Motherboard. Ill exchange the memory module and hope thats it. Cables are good, the motherboard came with new cables and am using them. Im a software guru, but these hardware issues floor me. I know a little but wished I knew more. I couldnt fire up the operating system and that is what has me puzzled. thanks again


On Saturday, November 30, 2002 at 7:38 pm, Beecher Wood wrote:
>Memory is so basic to the computer you sometimes can't finish the Bios, much less
>load an operating system. XP is fussy about memory. Some computers that ran 98 will
>reveal memory problems with XP. Try to substitute some other sticks of Ram for yours
>one at a time until the problem goes away. Also check your hard drive cables. Are
>they plugged in tight? Are they the correct type for the drive? 40 pin cables won't
>work on fast drives with XP, you'll get weird errors. Good Luck.
>
>

[Reply or follow-up to this message]

I had many weeks of trouble with XP, startup problems with page faults and other blue screen of death message. I took out one of the two 256mb DDR modules and problem went, seems like they were running at slightly different speeds, even though they were supposed to be the same. I have stuck a single 512mb stick in now and all my problems have gone.


On Saturday, November 30, 2002 at 7:38 pm, Beecher Wood wrote:
>Memory is so basic to the computer you sometimes can't finish the Bios, much less
>load an operating system. XP is fussy about memory. Some computers that ran 98 will
>reveal memory problems with XP. Try to substitute some other sticks of Ram for yours
>one at a time until the problem goes away. Also check your hard drive cables. Are
>they plugged in tight? Are they the correct type for the drive? 40 pin cables won't
>work on fast drives with XP, you'll get weird errors. Good Luck.
>
>

[Reply or follow-up to this message]

You can't change out a motherboard and expect XP to start and load new drivers needed for the board. Those days of doing it like previous versions of Windows are gone. XP sees the new MB as being a violation of the Licensing agreement. The new board would have to be identical to the old one including the BIOS signature to avoid this. Your only option is to do a repair re/install or a clean install. Check out this article: http://www.extremetech.com/article2/0,3973,11715,00.asp


On Saturday, November 30, 2002 at 7:47 pm, Larry wrote:
>Thank You Beecher, I hear a little click somewhere on the Motherboard. Ill exchange
>the memory module and hope thats it. Cables are good, the motherboard came with new
>cables and am using them. Im a software guru, but these hardware issues floor me.
>I know a little but wished I knew more. I couldnt fire up the operating system and
>that is what has me puzzled. thanks again
>
>

[Reply or follow-up to this message]

OK, I do understand the issues at hand here, Im sure its a different IDE controller chipset, the new MotherBoard has an onboard Processor that is close to twice as fast so that could be the problem. In typical HIA fashion I didnt back up my data and having to reformat and install is still turning my stomach. Question: I have another hard drive I could reload XP onto, if I stuck my existing hard drive on their as a second hard drive, will I be able to get to my data?


On Sunday, December 1, 2002 at 11:02 am, ckrokit wrote:
>You can't change out a motherboard and expect XP to start and load new drivers needed
>for the board. Those days of doing it like previous versions of Windows are gone.
> XP sees the new MB as being a violation of the Licensing agreement. The new board
>would have to be identical to the old one including the BIOS signature to avoid this.
> Your only option is to do a repair re/install or a clean install. Check out this
>article: http://www.extremetech.com/article2/0,3973,11715,00.asp
>
>

[Reply or follow-up to this message]

In theory, Yes.. If it was on a FAT 32 partition, you could without a doubt. If an NTFS partition, you should be able to unless you applied some additional security measures.. (I have often had to do this for clients in the same trouble) If so you would have to take possesion of the resource (drive or partition) and in some cases even that won't work. You are on the right track though! Be aware, that the drive you install onto cannot be easily changed like Ghosting or Drive Imaging as the same outcome can be the result (serial numbers of the drive are recorded during the install, look at other posts in this forum). So whatever drive you install onto must be the drive that you will want to use for a long time (and be large enough).. Good Luck! C K


On Sunday, December 1, 2002 at 1:52 pm, Larry wrote:
>OK, I do understand the issues at hand here, Im sure its a different IDE controller
>chipset, the new MotherBoard has an onboard Processor that is close to twice as fast
>so that could be the problem. In typical HIA fashion I didnt back up my data and
>having to reformat and install is still turning my stomach. Question: I have another
>hard drive I could reload XP onto, if I stuck my existing hard drive on their as
>a second hard drive, will I be able to get to my data?
>
>

[Reply or follow-up to this message]

Thanks CK, appreciate the assistance. Ido indeed have it at FAT32. Appreciate all the help from everyone! L


On Sunday, December 1, 2002 at 2:19 pm, ckrokit wrote:
>In theory, Yes.. If it was on a FAT 32 partition, you could without a doubt. If
>an NTFS partition, you should be able to unless you applied some additional security
>measures.. (I have often had to do this for clients in the same trouble) If so
>you would have to take possesion of the resource (drive or partition) and in some
>cases even that won't work. You are on the right track though! Be aware, that the
>drive you install onto cannot be easily changed like Ghosting or Drive Imaging as
>the same outcome can be the result (serial numbers of the drive are recorded during
>the install, look at other posts in this forum). So whatever drive you install onto
>must be the drive that you will want to use for a long time (and be large enough)..
> Good Luck! C K
>
>

[Reply or follow-up to this message]

That isn't the case, XP's license agreement allows for up to eight hardware changes before needing reactivated. I've exchanges MB's in hundreds of pc on me network and only had registration problems with two machines, but they were quickly resolved with a call to microsoft. Any time you get memory dumps of page faults, nine times out of ten, it's a memory problem.


On Sunday, December 1, 2002 at 11:02 am, ckrokit wrote:
>You can't change out a motherboard and expect XP to start and load new drivers needed
>for the board. Those days of doing it like previous versions of Windows are gone.
> XP sees the new MB as being a violation of the Licensing agreement. The new board
>would have to be identical to the old one including the BIOS signature to avoid this.
> Your only option is to do a repair re/install or a clean install. Check out this
>article: http://www.extremetech.com/article2/0,3973,11715,00.asp
>
>

[Reply or follow-up to this message]

I would agree except in this case he has changed out the motherboard and it has a different IDE controller on it. That alone will cause a blue screen or some other fault that will shut down the machine immediately. A blanket statement of 8 HDWE changes isn't exactly correct, depending on the hardware involved. If you change out a motherboard with that of a board with a different IDE controller, you will blue screen immediately at the very least or trigger a warning about windows shutting down your machine to prevent damage if you try to start up.. So much for 8 hardware changes.. I work on all different brands of machines, especially those of third party builders and swapping motherboards with different chipsets in them "ALWAYS" causes problems... There is no easy way to repair the XP install 100% of the time even with the experts of MS trying to guide you through it. It's easier to reinstall and restore the customers data. Just my experience.. C K


On Wednesday, March 12, 2003 at 11:17 am, mcseadmin wrote:
>That isn't the case, XP's license agreement allows for up to eight hardware changes
>before needing reactivated. I've exchanges MB's in hundreds of pc on me network
>and only had registration problems with two machines, but they were quickly resolved
>with a call to microsoft. Any time you get memory dumps of page faults, nine times
>out of ten, it's a memory problem.
>
>

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum